KR20190068829A - Apparatus and method for managing testcase for testing software - Google Patents

Abstract

According to one embodiment of the present invention, an apparatus for managing a test case for a software test comprises: a case generating unit for generating a plurality of first test cases for testing functional elements of first software and a plurality of second test cases for testing functional elements of second software; a first detection unit for detecting at least one third test case corresponding to a first detection condition among the second test cases by comparing the functional elements of the first and second software functional elements; a second detection unit for detecting at least one fourth test case corresponding to a second detection condition among the first and second test cases by comparing the first and second test cases; and a determination unit for determining at least one of the detected third and fourth test cases as an optimal test case.

Description

[0001] APPARATUS AND METHOD FOR MANAGING TESTCASE FOR TESTING SOFTWARE FOR SOFTWARE TEST [0002]

The present invention relates to a test case management apparatus and method for software testing.

The controller software (SW) is developed by developing the base model first, and when the functions included in the base model are added, changed or deleted, a part of the base model is modified to develop a derivative model. The derived model is tested using the test cases that were tested for the first base model.

There are two main ways to perform the test. One is the method of performing verification using all the test cases used as input data (SW re-verification) when verifying the first base model, and the other is considering the changed SW part in the first base model for verification efficiency. (SW regression verification) by selecting some of the test cases that were used to verify the base model.

However, in the case of the SW re-verification method, the reliability of the test can be secured. However, there is a problem that the test efficiency is inadequate due to the excessive test time, and the SW regression verification method is difficult to apply and the test time can be reduced There is a problem that test reliability is poor.

It is an object of the present invention to provide a test case management apparatus and method for software testing that can improve the efficiency and / or reliability of software testing.

The technical problems of the present invention are not limited to the above-mentioned technical problems, and other technical problems which are not mentioned can be understood by those skilled in the art from the following description.

The test case management device for software testing according to an embodiment of the present invention includes a plurality of first test cases for testing functional elements of the first software and a plurality of second test cases for testing functional elements of the second software, Comparing the functional elements of the first software and the functional elements of the second software to detect at least one third test case corresponding to the first detection condition among the plurality of second test cases And a second test section for comparing the plurality of first test cases with the plurality of second test cases to detect at least one fourth test case corresponding to a second detection condition among the plurality of first test cases and the plurality of second test cases, A second detecting section for detecting a test case, and a second detecting section for detecting the at least one third test < RTI ID = 0.0 > And the fourth test case as the optimum test case.

In one embodiment, the first detection condition may be a condition for detecting a test case corresponding to functional elements different from the functional elements of the first software among the functional elements of the second software.

In one embodiment, the second detection condition detects a test case defined by different values among the test cases corresponding to the same functional elements among the functional elements of the first software and the functional elements of the second software Lt; / RTI >

In one embodiment, the functional elements of the second software may be created by deleting some of the functional elements of the first software or adding other functional elements to the functional elements of the first software.

In one embodiment, each of the plurality of first test cases may include an input value of variables defined in the functional elements of the first software.

In one embodiment, each of the plurality of second test cases may include an input value of variables defined in the functional elements of the second software.

A test case management method for software testing according to an embodiment of the present invention includes a plurality of first test cases for testing functional elements of the first software and a plurality of second test cases for testing functional elements of the second software Detecting at least one third test case corresponding to a first detection condition among the plurality of second test cases by comparing the functional elements of the first software with the functional elements of the second software, Comparing the plurality of first test cases and the plurality of second test cases to detect at least one fourth test case corresponding to a second detection condition among the plurality of first test cases and the plurality of second test cases , And detecting the at least one third test case and the fourth test case The can include determining the optimum test cases.

In one embodiment, the first detection condition may be a condition for detecting a test case corresponding to functional elements different from the functional elements of the first software among the functional elements of the second software.

In one embodiment, the second detection condition detects a test case defined by different values among the test cases corresponding to the same functional elements among the functional elements of the first software and the functional elements of the second software Lt; / RTI >

In one embodiment, the functional elements of the second software may be created by deleting some of the functional elements of the first software or adding other functional elements to the functional elements of the first software.

In one embodiment, each of the plurality of first test cases may include an input value of variables defined in the functional elements of the first software.

In one embodiment, each of the plurality of second test cases may include an input value of variables defined in the functional elements of the second software.

According to the test case management apparatus and method for testing software according to an embodiment of the present invention, efficiency and / or reliability of software testing can be improved.

1 is a view for explaining functional elements of a first software and a second software according to an embodiment of the present invention.
2 shows a test case management apparatus for software testing according to an embodiment of the present invention.
3 is a flowchart illustrating a test case management method for software testing according to an embodiment of the present invention.
4 is a diagram illustrating a plurality of first test cases for testing functional elements of a first software according to an embodiment of the present invention.
5 is a view for explaining a plurality of second test cases for testing functional elements of a second software according to an embodiment of the present invention.
FIG. 6 and FIG. 7 illustrate a test case management method for software testing according to an embodiment of the present invention.
FIG. 8 illustrates a computing system for implementing a test case management method for software testing according to an embodiment of the present invention.

Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the embodiments of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the difference that the embodiments of the present invention are not conclusive.

In describing the components of the embodiment of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. Also, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted in an ideal or overly formal sense unless explicitly defined in the present application Do not.

Hereinafter, 'software' may mean software executed by the controller of the vehicle, but this is merely an example for the sake of understanding, but is not limited thereto. Further, the 'software' may include a first software and a second software, and the second software may delete some of the functional elements of the first software, add other functional elements to the functional elements of the first software, May be defined as software that alters all or a portion of the functional elements of the first software.

1 is a view for explaining functional elements of a first software and a second software according to an embodiment of the present invention.

Referring to Figure 1, functional elements of a first software (a) and a second software (b) are shown. Here, the functional element may include 'state' and 'transition' defined in the software, 'state' may mean the state of the vehicle controller at a specific point in time, and 'transition' May refer to an operation of connecting 'states'. In addition, 'transition' can be composed of 'transition condition' for occurrence of transition and 'action occurring when transition condition is satisfied'.

Referring to FIG. 1 (a), the first software may be composed of functional elements (sub 1 to sub 8). Referring to FIG. 1 (b), the second software may be composed of functional elements (sub 1 to 3, sub 4, sub 6, sub 8 to 11). That is, the second software may be a form in which sub 5 of functional elements of the first software is changed to sub 11, sub 7 is deleted, and sub 9 and sub 10 are added. As such, the second software may be defined as software that deletes some of the functional elements of the first software, adds other functional elements to the functional elements of the first software, or alters all or a part of the functional elements of the first software . On the other hand, for the sake of understanding, the functional elements of the first software and the second software are defined as " transition " below.

A test case (i.e., a test case for testing the added functional element) associated with the added functional elements (ex 9, 10) compared with the functional elements of the first software among the functional elements of the second software 2 software needs to be used for testing. If some of the functional elements of the second software are changed (ex. Sub 5 -> sub 11, see FIG. 1) or deleted (ex. Sub 7 deleted, see FIG. 1) The test case (s) associated with the functional elements affected by the functional elements also need to be used for the testing of the second software.

Accordingly, the test case management apparatus and method for software testing according to an exemplary embodiment of the present invention may include a technical idea for determining an optimal test case for the second software test.

Specifically, a test case management apparatus and method for software testing according to an embodiment of the present invention includes a test case corresponding to a functional element of a first software and a test case corresponding to a different functional element, Test cases defined by different values among the test cases corresponding to the same functional elements among the functional elements of the software and the functional elements of the second software can be detected and determined as the optimal test cases. This will be described in more detail below with reference to Figs. 2 to 7.

2 shows a test case management apparatus for software testing according to an embodiment of the present invention.

Referring to FIG. 2, a test case management apparatus 100 for software testing according to an exemplary embodiment of the present invention includes a case generation unit 110, a first detection unit 120, a second detection unit 130, (140).

The case generation unit 110 may generate a test case for testing the software. For example, the case generation unit 110 may detect a target of the functional elements of the software using a Simulink / Stateflow model and generate a test case for testing the detected target.

The case generation unit 110 may generate test cases for testing each of the first software and the second software. For example, the case generation unit 110 may generate a plurality of first test cases for testing functional elements of the first software and a plurality of second test cases for testing functional elements of the second software.

Each of the plurality of first test cases may include an input value of variables defined in the functional elements of the first software and each of the plurality of second test cases may include an input value of variables defined in the functional elements of the second software It may contain an input value. Here, the variable may be a variable related to the transition condition of the functional elements.

The first detection unit 120 can detect at least one third test case corresponding to the first detection condition. Here, the first detection condition may be defined as a condition for detecting a test case corresponding to functional elements of the first software and functional elements of the second software. For example, the first detection unit 120 compares the functional elements of the first software with the functional elements of the second software to compare at least one third test case corresponding to the first detection condition among the plurality of second test cases Can be detected.

The second detection unit 130 can detect at least one fourth test case corresponding to the second detection condition. Here, the second detection condition may be defined as a condition for detecting a test case defined by different values among the test cases corresponding to the same functional elements among the functional elements of the first software and the functional elements of the second software have. For example, the second detecting unit 130 compares a plurality of first test cases with a plurality of second test cases, and detects at least a first test case and a second test case corresponding to the second detection condition among the plurality of second test cases One fourth test case can be detected.

Also, the second detecting unit 130 may simulate the first software and the second software using a plurality of first test cases for testing the first software, and a plurality of second test cases for testing the second software Can be used to simulate the first software and the second software to detect the fourth test case based on the obtained coverage result. Here, the coverage result may be defined as pass / fail information obtained as a result of simulating software using a plurality of test cases, the test case corresponding to the path is a test case capable of testing software, The test case corresponding to the fail may be a test case in which the software can not be tested.

The determination unit 140 may determine the detected at least one third test case and the fourth test case as the optimum test case.

3 is a flowchart illustrating a test case management method for software testing according to an embodiment of the present invention. 4 is a diagram illustrating a plurality of first test cases for testing functional elements of a first software according to an embodiment of the present invention. 5 is a view for explaining a plurality of second test cases for testing functional elements of a second software according to an embodiment of the present invention. FIG. 6 and FIG. 7 illustrate a test case management method for software testing according to an embodiment of the present invention.

Referring to FIG. 3, a test case management method for software testing according to an exemplary embodiment of the present invention includes testing a plurality of first test cases for testing functional elements of a first software, (S110), and comparing the functional elements of the first software with the functional elements of the second software to generate at least one test case corresponding to the first one of the plurality of second test cases (S120), comparing the plurality of first test cases and the plurality of second test cases, and comparing the plurality of first test cases with the plurality of second test cases Detecting one fourth test case (S130), and detecting at least one third test case and a fourth test case And determining the optimal test case (S140).

Hereinafter, the above-described steps S110 to S140 will be described in more detail with reference to FIG. 2, FIG. 4 to FIG.

In step S110, the case generation unit 110 may generate test cases for testing the first software and the second software, respectively. For example, the case generation unit 110 may generate a plurality of first test cases for testing functional elements of the first software and a plurality of second test cases for testing functional elements of the second software.

Referring to FIG. 4, the case generation unit 110 may generate a plurality of first test cases for testing each of the functional elements (R1 to R9) of the first software. Each of the plurality of first test cases may include an input value of variables (ex. A and B) related to the transition condition of the functional elements of the first software, and as shown in Fig. 4, It can be defined as a set of values.

Referring to FIG. 5, the case generation unit 110 may generate a plurality of second test cases for testing each of the functional elements (R1 to R7, R10, and R11) of the second software. Each of the plurality of second test cases may include an input value of variables (ex. A and B) related to the transition condition of the functional elements of the second software, and as shown in Fig. 5, It can be defined as a set of values.

In step S120, the first detection unit 120 may detect at least one third test case corresponding to the first detection condition. Here, the first detection condition is defined as a condition for detecting a test case corresponding to the functional elements of the first software and the functional elements other than the functional elements of the second software (i.e., added or deleted functional elements) .

4 and 5, the first detection unit 120 includes function elements R8 and R9 deleted from two software and function elements added in the second software when compared with the function elements of the first software R10 and R11) can be detected as at least one third test case. Specifically, the test cases ({(0, 0), (1, 0), (1, 1), (1, 3)} related to R8 and test cases { 0, 0), (1, 0), (1, 0), (1, 0) (0, 0), (1, 0), (1, 2), (1, 0)} associated with R11 can be detected as the third test case . On the other hand, although not shown, the functional element R5 of the second software is the same as the functional element R5 of the first software but can be defined as a form in which the transition condition is changed. In this case, it is assumed that the functional element R5 does not correspond to the first detection condition do.

In step S130, the second detection unit 130 may detect at least one fourth test case corresponding to the second detection condition. Here, the second detection condition may be defined as a condition for detecting a test case defined by different values among the test cases corresponding to the same functional elements among the functional elements of the first software and the functional elements of the second software have.

Referring to FIGS. 4 and 5, the second detecting unit 130 detects a test case corresponding to the same functional element (R1 to R7) among the functional elements of the first software and the functional elements of the second software, (A test case corresponding to R6 and R7) defined by a value can be detected as a fourth test case.

4, the second detection unit 130 detects the test cases ({0, 0), (1, 0), (1, 1), (1, (1, 0), (1, 1), (1, 1), (1, 2), (1, 0) (1, 0), (1, 1), (1, 1), (1, 1), 1, 1), (1, 1), (1, 2)} and R7 associated with the test cases {(0, 0), (1, 0) (1, 0)}) can be detected as the fourth test case.

Also, the second detecting unit 130 may simulate the first software and the second software using a plurality of first test cases for testing the first software, and a plurality of second test cases for testing the second software Can be used to simulate the first software and the second software to detect the fourth test case based on the obtained coverage result.

For example, referring to FIG. 6, the second detecting unit 130 may detect the functional elements M1 of the first software and the functional elements of the second software (e.g., M2 can be simulated. As a result of the simulation, R6 and R7 among the functional elements M2 of the second software may not be covered by the plurality of first test cases. This may mean that R6 and R7 of the functional elements M2 of the second software may have been affected by changing the transition condition of the functional element R5 described above or deleting R8 and R9. Therefore, the second detection unit 130 can detect the test cases associated with the functional elements R6 and R7 of the first software with the fourth test case. 7, the second detecting unit 130 detects the functional elements M1 of the first software and the functional elements M2 of the second software using the plurality of second test cases for the second software, Can be simulated. As a result of the simulation, R6 and R7 among the functional elements M1 of the first software may not be covered by the plurality of second test cases. This may mean that R6 and R7 of the functional elements M1 of the first software may have been influenced by a transition condition change or addition of R10 and R11 of the functional element R5 described above. Accordingly, the second detecting unit 130 can detect the test cases associated with the functional elements R6 and R7 of the second software in the fourth test case.

In step S140, the determination unit 140 may determine the detected at least one third test case and the fourth test case as the optimum test case.

That is, the determination unit 140 determines the test cases ({0, 0), (1, 0), (1, 1), (1, 1) (1, 0), (1, 1), (1, 1), (1, 2), (1, 0)} related to R7) (1, 0), (1, 0), (1, 1), (1, 3)} associated with R8 and the test cases {(0, 0) 0), (1, 0), (1, 0)} associated with R6 among the functional elements of the second software, 1, 1), (1, 1), (1, 1), (1, 1) (1, 0), (1, 0), (1, 2)} associated with the test cases (1, 1), (1, 1), (1, 2) , (1, 0), (1, 2), (1, 0)} associated with R11 can be determined as the optimum test cases.

Therefore, according to the test case management apparatus and method for testing software according to an embodiment of the present invention, it is possible to test software by selectively using only a part of test cases rather than a test case for testing all functional elements, The efficiency can be improved and the software can be tested selectively using the test cases satisfying the first detection condition or the second detection condition, and the test reliability can be improved.

FIG. 8 illustrates a computing system for implementing a test case management method for software testing according to an embodiment of the present invention.

Referring to FIG. 8, a test case management method for software testing according to an embodiment of the present invention may be implemented through a computing system. The computing system 1000 includes at least one processor 1100, a memory 1300, a user interface input device 1400, a user interface output device 1500, a storage 1600, and / And a network interface 1700.

The processor 1100 may be a central processing unit (CPU) or a memory device 1300 and / or a semiconductor device that performs processing for instructions stored in the storage 1600. Memory 1300 and storage 1600 may include various types of volatile or non-volatile storage media. For example, the memory 1300 may include a ROM (Read Only Memory) and a RAM (Random Access Memory).

Thus, the steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by processor 1100, or in a combination of the two. The software module may reside in a storage medium (i.e., memory 1300 and / or storage 1600) such as a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, You may. An exemplary storage medium is coupled to the processor 1100, which can read information from, and write information to, the storage medium. Alternatively, the storage medium may be integral to the processor 1100. [ The processor and the storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside within the user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

The foregoing description is merely illustrative of the technical idea of the present invention and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention.

Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

100: Test case management device for software testing
110: Case generation unit
120: first detection unit
130:
140:
1000: Computing System
1100: Processor
1200: bus
1300: Memory
1310: ROM
1320: RAM
1400: User interface input device
1500: User interface output device
1600: Storage
1700: Network interface

Claims (12)

A case generation unit for generating a plurality of second test cases for testing functional elements of a plurality of first test cases and second software for testing functional elements of the first software;
A first detecting unit for comparing at least one third test case corresponding to a first detection condition among the plurality of second test cases by comparing the functional elements of the first software with the functional elements of the second software;
Comparing the plurality of first test cases and the plurality of second test cases to detect at least one fourth test case corresponding to a second detection condition among the plurality of first test cases and the plurality of second test cases A second detection unit for detecting the first detection signal; And
And a determination unit for determining the detected at least one third test case and the fourth test case as an optimal test case. The method according to claim 1,
Wherein the first detection condition is a condition for detecting a test case corresponding to the functional elements of the first software and the other functional elements among the functional elements of the second software. . The method according to claim 1,
The second detection condition is a condition for detecting a test case defined by different values among the test cases corresponding to the same functional elements among the functional elements of the first software and the functional elements of the second software A test case management device for software testing. The method according to claim 1,
Wherein the functional elements of the second software are generated by partially deleting the functional elements of the first software or adding other functional elements to the functional elements of the first software. The method according to claim 1,
Wherein each of the plurality of first test cases includes an input value of variables defined in the functional elements of the first software. The method according to claim 1,
Wherein each of the plurality of second test cases includes an input value of variables defined in the functional elements of the second software. Generating a plurality of second test cases for testing functional elements of a plurality of first test cases and second software for testing functional elements of the first software;
Detecting at least one third test case corresponding to a first detection condition among the plurality of second test cases by comparing the functional elements of the first software with the functional elements of the second software;
Comparing the plurality of first test cases and the plurality of second test cases to detect at least one fourth test case corresponding to a second detection condition among the plurality of first test cases and the plurality of second test cases ; And
And determining the detected at least one third test case and the fourth test case as the optimum test case. 8. The method of claim 7,
Wherein the first detection condition is a condition for detecting a test case corresponding to functional elements of the first software and functional elements of the second software among the functional elements of the second software . 8. The method of claim 7,
The second detection condition is a condition for detecting a test case defined by different values among the test cases corresponding to the same functional elements among the functional elements of the first software and the functional elements of the second software A test case management method for software testing. 8. The method of claim 7,
Wherein the functional elements of the second software are generated by deleting some of the functional elements of the first software or adding other functional elements to the functional elements of the first software. 8. The method of claim 7,
Wherein each of the plurality of first test cases includes an input value of variables defined in the functional elements of the first software. 8. The method of claim 7,
Wherein each of the plurality of second test cases includes an input value of variables defined in the functional elements of the second software.

Images