STLC (Software-testing Life Cycle) in manual testing tutorial which covers phases of the testing process, is another name for the software-testing procedure. The testing procedure is meticulously planned and carried out. All operations are carried out in order to increase the software product's quality.
1. Requirement Analysis:
Requirement analysis is the initial step in the manual testing process. In this phase, the tester examines the client's needs using the SDLC (Software Development Life Cycle) requirement document. After reviewing the requirements, the tester creates a test plan to determine whether or not the software meets them.
2. Test Plan Creation:
All of the testing strategies are defined in the test plan creation step of the STLC. The projected work and expense of the complete project are determined by the tester. This phase begins when the Requirement Analysis Phase has been completed successfully. This phase provides the testing strategy and effort estimation documents. Following the successful completion of Test Plan Creation, test case execution can begin.
3. Environment setup:
The setup of the test environment is a separate operation that can be undertaken concurrently with the development of test cases. Environment testing is not possible without it, hence it is an important aspect of the manual testing technique. To construct a test environment, you'll need a collection of critical software and hardware. The testing team does not construct the testing environment; it is the senior engineers who do so.
4. Test case Execution:
Following the successful completion of test planning, the test case execution takes place. The testing team begins case development and execution during this phase. The testing team documents the complete test cases and, if necessary, produces the test data. Peer members of the team or the Quality Assurance leader review the test cases that have been prepared.
During this phase, the RTM (Requirement Traceability Matrix) is also created. The Requirement Traceability Matrix is a standard structure for tracking requirements in the industry. The requirement statement is mapped to each test case. RTM allows for backward and forward traceability.
5. Defect Logging:
Software completion criteria are evaluated by testers and developers based on test coverage, quality, time consumption, cost, and essential business objectives. This phase specifies the software's properties and flaws. To determine the type of defect and its severity, test cases and bug reports are thoroughly examined.
Defect logging analysis primarily seeks to determine flaw distribution based on severity and type. If a defect is discovered, the software is returned to the development team for correction, after which it is re-tested on all elements of the testing.
When the test cycle is finished, a test closure report and test metrics are generated.
6. Test Cycle Closure:
All documentation relating to software design, development, testing results, and defect reports are included in the test cycle closure report.
This phase assesses the development strategy, testing technique, and potential faults in order to reuse similar practises in the future if a software with the same specification exists.
