Software Test Documentation

In the process of software testing, the test document is also an important process, so testers also need to learn how to write and read the test document.

First, the definition:

The test document (testing documentation) records and describes the entire test process, which is a very important document throughout the test activity. The core documents required for the test process implementation are: test plans, test cases, and software test reports.

Second, the importance of the test document

Software testing is a very complicated process, involving the work of other stages of software development, it is very important to improve the quality of software and ensure the normal operation of software, so it is necessary to write down the requirements, process and test results of the test in formal document form. The Software test documentation describes the tests and the results of the tests to be performed. It can be said that the preparation of test documents is an important part of the standardization of software testing work. Software Test documentation is not only considered during the testing phase, it should be started in the software development requirements analysis phase, some software developers design solutions should also be reflected in the test document, in order to facilitate the design of the test. The test document has a very clear guiding role and evaluation function for the testing stage work. The Software test documentation is used even when the software is in the maintenance phase, where it is often re-tested or regression tested.

Third, the content of the test document

The entire test process results in a number of test documents, which can generally be divided into two categories: the test plan and the test analysis report. The test plan document describes the scope, method, resource, and time progress of the test activity that will be performed. The test report is a test document that performs the test phase and analyzes the test results. Contains the execution details for the corresponding test item.

Test plan:

1, definition: Software testing is an organized and planned activities, should be given adequate time and resources to test plans, so that software testing under reasonable control of normal. Test planning, as the starting step of testing, is the key manager of the entire software testing process. The test plan specifies the methodology, test environment, test pass, or failure criteria to be used in each phase of the test.

2. Purpose and role of the test plan the purpose of the test plan is to define the intent of the test activity. It regulates the content, methods and processes of software testing and provides assurance for the organization to complete the testing tasks. Professional testing must be based on a good test plan. Although each step of the test is independent, there must be a test plan that plays a role in the framework structure.

3, the test Plan document test plan is a test plan, including the master plan also contains a rating plan, is to update the improved documentation.

4. The test plan's content software test plan is the most important part of the entire testing process, providing the basis for a manageable and high-quality test process. The test plan describes the expected goals of the software test in document form, and determines the methodological strategy to be used in the testing process. Test plans include test objectives, test scopes, test objects, test strategies, test tasks, test cases, resource configurations, test results analysis and measurements, and test risk assessments, which should be complete, but should not be exhaustive.

An ideal test plan should reflect the following characteristics:

(1), in the detection of major defects have a good choice;

(2), to provide the majority of code coverage;

(3), with flexibility;

(4), easy to implement, return and automation;

(5), define the type of test to be performed;

(6), the test document clearly describes the expected test results;

(7) To provide defect check when the defect is found;

(8), define the test target clearly;

(9), clearly define the test strategy;

(10), clearly defined test pass standard;

(11), no test redundancy;

(12), confirm the test risk;

(13), documentation to determine the requirements of testing;

(14), define the deliverables of the test pieces.

Iv. development of software test plan

(1) Summary test plan

The summary test plan is developed at the beginning of the software development, which includes: ① defines the tested object and the test target, ② determines the test phase and the test cycle, ③ formulates the tester, software and hardware resources and test progress plan, ④ clear task and distribution and Responsibility division, ⑤ defined software test methods, test standards. For example, the statement coverage reached 98%, the error correction rate of more than three levels of 98%, etc. ⑥ all decisions not to correct errors must be approved by a dedicated quality review organization, ⑦ support environment and test tools, etc.

(2) Detailed test plan

A detailed test plan is a specific test implementation plan for a tester or test team that specifies what the tester is responsible for testing, the strength of the test and the progress of the work, and is an important criterion for checking the actual performance of the test. The main contents of the detailed test plan are: Plan progress and actual progress table, test Essentials, test strategy, unresolved problems and obstacles.

1. Develop test outline (use case)

Test outline is the basis of software testing, to ensure that the test function is not omitted, and the function is not repeated testing, so as to reasonably arrange testers, so that software testing is not dependent on the individual. Test outlines include: test items, test steps, standards for test completion, and test methods (manual or automated tests). The test outline is not only the basis of software development testing, but also the important document and basis of quality assurance in the system requirement analysis stage. Both automated and manual tests must meet the requirements of the test outline.

2. Setting standards for test passing or failure

The test standard is a respectable statement that indicates when the test is finished, and the quality of the application being tested. Test criteria can be a series of statements or references to another document, such as a test process guide or test criteria. Test criteria should indicate:

(1), the exact test target

(2), how to establish the scale of measurement

(3), the use of those standards to evaluate the measurement

3, the necessary conditions for the development of test hang standards and recovery

Specifies the criteria for suspending all or part of the test item and indicates the criteria for the recovery test and the test activity that must be duplicated.

4, make the test task schedule (clear the test task, each task must be clear 7 topics. ）

Task: A concise sentence that describes the method and criteria for the task: The method to be used and the criteria to be followed when the task is performed.

Input and output: gives the required input and output schedule for the task: gives the start and duration of the task

Resources: The human and material resources needed to give the task

Risks and assumptions: indicate the assumptions that should be met to initiate the task, and the risks that may exist for the execution of the task

Roles and responsibilities: Identify who is responsible for the organization and execution of the task, and who will assume the responsibilities

5. Develop test work products to be delivered

Indicate the documentation, test code, and test tools that should be delivered, typically including test plans, test scenarios, test cases, test procedures, test logs, test summary reports, test input and output data, and test tools.

6. Develop workload estimates

Give the manpower requirements and totals for the tasks defined earlier

7. Write the test plan document

A test scenario document is a design test phase document that specifies a detailed documentation of the design test method that is performed to complete the performance test of the software or software integration.

Software Test Documentation