CN110704322B - Software testing method and system - Google Patents

Abstract

The application relates to a software testing method and a system, which belong to the technical field of software testing, and the software testing method comprises the following steps: creating an iteration case set for storing a current iteration case, a core case set for storing a test case aiming at a main flow of a product and a mirror case set for storing a historical iteration case in advance; carrying out configuration maintenance on the iteration use case set, the core use case set and the mirror image use case set; in the functional test, calling an iteration case set and a mirror image case set to carry out software functional test and defect verification; and after the software is released, calling the core case set to perform an online smoking test. By carrying out classification management on the cases in the software test and calling different case combinations at different testing stages, the reuse rate of the test cases is improved, and the efficiency of the software test is integrally improved.

Description

Software Testing Method and System

technical field

The application belongs to the technical field of software testing, and in particular relates to a software testing method and system.

Background technique

A computer system is composed of software and hardware. Software is a program that runs on a computer and corresponding documents. Software generally exists to provide functions and solve specific problems. After the computer software is developed, it needs to be tested, whether the function of the software conforms to the specifications, whether the performance meets the requirements, whether there are safety problems in the software, etc. The above-mentioned tests all depend on the design of test cases, and a good design of test cases can cover enough and complete scenarios.

In the process of using the software, new functions and performance requirements will be generated, or software functions that are no longer applicable will be discarded, which requires multiple revision tests. At this time, a large number of test cases will be generated. In the existing technology, the software testing of software companies is to write test cases for iterative content. After multiple iterations, there is no complete use case that can reflect the latest functions of the software. The learning cost for newcomers is high, which will affect the testing efficiency.

Contents of the invention

In order to overcome the problems existing in the related technologies at least to a certain extent, the present application provides a software testing method and system, which help to improve testing efficiency.

In order to achieve the above object, the application adopts the following technical solutions:

first,

The application provides a software testing method, the software testing method comprising:

Pre-create the iterative use case set used to save the current iterative use cases, the core use case set used to save the test cases for the main process of the product, and the mirror use case set used to save the historical iterative use cases;

Perform configuration maintenance on the iterative use case set, core use case set and mirror use case set;

In the function test, the use cases in the iterative use case set and the mirror use case set are called to perform software function test and defect verification;

After the software is released, call the centralized use cases of the core use cases for online smoke testing.

Optionally, the configuration maintenance of the iterative use case set, core use case set and mirror use case set includes:

In the first iteration,

Design iterative use cases for the functions to be launched in the iterative and save them into the iterative use case set;

Take out and save the use cases for the main process in the iterative use case set into the core use case set;

After the end of the first iteration, copy the use cases in the iterative use case set into the mirror use case set, and clear the iterative use case set;

In subsequent iterations,

Based on the function development status of the current iteration, one or more of the iterative use case set, the core use case set and the mirror use case set are configured and maintained.

Optionally, the function development status of the current iteration includes adding functions on the basis of the previous iteration, modifying functions on the basis of the last iteration, and deleting functions on the basis of the last iteration.

Optionally, when the current iteration is to add functions on the basis of the previous iteration, the following configuration maintenance is performed on the iterative use case set and the mirror image use case set:

Design iterative use cases for new functions and save them into iterative use case sets;

After the iteration ends, the use cases in the iterative use case set are copied into the mirror use case set, and the iterative use case set is cleared.

Optionally, when the current iteration is to modify the function on the basis of the previous iteration, the following configuration maintenance is performed on the set of mirrored use cases:

For the modified function, modify the corresponding functional use case in the mirrored use case set.

Optionally, when the current iteration is to delete the function on the basis of the previous iteration, the following configuration maintenance is performed on the set of mirrored use cases:

For the function to be deleted, delete the corresponding functional use case in the image use case set.

Optionally, checking and updating the set of core use cases is also included, so that the use cases in the set of core use cases are always aimed at the current main process of the software.

Optionally, it also includes pre-creating a regression case set for storing regression test cases;

Perform configuration maintenance on the set of regression use cases;

During the regression test, the use cases in the mirrored use case set and the regression use case set are called for testing.

Optionally, the configuration maintenance of the set of regression use cases includes:

Analyze the defects found in functional testing, and discover typical software defects;

Analyze the usage problems reported by users after the software is released, and find software online defects;

The use cases designed to discover the typical software defects and software online defects are stored in the regression use case set.

Second aspect,

The application provides a software testing system, the software testing system comprising:

The iterative use case module is used to save the current iterative use case;

The core use case module is used to save test cases for the main process of the product;

Mirror use case module, used to save historical iteration use cases;

Regression use case module, used to save regression test cases;

A processing module, used to add, delete and modify the iterative use case module, core use case module, mirroring use case module and regression use case module;

The test module is used to call the use cases in the iterative use case module, the core use case module, the mirror use case module and the regression use case module to perform software testing.

The application adopts the above technical solutions, and at least has the following beneficial effects:

By classifying and managing use cases in software testing, calling different combinations of use cases at different stages of testing, the reuse rate of test cases is improved, the learning cost of tester rotation and tester replacement is reduced, and the overall efficiency of software testing is improved. efficiency.

Other advantages, objects, and features of the present invention will be set forth in the ensuing description to some extent, and to some extent, will be obvious to those skilled in the art based on the investigation and research below, or can be Learn from the practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings are used to provide a further understanding of the technical solutions of the present application or the prior art, and constitute a part of the description. Wherein, the drawings expressing the embodiments of the present application are used together with the embodiments of the present application to explain the technical solutions of the present application, but do not constitute limitations on the technical solutions of the present application.

Fig. 1 is the schematic flow chart of the software testing method in one embodiment of the present application;

FIG. 2 is a schematic illustration of use case configuration maintenance of a software testing method in an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be described in detail below. Apparently, the described embodiments are only some of the embodiments of this application, not all of them. Based on the embodiments in the present application, all other implementation manners obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present application.

In order to facilitate the understanding of the technical solutions in the present invention, several concepts involved in the present application will be described below first.

Online defect (online bug): Refers to the problems discovered by real users when the software is released.

Typical defect (typical bug): Refers to a problem that occurs in a certain function of the software, and also occurs in other modules or software.

Iteration: It means that a product has many functions to be realized, and the plan is to complete the realization in several cycles, and the content to be realized in each cycle will be planned. This fixed cycle is called iteration.

In software testing, test cases are bound to be involved. In existing software testing, use cases are designed for new software functions. The classification of use cases is closely related to the habits or styles of the personnel who design these use cases. After the use cases are designed, they will be uploaded to the company’s test case storage tool. . When the function changes, design a test case for the new function and upload it to the use case storage tool. In this way, after several iterations, the test cases corresponding to the latest functions of the software need to go through the historical test cases, which may be in the use case document uploaded for the first time, or in the use case document uploaded for the second time, or may not be found at all. There is no corresponding use case. When regression testing software before going online, new functions are tested according to test cases, and previous functions can only be supplemented with regression use cases, or rely on experience, or exploratory testing, and the probability of missing tests is very high. In other words, in the existing software testing methods, there is a lack of effective management of test cases, and the reuse rate is low, resulting in low efficiency of software testing.

For this reason, the application proposes a kind of software testing method, as shown in Figure 1, in this software testing method, comprises the following steps:

Step S110, pre-create an iterative use case set for saving current iterative use cases, a core use case set for saving test cases for the main process of the product, and a mirror use case set for saving historical iterative use cases.

Step S120, performing configuration maintenance on the iterative use case set, the core use case set and the mirror use case set. Configuration maintenance includes operations such as adding, modifying, and deleting use cases for each use case set, so that each use case set contains corresponding test cases. The specific configuration maintenance process will be further described later.

Step S130, in the function test, call the use cases in the iterative use case set and the mirror use case set to perform software function test and defect verification;

Step S140, after the software is released, call the use cases in the core use case set to perform an online smoke test. The online smoke test here refers to a quick functional usage test of the released software as soon as the software is released.

This application classifies the use cases in software testing, organizes and manages them hierarchically, calls different combinations of use cases at different stages of testing, improves the reuse rate of test cases, and reduces the learning cost of tester rotation and tester replacement. Overall, the efficiency of software testing is improved.

The technical solution of the present invention will be described in detail below with a specific embodiment.

For a software product developed and tested, an iterative use case set used to save the current iterative use cases, a core use case set used to save test cases for the main process of the product, and a mirrored use case set used to save historical iterative use cases are created in advance.

In this embodiment, the configuration and maintenance of the iteration use case set, the core use case set and the mirror use case set specifically include two scenarios, that is, the first iteration and the iteration after the first iteration, which will be described separately below.

first iteration

The first iteration here refers to software development from scratch, and iterative testing for the functions to be launched in the first iteration. In the first iteration, iterative use cases are designed for the functions to be launched in the iteration and saved in the iterative use case set, and the use cases for the main process in the iterative use case set are taken out and saved into the core use case set;

In the functional test of the first iteration, the use cases in the iterative use case set and the mirror use case set (empty at this time) are called to perform software function test and defect verification;

After the first iteration, the use cases in the iterative use case set are copied into the mirror use case set, and the iterative use case set is cleared. Of course, after the first iteration is over, the software product will be released for the first time. After the software release, the core use cases will be called for online smoke testing.

subsequent iterations

Subsequent iterations refer to the second iteration of the software product and subsequent iterations. In subsequent iterations, based on the function development of the current iteration, one or more of the iterative use case set, the core use case set and the mirror use case set are configured and maintained.

Specifically, the function development of the current iteration includes adding functions on the basis of the previous iteration, modifying functions on the basis of the previous iteration, and deleting functions on the basis of the previous iteration.

For example, the current iteration is the second iteration, and the function development of the second iteration of the software product is nothing more than three situations: adding new functions on the basis of the previous (first) iteration; discovering the functions of the last (first) iteration If it does not meet the user's requirements, modify the function; if it is found that the function of the last (first) iteration is completely unused, delete it.

For these three situations, one or more of each use case set is configured and maintained. specific,

(1) When the current iteration is to add functions on the basis of the previous iteration, perform the following configuration maintenance on the iteration use case set and the mirror use case set:

Design iterative use cases for new functions and save them into iterative use case sets;

After the iteration ends, the use cases in the iterative use case set are copied into the mirror use case set, and the iterative use case set is cleared.

(2) When the current iteration is to modify the function on the basis of the previous iteration, perform the following configuration maintenance on the mirrored use case set:

For the modified function, modify the corresponding functional use case in the mirrored use case set without rewriting a test case.

(3) When the current iteration is to delete the function on the basis of the previous iteration, the mirror use case set is configured and maintained as follows:

For the function to be deleted, delete the corresponding functional use case in the image use case set.

And in this embodiment, the above three cases also include checking and updating the core use case set, so that the use cases in the core use case set are always aimed at the configuration maintenance process of the current main flow of the software. For example, design the main process use cases of new functions and put them into the core use case set. For example, when the main process use cases are modified or deleted in this iteration, make corresponding modifications and deletes in the core use case set. It should also be noted that the above-mentioned iterations and post-iteration releases also include a testing process similar to the combination of test cases in the first iteration.

On the basis of the foregoing embodiments, in another embodiment, the software testing method in the present invention also includes, pre-creating a set of regression use cases for storing regression test cases;

Configure and maintain the regression use case set;

During the regression test (for example, the regression test before the software is finally launched), the use cases in the mirror use case set and the regression use case set are called for testing.

Specifically, the configuration and maintenance of the regression use case set includes,

In each iteration, analyze the defects found in the functional test, and find typical software defects; after each iteration, analyze the usage problems reported by users after the software is released, and find software online defects; design The use cases used to discover the above-mentioned typical software defects and software online defects are saved into the regression use case set.

In this embodiment, the use case configuration maintenance in the software testing method of the present application is shown in FIG. 2 . In conjunction with Fig. 2, for the convenience of further understanding of the technical solution of the present application, in the implementation technical solution of the present application below, core use case (concentrated use case of core use case), mirroring use case (concentrated use case of mirror image use case), iterative use case (concentrated use case of iterative use case), The differences and uses of regression use cases (regression use case set use cases) are further explained:

Core use case versus mirror use case: the core use case reflects the main process (core process) of this product, and the mirror use case reflects all the function points of the current product.

Iteration use case versus mirror use case: Iteration use case is a functional checkpoint for a specific iteration, and mirror use case is a result of iteration accumulation to the current state.

Regression use cases: The typical defects extracted during the iterative process are converted into regression use cases, and defects that have occurred online (typical defects) are converted into regression use cases.

Core use cases can be used to understand the product, and can be used by anyone who is interested in addition to testing; regression use cases are used to supplement test coverage scenarios, iteration use cases are used to check corresponding iteration functions, and are used by testers; mirror use cases are used for inheritance, for This group is used to test the elderly/newcomers.

In addition, it should be noted that according to the labor cost that can be invested in the test, the configuration and maintenance of the regression use case set may not be performed. When performing regression testing, the use cases in the mirrored use case set are directly used for testing.

A software testing system is also provided in an embodiment of the present application, and the software testing system includes:

The iterative use case module is used to save the current iterative use case;

The core use case module is used to save test cases for the main process of the product;

Mirror use case module, used to save historical iteration use cases;

Regression use case module, used to save regression test cases;

The processing module is used to add, delete and modify the iteration use case module, core use case module, mirror use case module and regression use case module;

The test module is used to call the use cases in the iterative use case module, the core use case module, the mirror use case module and the regression use case module for software testing.

The specific implementations of the processing module and the testing module in the software testing system have been described in detail in the embodiments of the method, and will not be described in detail here.

The above is only a preferred embodiment of the present invention, but the protection scope of the present invention is not limited thereto, and any person familiar with the technology can easily think of changes or substitutions within the technical scope disclosed in the present invention. , should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be determined by the protection scope of the claims.

Claims (8)

1. A software testing method, comprising:

creating an iteration case set for storing a current iteration case, a core case set for storing a test case aiming at a main flow of a product and a mirror case set for storing a historical iteration case in advance;

configuring and maintaining the iteration use case set, the core use case set and the mirror image use case set;

in the functional test, calling the iteration case set and the mirror image case set to perform software functional test and defect verification;

after the software is released, calling a core case centralized case to perform an online smoking test;

the configuration and maintenance of the iteration use case set, the core use case set and the mirror use case set includes:

in the first iteration of the process,

designing an iteration case aiming at the function of the iteration to be on-line and storing the iteration case into an iteration case set;

taking out the use cases aiming at the main flow in the iteration use case set and storing the use cases into the core use case set;

after the first iteration is finished, copying the use cases in the iteration use case set into the mirror image use case set, and emptying the iteration use case set;

in the following iteration(s) of the process,

based on the function development condition of the current iteration, carrying out configuration maintenance on one or more of the iteration use case set, the core use case set and the mirror image use case set;

the function development condition of the current iteration comprises the steps of adding functions on the basis of the last iteration, modifying the functions on the basis of the last iteration and deleting the functions on the basis of the last iteration.

2. The software testing method according to claim 1, wherein when the current iteration is to add functions on the basis of the last iteration, the following configuration maintenance is performed on the iteration case set and the mirror case set:

designing an iteration case aiming at the newly added function and storing the iteration case into an iteration case set;

after the iteration is finished, copying the use cases in the iteration use case set into a mirror image use case set, and emptying the iteration use case set.

3. The software testing method of claim 1, wherein when the current iteration is to modify the function on the basis of the last iteration, the mirror image case set is configured and maintained as follows:

and modifying the corresponding function use case in the mirror image use case set aiming at the modified function.

4. The software testing method according to claim 1, wherein when the current iteration is to delete functions on the basis of the last iteration, the following configuration maintenance is performed on the mirror image case set:

and deleting the corresponding function use case in the mirror image use case set aiming at the function to be deleted.

5. The software testing method according to any one of claims 2 to 4, further comprising checking and updating the core case set, so that the use cases in the core case set always aim at the current main flow of the software.

6. The software testing method according to claim 1, further comprising creating a regression case set for storing regression test cases in advance;

carrying out configuration maintenance on the regression case set;

and calling the mirror image case set and the regression case set for testing during regression testing.

7. The software testing method of claim 6, wherein the configuring and maintaining the regression case set comprises:

analyzing the defects found in the functional test, and finding typical defects of the software;

analyzing the use problems reported by users after the software is released, and finding out the online defects of the software;

and storing the use cases designed for finding the typical defects of the software and the defects on the software line into the regression use case set.

8. A software testing system, comprising:

the iteration use case module is used for storing the current iteration use case;

the core case module is used for storing a test case aiming at the main flow of the product;

the mirror image use case module is used for storing a historical iteration use case;

the regression case module is used for storing regression test cases;

the processing module is used for adding, deleting and modifying the iteration case module, the core case module, the mirror image case module and the regression case module;

the test module is used for calling the cases in the iteration case module, the core case module, the mirror image case module and the regression case module to perform software test;

the processing module configured to:

in the first iteration of the process,

designing an iteration case aiming at the function of the iteration to be on-line and storing the iteration case into the iteration case module;

taking out the use cases aiming at the main flow in the iteration use case module and storing the use cases into the core use case module;

after the first iteration is finished, copying the use case in the iteration use case module into the mirror image use case module, and emptying the iteration use case module;

in the following iteration(s) of the process,

based on the function development condition of the current iteration, one or more of the iteration use case module, the core use case module and the mirror use case module are configured and maintained;

the function development condition of the current iteration comprises the steps of adding functions on the basis of the last iteration, modifying the functions on the basis of the last iteration and deleting the functions on the basis of the last iteration.

Images