Choosing Automation Test Cases
Let me begin the blog by letting all you know what prompts a tester to automate the test cases.
There is a module to be tested and you write test cases, execute them and happy with the results, your job is done.
Ask some of these questions here:
1. Will these test cases be executed anytime again?
2. How frequently should you be executing them?
3. Who will execute them next time?
Once you have the answers, lets dwell on to deciding how automation can help.
If you have
There is a module to be tested and you write test cases, execute them and happy with the results, your job is done.
Ask some of these questions here:
1. Will these test cases be executed anytime again?
2. How frequently should you be executing them?
3. Who will execute them next time?
Once you have the answers, lets dwell on to deciding how automation can help.
If you have
- Multiple rounds of testing like feature functionality testing, regression testing etc in the same release cycle
- Execute the same test cases in future releases regression suites
- Test cases with varying test data
- Scenarios of complex flows, its good to automate them which will give you the ease to jump in a particular step without executing the previous steps manually
- Many types of users doing same action and you need to make sure your application works fine for each one of type of login
- Multiple browsers, then its a good idea to automate those test cases that will be run on them.
Comments
Post a Comment