JP2014115884A - Test case generation system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a test case generation system which can generate test cases corresponding to all system configurations of a distributed control system which dynamically changes the system configuration.SOLUTION: An input/output wiring diagram 31 is described including processing, a device to be controlled, as input/output information thereof, and range information of a control device. System configuration information 35 indicates information on a relation between the control device and the device to be controlled, and the range information of the control device. Input-output data information 36 indicates a range of input/output values. A test case generation part 34 generates a test case on the basis of the information extracted from the input/output wiring diagram 31, the system configuration information 35, and the input-output data information 36.

Description

  The present invention relates to a test case generation system for describing test cases in a plurality of system configurations without omission in a distributed control system in which a plurality of control devices are connected via a network and the system configuration dynamically changes.

In a distributed control system in which a plurality of control devices are connected via a network and the system configuration dynamically changes, it is necessary to perform tests in various different test environments in the same function confirmation test of the same system.
In the conventional test case generation system, the source code to be tested is analyzed, and numerical values and variables used in assignment statements and conditional branch statements related to the output value of the module are extracted to obtain the range of input values. As a result, there are some which generate “input value” and “expected value (output value)” as a test case without waste (see, for example, Patent Document 1).
In addition, different test data for each test environment / condition is described as a variable in a common test case, and a test case corresponding to multiple test environments / conditions is generated by referring to a test data list prepared in advance. There is a system that performs this (for example, see Patent Document 2).

JP 2009-32133 A JP-A-7-93185

  However, in a distributed control system test in which multiple control devices are connected via a network and the system configuration changes depending on the test environment and conditions, it is necessary to perform tests of the same function with multiple system configurations. It is difficult to extract without leakage.

Such distributed control system software often manages system configuration parameters separately from modules to be tested, and is the same in a system that analyzes source code as described in Patent Document 1. Even for a program, it is difficult to extract a test case of a distributed control system whose input data acquisition range varies depending on the system configuration.
Further, Patent Document 2 describes that a variable part in a test case is described as a variable and creates a test case for each test condition in combination with a test data list, but not only the position of the monitoring control target device, In a distributed control system in which the number fluctuates, it is difficult to simply represent the fluctuation part as a variable.

  The present invention has been made to solve the above problems, and even in a distributed control system in which the system configuration changes dynamically, test cases corresponding to all system configurations can be created without omission. The purpose is to obtain a test case generation system that can be used.

  In the test case generation system according to the present invention, a plurality of control devices are communicatively connected, and each control device generates a test case related to the processing of the control device in the distributed control system that controls a specific control target device. This is a test case generation system that describes processing and input / output of processing, and indicates which control device corresponds to the input / output and which control device corresponds to the input / output Input / output analysis unit that extracts processing and input / output information as input / output relation information from the input / output wiring diagram described including the range information of the control device, and which control target device each control device controls System configuration information indicating the range information of the control device, input / output data information indicating the value range of input / output, system configuration information and input / output Based on the information, the control target device and the control device to be input / output corresponding to the process for generating the test case are specified, and the value of the input / output data is obtained from the input / output data information to enter the control device. A test case generation unit that generates a test case corresponding to the range of the output data is provided.

  In the test case generation system of the present invention, processing and processing input / output are described, and input / output corresponding to which control target device is input / output corresponding to which control device. I / O wiring diagram described including the range information of the control device to be shown, system control information indicating the range information of the control device, input / output, indicating which control target device each control device controls Since test cases are generated based on input / output data information indicating the range of values taken by the system, all systems, even distributed control systems where the system configuration changes dynamically Test cases corresponding to the configuration can be created without omission.

It is a block diagram which shows the distributed control system made into the test object of the test case generation system by Embodiment 1 of this invention. It is explanatory drawing which shows the structural example of the distributed control system used as the test object of the test case generation system by Embodiment 1 of this invention. It is a block diagram which shows the test case production | generation system by Embodiment 1 of this invention. It is explanatory drawing which shows the example of description of the input-output wiring diagram of the test case generation system by Embodiment 1 of this invention. It is a flowchart which shows operation | movement of the test case production | generation system by Embodiment 1 of this invention. It is explanatory drawing which shows the example of entry of the input-output wiring diagram of the test case generation system by Embodiment 1 of this invention. It is explanatory drawing which shows the example of a description of the composition pattern of the test case generation system by Embodiment 1 of this invention. It is explanatory drawing which shows the example of description of the arrangement | positioning information of the control object apparatus of the test case generation system by Embodiment 1 of this invention. It is explanatory drawing which shows the example of a description of the input-output data information of the test case generation system by Embodiment 1 of this invention. It is explanatory drawing which shows a part of test case produced | generated by the test case production | generation system by Embodiment 1 of this invention. It is a block diagram which shows the test case production | generation system by Embodiment 2 of this invention. It is a block diagram which shows the test case production | generation system by Embodiment 3 of this invention. It is a flowchart which shows operation | movement of the same process determination part of the test case generation system by Embodiment 3 of this invention. It is a block diagram which shows the test case production | generation system by Embodiment 4 of this invention. It is a block diagram which shows the other example of the test case production | generation system by Embodiment 4 of this invention.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing the configuration of a distributed control system to be tested by the test case generation system shown in the present invention. In FIG. 1, a distributed control system 1 includes a plurality of control devices 10-1 to 10-n connected via a control network 11, and the plurality of control devices 10-1 to 10-n communicate with each other through the control network 11. The control devices 10-1 to 10-n monitor and control the control target devices 13-1 to 13-m and 14-1 to 14-m via the input / output networks 12-1 to 12-n. In the present invention, a test case for testing software of the control devices 10-1 to 10-n constituting the distributed control system 1 is generated.

  FIG. 2 shows a system configuration example of the distributed control system 1 to be tested by the test case generation system shown in the present invention. Control devices 21 to 27 in FIG. 2 correspond to the control devices 10-1 to 10-n in FIG. In the present invention, the minimum unit of the system configuration that is not disconnected when the system is operating is referred to as “organization”. The system shown in FIG. 2 includes three patterns: a knitting 1a composed of the control devices 21 to 24, a knitting 1b composed of the control devices 25 to 27, and a knitting 1c configured by connecting the knitting 1a and the knitting 1b. Consists of.

  As described above, the present invention is directed to the distributed control system 1 in which the change pattern of the system configuration is known and finite. As a distributed control system 1 to which this embodiment can be applied, for example, there is a “train monitoring control system” that performs monitoring control of various devices mounted on a train. For trains, system configuration patterns (for example, 6-car trains, 4-car trains, etc.) that can be taken according to the travel route are determined in advance, and the system configuration patterns must be defined and managed in the train monitoring control system. Is possible. Since trains differ in the number and position of devices to be monitored and controlled (for example, devices mounted on trains such as motors, brakes, and air conditioners) depending on the system configuration pattern, a test case for a train monitoring and control system is conventionally created. In this case, it was difficult to create a test case without omission according to the system configuration.

  FIG. 3 is a block diagram showing the configuration of the test case generation system shown in Embodiment 1 of the present invention. As shown, the test case generation system includes an input / output wiring diagram 31, an input / output relationship analysis unit 32, input / output relationship information 33, a test case generation unit 34, system configuration information 35, input / output data information 36, and a test case 37. It has. The input / output wiring diagram 31 describes processing and input / output of processing, and the control indicating which input / output corresponds to which control target device and which control device corresponds to the input / output. It is described including the range information of the device. The input / output relationship analysis unit 32 analyzes the structure of the input / output wiring diagram 31, acquires the input / output connection relationship and the name and range of the input / output data, and stores the input / output relationship information 33. The test case generation unit 34 generates a test case 37 from the input / output relationship information 33, the predefined system configuration information 35, and the predefined input / output data information 36. The system configuration information 35 is information for managing the system configuration defined at the time of designing the distributed control system. As the system configuration information 35, knitting and combination patterns (referred to as knitting patterns) that the system can take, arrangement information indicating the number and positions of monitoring control target devices, and the like are managed. The input / output data information 36 is information for managing the name of input / output data of the module to be tested, the minimum value, maximum value, normal range, abnormal range, and the like of the data.

FIG. 4 shows a description example of the input / output wiring diagram 31. The input / output wiring diagram 31 includes inputs 41a and 41b, a process 42, and outputs 43a and 43b. The process 42 indicates a module to be tested by the test case generation system shown in the present invention, and only one is described on the input / output wiring diagram 31.
Inputs 41 a and 41 b indicate input data for the process 42, and one or more inputs are always described on one input / output wiring diagram 31. An input data name is described in the center of the boxes of the inputs 41a and 41b. As the input data name, the input / output data name defined in the input / output data information 36 in FIG. 3 is used. A data range 44 is described above the inputs 41a and 41b. The data range 44 is described by separating the monitoring control target device name and the range specifier by a comma. The monitoring control target device name describes the name of the monitoring control target device that is the data acquisition source / setting destination. In the range specifier, the range to acquire / set data is described with alphabetic symbols.

  The outputs 43a and 43b indicate output data for the processing 42, and one or more outputs are always described on one input / output wiring diagram 31. Similarly to the inputs 41a and 41b, the outputs 43a and 43b describe the output data name at the center of the box and the data range 44 at the top of the box.

  For example, in the case of a train monitoring control system, when data is acquired from the entire train including multiple trains or when data is set for the entire train, the range specifier is set to “T” and data is acquired from within the train If the data is set in the field, “F” is described in the range specifier, and “S” is described in the range specifier when only the data of the own node is acquired / set. When “motor, T” is described as the data range 44, it indicates that data is input / output only to a control device that monitors and controls the motor in the entire train. The number and position of the control devices that monitor and control the motor vary depending on the train configuration, but the input / output wiring diagram 31 describes the range of data without describing the train configuration directly. For example, the same input / output wiring diagram 31 can be used in all train configurations. Thus, in the input / output wiring diagram 31, the system configuration can be described abstractly, so that it can be used as a test case description method with a high degree of abstraction.

FIG. 5 is a flowchart describing the operation of the test case generator 34.
First, in step S1, a list of knitting patterns that the test target system can take is acquired from the system configuration information 35.
In the loop L1, the processes up to L1E are repeated for the number of knitting pattern patterns acquired in step S1. For example, when the system configuration list has two patterns of four-car configuration and six-car configuration, the processing from L1 to L1E is executed for each of the patterns of four cars and six cars.
In step S 2, the input / output data range information is acquired from the input / output relationship information 33, and the monitoring control target device arrangement information defined by the system configuration information 35 is acquired. A list of input / output data used in the test case is acquired by combining the range information (monitor control target device name and range specifier) of the input / output data and the placement information of the monitor control target device.
In step S3, the value range of each data in the input / output data list acquired in step S2 is acquired from the input / output data information 36. The value range here refers to the maximum value, minimum value, normal value range, and abnormal value range.

In the loop L2, a test case is created using the input / output data list acquired in step S2. In the loop L2, the processes of L2 to L2E are repeated until all combinations of test cases can be output.
In step S4, a test case relating to input data is generated from the input / output data list acquired in step S2. Specifically, based on the range acquired in step S3, a test case for substituting normal values or abnormal values into input data is generated. At the time of test case generation, a configuration may be adopted in which representative values are determined using “equivalence division method” and “boundary value analysis” used in a general black box test.
In step S5, a test case relating to output data is generated from the input / output data list acquired in step S2. In this embodiment, since there is no function for automatically calculating an expected value for output, a test case for collating output results is output with the expected value portion blank. At this time, the value range acquired by the input / output data information 36 may be output as a test case comment to assist in test case design.
Steps S4 and S5 are performed for all combinations of input data, and the steps from step S2 to step S5 are repeated for all the knitting patterns, so that test cases corresponding to all the knitting patterns are created without omission. Is possible.

  Hereinafter, a specific example when the present embodiment is applied to a train monitoring control system will be described. For example, "When the driver pushes the door opening switch placed on the vehicles at both ends of the train in the train, if all speedometers in the train are within 5 km / h, the door in the train is opened." A specific example of creating a test case for the “door open determination” function will be described.

  FIG. 6 shows an example of entry of the input / output wiring diagram 31 in this specific example. The door open determination process 63 has an input signal “door open switch pressed” 61, an input signal “speed” 62, and an output signal “door open command” 64. The input signal “door open switch pressed” 61 is information that can be acquired from the cab in the train, and stores information on whether or not the door open switch in the cab has been pressed. The input signal “speed” 62 is train speed information that can be acquired from a speedometer in the train. The output signal “door opening command” 64 is command information for opening the door in the train.

  FIG. 7 shows a description example of the composition pattern in this specific example. The knitting pattern indicates the system configuration 72 of the control device for each knitting pattern name 71 in a table format. In the example of FIG. 7, the four-car train is composed of the control devices 1 to 4, the three-car train is composed of the control devices 5 to 7, and the seven-car train is composed of the control devices 1 to 7.

  FIG. 8 shows a description example of the arrangement information of the control target device in this specific example. The arrangement information indicates the number of mounted control device numbers 81 for each control device number 82 in a table format.

  FIG. 9 shows a description example of input / output data information in this specific example. The input / output data information includes a data name 91, a byte offset 92 in the transmission packet, a data size 93, a normal data range 94, an abnormal data range 95, and the like.

A procedure for generating a test case from the input / output wiring diagram of FIG. 6 based on the information of FIGS. 7 to 9 will be described below with reference to the flowchart of FIG.
First, in step S1, a list of knitting patterns is acquired from the system configuration information 35 shown in FIG. Here, three patterns of four-car train, three-car train, and seven-car train are acquired.
Next, the processing of the loops L1 to L1E is performed for all the knitting patterns extracted in step S1. Hereinafter, the case of four-car train will be described.

  In step S2, first, from the input / output relation information 33 extracted from the input / output wiring diagram 31 shown in FIG. 6, "door open switch press" 61, "speed" 62, and "door open command" as output signals are input signals. 64 are extracted. Since it can be seen from the list information of the composition pattern of the system configuration information 35 shown in FIG. 7 that the four-car train is composed of the control devices 1 to 4, the system control information 35 shown in FIG. Obtain device placement information. For example, since the “door open switch pressed” signal is designated as “driver's cab, T” as the data range of the input / output wiring diagram 31, the control device 1 with one or more monitoring control target devices in the cab is It can be seen that it is sufficient to create a test case for setting the input signal “door open switch pressed” for the control device 4.

In step S3, a value range (normal range 94 and abnormal range 95) corresponding to the data name is acquired from the input / output data information 36 shown in FIG. For example, it can be seen from FIG. 9 that “door open switch pressed” is 1-bit data in which the normal range is “ON” and the abnormal range is “OFF”.
In loops L2 to L2E, test cases corresponding to all combinations of the value ranges acquired in step S3 are created for the list of input data acquired in step S2.
In step S4, with respect to the list of input data acquired in step S2, one unselected combination is selected from the value range acquired in step S3, and a test case is generated. For example, regarding the “door open switch pressed” signal, (1) the control device 1 is ON, the control device 4 is ON, (2) the control device 1 is ON, the control device 4 is OFF, and (3) the control device 1 is OFF. Four test cases are generated: the control device 4 is ON, (4) the control device 1 is OFF, and the control device 4 is OFF.
In step S5, a test case relating to the output signal “door opening command” is generated. In this embodiment, since there is no function for automatically calculating an expected value for output, a test case for collating output results with the expected value portion blank is output. The expected value is manually input by the test designer after generating the test case.

  FIG. 10 shows a part of the output test cases in this specific example. In this example, there are two test cases: the case where the door opens normally when the speed is 5 km / h or less and the door opens normally, and the case where the door is not opened when the speed is 6 km / h or higher and the door is opened. Is described. In the command 101, a command indicating an operation for actually executing the test is described. When setting a value for input data, a SET command is described. When checking the value of output data, a CHECK command is described. The control device number 102 indicates the control device number that is the target of the SET command and the CHECK command, and the data name 103 indicates the name of the input / output data that is the target of the SET command and the CHECK command. A value 104 indicates a set value for the input data and a collation value for the output data. The expected value of the output data is manually input after the test designer generates the test case. Note that a line beginning with # in FIG. 10 indicates a comment line.

  As described above, in the present embodiment, the test case generation unit 34 generates a test case from the input / output wiring diagram 31 that abstractly describes the system configuration and the system configuration information 35 that is managed in advance. In a distributed processing system where it is necessary to perform the above test with a plurality of system configurations, test cases can be extracted without omission. Further, since the input / output wiring diagram 31 describes the system configuration abstractly, it can be reused in different models having the same function.

  As described above, according to the test case generation system of the first embodiment, a control device in a distributed control system in which a plurality of control devices are communicatively connected and each control device controls a specific control target device. Is a test case generation system that generates a test case related to the process of the process, the process and the input / output of the process are described, the input / output corresponds to which control target device, and which control device corresponds An input / output analysis unit that extracts processing and input / output information as input / output relation information from an input / output wiring diagram including control device range information that indicates whether the input / output is the input / output, and individual control devices Indicates which control target device is to be controlled, system configuration information indicating range information of the control device, input / output data information indicating a value range of input / output, and system Based on the system configuration information and the input / output relation information, the control target device and control device that are the input / output corresponding to the process for generating the test case are specified, and the value of the input / output data is obtained from the input / output data information. Since the test case generation unit that generates test cases corresponding to the control device and the range of input / output data is provided, all system configurations can be used even in distributed control systems where the system configuration changes dynamically. Corresponding test cases can be created without omission.

Embodiment 2. FIG.
FIG. 11 is a block diagram showing the configuration of the test case generation system according to Embodiment 2 of the present invention. In the second embodiment, a test case extraction unit 111, a similarity determination unit 112, and a representative test case 113 are added to the configuration of the first embodiment shown in FIG. Since other configurations are the same as those of the first embodiment, the same reference numerals are given to corresponding portions, and the description thereof is omitted.
The similarity determination unit 112 calculates the similarity between devices from the system configuration information 35. The test case extraction unit 111 extracts a test case from the test case 37 using the similarity generated by the similarity determination unit 112 and stores it as a representative test case 113.

  In a distributed control system, the configurations of monitoring and control target devices are often similar, and in such a case, the same program is often executed in control devices having similar device configurations. For example, in a train monitoring and control system, the configuration of the monitoring and control target device is often similar depending on the vehicle type, such as a motor vehicle or a passenger car. In the present embodiment, test cases are extracted using the property that “the same control process is often performed in a control device having a similar configuration of the monitoring control target device” of the distributed control system.

  In the similarity determination unit 112, the similarity between the control devices is determined by the presence / absence and the number of the monitoring control target devices. The similarity is, for example, 1 point when the presence or absence of the monitoring control target device matches the log analysis target, and 2 points when the number matches, and is calculated by the sum of all the monitoring control target devices. It is determined that the control devices exceeding the threshold are similar. In the present embodiment, the control devices determined to be similar are handled as the same processing being executed.

  The test case excerpt unit 111 is a test case in which the same operation is performed on the control devices determined to be similar by the similarity determination unit 112 among the test cases 37 generated by the test case generation unit 34. One of these is extracted as a representative test case 113. Further, the test case extraction unit 111 extracts one of the test cases for confirming the same content as the representative test case 113 with respect to the control device determined to have a similar device configuration.

  A specific example in the second embodiment will be described with reference to FIGS. Now, from the monitoring control target device arrangement information shown in FIG. 8, the control device 1 and the control device 7, the control device 2 and the control device 6, and the control device 4 and the control device 5 have similar device configurations. Suppose that it is determined to be. At this time, when generating a test case for data common to a plurality of control devices with the same data name, such as the input “door open switch press” 61 and the output “door open command” 64 in FIG. One of the test cases for performing operations and confirmations on similar control devices is a representative test case. For example, in the test case in FIG. 10, a test case in which the “door open switch” command is turned on for only one control device is applied to the control device 1, the control device 4, the control device 5, and the control device 7 on which the cab is mounted. In this specific example, since the device configurations of the control device 1 and the control device 7 and the control device 4 and the control device 5 are determined to be similar, the control device 1 and the control device 4 are generated. Are extracted as representative test cases. As a result, the test cases can be reduced by 50%. Further, in the test for confirming “door open”, a test case for confirming all “door open” of the control devices 1 to 7 is generated. In this specific example, the control device 1 and the control device 7, and Since the device configurations of the control device 2 and the control device 6, and the control device 4 and the control device 5 are determined to be similar, the control device 1, the control device 2, and the control device 4 are selected as representative test cases. To do. As a result, the test cases can be reduced from the conventional 7 cases to 4 cases, and the test cases can be reduced by 43%.

  As described above, according to the test case generation system of the second embodiment, the similarity determination unit that determines the similarity of the control target device configuration between the control devices indicating the relationship between the control device and the control target device; A test case excerpt that extracts one of the test cases corresponding to the processing of the same content as a representative test case for a control device having a similar control target device configuration, and outputs the representative test case as a test case As a result, the number of test cases can be reduced without degrading test coverage, and the efficiency of test case creation can be improved.

Embodiment 3 FIG.
FIG. 12 is a block diagram showing the configuration of the test case generation system according to the third embodiment of the present invention, in which the same process determination unit 114 is added to the configuration of the second embodiment shown in FIG. The same process determination unit 114 determines whether or not the same processing is executed between the control devices determined to be similar by the similarity determination unit 112.
A detailed processing flow of the same processing determination unit 114 is shown in FIG. First, in step S11, the control target device name described in the data range information described above the input or output is acquired from the input / output wiring diagram 31 of the test target module. Next, the number of mounted control target devices acquired in step S11 is acquired from the system configuration information 35 for the control device determined to be similar by the similarity determination unit 112 in step S12. Finally, in step S13, if the number of control target devices acquired in step S12 matches, it is determined that the processes are the same, and if they do not match, it is determined that the processes are not the same.
With respect to inputs determined to be the same by the same process determination unit 114, the test case extraction unit 111 extracts one of the test cases performing the same operation as the representative test case 113.
In addition, regarding the outputs determined to be the same by the same process determination unit 114, the test case extraction unit 111 extracts one of the test cases for checking the same content as the representative test case 113.

  As described above, according to the test case generation system of the third embodiment, the input / output relationship of the process defined in the input / output wiring diagram with respect to the control device determined to be similar by the similarity determination unit. And the same processing determination unit that determines whether the control devices have the same input / output processing from the arrangement information of the control target devices defined in the system configuration information, and the test case excerpt unit has the same processing Since a representative test case is generated for a control device that is determined to be a test case, it is possible to prevent a test case from being mistakenly deleted when the test cases are reduced. The efficiency of creation can be improved and the accuracy of narrowing down test cases can be improved.

Embodiment 4 FIG.
FIG. 14 is a block diagram showing a configuration of a test case generation system according to Embodiment 4 of the present invention. In the fourth embodiment, an extract number storage unit 115 and a control device-specific extract number 116 are added to the configuration of the second embodiment shown in FIG. The extraction frequency storage unit 115 stores the extraction frequency for each control device number extracted as the representative test case as the extraction frequency 116 for each control device so that the test case is not biased to the operation or confirmation for only the same control device. .

When extracting the test case, the test case extraction unit 111 inquires the extraction number storage unit 115 about the extraction number of the control device to be extracted, and selects the test case for the control device with the smallest number of extractions. Take composition. Alternatively, in this case, the number of times extracted for each control device may be weighted.
This embodiment can also be configured as shown in FIG. 15 in combination with the third embodiment. That is, the extraction number storage unit 115 and the number of extractions 116 for each control device may be added to the configuration of the third embodiment. Since the operation in this case is the same as the above-described operation in the third embodiment, the description thereof is omitted here.

  As described above, according to the test case generation system of the fourth embodiment, the extraction number storage unit that stores the number of extractions for each control device extracted as a test case is provided, and the test case extraction unit is obtained from the test case. When extracting a representative test case, the test case for the control device with the fewest number of extractions was selected as the representative test case, so even when the number of test cases was reduced, a test case could be added to a specific control device. It is possible to create a uniform test case that does not concentrate.

  In the present invention, within the scope of the invention, any combination of the embodiments, or any modification of any component in each embodiment, or omission of any component in each embodiment is possible. .

  DESCRIPTION OF SYMBOLS 1 Distributed control system, 1a, 1b, 1c organization, 10-1 to 10-n, 21 to 27 control device, 11 control network, 12-1 to 12-n input / output network, 13-1 to 13-m, 14 -1 to 14-m Control target device, 31 I / O wiring diagram, 32 I / O relationship analysis unit, 33 I / O relationship information, 34 Test case generation unit, 35 System configuration information, 36 I / O data information, 37 Test case, 41a, 41b input, 42 processing, 43a, 43b output, 44 data range, 111 test case excerpt section, 112 similarity determination section, 113 representative test case, 114 identical process determination section, 115 excerpt count storage section, 116 control device The number of excerpts.

Claims (4)

A test case generation system in which a plurality of control devices are connected in communication, and each control device generates a test case related to processing of the control device in a distributed control system that controls a specific control target device,
Range information of the control device that describes the process and the input / output of the process, and that the input / output corresponds to which control target device, and which control device corresponds to the input / output An input / output analysis unit that extracts the processing and input / output information as input / output relation information from an input / output wiring diagram including
System control information indicating which control target device the individual control device controls, and range information of the control device;
Input / output data information indicating a value range of the input / output, and
Based on the system configuration information and the input / output relation information, a control target device and a control device that are input / output corresponding to a process for generating a test case are specified, and the value of the input / output data is set to the input / output data. A test case generation system including a test case generation unit that generates a test case corresponding to a range of the control device and the input / output data, acquired from information. A similarity determination unit that determines the similarity of the control target device configuration between the control devices indicating the relationship between the control device and the control target device;
A test case excerpt unit that extracts one of the test cases corresponding to the processing of the same content as a representative test case for a similar control device of the control target device configuration;
The test case generation system according to claim 1, wherein the representative test case is output as a test case. For control devices determined to be similar by the similarity determination unit, control is performed based on the input / output relationship of the process defined in the input / output wiring diagram and the arrangement information of the control target device defined in the system configuration information. Equipped with the same processing determination unit that determines whether devices have the same input / output processing,
The test case generation system according to claim 2, wherein the test case excerpt unit generates a representative test case for a control device determined to have the same processing. An extract number storage unit that stores the number of extracts for each control device extracted as a test case is provided.
The test case excerpt section extracts a test case for the control device with the smallest number of extractions as a representative test case when extracting the representative test case from the test case. Test case generation system.

Images