Test page
ou must have found this eye-catching statement very promising. In most areas of our life, we all desire the best. Best quality, best price, best practices, best time, best service, and this & that, so why not the best test cases for web application? Right?
But please, pause, and I would like you to pay attention to the word ‘Best.’
Before and during writing the article, I researched and tried to understand who that single person or organization in the software testing world is, talking about best test cases, best practices for writing test cases, etc.
Many are writing something on the theme of ‘Best,’ but no surprise, none of them are credible and trustworthy subject matter experts or organizations! Almost 99% of them focus on ‘step-by-step verifications of specified requirements’ and have no discussions around risk, context, ideas, different situations, users, use cases, what a web application looks like, etc. Seeing those articles caused me a headache. Why are these people and content publishing businesses not carefully studying the craft of software testing?
But keep hope, friends, and let’s move our attention from myths to the world’s reality. Although this means that best test cases for a web application are myths and instead of aimlessly chasing the best, it is good for our health if we understand first that an attempt to declare a test case or suite of test cases as ‘Best’ is heavily context driven.
Context-driven? Yes, because information objectives of the testing effort play an essential role in the thinking, designing, and selection of a handful of test cases. Does that make sense? It may not now, but it will soon as you progress reading this post.
Now, while you will soon come to know what a Test Case looks like and what makes it good or bad, if not best, you must recall that ‘Best’ is contextual, and it is the right time to explore this further as an adult and learning software tester. Ready for the learning journey?
What do you Test with Web Applications?
To answer this question reasonably, let’s build a shared understanding that a web application is a solution, a convenient way to solve a user’s problem, or an attempt to satisfy the user’s requirements. For example – Look at how reserving a plane ticket or a hotel room has become so easy as you can reasonably quickly, safely, and anytime do it using a dedicated web application that is online almost 24*7 and allows you to accomplish your work without you having to go outside home.
Web application as a solution to a user’s problem (alternatively, a means to satisfying a user’s needs)
As a software tester, be proactive and curious to know, as accurately as possible, what is the problem a web application under test is solving, and for whom? In simple words, know who the users are, their use cases, and in what situations and environments they use the application.
Also, learn reasonably as much as you can about their desires of web application quality.
Requirements
Now, users want to accomplish something useful using the web application and feel happy.
For example, in the case of a food delivery web application, a hungry user will feel accomplished in at least two ways.
- When their overall user experience with the web application is outstanding, they can order food quickly, get discounts, pay safely by choosing one from multiple methods offered, track the order, and get it in the promised time as the app suggests.
- They ultimately get the food warm, fresh, non-contaminated, reasonably priced, and with minimal communication with restaurant and delivery personnel.
As web application testers, we have more control over testing the overall user experience (point 1 above) and significantly less control over the other(point 2 above). Isn’t it?
A solid understanding of two types of typical and time-tested requirements drives web application testing.
- Functional/behavioral requirements: Requirements that help build different core features/functions/workflow in the web application.
- Function enabler requirements: Requirements that make this functional/behavioral accomplishment experience a safe, fast, Inclusive, synced, and deeply satisfying experience for targeted users.
What to test:
Now, typically, you can start testing whatever you prioritize; provided your information objectives, timelines, and testing budgets are reasonably defined, and you have a test strategy in place.
First, however, it would be best to learn what tests to design to reach that readiness state.
Hence, I strongly recommend some lovely and handy (not easy!) guides available: HTSM by James Bach and ‘The Little Black Book On Test Design‘ by Rikard Edgren.
HTSM beautifully shows you the product elements and quality criteria dimensions of the strategy model. Here is a non-adulterated glimpse.
Product Elements are aspects of the product that you consider testing.
Quality Criteria Categories are dimensions in which people determine the value of the product.
Take 60-90 seconds. Please save these guides and later print them, put them on your desk, and spend the best of your time with them to guide your testing and generate valuable test ideas (and test cases, maybe).
Test page
ou must have found this eye-catching statement very promising. In most areas of our life, we all desire the best. Best quality, best price, best practices, best time, best service, and this & that, so why not the best test cases for web application? Right?
But please, pause, and I would like you to pay attention to the word ‘Best.’
Before and during writing the article, I researched and tried to understand who that single person or organization in the software testing world is, talking about best test cases, best practices for writing test cases, etc.
Many are writing something on the theme of ‘Best,’ but no surprise, none of them are credible and trustworthy subject matter experts or organizations! Almost 99% of them focus on ‘step-by-step verifications of specified requirements’ and have no discussions around risk, context, ideas, different situations, users, use cases, what a web application looks like, etc. Seeing those articles caused me a headache. Why are these people and content publishing businesses not carefully studying the craft of software testing?
But keep hope, friends, and let’s move our attention from myths to the world’s reality. Although this means that best test cases for a web application are myths and instead of aimlessly chasing the best, it is good for our health if we understand first that an attempt to declare a test case or suite of test cases as ‘Best’ is heavily context driven.
Context-driven? Yes, because information objectives of the testing effort play an essential role in the thinking, designing, and selection of a handful of test cases. Does that make sense? It may not now, but it will soon as you progress reading this post.
Now, while you will soon come to know what a Test Case looks like and what makes it good or bad, if not best, you must recall that ‘Best’ is contextual, and it is the right time to explore this further as an adult and learning software tester. Ready for the learning journey?
What do you Test with Web Applications?
To answer this question reasonably, let’s build a shared understanding that a web application is a solution, a convenient way to solve a user’s problem, or an attempt to satisfy the user’s requirements. For example – Look at how reserving a plane ticket or a hotel room has become so easy as you can reasonably quickly, safely, and anytime do it using a dedicated web application that is online almost 24*7 and allows you to accomplish your work without you having to go outside home.
Web application as a solution to a user’s problem (alternatively, a means to satisfying a user’s needs)
As a software tester, be proactive and curious to know, as accurately as possible, what is the problem a web application under test is solving, and for whom? In simple words, know who the users are, their use cases, and in what situations and environments they use the application.
Also, learn reasonably as much as you can about their desires of web application quality.
Requirements
Now, users want to accomplish something useful using the web application and feel happy.
For example, in the case of a food delivery web application, a hungry user will feel accomplished in at least two ways.
- When their overall user experience with the web application is outstanding, they can order food quickly, get discounts, pay safely by choosing one from multiple methods offered, track the order, and get it in the promised time as the app suggests.
- They ultimately get the food warm, fresh, non-contaminated, reasonably priced, and with minimal communication with restaurant and delivery personnel.
As web application testers, we have more control over testing the overall user experience (point 1 above) and significantly less control over the other(point 2 above). Isn’t it?
A solid understanding of two types of typical and time-tested requirements drives web application testing.
- Functional/behavioral requirements: Requirements that help build different core features/functions/workflow in the web application.
- Function enabler requirements: Requirements that make this functional/behavioral accomplishment experience a safe, fast, Inclusive, synced, and deeply satisfying experience for targeted users.
What to test:
Now, typically, you can start testing whatever you prioritize; provided your information objectives, timelines, and testing budgets are reasonably defined, and you have a test strategy in place.
First, however, it would be best to learn what tests to design to reach that readiness state.
Hence, I strongly recommend some lovely and handy (not easy!) guides available: HTSM by James Bach and ‘The Little Black Book On Test Design‘ by Rikard Edgren.
HTSM beautifully shows you the product elements and quality criteria dimensions of the strategy model. Here is a non-adulterated glimpse.
Product Elements are aspects of the product that you consider testing.
Quality Criteria Categories are dimensions in which people determine the value of the product.
Take 60-90 seconds. Please save these guides and later print them, put them on your desk, and spend the best of your time with them to guide your testing and generate valuable test ideas (and test cases, maybe).
Test page
ou must have found this eye-catching statement very promising. In most areas of our life, we all desire the best. Best quality, best price, best practices, best time, best service, and this & that, so why not the best test cases for web application? Right?
But please, pause, and I would like you to pay attention to the word ‘Best.’
Before and during writing the article, I researched and tried to understand who that single person or organization in the software testing world is, talking about best test cases, best practices for writing test cases, etc.
Many are writing something on the theme of ‘Best,’ but no surprise, none of them are credible and trustworthy subject matter experts or organizations! Almost 99% of them focus on ‘step-by-step verifications of specified requirements’ and have no discussions around risk, context, ideas, different situations, users, use cases, what a web application looks like, etc. Seeing those articles caused me a headache. Why are these people and content publishing businesses not carefully studying the craft of software testing?
But keep hope, friends, and let’s move our attention from myths to the world’s reality. Although this means that best test cases for a web application are myths and instead of aimlessly chasing the best, it is good for our health if we understand first that an attempt to declare a test case or suite of test cases as ‘Best’ is heavily context driven.
Context-driven? Yes, because information objectives of the testing effort play an essential role in the thinking, designing, and selection of a handful of test cases. Does that make sense? It may not now, but it will soon as you progress reading this post.
Now, while you will soon come to know what a Test Case looks like and what makes it good or bad, if not best, you must recall that ‘Best’ is contextual, and it is the right time to explore this further as an adult and learning software tester. Ready for the learning journey?
What do you Test with Web Applications?
To answer this question reasonably, let’s build a shared understanding that a web application is a solution, a convenient way to solve a user’s problem, or an attempt to satisfy the user’s requirements. For example – Look at how reserving a plane ticket or a hotel room has become so easy as you can reasonably quickly, safely, and anytime do it using a dedicated web application that is online almost 24*7 and allows you to accomplish your work without you having to go outside home.
Web application as a solution to a user’s problem (alternatively, a means to satisfying a user’s needs)
As a software tester, be proactive and curious to know, as accurately as possible, what is the problem a web application under test is solving, and for whom? In simple words, know who the users are, their use cases, and in what situations and environments they use the application.
Also, learn reasonably as much as you can about their desires of web application quality.
Requirements
Now, users want to accomplish something useful using the web application and feel happy.
For example, in the case of a food delivery web application, a hungry user will feel accomplished in at least two ways.
- When their overall user experience with the web application is outstanding, they can order food quickly, get discounts, pay safely by choosing one from multiple methods offered, track the order, and get it in the promised time as the app suggests.
- They ultimately get the food warm, fresh, non-contaminated, reasonably priced, and with minimal communication with restaurant and delivery personnel.
As web application testers, we have more control over testing the overall user experience (point 1 above) and significantly less control over the other(point 2 above). Isn’t it?
A solid understanding of two types of typical and time-tested requirements drives web application testing.
- Functional/behavioral requirements: Requirements that help build different core features/functions/workflow in the web application.
- Function enabler requirements: Requirements that make this functional/behavioral accomplishment experience a safe, fast, Inclusive, synced, and deeply satisfying experience for targeted users.
What to test:
Now, typically, you can start testing whatever you prioritize; provided your information objectives, timelines, and testing budgets are reasonably defined, and you have a test strategy in place.
First, however, it would be best to learn what tests to design to reach that readiness state.
Hence, I strongly recommend some lovely and handy (not easy!) guides available: HTSM by James Bach and ‘The Little Black Book On Test Design‘ by Rikard Edgren.
HTSM beautifully shows you the product elements and quality criteria dimensions of the strategy model. Here is a non-adulterated glimpse.
Product Elements are aspects of the product that you consider testing.
Quality Criteria Categories are dimensions in which people determine the value of the product.
Take 60-90 seconds. Please save these guides and later print them, put them on your desk, and spend the best of your time with them to guide your testing and generate valuable test ideas (and test cases, maybe).
