When not to Automate
- Rarely run tests
- This can go both ways,
- why cant I put in a one time effort to automate, so that I can forget it forever
- why should I spend effort on creating and maintaining some automation that would be run once in 6 months
- Usability tests : Be careful before automating usability tests.
- Work in progress areas
- This can also go both ways. I hear teams now wanting to start writing automation code using wireframes.
- Delay in ROI of the automation
- Consider if there are items to be worked upon - a lot, before you can actually use automation scripts. With agile, there then would be a built up of back log of features to be tested.
- If metrics show that automation has not been catching defects in the area, rethink, relook at if automation is the right solution or automation was rightly implemented.
- Watch out for areas from experience , where only manual test could catch issues.
No comments:
Post a Comment