Test Requirement
The test should begin in the requirement analysis phase of SDLC. The actual requirement should be understood clearly with the help of the Requirement Specification document (BRD, FSD, etc.).
During the requirement analysis, the following points should be considered –
- Can the requirement be realized in practice?
- Can the requirement be tested effectively?
Test Planning
During this phase, Test Strategy, Test Plan, and Test Bed will be created. A test plan is a systematic approach to the testing of software. The plan should identify the –
- Which aspect of the system should be tested?
- Criteria of success.
- The method and techniques should be used.
- Manual and Automation Testing
- Defeat Management tool.
Test Analysis
- Analysis of the system requirement, if required recorded in RCN (Requirement Clarification Note).
- Walkthroughs
- SME (Subject Matter Experts).
Test Design
- Test Scenario will be identified.
- Test cases will be prepared.
- Test data and test scripts will be prepared.
- A test case review will be conducted.
Test Execution
- Testcases will be executed.
- The test results will be analyzed.
- Defeat is raised, fixed, retested, and closed.
Defect Life Cycle in Testing
New
Whenever the defect is found for the very first time, the test engineer will set the status as New.
Open
Whenever the developer accepts the defect then they will set the status as Open.
Re-opened and Closed
Whenever the defect is rectified, the next build will be deployed in the testing environment then the Test Engineer will check whether the defect is working properly or not. If a defect is working as expected then the tester will close the defect and set the status Closed. If the defect is not working as expected the tester will reopen the defect and set the status as Re-opened.
Duplicate
If 2 defects are raised and the root cause of both defects is the same, then it is marked as Duplicate by the developer.
Differed
Whenever the defect arises, the test engineer will assign it to the developer. If the defect isn’t going to be fixed in the current release/sprint, then the test engineer will set the status as Differed. It means the defect is differed/move to the next sprint.
Rejected
Whenever the developer confirms that it is not at all a bug/defect, then they will set the status as Rejected.
Fixed
Whenever the developer fixes the raised bug, then they will set the status as Fixed.
Test Report
- A test summary report will be prepared.
- Test Metrics and process improvements will be made.
- Build release.
- Receiving acceptance.
https://medium.com/@manisha10850/software-testing-life-cycle-stlc-testing-0b158ef960f7a>