Automation or Manual - Testing Strategy and Methodology
Ideally test automation should be carried out in a planned manner after getting to know the business requirements of the client and objectives that the software application is expected to fulfill. Moreover it important for to develop a strategy that is aligned with the resources of the client and uses the right mix of automation tools. Moreover effort should be made to keep the costs in control during the planning stage itself and keep a hawk eye on the entire automation process from a budget perspective. Take a holistic approach to testing your software and try to include automation wherever it
can offer you an advantage while keeping the entire process streamlined.
Automated Testing Positive
- Far more code is covered in a shorter time using automation
- It relieves human testers from highly repetitive, low-value test work
- Automation can allow non-technical staff or customers to run tests
- Automation enables time savings due to parallelization of test execution
- Automated tests can simulate thousands of users and configurations easily
Negative :
- Automation and maintenance of test suites requires significant investment in tools and skills
- Automation cannot replace human cognitive skills required for evaluating software’s UI or UX
- It is not appropriate for exploratory testing used to improve the software’s design
Manual Testing
Positive :
- Exploratory testing is best done manually
- Manual testing is cost-efficient for tests run only a few times
- Manual testing of UIs is most effectively done by humans
- A software’s UX can only be evaluated by human testers
Negative :
- Relative to the amount of code coverage, manual tests are inefficient
- Manual testing is prone to human error, so may lead to inconsistent or result
- Human test resources are more expensive than test machines The simulation of large numbers of users or configurations is nearly impossible to accomplish manually
No comments:
Post a Comment