The significance of testing is not only to find bugs, but also to prevent defects and improve product quality. Around this goal, what should testers focus on throughout the product development process? This article discusses this issue.
First, the needs analysis stage:
1. Understand requirements and sort out user scenarios
The demand here refers to the business demand. In addition to paying attention to the technical aspects of the demand, it is also necessary to pay attention to its business demand. The purpose is to help the test integrate into the team and let the BOSS recognize the content and method of the test, instead of always compressing the test time in exchange for the progress of the project. User scenarios refer to how users use the product, so it is important to understand users: what types of users are there, how users get value from the product, what valuable solutions are provided by competitors, and what specifications and requirements exist in the product area And so on, get the test scene according to the user scene abstraction, analyze the input and output of the scene (including normal and abnormal input)
2. Develop an overall test strategy, clarify the test scope, test objectives, test focus and difficulties, and test depth and breadth
The difficulty of testing is from a technical point of view, which is an analysis of the difficulty of testing. The focus of the test is determined by comprehensive factors such as product goals and implementation, such as the main function, and the function with high quality requirements needs to be tested. Under the framework of the overall testing strategy, there are also phased testing strategies and version testing strategies.
Participated activities and references, output documents
Activities involved: needs review
Reference documents: question list template for requirements review, guidance document for requirements review
Output Documentation: List of Questions for Requirements Review
Assessment indicators: the value of the accepted questions (calculation formula based on quantity and weight)
2. Test analysis and design stage:
1. Test layering and determine the test strategy for each layer, such as unit testing, integration testing, system testing, and acceptance testing under the V model, which is an example of test layering. The test strategy includes test objects and objectives, entry and exit criteria, and test case selection.
2. Ensure the quality of test design. The output of the test case should be consistent with the test strategy.
Participated activities and references, output documents
Activities involved: test case writing, test case review
Reference documents: test case review template, test case design method guidelines
Output Documentation: Test Case Review Comments and Suggestions List, Test Case (Revised Version)
3. During the test execution
1. Develop test strategies for each version (or iteration), such as the test objectives of this version, the key content, the selection and execution sequence of test cases, automated testing strategies, etc.
2. Track test execution, evaluate the quality of the current version in real time, and adjust the test strategy
Participated activities and references, output documents
Activities involved: Test execution (manual execution, automated execution)
Reference Documentation: Test Cases
Output documents: version test report, performance test report, special test report, compatibility test report
4. Version release
1. Continuous follow-up of online quality
Participated activities and references, output documents
Activities involved: online verification, test verification (including localization test) that needs to be performed in the live network environment, follow-up user feedback
Reference documentation: localization checklist, pre-release testing checklist
Output documentation: test case revisions, automation script additions, QA reports, test summaries