CN104317719B - Method for controlling software testing quality - Google Patents

Abstract

The invention discloses a method for controlling the quality of software testing. The method classifies test cases, classifies testers, and finds as many bugs as possible in a round of testing through a test control flow. Using the technology provided by the present invention, by reasonably arranging testers and test tasks, and through strict process control, layer by layer supervision and layer by layer confirmation, as many bugs as possible can be found in as few test rounds as possible, and the improvement can be improved. Test quality, reduce test cost, and urge testers to make progress consciously.

Description

A Method of Controlling the Quality of Software Testing

technical field

The present invention relates to the field of software testing, in particular to a method for controlling the quality of software testing. By classifying test cases, grading testers, and controlling test procedures, the present ubiquitous test modes and procedures are replaced; There are many bugs, instead of multiple rounds of repeated testing, the quality of testing is improved, and the cost of testing and products is reduced.

Background technique

As an important means to ensure software quality, software testing has been paid more and more attention, and software testing time occupies the entire project cycle time is getting longer and longer. At this time, few people think about the quality of software testing itself.

At present, the general company software testing process is for all test engineers to write test cases together, review test cases together, execute test cases by module, cross-execute test cases, submit bugs, etc. The test tasks are not divided according to the test engineer's ability and experience, and the test quality of the test engineer is not inspected and controlled. This often leads to incomplete bug discovery in the system test, resulting in repeated submission of the system test version, and the system version of some intermediate projects The number even reached 20 rounds, resulting in a series of problems such as delayed project delivery, reduced customer satisfaction, and increased project costs.

Contents of the invention

The technical problem to be solved by the present invention is: in order to solve the above problems, a method for controlling the quality of software testing is hereby proposed, through reasonable arrangement of testers and test tasks, and strict process control, layer-by-layer supervision and layer-by-layer confirmation, Find as many bugs as possible in as few test rounds as possible, improve test quality, reduce test cost, and urge testers to make progress consciously.

The technical scheme adopted in the present invention is:

A method for controlling the quality of software testing. The method classifies test cases, classifies testers, and through the test control process, finds as many bugs as possible in one round of testing, avoids missed testing and repeated rework, and improves testing. quality, lower testing and production costs.

in,

Classification of test cases: System test cases are divided into function point test cases and scene test cases. Specific and cross-use scenarios, aiming at demand points;

Classification of testers: According to the experience, ability and other qualities of test engineers, testers are divided into junior test engineers, intermediate test engineers, and senior test engineers;

Among them, junior test engineers are responsible for executing functional test cases;

Intermediate test engineers are responsible for designing and maintaining function point test cases, verifying function point use cases that junior test engineers have passed, and executing scenario test cases;

Senior test engineers are responsible for designing and maintaining scenario test cases, verifying the scenario test cases and free tests that intermediate test engineers have passed.

The test control process includes a function point test case execution process, and the specific steps are as follows:

1) Intermediate test engineers design and write function point test cases according to requirements and UI before testing, and pass the review;

2) At the beginning of the system test, the junior test engineer executes the test according to the function point test case. If the test case fails, the bug will be reported, and the use case will be left for the next round of execution; if the test case passes, it will be delivered to the intermediate test engineer for confirmation;

3) The intermediate test engineer executes the use case that the junior test engineer has passed, and if it is confirmed, it will be delivered to the senior test engineer for automation, and the use case does not need to be executed in the next round; Round continue to repeat the 2 steps;

4) The senior test engineer receives the function point use case submitted by the intermediate test engineer, and implements it automatically to facilitate regression testing. So far, the execution of the function point test case of this round is completed.

The test control flow includes a scenario test case execution flow, and the specific steps are as follows:

1) Senior test engineers design and write scenario test cases according to requirements before testing, and pass the review;

2) At the beginning of the system test, the intermediate test engineer executes the test according to the scenario test case. If the test case fails, the bug will be reported, and the use case will be left for the next round of execution; if the test case passes, it will be delivered to the senior test engineer for confirmation;

3) The senior test engineer executes the scenario test case that the intermediate test engineer has passed. If the test case is confirmed to be passed, the use case will be automatically implemented to facilitate the regression test. The use case does not need to be executed in the next round; , repeat step 2) in the next round of this use case;

4) The senior test engineer is responsible for executing the free test. If the use case fails, the bug will be reported; if the use case passes, the scenario test case will be executed.

Beneficial effects of the present invention: By adopting the technology provided by the present invention, by reasonably arranging test personnel and test tasks, and through strict process control, layer by layer supervision and layer by layer confirmation, it is possible to find as many as possible in as few test rounds as possible. More bugs, improve test quality, reduce test cost, and urge testers to make progress consciously.

Description of drawings

Fig. 1 is the flowchart of the realization of the method of the present invention.

detailed description

Below according to accompanying drawing of description, in conjunction with specific embodiment, the present invention is further described:

A method for controlling the quality of software testing. The method classifies test cases, classifies testers, and through the test control process, finds as many bugs as possible in one round of testing, avoids missed testing and repeated rework, and improves testing. quality, lower testing and production costs.

in,

Classification of test cases: System test cases are divided into function point test cases and scene test cases. Specific and cross-use scenarios, aiming at demand points;

Classification of testers: According to the experience, ability and other qualities of test engineers, testers are divided into junior test engineers, intermediate test engineers, and senior test engineers;

Among them, junior test engineers are responsible for executing functional test cases;

Intermediate test engineers are responsible for designing and maintaining function point test cases, verifying function point use cases that junior test engineers have passed, and executing scenario test cases;

Senior test engineers are responsible for designing and maintaining scenario test cases, verifying the scenario test cases and free tests that intermediate test engineers have passed.

The test control process includes a function point test case execution process, and the specific steps are as follows:

1) Intermediate test engineers design and write function point test cases according to requirements and UI before testing, and pass the review;

2) At the beginning of the system test, the junior test engineer executes the test according to the function point test case. If the test case fails, the bug will be reported, and the use case will be left for the next round of execution; if the test case passes, it will be delivered to the intermediate test engineer for confirmation;

3) The intermediate test engineer executes the use case that the junior test engineer has passed, and if it is confirmed, it will be delivered to the senior test engineer for automation, and the use case does not need to be executed in the next round; Round continue to repeat the 2 steps;

4) The senior test engineer receives the function point use case submitted by the intermediate test engineer, and implements it automatically to facilitate regression testing. So far, the execution of the function point test case of this round is completed.

The test control flow includes a scenario test case execution flow, and the specific steps are as follows:

1) Senior test engineers design and write scenario test cases according to requirements before testing, and pass the review;

2) At the beginning of the system test, the intermediate test engineer executes the test according to the scenario test case. If the test case fails, the bug will be reported, and the use case will be left for the next round of execution; if the test case passes, it will be delivered to the senior test engineer for confirmation;

3) The senior test engineer executes the scenario test case that the intermediate test engineer has passed. If the test case is confirmed to be passed, the use case will be automatically implemented to facilitate the regression test. The use case does not need to be executed in the next round; , repeat step 2) in the next round of this use case;

4) The senior test engineer is responsible for executing the free test. If the use case fails, the bug will be reported; if the use case passes, the scenario test case will be executed.

Claims (3)

1. A method for controlling software test quality is characterized in that: the method classifies the test cases, classifies the testers, finds more bugs in one round of test through the test control flow, avoids missing test and repeated rework, wherein,

classifying test cases: the system test cases are divided into function point test cases and scene test cases, and the function point test cases aim at single and specific function points; the scene test case aims at complex and crossed use scenes;

grading the testers: according to the experience and the capability of the test engineer, dividing the test personnel into a primary test engineer, a middle test engineer and a high test engineer;

wherein, the primary test engineer is responsible for executing the function point test case;

the middle-level test engineer is responsible for designing and maintaining the function point test cases, verifying the function point test cases which are executed by the primary test engineer and executing the scene test cases;

the high-level test engineer is responsible for designing and maintaining the scene test cases, and verifying the passed scene test cases and free tests executed by the middle-level test engineer.

2. The method for controlling the quality of software testing according to claim 1, wherein: the test control flow comprises a function point test case execution flow, and the specific steps are as follows:

1) before testing, a middle-level test engineer designs and compiles a function point test case according to requirements and a UI (user interface), and passes the evaluation;

2) when the system test is started, a primary test engineer executes the test according to the function point test case, if the case does not pass, the bug is reported, and the case is left to be executed continuously in the next round; if the case passes, the case is delivered to a middle-level test engineer for confirmation;

3) the middle-level test engineer executes the case which passes the execution of the primary test engineer, confirms that the case passes the execution of the primary test engineer and delivers the case to the high-level test engineer for automation, and the case does not need to be executed in the next round; if the test case fails, returning the test case, submitting bug, and repeating the step 2) in the next round of the case;

4) and the high-level test engineer receives the function point test cases submitted by the middle-level test engineer, the function point test cases are automatically realized, the regression test is convenient, and the execution of the function point test cases of the round is completed.

3. A method of controlling the quality of a software test according to claim 1 or 2, characterized by: the test control flow comprises a scene test case execution flow, and the specific steps are as follows:

1) before testing, a high-level test engineer designs and compiles a scene test case according to requirements and passes the review;

2) when the system test is started, a middle-level test engineer executes the test according to the scene test case, if the case does not pass, the bug is reported, and the case is left to be executed continuously in the next round; if the case passes, the case is delivered to a high-level test engineer for confirmation;

3) the high-level test engineer executes the passed scene test case executed by the middle-level test engineer, confirms that the passed scene test case passes, automatically realizes the case, is convenient for regression test, and does not need to execute the case in the next round; if the test case fails, returning the test case, submitting bug, and repeating the step 2) in the next round of the case;

4) the senior test engineer is responsible for executing the free test, and if the case does not pass, the bug is reported; and the case passes, and the scene test case is executed.