Steps in Manual Testing
The below diagram lists the steps in the manual testing process:
- Requirement Analysis: Study the software project documentation, guides, and Application Under Test (AUT). Analyze the requirements from SRS.
- Test Plan Creation: Create a test plan covering all the requirements.
- Test Case Creation: Design the test cases that cover all the requirements described in the documentation.
- Test Case Execution: Review and baseline the test cases with the team lead and client. Execute the test cases on the application under test.
- Defect Logging: Detect the bugs, log and report them to the developers.
- Defect Fix and Re-verification: When bugs are fixed, again execute the failing test cases to verify they pass.
Manual Testing – Software Testing
Manual testing is a technique to test the software that is carried out using the functions and features of an application. In manual software testing, a tester tests the software by following a set of predefined test cases. In this testing, testers make test cases for the codes, test the software, and give the final report about that software. Manual testing is time-consuming because it is done by humans, and there is a chance of human errors.
Table of Content
- Characteristics of Manual Testing
- Why Need Manual Testing?
- Steps in Manual Testing
- Types of Manual Testing
- Tools Used for Manual Testing
- Differences between Manual Testing and Automation Testing
- Advantages of Manual Testing
- Disadvantages of Manual Testing
- Conclusion
- FAQs of Manual Testing
Every new application must be manually tested before its testing can be automated. Manual Testing requires more effort than automation testing but is necessary to check automation feasibility. There is no requirement for knowledge of any testing tool in manual testing.