![Tasks or features which are stable
enough [If the module of the application is not stable
enough, the effort in automation is wasted to an extent]](https://image.slidesharecdn.com/whichtestcasestoautomate-120203102712-phpapp01/85/Which-test-cases-to-automate-5-320.jpg)
Which test cases to automate
- 1. Which test cases to automate http://qtp.blogspot.com
- 2. ONE Usually what works in ENVIRONMENT may not work in ANOTHER!
- 3. No BEST PRACTICE for what should be automated because Depends a lot on factors like Decision To Automate AUT Environment Hardware Dependencies Potential Impacts Others
- 4. Repetitive tasks are good candidates for automation e.g. regression tests
- 5. Tasks or features which are stable enough [If the module of the application is not stable enough, the effort in automation is wasted to an extent]
- 6. Smoke tests are also good candidates for automation
- 7. Tasks involving complex calculations are apt for automation
- 8. Certain tasks which require regular setup of environment, for example, are good candidates for automation
- 9. Ask questions like How long will it take to automate? How long does it take to test manually? Can you afford the time to automate?
- 10. Automate things which are difficult for humans, for example time sensitive actions requiring accurate timing to capture a state change or certain actions like loading a component with a hundred operations per second
- 11. Tasks or Test Cases requiring multiple data sets can be automated
- 12. Mostly apply common sense to decide between which tasks to automate and which to test manually
- 13. You can base your decision on ROI {Return On Investment} You can Google for more on ROI
Editor's Notes
- #4: decision to automate