To do their best, you must first sharpen your tools ". Professional tests must be based on a good test plan. Although each step of the test is independent, there must be a test plan that acts as a framework structure. The test plan should be used as the initial step and an important part of the test. A test plan should include product Basic Information Survey, Test Requirement Description, test strategy and record, test resource configuration, schedule, problem tracking report, Test Plan Review, and result. Product Basic Information Survey:
This part should include some basic information about the product, such as the product operation platform and application fields, product features, main functional modules, and product features. For large test projects, the purpose and focus of the test should also be included.
Key points include:
Objective: To describe how to establish the test on an objective basis, define the testing strategy, test configuration, and roughly estimate the period required for the test and the time for submission of the final test report.
Change: events that may lead to changes to the test plan. The test tool has been improved, the test environment has changed, or new features have been added.
Technical Structure: drawing can divide the software to be tested into several components and plan a complete system suitable for testing, including how data is stored, how to pass (data flow diagram), what is the purpose of testing each part. How to update data in each part. There are also conventional technical requirements, such as operating platforms and databases.
Product Specifications: Describes the manufacturer and product version.
Test scope: briefly describes how to build a test platform and potential risks of testing.
Project information: describes the relevant materials of the project to be tested, such as user documents, product descriptions, and examples of main functions.
Test requirements:
This section lists all functional items to be tested. All functional items that do not appear in this list are excluded from the test
. If one day you find a problem in an untested part, you should be glad to have this documented document to prove that you have tested nothing. Key points include:
Functional testing: theoretically, testing covers all functional items, such as adding, editing, and deleting records in the database. This is a huge project, but it is conducive to the integrity of the test.
Design test: for some user interfaces, menu structures, and whether the design of forms is reasonable, etc.
Overall consideration: This part of testing needs to take into account the flow of data streams from one module of the software to another module.
Correctness in the process.
Test policies and records:
This is the focus of the entire test plan. To describe how to conduct tests fairly and objectively, consider: modules, functions,
Overall, system, version, pressure, performance, configuration, installation, and other factors. Take into account the details as much as possible, the more detailed the better, and create a template for the test record document to prepare for the upcoming test. The important parts of the test record
The details are as follows:
Fairness statement: it is necessary to describe the fairness of the test and the standards observed to prove that the test is objective. On the whole, the software functions must meet the requirements and be implemented correctly, it must be consistent with the description of the user document.
Test Case: describe what the test case is, what tools are used, what tool sources are, how the tool is executed, and what data is used. Leave room for future regression tests in the test records. Of course, consider the impact of other software installed on the software being tested.
Special considerations: Sometimes, we need to test the software in some special aspects for the impact of some external environments.
Experience judgment: consider the problems that often occur during previous tests.
Imagine: Adopting divergent thinking will often help you find new ways of testing.
Test Resource Configuration:
Project Resource Plan: develop a project resource plan that includes tasks and resources required for each stage. When something similar to the term of use or resource sharing occurs, update this plan.
Schedule:
The test schedule can be made into a common form of multiple projects, which can be produced according to the approximate time estimation. the operation process is as follows:
It should take the regular cycle of software testing as a reference, or it can be determined based on the module to be tested.
Problem tracking report:
In the testing plan stage, we should clarify how to prepare a problem report and how to define a problem
Nature. The problem report should include the problem discoverer and modifier, the frequency of the problem, the test cases used to determine the problem, and the test environment when the problem is generated.
The Problem description should be as quantitative as possible. There are several types of problems:
1. Serious problems: serious problems mean that the function is unavailable, or mistakes in permission restrictions. They may also be caused by changes in some places.
2. General problem: the function is not implemented according to the design requirements or the implementation of some interface interactions is incorrect.
3. Recommended problem: the function runs less quickly than required, or does not meet certain conventions, but does not affect the system performance. The interface is incorrect first, and the format is incorrect, prompts for Fuzzy obfuscation.
Test Plan Review:
It is also called the test specification review. Before the test is actually carried out, it must be carefully and responsibly checked to obtain the entire test.
The identity of the department personnel, including the consent and signature of the Department owner.
Result:
The plan does not end here. In the review of the final test results, it is necessary to strictly verify the plan and actual implementation.
Whether there is any deviation in the line is reflected in whether the final report content is consistent with the test plan, and then you can start to prepare the next test plan. |
