Manual Testing is the Software Testing Technique which is carried out using the functions and features of an application. In manual testing, a tester carries out tests on the software by following a set of predefined test cases. In this testing, testers make test cases for the codes and test the software and give the final report about that software. Manual testing is a time consuming testing because it is done by humans and there is a chance of human errors.
Every new application must be manually tested before its testing can be automated. Manual Testing requires more effort rather than automation testing but is necessary to check automation feasibility. There is no requirement of knowledge of any testing tool in manual testing.
Characteristics of Manual Testing:
- Manual testing is time consuming.
- High chances of human error in manual testing.
- Possibility of exploratory testing.
- There is no need of programming language in manual testing.
- Manual testing doesn’t use frameworks.
- Less accuracy.
Steps in Manual Testing:
- Study the software project documentation and guides.
- Study the Application Under Test (AUT).
- Design the test cases that cover all the requirements described in the documentation.
- Review and baseline the test cases with team lead and client.
- Execute the test cases on the application under test.
- Report bugs.
- When bugs are fixed, again execute the failing test cases to verify they pass.
Advantages of Manual Testing:
- Fast and accurate visual feedback.
- Less expensive.
- No coding required.
Disadvantages of Manual Testing:
- Less reliable.
- Can not be reused.
- Some specific tasks can’t be performed manually.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Software Engineering | Differences between Manual and Automation Testing
- Beta Testing | Software Testing
- Software Engineering | Differences between Sanity Testing and Smoke Testing
- Software Testing | Endurance Testing
- Software Testing | Dynamic Testing
- Software Testing | Accessibility Testing
- Smoke Testing | Software Testing
- Performance Testing | Software Testing
- Software Testing | Non-functional Testing
- Sandwich Testing | Software Testing
- Software Engineering | Comparison between Regression Testing and Re-Testing
- Alpha Testing | Software Testing
- Unit Testing | Software Testing
- Stress Testing | Software Testing
- Sanity Testing | Software Testing
- Gray Box Testing | Software Testing
- Acceptance Testing | Software Testing
- Software Testing | Reliability Testing
- Software Testing | Scalability Testing
- Software Testing | Scenario Testing
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.