If you are practicing quality assurance then, then you must have had a discussion around automated or manual testing. This is nothing new, and lots of techies have different views around this. Whether you are a big team and already established an automation framework or you are a small team, new to automation, it is always necessary to keep this balance right in order to get maximum efficiency. In the two-part series, we discuss manual and automated testing models adopted by our software quality assurance experts.
Automated Vs Manual testing – keeping the balance right
Surely automation testing is having the benefits of increasing efficiency, getting faster regressions, and thus contributing to timely project deliveries. It also removes the execution of repetitive test cases or regression cases manually and saves a tester’s life.
But before considering automated software testing, there are certain points which you should evaluate. You must have heard the statement “You can not automate everything” which is very true. Manual testing is required in many cases. In fact, the biggest drawback of manual testing itself is its biggest advantage that it requires human intervention!
There are certain cases of software quality assurance that require human instinct and intuitiveness to test a system. To name a few, these are the following cases where manual testing plays a vital role:
1. Usability Testing – This is testing an application in the view of how easy or difficult is to understand. This is to test how interactive the application is to the users who are going to use it. These kinds of tests can not be automated and must be performed manually.
2. UI and UX Testing – UI and UX testing can not be automated and even if you try, it would be only to some extent. Automation scripts can be used to test the layout, CSS errors, and HTML structure but the whole user experience can not be automated
as it is very subjective.
3. Exploratory Testing – Cem Kaner who coined the term in 1984, defines exploratory testing as – “A style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the
4. Ad-hoc testing – This is completely unplanned testing which relies on the quality assurance tester insight and approach. There is no script ready for this testing and has to be performed manually.