Testing Procedure in the Realm of ManualTesting

In the world of software development, manual testing plays a crucial role in ensuring the quality of a product. Here's a step-by-step breakdown of the stages involved in manual testing and the objectives at each step.

Gathering Requirements

The first stage in the manual testing process is gathering requirements. This step is essential as it helps us understand the application and the end user's expectations of the product. During this stage, it's important to consider the type of testing, its scope, and the amount of time available.

Discussion and Sharing

Once the requirements are gathered, the next stage is discussion and sharing. Here, the information is combined and ranked into relevant parts for test scenarios and cases. The business analyst may provide feedback and suggestions for how the testing or product should be improved based on their understanding of the product from the customer's point of view.

Setting Up Resources and Test Environment

The third stage is setting up the resources and test environment. This involves planning and allocating time for hardware, manual testing tools, and other necessary materials and assets. A visual overview, such as a mind map, can be beneficial for understanding the software testing project. Access to additional resources, such as conversations with developers during a product demo, can also be helpful.

Creation of Test Cases and Scenarios

The fourth stage is the creation of test cases and scenarios. This provides guidance on what to test, how to test it, what data to use, and what kinds of outcomes to anticipate. It's a good idea to update the test cases and maintain them on file in case further regression testing is required.

Retesting

After a reported defect is fixed, the tester is responsible for retesting it to verify the repair. Each test case is completed by one or more individuals following the guidelines provided. Any discrepancies found during test execution are reported as problems and sent to the developers.

Test Execution

The main objectives of a tester during test execution are achieving the stated objective and documenting any discrepancies. A test team cannot approve a product under test unless all test cases are marked as passed.

Test Report

At the end of the manual testing process, all stakeholders receive a test report. The report includes information pertaining to the product's testing status, various testing metrics, a list of the regions tested, a declaration of any locations outside of scope, and non-testable items.

Release

Once it has been demonstrated that the product satisfies the needs of the business owner, it can be given to a release manager and scheduled for release.

Please note that the source of the manual testing course for beginners could not be specified in the search results. However, numerous resources are available online for those interested in learning more about manual software testing.