The following takes a commonly used software test plan template as an example to introduce how to formulate a test plan. It is used in the first stage of software evaluation. When the business system is used, it needs to be added or deleted appropriately according to the actual situation, as well as the risk management response plan.
It is mainly divided into the following parts:
Introduction to Documentation
Test Resources and Tools
Test Strategy
Test Phase Start/End Criteria
Risk and Response Plan
Quality Objectives
Test Process Management
Test Scope Definition
Test Schedule (Schedule, Personnel Arrangement)
Test Deliverables
Appendix - Test Concerns point
Document introduction
generally includes test plan writing purpose, restrictions and reference documents.
The writing purpose needs to be written according to the document reading audience. If the project is outsourced, it needs to be considered whether it will be incorporated in the acceptance document.
The test environment
generally includes hardware environment and software environment, as shown in the figure below:
Test tools
All tools used in the testing process, including use case writing tools, test execution tools, defect management systems, requirements management systems, etc.
Test strategies and methods The
common test strategies are as follows:
Try to find as many defects as possible (especially serious defects) within a limited time.
The test plan and the requirements reading are synchronized.
The use case design needs to be highly matched with the product requirements. Guided by the requirements Design more and more effective use cases
and gradually improve the test case library (test cases need to be revised and adjusted dynamically according to the execution process) to ensure that the test
process is controlled
. Data, that is, the input domain of the program is divided into several parts (subsets), and then a small number of representative data are selected from each subset as test cases. Boundary value analysis method The boundary value analysis method is a supplement to the equivalence class partition method. Usually the boundary of the input and output equivalence classes is the boundary case that should focus on testing. The error guessing method is based on experience and intuition to speculate on all possible errors in the program, so as to design test cases in a targeted manner. The basic idea of the error guessing method: List all possible errors and error-prone special cases in the program, and select Cases based on them. Decision table method Decision table is a tool for analyzing and expressing the situation of performing different operations under multiple logic conditions. The advantage of the decision table is that it can list all complex problems according to various possible situations to avoid omissions. In some data processing problems, the implementation of certain operations depends on the combination of multiple logical conditions, that is, different operations are performed for the combined values of different logical conditions. Decision tables are well suited to this type of problem. scene analysis
For the field of business function testing, scenario analysis is the most common and main design method. It starts with a solid understanding of the overall business. It is a user-oriented test case design method to design Cases from the perspective of users in combination with analysis of application scenarios.
The definition of the severity level of the defect
is not explained here, and it is usually defined according to the industry standard. However, in business-oriented products, product managers and user representatives need to determine the severity of defects, which is mainly calculated based on the degree of impact on users.
In addition, common test types are as follows:
Start/end criteria definition
The start standard and end standard are usually determined according to the company's internal test process, such as test delivery to the product manager or acceptance, or reaching the defined quality standard.
Interruption Standards
In the process of software development, it is inevitable that some accidents will cause the project to be interrupted. At this time, the test should also be suspended according to the agreement in advance. Generally, the following situations exist: when the software project needs to be suspended for
adjustment, the test should be suspended accordingly.
When a software project has a major progress deviation in the development life cycle and needs to be suspended or terminated, the test should be suspended or terminated accordingly.
If the development task is suspended, the corresponding test is also suspended.
Risk and response plans
generally include demand risks, time risks, resource risks, etc. It should be noted that each risk identification requires corresponding response plan measures, at least two.
Quality goals
generally include product quality goals and test quality goals.
The following test quality goals can be used as a reference:
all Cases have been executed at least once,
all bugs with a severity level and above have been fixed, and testers have passed
the core functions. Intermediate and above are not allowed Bug
General functions and functions not directly used by end users are not allowed to have bugs above the middle level.
The trend of defects is declining and close to 0.
No bugs above the middle level are found in the last 10% of the time.
Test process management
usually includes process management and defects of test documents. Process of processing, reporting meeting, form of progress report, etc.
Document process management, such as management personnel, storage, handover, sharing, etc., needs to be defined in a well-defined form, and the defect handling process can be described by the workflow defined in the defect management system.
Test scope definition
The scope of the test can be drawn up in advance according to the milestones of the project plan, such as which stage needs to be tested for the performance of the underlying framework, whether the interface test needs to be completed, which function points are included in the functional test, and so on. The non-test scope generally indicates the function points or test types that are not within the scope of this time. Sometimes due to the progress of the project, some function points may be temporarily deleted and need to be updated synchronously.
Test scheduling (schedule, personnel arrangement)
schedule can be divided with reference to the following nodes, and different stages can be divided according to specific nodes.
The arrangement of personnel and tasks can be based on the allocation of available fixed resources and temporary resources that have been sorted out in the early stage to make corresponding mobilization plans.
Test deliverables
Generally, the test products that need to be delivered after the end of a project include: software test plan, test case, defect report, project test report, user operation manual (if provided by the test team) Appendix- Test
Concern
Add multiple appendices, such as explanations of related terms, abbreviations, tests that require special attention, etc.
Test concerns are generally provided by technical leaders, product managers, and user representatives, and can be specified in the test plan in advance to remind testers of their precautions.
Such as adding, deleting, checking and modifying function points, data import, export, and specific input box functions. The key points of the test are 1.
The association and integrity of the database data cannot be destroyed.
, then back and repeat 3 times, check for errors
4 Modify the data in use;
5 Continuously query the correctness for multiple times
6 Import data format requirements should not be too strict, prompt clear
7 Whether the dynamic monitoring of data is correct
8 For date and time Type data, check the correctness of the format and the validity of the time and date. For example, the start time cannot be later than the end time, etc.
9 Repeated data processing, especially the repeated test plan of key values
After the completion of the test plan, it needs to be confirmed with the core person in charge of the project, and the next link can start after the review is passed. It should be noted that the test plan is a part of the project plan and is also an extension of the project plan. After the completion of the formulation, it still needs to be dynamically adjusted according to the actual situation in order to achieve the most ideal guidance purpose.
Finally: The complete software testing video tutorial below has been organized and uploaded, and friends who need it can get it by themselves [Guaranteed 100% free]
Software Testing Interview Documentation
We must study to find a high-paying job. The following interview questions are the latest interview materials from first-tier Internet companies such as Ali, Tencent, and Byte, and some Byte bosses have given authoritative answers. Finish this set The interview materials believe that everyone can find a satisfactory job.
