This article is shared from Tianyi Cloud Developer CommunityIntegrated test testing strategy》, author: Gao ****hao
Testing strategies before integration testing:
1. Product learning and training：
【Purpose】
The main purpose of this part is to be familiar with and understand the product, and to understand some product details. Avoid missing the details that cannot be reflected in the requirements document in the subsequent process. (If you find omissions, you can ask the product manager to add the corresponding content to the requirement)
【Work content and methods】
1) Participate in the requirements and UI review meetings of the project organization, and be familiar with relevant documents, system architecture, internal logic of specific complex functions, etc.
2) Organize the details that are easily missed into the document.
3) Use the method of repeating the product, project, and R&D description content to ensure that both parties are consistent in their understanding.
4) (You can consider starting the basic architecture of the test key points, such as testing projects, modules, etc. The details of the test key points can be sorted out later before the use case design).
5) If the specific meeting time conflicts with other tasks, negotiate with the meeting organizer whether the meeting can be postponed, or whether there are members in the group who can perform tasks on their behalf.
【time】
Write test points and plan in advance
【Achievements】
"Test Points Easily Missed" and "Test Points Framework"
2. Test strategy and planning design:
【Purpose】
Complete the test strategy and planning design, and guide the execution of the test process.
【Work content and methods】
1) Modify the in-group test strategy and plan template generation according to the specific situation of the project
2) Complete the review within the strategy & plan group.
【time】
According to the project schedule, complete the test strategy and plan design on schedule. If there is a work conflict in the middle, the completion time of the plan will be postponed. (It is best to have a specific time)
【Achievements】
Testing strategies and plans
3. Time and personnel planning
【Purpose】
Ensure that relevant characters are completed before the deadline. Including test strategies, test cases, and test rounds. And ensure that the task time and person in charge are clear.
【Work content and methods】
1) Divide the key test points, the person in charge of the test case design module and the implementation time.
【time】
1) Test key points and use case design work division. According to the department’s tasks, negotiate working hours with the supervisor. Try to advance the time to ensure that relevant documents have free time to complete.
2) The test round and the test module manager will start dividing the items after the test rounds are submitted and tested. If there is insufficient staff due to task conflicts, report to the test supervisor and the supervisor negotiates with the project manager.
4. Test resource documentation first version
【Purpose】
a) Clarify the software and hardware resources, testing tools, data requirements, etc. of the preliminary test. For R&D and other relevant personnel to plan and prepare in advance.
【Work content and methods】
According to the content of the demand review, organize the relevant requirements into documents.
【Achievements】
"Testing Resource Requirements Tracking Table (Preliminary Edition)" and "Tools & Test Data & Research Requirements Table (Preliminary Edition)".
5. Key points for testing
【Purpose】
b) Complete the key points of the system testing and write the following test cases, test plans and other documents as outline or support. And facilitate the review of test-related content.
c) Complete the test scope sorting out and reach agreement with projects, products, and R&D.
【Work content and methods】
1) Clarify the outline of the test points and divide the specific module content into the members in the group. Detailed content design is completed by members in the group
2) Mail lists the test points and sorts out the requirements. Provide specific sample templates. Ensure that the key points of the team members meet the requirements. The specific content includes functions, performance, stability testing requirements, corresponding content that may require R&D support, special testing environments, testing equipment, etc.
3) After the team members have fully tested the key points, they are integrated into the unified document. Organize product managers, project managers, and corresponding developers to conduct reviews. Clarify the test scope.
4) Changes to the key points of the test must be negotiated with the project manager and product manager.
【time】
After the requirements review is completed.
【Achievements】
"Project Testing Points"
6. Test design related documents
【Purpose】
Complete the corresponding documents according to the relevant contents required for the project. Ensure the normal execution of the corresponding test items. It mainly includes: test environment topology diagram, performance testing scheme, stability testing scheme, test resource requirements tracking table, R&D support requirements table, and functional test cases.
【Work content and methods】
According to the test key points, the corresponding test items are sorted out for each item and into each document.
1) The test environment is based on the R&D topology diagram planning. After the planning is completed, the product manager, project manager, superior supervisor, SE will be sent by email. If necessary, a meeting will be organized for review.
2) The test resource requirements tracking table lists various software and hardware resources, organizes internal reviews, and tracks them. Clarify the latest results into the document and send them regularly to the product manager, project manager, and superior supervisor.
3) After the R&D support demand table is sorted out, send the product manager, project manager, superior supervisor, SE. Ensure that all parties reach an agreement. If necessary, a meeting will be organized for review. If the R&D support needs are more complex, they will be assigned to the members of the group to sort out the specific needs. (Test the qualification tool requirements)
4) Performance and stability testing solutions can be single-lined documents or integrated into the test case sheet page. After completion, organize a meeting to conduct review.
5) Functional test case writing tasks are divided into the corresponding person in charge according to the plan. If there is a conflict between personnel and time, the superior supervisor will be notified and the superior supervisor will communicate with the project manager to handle the problem.
【time】
After the test points are reviewed. Flexible time points are formulated according to departmental task situations and timely update task lists.
【Achievements】
"Test Environment Topology Chart", "Performance Test Scheme", "Stability Test Scheme", "Test Resource Requirement Tracking Table", "Tool/Test Data Requirement Table", "Functional Test Cases"
7. Test data, scripts, and tool preparation:
【Purpose】
Prepare test data and scripts related to the test. (Try to communicate and negotiate complex preparations and negotiate as much as possible through research and development).
【Work content and methods】
Sorting the results according to the test points, and organizing the data and scripts required for the group. Divide to specific personnel for preparation.
【time】
The specific execution time and personnel shall communicate and negotiate with the direct supervisor.
【Achievements】
Related test scripts, tools, and data.
Testing strategies during integration testing:
1. Round test strategy review:Before the test process is submitted, the testing person in charge will initiate a review meeting for the testing key points and testing strategy. The round test content and test plan are formulated and evaluated based on the overall project test points, test plans, round test points, etc. The test strategy includes at least the range of rounds of tests and corresponding test methods.
2. Test execution:The test instructions are sent by email, which should include the test member task assignment. For major issues, inform relevant personnel by email during the test cycle.
3. Test feedback and summary:Daily feedback on test questions is provided, including detailed test case execution number, test module completion progress, execution time, important questions, etc.
4. After the functional test is completed:Performance test and stability test can be carried out. The project manager must formulate the performance test items and stability test items of this project based on the requirements and the performance test conditions and stability test conditions of the original project, and based on the estimated workload. Assign tasks well.
Change strategies during integration testing:
1. Test time changes:Negotiate with the project manager for the latest time, state the reason for the change, and send it to the project related personnel by email. Reports will be recorded after the test is completed.
2. Test content changes:Email the relevant personnel and state the temporary change risk. After the test is finished, the test report will be recorded.
3. Test version changes:Confirm changes with the project manager, product manager, SE and confirm the post-change test strategy. Email to the relevant personnel. Negotiate the processing method with the project manager and record the change process into the test report.
Testing strategies after integration test:
1. Test report:Summarize the testing situation of the entire project, some experiences and lessons learned, etc., and carry out the conference in the form of a document and record the documents. "Rotary Test Report", "Test Summary Report", "Test Technology/Experience Sharing"
Abnormal termination test strategy:
The project may have major problems with some functions in the round, which leads to failure to test and the project is aborted abnormally. If the above situation exists, the strategy is as follows:
2. If large-scale functional use cases cannot be tested, and the impact is relatively large, this round will be abnormally aborted and advanced defects will be submitted; at the same time, each module will conduct a simple smoke test to check whether there are other major problems and communicate with the development in a timely manner.
3. When this round is abnormally aborted, the test strategies for the relevant round phases will be postponed in sequence.