Manual Testing:
In the Manual Testing, we will write some test cases (A document with an expected result -user action and its sub-sequence result) based on the client requirements and execute these test cases manually in the application and verify the actual behaviour of the application we respect to the given expected results.
Manual testers workflow: Requirements -> Analysis -> Test cases -> Execute Test cases against the build deployed by the developer.
Automation Tester:
Automation testing is done by the tools. Here they going to give all the requirements about the project in script format to that tool. The tool interacts with that application and it will give the output. Automation testing is mainly used for Regression.
- These people get KT from the manual tester (How we execute the test cases on the browser).- After manual testing is done by the manual tester, then they analyze the test cases.- Then they start development Scripts.- Execute these Scripts against the build deployed by the developer
The objective of Automation Testing:
- To identify the defects.
- To reduce manual testing activities and redundant test operations using a Systematic solution to achieve better testing coverage.
- To speed up a software testing process, and to reduce software testing cost & time during a software life cycle.
- To increase the quality & effectiveness of a software test process by achieving Predefined test criteria in a limited schedule.
When to Use Automation Testing:
- The repetitive tasks are boring or tend to cause human errors.
- Relatively stable areas of the application over volatile ones must be automated.
- Application with multiple releases / Builds.
- The application where long & iterative Regression testing cycles are required.
When to not use Automation Testing:
- Unstable Application.
- Tests without Predictable results (Expected results).
- Test cases that require human intervention.
