Manual Testing
Here are some critical points about manual testing:
Test Planning: Testers create a test plan that outlines the scope, objectives, and approach for manual testing. This plan includes details on what features or functionalities will be tested, test scenarios, and test cases.
Test Execution: Testers manually execute test cases, following predefined steps, and record the results. They may use various testing techniques such as functional testing, regression testing, integration testing, and user acceptance testing, among others.
Exploratory Testing: Besides scripted test cases, manual testing often involves exploratory testing, where testers explore the software to find defects and issues that predefined test cases might not cover.
Ad Hoc Testing: Testers may perform ad hoc, informal, and unstructured testing. This can help discover unexpected issues and usability problems.
Usability Testing: Manual testing also includes evaluating the software’s user interface and user experience (UI/UX) aspects to ensure it is user-friendly and meets user expectations.
Regression Testing: After developers make changes to the software, testers often perform regression testing to ensure that new changes haven’t introduced any new defects and that existing functionality still works as expected.
User Acceptance Testing (UAT): In UAT, the end-users or stakeholders manually test the software to validate whether it meets their specific requirements and business needs.
Defect Reporting: Testers document any defects or issues during testing, providing detailed information to help developers understand and fix the problems.
Test Documentation: Manual testing involves the creation and maintenance of test documentation, including test cases, test scripts, test data, and test reports.
