JP2002278795A - Method and device for supporting test for object oriented development - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently perform a test by a plurality of test cases with respect to a test object prepared by object oriented development. SOLUTION: This method is provided with a step of preparing test data including the plurality of test cases for a test target object and driver information for performing processing common to the plurality of test cases a step, of acquiring an input value and an expected value in each of the plurality of test cases in the test data, a step of acquiring test driver information from the test data, inputting the input value and the expected value to a test driver designated by the test driver information and performing a test in each test case, and of outputting test results.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to an object-oriented development test support method and apparatus for supporting a test of a test target object created by object-oriented program development.

[0002]

2. Description of the Related Art Conventionally, methods and apparatuses for automatically generating test items and automatically generating test drivers have been considered as techniques for supporting testing of objects created in object-oriented program development work. For example, there is one described in JP-A-5-34205. According to the technology described in this publication, it is considered that test items are automatically generated, evaluated, and a test program is automatically generated. By setting and combining, it is considered that an extraction condition and a conclusion are automatically generated and a test driver is generated.

[0003] Also, there is one disclosed in JP-A-11-154106. The technique described in this publication focuses on a combination of test items, and automatically generates test items based on a combination of test conditions including a program structure, a statement, an expression, and an element, and generates the generated test items. It is considered that a test driver according to the above is also automatically generated. In any case, it is considered that test data is automatically generated and a test driver is automatically generated from the test data.

[0004]

However, the technology described in Japanese Patent Application Laid-Open No. Hei 5-342054 discloses a data type,
By combining basic data attributes such as value range and length, test drivers generated by embedding test data and test data can be automatically generated, but test drivers are automatically generated for each test case There is a problem that must be done. Also, JP-A-11-154
The technology described in Japanese Patent Publication No. 106 is disclosed in Japanese Patent Application Publication No.
By combining test conditions from expressions and elements, data to be used in a test and a test driver generated by embedding test data can be automatically generated.
There is a problem that a test driver must be automatically generated for each case. That is, all of the prior arts have to automatically generate a test driver for each test case, and there is a problem that it is inefficient to set and test a plurality of test cases.

An object of the present invention is to provide a test support method and apparatus for object-oriented development that can efficiently execute tests using a plurality of test cases.

[0006]

In order to achieve the above object, a test support method for object-oriented development according to the present invention provides a plurality of test cases for an object to be tested and a driver for performing processing common to the plurality of test cases. Creating test data including information, acquiring input values and expected values for each of a plurality of test cases in the test data, acquiring test driver information from the test data, The method includes a step of inputting the input value and the expected value to a designated test driver, executing a test for each test case, and outputting a test result.

[0007] The test support apparatus for object-oriented development of the present invention comprises: means for creating test data including a plurality of test cases for a test target object and driver information for performing processing common to the plurality of test cases;
Means for obtaining input values and expected values for each of a plurality of test cases in the test data; obtaining test driver information from the test data; and providing the input values and expected values to a test driver specified by the test driver information. And means for executing a test for each test case, and means for outputting a test result. Further, it is characterized by further comprising means for managing a test driver in the test data and means for managing a test case in the test data. Further, it is characterized by further comprising means for displaying a test case and means for displaying a test status. In the present invention, by describing a common processing flow with a common driver for a plurality of test cases, one driver is used for a plurality of test cases, and an input value and an expected value for each test item are used. The object (or class) to be tested can be efficiently tested.

[0008]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of an object-oriented development test support apparatus to which the present invention is applied. The apparatus shown here comprises a tester 1300 for controlling a test and a tester 1300
Test data 1500, a test driver 1400 describing a test scenario, and test data 1500
Data management function 1700 that manages test data, test data display section 1800 that displays test data, tester 1
A test status display unit 1100 displays the progress of the test by 300, and a test result unit 1200 displays the test results. Test data 1500
Is the test driver name 151 that uses the test data.
0, initialization processing parameters 1520 used by the test driver 1400 in the initialization processing 1410, preprocessing parameters 1530 used by the test driver 1400 in the test scenario 1420, a plurality of test cases 1541, 1542, 1543 used by the test scenario 1420, Post-processing parameters 15 used by test scenario 1420
50, an end processing parameter 1560 used by the test driver 1400 in the end processing 1430. The test driver 1400 performs initialization processing 1410,
A test scenario 1420 and an end process 1430 are included. The test scenario 1420 includes a pre-process 1421, and a post-process 1422.

The tester 1300 receives test data 1500
Read and outline how to test the object (or class) under test. First, the tester 1300 acquires the test data 1500 (191).
0). Thereafter, the test driver name 1520 in the tester data 1500 is read, and the specified test driver 1
400 (1920). Although only one test driver is described in FIG. 1, there are as many test drivers as can be specified by the test driver name. Thereafter, the test driver 1400 sets the initialization processing parameter 1
520 is read, and initialization processing 1410 is performed (193).
0). The test scenario 1420 reads the preprocessing parameter 1530 and performs the preprocessing 1421 (19)
40). Further, the test scenario 1420 reads and tests one test case 1541 (195).
0). The test scenario 1420 has the post-processing parameter 15
50, and post-process 1422 is performed (196).
0). The tester 1300 displays the progress of the test on the test status display unit 1100 (1965). When the test using one test case 1541 is completed in this way, the test scenario processing (processing from 1940 to 1960) is similarly performed for the test cases 1542 and 1543 using the common test driver 1400. When the tests for all the test cases are completed, the end processing parameter 1560 is read and the end processing 1430 is performed (1970). Then, the test result is displayed on the test result display section 1200 (1980).

FIGS. 2 to 7 are diagrams showing a specific example of a case where a test is performed by a test data list including a plurality of test data including a plurality of test cases. FIG. 2 is a flowchart of the test method, and FIG. FIG. 4 is an apparatus configuration diagram shown in a class diagram expression, FIG. 5 is a flowchart of a test case test,
FIG. 6 is a diagram showing a specific example of the test status display screen, and FIG. 7 is a diagram showing a specific example of the test result screen. In FIG. 3, a concrete example of testing an instance 3201 which is the actual state of the subtraction class and an instance 3203 which is the actual state of the division class using a “four arithmetic operation_calculating driver” 3202 having an interface common to these instances, A specific example in which an instance 3205 which is the actual state of the square root class is tested using another “operation_calculation driver” 3204 is shown.

In FIG. 3, when a test is performed on the instance 3201 of the subtraction class, the instance 3201 of the subtraction class and the test case 3001 of the subtraction class are tested.
Subtraction test data 310 consisting of 3002 and 3003
1. “Four arithmetic operations_calculate” driver 32 used as a test driver for instance 3201 of subtraction class
Test using 02. When a test is performed on the instance 3203 of the division class, the instance 3203 of the division class and the instance 32
The test is performed using “division arithmetic operation_calculating driver” 3203 used as a test driver for division test data 3102 composed of test cases 3004, 3005, and 3006 of No. 03 and a division class instance 3203.
On the other hand, when testing the instance 3205 of the square root class, the instance 3205 of the square root class is tested.
And the square root test data 3103 composed of the test cases 3007 and 3008 of the instance 3205 of the square root class, and “operation_calculation driver” used as a test driver of the instance 3205 of the square root class.
Test using 3204.

FIG. 4 is a diagram showing, in a class diagram expression, a specific configuration when testing the instances of the subtraction class and the square root class shown in FIG. Here, a subtraction test data list 4000, “subtraction_calculated test data” 4001, an arithmetic class 4100 which is a class for processing addition, subtraction, multiplication and division and a root class of a square root class, and four rules which are parent classes of classes for processing addition, subtraction, multiplication and division, respectively A multiplication class 4111, a division class 4112, an addition class 4113, a subtraction class 4114, and a square root class 41, which are subclasses of the operation class 4101 and the four arithmetic classes 4101
15. Classes 4111 and 4 for processing addition, subtraction, multiplication and division, respectively
Four arithmetic operations Pool that reuses objects, avoiding generating 112, 4113, 4114, 4115 every time
Class 4200, “Four arithmetic operations_calculate_test driver” 4522, which tests using the interface of the four arithmetic operations class, and test data 4001, are read, and the test data can be quickly handled to “four arithmetic operations_calculate_test driver” 4522. A test driver 4521 that provides an interface and performs tests according to test cases;
Read “subtraction_calculated test data” 4001,
The tester 4410 includes a tester 4410 that performs tests by the number of test cases using the test driver 4522, displays a subtraction test status 4003, and returns a subtraction test result 4002.

A method of testing the subtraction class 4114 will now be described with reference to the flowchart of FIG. 2 for the specific examples of FIGS. First, the tester 4410 extracts one “subtraction_calculated test data” 4001 from the subtraction test data list 4000 (step 200).
1). Next, the test data 6020 under test is displayed on the test status display unit 1100 as the subtraction test status 4003 as shown in FIG. 6 (step 2110).

FIG. 6 shows an example of a subtraction test situation 4003. The subtraction test status 4003 includes a test data progress display bar 6010 indicating the number of test data in the test data list that has been completed, a test data name 6020 displaying the test data currently being tested, and a description of the test data. A test case progress bar 6030 indicating whether or not the test case has been completed, the number of test cases completed by the current test data test case 6070, the number of completed test cases 6070, the number of successful test cases 6040, the failure The number of test cases 6050 and the number of test cases 6060 where an exception has occurred.

Next, the tester 4410 reads the test driver name “four arithmetic operations_calculate_test driver” 4522 from the “subtraction_calculate test data” 4001 (step 2002). Next, the tester 4410 reads the initialization processing tag from the test data 4001, and reads the initialization data indicating that the number of pools is “10” (Step 2003). Next, tester 4410 sets test data 4
Read the end processing tag from 001 (Step 200)
4). Further, the tester 4410 has the test data 4001
The pre-processing tag is read from, the class name is subtracted, and the pre-processing data indicating that the pool usage is "true" is read (step 2005).

Next, the tester 4410 stores the test data 4
001, the post-processing tag is read, and the pool return
ue "(step 200).
6). Next, the subclass of the test driver, “four arithmetic operations_test test driver” 4522, uses the data with the pool number “10”, which is the initialization data, to assign an instance of the four arithmetic operation pool class 4200 to the pool number. It is generated with 10 pieces (step 2007). Next, the first test case 3001 is obtained from the test data 4001.
(FIG. 3) is taken out (step 2008). Then, the class name which is the pre-processing data is subtracted, and the pool usage is "tru
e "and the four arithmetic operation pool class 420
An instance 3201 of the subtraction class 4114 is obtained from the instance of 0 (step 2009). Next, the test case tag is read, and the input data whose base value is "10" and the comparison value is "5" and the output data whose calculation result is "5" are read (step 2010). Next, the test case is tested (step 2011).

The flow for testing a test case will be described with reference to FIG. First, the value “1” based on the instance 3201 of the subtraction class 4114 created in the preprocessing is used.
"0" is set (step 5020). Next, a value “5” to be compared with the instance 3201 of the subtraction class 4114 created in the preprocessing is set (step 5030). Next, the “calculate” method of the instance 3201 of the subtraction class 4114 created in the preprocessing is called, and the original value “10” is subtracted from the value “5” to be compared (step 5040). Next, the subtraction class 41 created in the preprocessing
The calculation result is obtained from the fourteen instances 3201 (step 5050). Then, as shown in FIG. 7, a test data name 7010, a test case number 7
020 is output (step 5055).

FIG. 7 shows a specific example of a test result. The test result 7000 displays the result of the test for each test case in three types: success, failure, and occurrence of an exception. The test result 7000 includes a test data name 7010 including the test case, a test case number 7020 indicating the number of the test case in the test data name, “success” when the test of the test case succeeds, and “failure” when the test of the test case fails. If an exception occurs during the test of the test case, “success, failure, exception” 7030 indicating “exception”, a test case displaying the input value of the test case, the expected result, and the test execution result when the test fails It consists of details 7040.

Next, the test driver 4521 compares the value "5" of the calculation result of the output data read from the test case tag with the calculation result obtained from the instance 3201 of the subtraction class 4114 (step 506).
0), if different from the result described in the test data,
"Fail" is output in the "success, failure, exception" column of the test result (step 5070). Next, the test case value and the test execution result are output to the test case details column of the test result (step 5073). Further, the number of failed test cases 6050 in the test status display section 1100 is set to “1”.
Increase (step 5075).

On the other hand, if the result is the same as the result described in the test data, "success" is output in the "success, failure, exception" column of the test result (step 5090). Next, the number of successful test cases 6040 in the test status display section 1100 is displayed.
Is increased by “1” (step 5095). If an exception occurs during the test of the test case and the test fails, “Exception” is displayed in the “success, failure, exception” column of the test result.
Is output (step 5080). Then, the number 60 of test cases in which an exception has occurred in the test status display section 1100 is displayed.
60 is increased by "1" (step 5085). Next, the number of completed test cases 6070 in the test status display section 1100
Is increased by “1” (step 5100).

Returning to FIG. 2, using the post-process data indicating that the pool return is "true", the pool return is "true".
Therefore, the instance 3201 of the subtraction class 4114 is returned to the instance of the four arithmetic operation Pool class 4200 (step 2012). Next, the number of test case completions 6030 on the test status display unit 1100 is displayed again (step 2130). Step 200 is also performed for the test cases 3002 and 3003 of the test data 4001.
9 to 2012 (step 201).
3). Finally, an end process is performed using the end process data (step 2014), and the test status display unit 1100 is performed.
Redisplays the number of completed test data (step 215)
0). The processing from step 2003 to 2014 is repeated until there is no more test data in the subtraction test data list 4000 (step 2015).

As described above, according to the present embodiment, (1) When testing classes that implement the same interface, one driver is provided, and test data corresponding to each class is described. Be able to test. (2) If a test driver is provided, it is not necessary to change the driver even if the test data is increased, and it becomes easy to retest. (3) When multiple child classes inherited from one parent class are created, one driver corresponding to the method of the parent class is created and a test is performed for each child class as long as the method of the parent class is used. Once you have the data, you can test it. (4) It is possible to test whether the created subclass operates according to the processing flow provided by the parent class. (5) The input / output data actually used by the test driver and the PCL can be synchronized. (6) Since a plurality of test cases use the same test driver, there is an effect of preventing a bug in the test driver.

[0023]

As is apparent from the above description, according to the present invention, a test using a plurality of test cases can be efficiently performed on a test object created by object-oriented development.

[Brief description of the drawings]

FIG. 1 is a configuration diagram showing an embodiment of an object-oriented test support device to which the present invention has been applied.

FIG. 2 is a flowchart illustrating a specific example of a test method.

FIG. 3 is a relationship diagram between test data and a test driver.

FIG. 4 is a diagram showing a specific example of an object-oriented test support device.

FIG. 5 is a flowchart showing a test procedure of a test case.

FIG. 6 is a diagram showing a display screen example of a test status.

FIG. 7 is a diagram showing a specific example of a test result display screen.

[Explanation of symbols]

1100: Test status display section, 1200: Test result display section, 1300: Tester, 1400: Test driver, 1500: Test data, 1510: Test driver name, 1520: Initialization processing parameter, 1530: Preprocessing parameter, 1541-1543 …test case,
1550: Post-processing parameters, 1560: End processing parameters, 1600: Test data list, 1700: Test data management function, 1800: Test data display unit.

Continued on the front page (72) Inventor Kenji Arai 6-81 Onoe-cho, Naka-ku, Yokohama-shi, Kanagawa Prefecture Hitachi Software Engineering Co., Ltd. In-house (72) Inventor Takashi Tamori 6-81-Oue-cho, Naka-ku, Yokohama-shi, Hitachi Software Engineering Co., Ltd. In-house F-term (reference) 5B042 GA08 HH12 HH17 MC00 5B076 DD04 EC05 EC10

Claims (4)

[Claims] An object-oriented development test support method for supporting a test of a test target object created by object-oriented program development, comprising: a plurality of test cases for a test target object; and a process common to the plurality of test cases. Generating test data including driver information for performing a test operation; obtaining input values and expected values for each of a plurality of test cases in the test data; obtaining test driver information from the test data; A test driver for inputting the input value and the expected value to a test driver specified by driver information, executing a test for each test case, and outputting a test result; How to help. 2. An object-oriented development test support apparatus for supporting a test of a test target object created by object-oriented program development, comprising: a plurality of test cases for a test target object; and a process common to the plurality of test cases. Means for generating test data including driver information for performing the test, means for obtaining input values and expected values for each of a plurality of test cases in the test data, and obtaining test driver information from the test data, A test for object-oriented development, comprising: means for inputting the input value and expected value to a test driver specified by driver information, executing a test for each test case, and outputting a test result. Support equipment. 3. The test support apparatus for object-oriented development according to claim 2, further comprising: means for managing a test driver in the test data; and means for managing a test case in the test data. . 4. The test support apparatus for object-oriented development according to claim 3, further comprising: means for displaying a test case; and means for displaying a test status.