Automation is one of the key goals that always take precedence over manual testing. In fact most of the teams have some predefined targets set for the automation numbers. With the recent developments in automation framework including data driven and fuzz testing, it’s possible to figure out new product bugs through automation apart from just figuring out regression bugs in subsequent builds. If the automation framework is stable enough to give consistent results then it makes sense to automate as many numbers of test cases as possible. This not only saves hours of manual repetitive testing but also provides opportunity for testers for performing exploratory testing that requires creativity and thinking out of the box. However if the framework is unstable and we are observing frequent failures because of automation issues then it may not be of much use to increase automation numbers as majority of the time will be spent on fixing automation issues rather than finding real product bugs. In such situation we should target only high priority scenarios for automation and execute the remaining cases manually. Though fixing/changing the automation infrastructure is a solution but again it had lot of dependency on the test cost involved and may not get approved easily unless there is a huge return on investment.

This entry was posted in Information Technology. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s