CN107193740A - The software test case test system and method for a kind of Reuse-Oriented - Google Patents

Abstract

The invention discloses a reuse-oriented software test case system, which includes a reuse test case library, including four granular organizations of test scenarios, test cases, test steps, and test data; and, test elements, reference, combination, and inheritance The test case library is used to test; the comparison module is used to compare the requirements of the test elements and determine how the test elements are reused for the reuse test case library. The invention also discloses a reuse-oriented software test case method. The invention sets the reuse test case library to abstract and extract the reusable test assets of different granularity, and the use cases are layered and reused, which greatly realizes the high-quality test of the software.

Description

A reuse-oriented software test case test system and method

technical field

The invention relates to the technical field of software testing, in particular to a reuse-oriented software testing case testing system and method.

Background technique

With the increasing popularity and deepening of computer applications, the number of software products has expanded rapidly at an alarming rate. The role of software in modern society is indispensable, and software cannot be wrong. In the software life cycle, software testing plays an important role and directly affects the quality of software.

However, ensuring high-quality software is usually very expensive, because testing is the main means of achieving quality, and achieving quality assurance consumes 50% to 60% of the software development effort and hinders the progress of the entire project. Because of this, inadequate quality assurance, especially insufficient testing, results in uneven software quality.

In the face of increasingly complex software systems, reuse is considered to be an important way to improve the efficiency and quality of software development and realize the industrial production of software products. The application of reuse technology in software requirements engineering and design engineering has achieved remarkable results .

Test reuse is to use the idea of reuse in software testing, and make full use of the results, knowledge and experience accumulated in past software testing to develop new tests.

Contents of the invention

The purpose of the present invention is a software test case test system oriented to reuse, which is used to solve the problem that the existing software test cannot fully guarantee the test quality, improve test work efficiency and reduce test cost.

The technical scheme adopted by the present invention to solve the technical problems is: a software test case test system oriented to reuse, which is characterized in that it includes

Reusable test case library, including four granular organizations of test scenarios, test cases, test steps and test data; and,

Test elements, reference, combination, inheritance reuse test case library, to be tested;

The comparison module is used to compare the requirements of the test elements and determine how the test elements are reused for the reuse test case library.

Further, the test scenario includes scenario attributes, scenario test cases, scenario test data, and scenario constraints; the scenario attributes are used to describe all attributes of the test scenario; scenario test data is a combination of data related to the test scenario; scenario A test case is a test case contained in a test scenario; a scenario constraint describes the execution method and sequence of running test cases contained in a test scenario.

Further, the test case is a collection of instructions for the actual operation of the system under test. The test case includes use case attributes, use case test data, use case test steps, and use case constraints; attributes are used to describe all attributes of the test case; use case test data Relevant data used for the use case; use case test steps are the basic operations in the testing process, including use case attributes and use case data; use case constraints refer to the execution method and sequence of the test steps contained in the test case.

Further, the execution method includes manual execution test and automated execution test; during manual execution, testers are required to prepare test preconditions, which are necessary conditions for successful use case execution according to business needs;

The execution sequence described above is to execute the current use case according to the dependency conditions.

Further, the test steps are basic operations in the test process, including attributes and data.

Further, all data required for the test data test is composed of attributes.

Further, the attribute is a correspondence between a name and a value.

Further, the reference is that the test element directly refers to the test scenario of the reuse test case library, or/and the test case, or/and the test step, or/and the test data;

Described combination is that the different test cases in the combined multiplexing test case library are new test scenarios; the combination of different test steps is a new test case; the combination of different test data is new test data;

The inheritance refers to inheriting and reusing the test scenarios, or/and test cases, or/and test steps, or/and test data in the test case library, and improving it according to the system under test to form new test cases.

Further, the requirement comparison is: comparing the test elements of the current version with the test elements of the previous version to determine the requirements.

A kind of reuse-oriented software test case test method, utilize any one described a kind of reuse-oriented software test case test system, it is characterized in that, specifically comprises the following steps:

1) Compare the current version of the test element with the previous version to determine the requirements;

2), if the test element needs to be referenced, then perform the step 3) operation; if the test element needs to be combined, then perform the step 4) operation; if the test element needs to be inherited, then perform the step 5) operation;

3) The test elements directly refer to the reuse test case library according to the requirements, and the test elements are directly reused;

4) The test elements combine the specific granular organization of the reuse test case library according to the requirements, and perform the direct reuse of the test elements;

5) The test elements inherit the original granular organization according to the requirements, improve the existing test elements, and form new test elements for reuse;

6). The reuse test case ends.

The beneficial effects of the present invention are:

1. The present invention sets up the reuse test case library to abstract and extract reusable test assets of different granularities, and use cases are reused in layers, greatly realizing high-quality software testing.

2. The present invention can realize the reuse of use cases through reference, combination and inheritance, regardless of whether it is a new version or an old version.

3. The present invention realizes automatic testing of software, reuse of use cases, and saves testing costs.

Description of drawings

Fig. 1 is a module structure connection diagram of the present invention;

Fig. 2 is a flow chart of the method of the present invention.

detailed description

In order to clearly illustrate the technical features of this solution, the present invention will be described in detail below through specific implementation modes and in conjunction with the accompanying drawings. The following disclosure provides many different embodiments or examples for implementing different structures of the present invention. To simplify the disclosure of the present invention, components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in different instances. This repetition is for the purpose of simplicity and clarity and does not in itself indicate a relationship between the various embodiments and/or arrangements discussed. It should be noted that components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and processes are omitted herein to avoid unnecessarily limiting the present invention.

As shown in Figure 1, a software test case test system for reuse includes

Reusable test case library, including four granular organizations of test scenarios, test cases, test steps and test data; and,

Test elements, reference, combination, inheritance reuse test case library, to be tested;

The comparison module is used to compare the requirements of the test elements and determine how the test elements are reused for the reuse test case library.

The test scenario includes scenario attributes, scenario test cases, scenario test data, and scenario constraints; the scenario attributes are used to describe all attributes of the test scenario; the scenario test data is a combination of data related to the test scenario; the scenario test case is a test scenario that contains The test cases; scenario constraints describe the execution method and sequence of test scenarios including test cases. For example, scenario S={ATTRIBUTE, DATA, CASE, CONSTRAIN}; where ATTRIBUTE is an attribute, including but not limited to the name of the scenario, the module to which the scenario belongs, and the number of test cases included in the scenario.

DATA is test data, such as the name of the virtual machine required to create a virtual machine scenario.

CASE is the test case included in the scenario. For example, the scenario of creating a virtual machine includes use cases for logging in to the system, creating an organization, creating a virtual data center, creating a virtual machine, and exiting the system.

CONSTRAIN is the constraint of the scene, indicating the execution sequence of CASE (test case).

A test case is a collection of instructions for the actual operation of the system under test. The test case includes use case attributes, use case test data, use case test steps, and use case constraints; attributes are used to describe all attributes of the test case; use case test data is used by the use case Relevant data; use case test steps are the basic operations in the test process, including use case attributes and use case data; use case constraints refer to the execution method and order of the test steps contained in the test case. For example, CASE={ATTRIBUTE, DATA, STEP, CONSTRAIN}; where ATTRIBUTE is an attribute, including but not limited to the name of the use case, the serial number of the use case, and the module to which the use case belongs.

DATA is test data, such as the name of the virtual machine required to create a virtual machine use case.

STEP is the test steps included in the test case. For example, creating a virtual machine test case includes entering the virtual machine name, virtual machine configuration, and selecting a virtual data center.

CONSTRAIN is the constraint of the use case, indicating the execution sequence of STEP (test steps).

Execution methods include manual execution of tests and automated execution of tests; manual execution requires testers to prepare test preconditions, which are necessary conditions for successful use case execution according to business needs; execution order is to execute the current use case based on dependent conditions .

Test steps are basic operations in the testing process, including attributes and data.

Test data All data required for testing, composed of attributes. For example virtual machine name=vm.

Attributes are the correspondence between names and values.

When software testers start to reuse test cases, they can use reference, combination and inheritance to reuse test cases from test data, test steps, test cases and test scenarios, from fine to coarse, according to inter-project requirements.

Requirement comparison is: compare the test elements of the current version with the test elements of the previous version to judge the requirements.

Reference is a test element that directly refers to the test scenario, or/and test case, or/and test step, or/and test data of the reuse test case library.

Combination is to combine and reuse different test cases in the test case library into new test scenarios; combine different test steps into new test cases; combine different test data into new test data.

Inheritance refers to inheriting and reusing the test scenarios, or/and test cases, or/and test steps, or/and test data in the test case library, and improving it according to the system under test to form new test cases.

As shown in Figure 2, a kind of software test case testing method oriented to reuse, utilizes a kind of software test case test system oriented to reuse, specifically comprises the following steps:

1) Compare the current version of the test element with the previous version to determine the requirements;

2), if the test element needs to be referenced, then perform the step 3) operation; if the test element needs to be combined, then perform the step 4) operation; if the test element needs to be inherited, then perform the step 5) operation;

3) The test elements directly refer to the reuse test case library according to the requirements, and the test elements are directly reused;

4) The test elements combine the specific granular organization of the reuse test case library according to the requirements, and perform the direct reuse of the test elements;

5) The test elements inherit the original granular organization according to the requirements, improve the existing test elements, and form new test elements for reuse;

6). The reuse test case ends.

The above is only a preferred embodiment of the present invention. For those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications are also considered as the present invention. protection scope of the invention.

Claims (10)

1. A software test case test system for reuse, characterized in that it comprises Reusable test case library, including four granular organizations of test scenarios, test cases, test steps and test data; and, Test elements, reference, combination, inheritance reuse test case library, to be tested; and, The comparison module is used to compare the requirements of the test elements and determine how the test elements are reused for the reuse test case library. 2. a kind of reuse-oriented software test case test system according to claim 1, is characterized in that, described test scene comprises scene property, scene test case, scene test data, scene constraint; Described scene property It is used to describe all the attributes of the test scenario; the scenario test data is the data combination related to the test scenario; the scenario test case is the test case contained in the test scenario; the scenario constraint is to describe the execution mode and sequence of the test scenario including the test case operation. 3. a kind of reuse-oriented software test case testing system according to claim 1, is characterized in that, described test case is the collection of the instruction of actual operation to system under test, and test case comprises use case attribute, use case test Data, use case test steps, and use case constraints; attributes are used to describe all attributes of a test case; use case test data is the relevant data used in the use case; use case test steps are basic operations in the testing process, including use case attributes and use case data; use case Constraints refer to the execution method and order of the test steps contained in the test case. 4. according to a kind of reuse-oriented software test case test system according to any one of claim 2 or 3, it is characterized in that, described execution mode comprises manual execution test and automatic execution test; Need tester during manual execution Be ready to test the preconditions, which are the conditions necessary for the successful execution of use cases according to business needs; The execution sequence described above is to execute the current use case according to the dependency conditions. 5. A kind of reuse-oriented software test case test system according to claim 1, characterized in that, said test steps are basic operations in the test process, including attributes and data. 6. A kind of reuse-oriented software test case test system according to claim 1, characterized in that, all data required for the test data test is composed of attributes. 7. A reuse-oriented software test case testing system according to claim 6, wherein said attribute is a correspondence between a name and a value. 8. a kind of reuse-oriented software test case test system according to claim 1, is characterized in that, described reference is the test scene that test element directly quotes reuse test case storehouse, or/and test case, or / and test steps, or / and test data; Described combination is that the different test cases in the combined multiplexing test case library are new test scenarios; the combination of different test steps is a new test case; the combination of different test data is new test data; The inheritance refers to inheriting and reusing the test scenarios, or/and test cases, or/and test steps, or/and test data in the test case library, and improving it according to the system under test to form new test cases. 9. A kind of reuse-oriented software test case test system according to claim 1, characterized in that, the comparison of the requirements is: the test elements of the current version are compared with the test elements of the previous version, and the requirements are judged . 10. a kind of software test case test method for reuse, utilize a kind of software test case test system for reuse described in any one of claim 1-9, it is characterized in that, specifically comprise the following steps: 1) Compare the current version of the test element with the previous version to determine the requirements; 2), if the test element needs to be referenced, then perform the step 3) operation; if the test element needs to be combined, then perform the step 4) operation; if the test element needs to be inherited, then perform the step 5) operation; 3) The test elements directly refer to the reuse test case library according to the requirements, and the test elements are directly reused; 4) The test elements combine the specific granular organization of the reuse test case library according to the requirements, and perform the direct reuse of the test elements; 5) The test elements inherit the original granular organization according to the requirements, improve the existing test elements, and form new test elements for reuse; 6). The reuse test case ends.