JPH04148346A - Test executing system for cause-result graph technique utilization - Google Patents

Abstract

PURPOSE:To hardly necessitate the labor of assisting a machine by a person, and to efficiently operate a test by providing a test item preparing means, test data preparing means, test executing means, and test evaluating means, which utilizes a cause-result graph. CONSTITUTION:This system is equipped with a test data preparing means 2 which prepares an input 14 for test and an output 15 for test as the test data based on the test item data and the graph data prepared by utilizing the cause- result graph technique. Also a test executing means 3 which executes the test of a system by using the prepared input 14 for test and a program 17 to be tested, and a test evaluating means 4 which evaluates an executed test result 18 from both the test result 18 and the output 15 for testing are provided. Thus, it is hardly necessary for the person to intervene, and the test can be efficiently operated.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a test execution method using cause-effect graph techniques.

[Conventional technology]

Conventionally, graph data in cause-effect graph technique is created and test items are automatically generated, but for subsequent tests, humans must think about, create, and prepare test data according to the test items. , partially automating tests. Also, during testing, humans judge the test results based on the test specifications and according to each condition.

[Problem to be solved by the invention]

In the conventional test execution method using the cause-effect graph technique described above, humans have to perform the testing process of system development manually from start to finish, especially in systems that involve screen input/output. The drawback is that it takes time to enter parameters each time, and the device must be attached to the device most of the time during testing.

[Means to solve the problem]

The test execution method using the cause-effect graph technique of the present invention uses test item data and graphs created using the cause-effect graph technique in testing a system that inputs data from a screen and outputs the results to an input/output device. A system test is executed using a test data creation means that creates a test input and a test output as test data based on the data, and a test input and a test program created by this test data creation means. It is configured by having a test execution means for obtaining a test result, and a test evaluation means for evaluating the test result from the test result executed by the test execution means and the test output.

〔Example〕

Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of the present invention, in which test item creation means 1. test data creation means 2. test data creation means 2. It is composed of a test execution means 3 and a test evaluation means 4. First, when a cause-effect graph is created manually, the test item creation means 1 using the cause-effect graph creates test items using a function for creating a decision table. This means 1 includes a function to define a cause-effect graph and create and save graph data 11, a function to automatically create a decision table from the created graph data 11 and save test item data 12, and a function to automatically create a decision table from the created graph data 11 and save test item data 12. It has a function of creating and outputting an inspection specification 13 based on the , and a function of defining relationships among a plurality of cause-effect graphs and associating test items of the entire system when creating a decision table.

The present invention uses graph data 11 and test item data 12 created by these functions.

The two files storing the created graph data 11 and test item data 12 are used to create test data in the test data creation means 2, and the data input from the screen during the test is finally stored in the test input file 14. The output results are stored in a test output file 15, and a test data list 16 is output. Next, the test execution means 3 performs a test using the test input file 14 and the program under test 17, and stores the results output from the test in the test result output file 18. Finally, the automatic test evaluation means 4 performs an evaluation by comparing the test output file 15 with the test result output file 18 and compiles them into a test result list 19 and an error list 20.

FIG. 2 is a flowchart showing the operation of the test data creation means 2. To proceed with the explanation of the operation of the test data creation means with reference to FIG. 2, first, the code is read from the test item data 12 (step ■). The next step is to create and output the divine input data for all the content information of the cause of the code. If the step is completed, create and output the output data (step @
). In step 0, the cause 1 is
After acquiring necessary information from the graph data 11 based on the content information, input item data for the test is created and output to the test input file 14. Step 0 is the same as step O, creating test output data based on the content information of the results and outputting it to the test output file 15. Next, the created test data is output to the test data list (
Step 0) 0 Next, determine whether processing has been completed for all test item data. If not, return to step @ to continue processing.

FIG. 3 is a flowchart showing the operation of the test execution means 3.

To explain the operation of the test execution means 3 with reference to FIG. 3, first, the test input file 14 is allocated to the screen input of the program under test, and the test result output file 18 is allocated to the result output ( Step 0) 0 Next, the following steps (h- et al. Step (Determine whether the processing in 9g has been performed for all test items (step @ to determine if there is an input request from the program), For example, test input file 1 according to the input request.
Read the test data from step 4 (step O), and determine whether a record with a different test number has been input due to an error in the program under test (step @). If it is a different test number, it is determined as an error and the If not, pass the program under test test data and return the process to step @.Step [Share] If there is no input request, determine whether there is an output request from the program under test ( Step @),
If there is no test, return to step @, and if there is, output the result to the test result output file 18 and return to step O) and step G.

FIG. 4 is a flowchart showing the operation of the test evaluation means 4.

The operation of the test evaluation means 4 will be explained with reference to FIG. 4. Records are read from the test output file 15 and the test result output file 18 (steps @, @). Next, it is determined whether the contents of the read records match (Step @), and if they match, the number of normal records is counted (Step O), and if they do not match, the resulting contents are added to the error list 20. (Step @) and count the number of errors (Step ◎). Step ◎ or Step FIG. 5 is a flowchart of the operation of creating and outputting input data of the step of the test data creating means 2.

First, extract the 1 cause item number in the test item data (
Step O). Next, the cause information indicated by the record number of the cause item extracted from step 岨(Stella 70), the screen input specifications obtained from the cause-effect graph include the attributes of the input items,
There are number of digits, input data range, etc., and information is classified and collected for each input item based on keywords (Step @). Therefore, we need to judge whether we have finished acquiring the specification information for the manual item (Step 0). If there is still information about the same item, go to Step 0; if not, analyze the data range (Stella X9>, data range In this analysis, the range of the actual input value is determined from the specification information about the input items obtained from Stellar Meeting, and the 9th specified attribute, which is necessary when creating the next test data, is determined.
Create data that satisfies the conditions for the number of digits, and perform step 6 of it.
Create test data that matches the grasped data range (Step Figure 6 shows the relationship between graph data and test item data. Figure 6 (a)
and (b) are format diagrams of records of graph data and test item data, respectively, where the result number and cause number in the test item data are stored numbers, and refer to the record numbers of the content information of causes and results in the graph data. It shows that there is. FIG. 7 is a record format diagram of a file used by the test data creation means and the test automatic execution means. In the test input file shown in FIG. 7(a), the single-manpower item data at the time of the test is expressed in code, and the data is distinguished by the test number, screen number, and input item number. If the data length is too large to fit within 256 bytes, it can be accommodated by adding a number to the record number. Figures 7(b) and (c)
) test output files and test result output files are distinguished by test number, and if the data length is large, they are matched by record number.

〔Effect of the invention〕

As explained above, the present invention creates test data based on test item data and graph data created using a cause-effect graph, executes a program under test using this test data, and obtains results. Since the test results are automatically evaluated using the test results generated and the test output created during test data creation, there is almost no need for a human to be present at the machine, and testing can be performed efficiently. effective.

[Brief explanation of drawings]

FIG. 1 is a block diagram of an embodiment of the present invention, FIG. 2 is a flowchart showing the operation of the test data creation means in FIG. 1, FIG. 3 is a flowchart showing the operation of the test execution means in FIG. 4 is a flowchart showing the operation of the test evaluation means in FIG. 1, FIG. 5 is a flowchart showing the operation of creating and outputting input data in the flowchart of the test data creation means in FIG. 2, and FIG. 6(a) and (b) is a format diagram of graph data and test item data, respectively, and FIGS. 7(a), (b), and (c) are format diagrams of files created by the test data creation means and test execution means. 1... Means for creating test items using a cause-effect graph, 2... Means for creating test data, 3.
...Test execution means, 4...Test evaluation means, 11...Graph data, 12...
・Test item data, 13...Inspection specifications, 1
4...Test input file, 15...
・Test output file, 16...Test data list, 18...Test result output file,
19...Test result list, 20.0. ...
error list.

Claims (1)

[Claims] In testing a system that inputs data from a screen and outputs results to an input/output device, test input and test output are created as test data based on test item data and graph data created using cause-effect graph techniques. a test data creation means for creating a system; a test execution means for executing a system test and obtaining a test result using the test input created by the test data creation means and the program under test; 1. A test execution method using a cause-effect graph technique, comprising a test evaluation means for evaluating a test result from the test result and the test output.