JP6917753B2 - Test scenario generator, test scenario generation method, and test scenario generation program - Google Patents

Description

The present invention relates to a test scenario generator for generating test scenario data for testing a graphic screen in which a plurality of parts are arranged, a test scenario generation method, and a test scenario generation program.

A monitoring control system that monitors and controls a plurality of devices installed in a facility or facility displays a graphic screen in which a plurality of components including a symbol component whose mode changes depending on the state of the device to be monitored are arranged. Display on.

In the process of developing such a graphic screen, test scenario data is created in order to confirm whether or not the graphic screen is displayed according to the specifications, and a screen test, which is a test of the graphic screen, is performed according to the test scenario data. Similarly, when the specifications of the graphic screen are changed, a screen test is carried out in the same manner.

Patent Document 1 describes a method of comparing a correct image with an image at the time of a test in a screen test and automatically determining whether the test result is truly defective or defective due to a specification change. It is disclosed.

JP-A-2007-265263

However, in the conventional screen test, it is necessary to manually correct the test scenario data even if the specifications of the graphic screen are changed.

The present invention has been made in view of the above, and an object of the present invention is to obtain a test scenario generator capable of automatically generating test scenario data of a changed graphic screen.

In order to solve the above-mentioned problems and achieve the object, the test scenario generation device of the present invention includes a difference data generation unit, a test scenario generation unit, and a test scenario data editing unit . Differencing the data generation unit generates the difference data indicating the difference graphic screen before and after the change when the graphic screen in which a plurality of components are disposed is changed. Test scenario generation unit defines the difference component data generated by the difference amount data generating unit, on the basis of the default test scenario data of a preset part article, the graphic test contents of the screen after the change at the next Generate test scenario data. The test scenario data editing unit edits the test scenario data generated by the test scenario generation unit based on the input operation to the input device.

According to the present invention, there is an effect that the test scenario data of the changed graphic screen can be automatically generated.

The figure which shows the structural example of the test scenario generation apparatus which concerns on Embodiment 1. The figure for demonstrating the process of the test scenario generator which concerns on Embodiment 1. The figure which shows an example of the monitoring screen before the change which concerns on Embodiment 1. The figure which shows an example of the monitoring screen data before the change which concerns on Embodiment 1. The figure which shows an example of the monitoring screen after the change which concerns on Embodiment 1. The figure which shows an example of the monitoring screen data after the change which concerns on Embodiment 1. The figure which shows an example of the difference data which concerns on Embodiment 1. The figure which shows an example of the default test scenario data which concerns on Embodiment 1. The figure which shows an example of the standard test scenario data which concerns on Embodiment 1. The figure which shows an example of the whole test scenario data which concerns on Embodiment 1. The figure which shows another example of the whole test scenario data which concerns on Embodiment 1. The figure which shows an example of the partial test scenario data which concerns on Embodiment 1. A flowchart showing an example of processing of the processing unit according to the first embodiment. Flow chart showing an example of test scenario processing by the processing unit according to the first embodiment A flowchart showing another example of test scenario processing by the processing unit according to the first embodiment. The figure which shows an example of the hardware configuration of the test scenario generator which concerns on Embodiment 1. The figure which shows the structural example of the test scenario generation apparatus which concerns on Embodiment 2. The figure which shows an example of the standard test scenario data which concerns on Embodiment 2. The figure which shows an example of the difference data which concerns on Embodiment 2. The figure which shows an example of the default test scenario data which concerns on Embodiment 2. The figure which shows an example of the test scenario data of the monitoring screen after the change which concerns on Embodiment 2. A flowchart showing an example of processing of the processing unit according to the second embodiment. A flowchart showing another example of the processing of the processing unit according to the second embodiment. The figure which shows the structural example of the test scenario generation apparatus which concerns on Embodiment 3. The figure which shows an example of the test scenario edit screen which concerns on Embodiment 3. A flowchart showing an example of processing of the processing unit according to the third embodiment. A flowchart showing an example of the process of step S60 shown in FIG.

Hereinafter, the test scenario generation device, the test scenario generation method, and the test scenario generation program according to the embodiment of the present invention will be described in detail with reference to the drawings. The present invention is not limited to this embodiment.

Embodiment 1.
FIG. 1 is a diagram showing a configuration example of a test scenario generator according to the first embodiment of the present invention. The test scenario generation device 1 shown in FIG. 1 is a device that generates test scenario data for testing screen data used in a monitoring control system that monitors and controls the state of a facility or equipment. The facility or equipment to be monitored in the monitoring control system is, for example, a plant such as a water purification plant, a power plant, and a factory, and includes one or more monitored devices which are devices to be monitored.

The screen data used in the monitoring control system is the data of the monitoring screen displayed in the monitoring control system. Such a monitoring screen is a graphic screen on which a plurality of parts including a symbol component indicating a monitored device, a line component connecting the monitored devices, and a character string component are arranged. The data of the parts arranged on the monitoring screen includes the data of the parts image and the data of one or more attributes.

The part image data is line art data, and depending on the attribute data, the size of the line art, the color of the line art, the shape of the line art, the presence or absence of numerical values in the line art, the size of the characters in the line art, and the color of the characters in the line art. At least one of is defined.

The data of the component image may not be the data of the line drawing but may be the data including the data of a plurality of component images having different colors and shapes. That is, the data of the part image includes the size of the part image, the color of the part image, the shape of the part image, the presence / absence of a numerical value in the part image, the size of the character in the part image, and the color of the character in the part image. At least one of the data may be defined by the attribute data.

Each attribute data is attribute data indicating the behavior of the component. The behavior of the part shows how the part image behaves depending on the signal state of the monitored device, and the attribute data is monitored with at least one of the size, color, shape, and display value of the part image. It is the data associated with the state of each signal of the target device. The signal of the monitored device is an instrumentation signal from the monitored target or a control signal to the monitored target.

The test scenario generator 1 is data for performing an automatic test for automatically testing whether or not the attribute data included in the data of each component arranged on the monitoring screen is set according to the specifications, and is data on the monitoring screen. Includes data defining test content. Such test scenario data is generated by the test scenario generator 1.

The test scenario generation device 1 includes a processing unit 10 and a storage unit 20. The processing unit 10 includes a screen data acquisition unit 11, a difference data generation unit 12, and a test scenario generation unit 13. The storage unit 20 includes a screen data storage unit 21, a difference data storage unit 22, a default test scenario storage unit 23, and a test scenario storage unit 24.

Hereinafter, the processing in the test scenario generation device 1 according to the first embodiment will be described with reference to FIGS. 1 and 2. FIG. 2 is a diagram for explaining the process of the test scenario generation device 1 according to the first embodiment.

The screen data acquisition unit 11 shown in FIG. 1 acquires screen data input from the input device 40, and stores the acquired screen data in the screen data storage unit 21. The screen data acquisition unit 11 can acquire the updated screen data each time the screen data is updated, and can store the acquired screen data in the screen data storage unit 21.

The screen data includes component data which is data of each component arranged on the monitoring screen, and the component data is data in which the component image data and one or more attribute data are associated with each component type. Further, the screen data includes version information indicating a version number indicating an update history, and a new version number is assigned to the screen data each time the screen data is updated.

Here, it is assumed that the screen data storage unit 21 stores the latest screen data 3 and the screen data 4 of the previous version. In the following, the latest screen data 3 will be referred to as the screen data 3 after the change, and the screen data 4 of the previous version will be referred to as the screen data 4 before the change. The screen data of the previous version may be called the screen data of the previous generation.

As shown in FIG. 2, the difference data generation unit 12 acquires the screen data 3 after the change and the screen data 4 before the change, and generates the difference data 5 indicating the difference between the monitoring screens before and after the change. Here, the difference data 5 shows the data indicating the parts added from the monitoring screen before the change, the data indicating the deleted parts, and the attributes added from the monitoring screen before the change on the monitoring screen after the change. Includes at least one of data and data indicating deleted attributes.

As shown in FIG. 2, the test scenario generation unit 13 is based on the difference data 5 generated by the difference data generation unit 12 and the default test scenario data 6 of the parts stored in the default test scenario storage unit 23. Generate either test scenario data 8 or 9.

The test scenario data 8 and 9 are test scenario data for automatically performing the screen test. The test scenario data 8 includes data on the test contents of each component included in the changed monitoring screen. The test scenario data 9 includes data on the test contents of each component included in the difference between the screen data 4 before the change and the screen data 3 after the change.

With the test scenario data 8, it is possible to perform a screen test of the entire monitoring screen after the change. Further, the test scenario data 9 allows a screen test to be performed on the difference between the screen data 4 before the change and the screen data 3 after the change among the monitoring screens after the change. Hereinafter, in order to clarify the distinction between the test scenario data 8 and the test scenario data 9, the test scenario data 8 may be described as the overall test scenario data 8 and the test scenario data 9 may be described as the partial test scenario data 9.

The default test scenario data 6 includes the default data of the part which is the part data of the test scenario set in advance for each part, and the default data of each part includes the default data of the attribute which is the data of each attribute of the part. include.

The test scenario storage unit 24 stores the test scenario data 7 of the monitoring screen before the change. Hereinafter, the test scenario data 7 of the monitoring screen before the change will be referred to as the reference test scenario data 7.

First, the generation of the overall test scenario data 8 by the test scenario generation unit 13 will be described. When the difference data 5 generated by the difference data generation unit 12 includes a component or attribute to be deleted, the test scenario generation unit 13 reads the reference test scenario data 7 from the test scenario storage unit 24. Then, the test scenario generation unit 13 deletes the data of the component to be deleted or the data of the attribute from the read reference test scenario data 7, and generates the overall test scenario data 8.

Further, when the difference data 5 generated by the difference data generation unit 12 includes the parts or attributes to be added, the test scenario generation unit 13 defaults the default data of the parts to be added or the default data of the attributes to be added. Read from scenario data 6.

The test scenario generation unit 13 adds the default data of the read parts or the default data of the attributes to the reference test scenario data 7, and generates the overall test scenario data 8. The test scenario generation unit 13 stores the generated overall test scenario data 8 in the test scenario storage unit 24. By using the overall test scenario data 8 stored in the test scenario storage unit 24, it is possible to perform a screen test of the entire monitoring screen after the change.

Next, the generation of the partial test scenario data 9 by the test scenario generation unit 13 will be described. When the difference data 5 generated by the difference data generation unit 12 includes the parts or attributes to be added, the test scenario generation unit 13 starts with the default test scenario data 6 and defaults the default data of the parts to be added or the attributes of the addition target. Data is read from the default test scenario storage unit 23. The test scenario generation unit 13 uses the read default data as the test data of the component or attribute to be added. Hereinafter, the default data of the parts will be described as the default data of the parts, and the default data of the attributes will be described as the attribute default data.

Further, when the difference data 5 includes a part or attribute to be deleted, the test scenario generation unit 13 generates test data of the part or attribute to be deleted. The test data of the part or attribute to be deleted includes data that identifies the part or attribute to be deleted.

The test scenario generation unit 13 generates partial test scenario data 9 including at least one of the test data of the component or attribute to be added and the test data of the component or attribute to be deleted, and stores the partial test scenario data 9 in the test scenario storage unit 24. By using the partial test scenario data 9, a screen test can be performed on the difference before and after the change.

Hereinafter, the test scenario generation unit 13 will be described in more detail with reference to FIGS. 3 to 12. FIG. 3 is a diagram showing an example of the monitoring screen 8 ₁ before the change, and FIG. 4 is a diagram showing an example of the screen data 4 which is the data of the _{monitoring screen 81 1.} In the following, even if the parts are of the same type, numbers are added to the part types so that they can be distinguished.

First, a description will be given of the monitoring screen 8 ₁ before the change. The monitoring screen ₈₁ shown in FIG. 3, the parts 80a of the string button, and the part 80b of the solenoid valve, pump parts 80c, and 80e, numeric button 80d, and a 80f are disposed. Further, a wire component is arranged between the components 80b, 80c, and 80e. In the following, the parts 80a to 80f arranged on the monitoring screen and the parts 80g described later may be collectively referred to as the parts 80.

As shown in FIG. 4, the screen data 4 is a data of the monitoring screen ₈₁ before the change, the "component type", "coordinate position", and one or more "attributes" of the data associated with that.

The "part type" is data indicating the type of the part. The "coordinate position" is data indicating the coordinate position of the component 80. The "attribute" is attribute data which is data indicating each attribute of the component 80, and each "attribute" includes data in which the "state" and the "mode" are associated with each other.

The "state" is data indicating the state of the signal of the monitored device. The signal of the monitored device is a signal indicating whether the monitored device is in a normal state or an abnormal state, a signal indicating that the monitored device is in a serious failure state, and a signal indicating that the monitored device is in a minor failure state. It is a signal indicating or a signal indicating a numerical value.

The "mode" is at least one data of the size, color, shape of the component image, the presence / absence of a numerical value in the component image, the size of characters in the component image, and the color of the characters in the component image. As described above, the signal of the monitored device is an instrumentation signal or a control signal.

In the example shown in FIG. 4, the component type "automatic operation button" of the component 80a has the coordinate position "x1, y1", the state "normal state", and the attributes of the mode "character string" normal operation ", black". The attributes of the state "abnormal state" and the mode "character string" abnormal state ", red" are associated.

The attributes of the state "normal state" and the mode "character string" normal operation ", black" will include the black character string "normal operation" in the part image when the monitored device is in the normal state. Shows the behavior of the part image. In addition, the attributes of the state "abnormal state" and the mode "character string" abnormal state ", red" include the red character string "abnormal state" in the component image when the monitored device is in the abnormal state. Shows the behavior of the part image.

The "solenoid valve 1", which is the component type of the component 80b, includes the coordinate position "x2, y2", the attributes of the state "operating state" and the mode "green", and the attributes of the state "stop state" and the mode "red". Is associated with. The attributes of the state "operating state" and the mode "green" indicate the behavior of the part image in which the part image turns green when the monitored device is in the operating state. The attributes of the state "stop state" and the mode "red" indicate the behavior of the part image in which the part image turns red when the monitored device is in the stopped state.

The component type "pump 1" of the component 80c includes the coordinate position "x3, y2", the attributes of the state "operating state" and the mode "green", and the attributes of the state "stop state" and the mode "red". Is associated. The attribute of the part type "pump 1" is the same as the attribute of the part type "solenoid valve 1".

The "numerical value button 1", which is the component type of the component 80d, has the coordinate position "x3, y3", the attributes of the state "operating state" and the mode "numerical display, green", and the state "abnormal state" and the mode "numerical display". , Red ”attribute is associated.

For the attributes of the state "operating state" and the mode "numerical display, green", when the monitored device is in the operating state, the numerical value corresponding to the magnitude of the signal from the monitored device is displayed in green on the component image. Shows the behavior of the part image. For the attributes of the state "abnormal state" and the mode "numerical display, red", when the monitored device is in an abnormal state, the numerical value according to the magnitude of the signal from the monitored device is displayed in red on the component image. Shows the behavior of the part image.

Similar to the part type "pump 1", the part type "pump 2" of the part 80e is associated with the coordinate position and the attribute, and the part type "numerical value button 2" of the part 80f is also the part type "numerical value". Similar to "Button 1", coordinate positions and attributes are associated.

Next, a description will be given monitoring screen ₈₂ after the change. Figure 5 is a diagram showing an example of a monitoring screen _82, FIG. 6 is a diagram showing an example of screen data 3 is data of the monitoring screen ₈₂ shown in FIG.

_{In the monitoring screen 8 2} shown in FIG. 5, _{in addition to the monitoring screen 8 1} shown in FIG. 3, 80 g of the solenoid valve component is arranged, and the solenoid valve component 80 b is deleted from _{the monitoring screen 81 1.} Screen data 3 is data of such monitoring screen _82, as shown in FIG. 6, in addition to the screen data 4 shown in FIG. 4, further a component type of the component 80g and "electromagnetic valve 2", coordinate positions ""x4,y2", the attributes of the state "operating state" and the mode "green", and the attributes of the state "stopped state" and the mode "red" are associated. Further, in the screen data 3, the coordinate position and the attribute of the "solenoid valve 1" which is the component type of the component 80b are deleted from the screen data 4 shown in FIG.

Here, it is assumed that the screen data 3 and 4 are in the above-mentioned state. In this case, the difference data generation unit 12 generates the difference data 5 shown in FIG. 7. FIG. 7 is a diagram showing an example of the difference data 5. The difference data 5 shown in FIG. 7 is data including "part type", "coordinate position", "attribute state", and "change content". The "attribute state" is the same as the "state" of the screen data 4 shown in FIG. The "coordinate position" is data indicating the coordinates of the component. The "change content" is data indicating addition or data indicating deletion.

In the example shown in FIG. 7, in the difference data 5, the coordinate position "x2, y2" and the change content "delete" are associated with the part type "solenoid valve 1", and the coordinate position is associated with the part type "solenoid valve 2". "X4, y2" and the change content "addition" are associated with each other. Further, the attribute states "operating state" and "stop state" are associated with the component type "solenoid valve 2".

Therefore, the difference data 5 shown in FIG. 7 indicates that the component 80b having the coordinate position “x2, y2” and the component type “solenoid valve 1” has been deleted. Further, in the difference data 5 shown in FIG. 7, 80 g of the component of the component type “solenoid valve 2” is added to the coordinate positions “x4, y2”, and the attribute state “operating state” of the component 80 g of the component type “solenoid valve 2” is obtained. "And" stopped state "are added. The difference data 5 is data in a list format, but may be data in another format.

The test scenario generation unit 13 is based on the difference data 5 generated by the difference data generation unit 12 and the default test scenario data 6 stored in the default test scenario storage unit 23, and is based on the overall test scenario data 8 or the partial test scenario data. Generate 9.

FIG. 8 is a diagram showing an example of default test scenario data 6. As shown in FIG. 8, the default test scenario data 6 includes a plurality of component default data for each component type in which the component type data and the attribute test content data are associated with each other. The data of the attribute test contents is the above-mentioned attribute default data, and hereinafter, the data of the attribute test contents may be described as the attribute default data.

The "state" in the attribute default data is data indicating the state determined by the monitoring control system by the signal of the monitored device, and the "mode" in the attribute default data is the correct answer of the behavior of the component image corresponding to the "state". It is the data that defines.

In the example shown in FIG. 8, the default test scenario data 6 includes the component default data of the component type “automatic operation button”, the component type “solenoid valve”, the component type “pump”, and the component type “numerical button”. included.

The component default data of the component type "automatic operation button" includes the attribute default data indicating the status "normal state" and the mode "character string" normal operation "is black", and the status "abnormal state" and the mode ". Includes data associated with the attribute default data that indicates that the string is "red in abnormal state".

In addition, the component default data of the component type "solenoid valve" includes the attribute default data indicating the state "operating state" and the mode "green", and the state "stop state" and the mode "red". Contains attribute default data. Further, the component default data of the component type "solenoid valve" includes the attribute default data indicating the state "serious failure" and the mode "gray", and the state "minor failure" and the mode "orange". Included with attribute default data.

The state "operating state" indicates that the monitored device is in the operating state. The state "abnormal state" indicates that the monitored device is in an abnormal state. The state "serious failure" indicates that the monitored device is in a serious failure state. The state "minor failure" indicates that the monitored device is in a minor failure state.

In addition, the component default data of the component type "pump" includes the attribute default data indicating the state "started state" and the mode "green" and the attribute default indicating the states "stopped" and "red". Includes data and attribute default data indicating the state "opening" and the aspect "being a black number". Further, the component default data of the component type "pump" includes the attribute default data indicating the state "serious failure" and the mode "gray" and the attribute indicating the state "minor failure" and the mode "orange". Contains default data.

In addition, the component default data of the component type "numerical button" includes the attribute test contents of the status "operating status" and "green numerical display", and the status "abnormal status" and "red numerical display". ”Attribute test contents and are included. The above-mentioned states "operating state", state "abnormal state", state "opening", state "serious failure", and state "minor failure" are determined by the monitoring control system by the signal of the monitored device. Is.

As described above, the test scenario generation unit 13 can generate the overall test scenario data 8 and the partial test scenario data 9. First, an example of the generation process of the overall test scenario data 8 will be described.

The test scenario generation unit 13 extracts component default data or attribute default data from the default test scenario storage unit 23 based on the difference data 5. The test scenario generation unit 13 adds the extracted data to the reference test scenario data 7 read from the test scenario storage unit 24. Further, the test scenario generation unit 13 deletes component or attribute data from the reference test scenario data 7 based on the difference data 5.

FIG. 9 is a diagram showing an example of the reference test scenario data 7. As shown in FIG. 9, the reference test scenario data 7 includes a plurality of component test data for each component in which the coordinate positions of the components 80 and the attribute test contents are associated with each other.

Specifically, the reference test scenario data 7 includes the component test data of the components 80a to 80f, and each component test data includes data indicating the content of the attribute test. The attribute test content in the reference test scenario data 7 includes data indicating a state and a mode as in the attribute test content in the default test scenario data 6. The content of the attribute test is the attribute default data described above.

When the difference data 5 is in the state shown in FIG. 7, the test scenario generation unit 13 adds the change content indicated by the difference data 5 among the attribute default data included in the component default data of the component type “solenoid valve”. Is read from the test scenario storage unit 24. The data whose change content is "additional" is the attribute default data of the attribute including the state "operating state" and the attribute default data of the attribute including the state "stop state".

The test scenario generation unit 13 adds the data read from the test scenario storage unit 24 to the reference test scenario data 7, and the attribute data of the component type “solenoid valve 1” whose change content indicated by the difference data 5 is “deleted”. Is deleted from the reference test scenario data 7 to generate the overall test scenario data 8.

FIG. 10 is a diagram showing an example of the overall test scenario data 8. As shown in FIG. 10, the overall test scenario data 8 includes the part test data of the parts 80a, 80c to 80f in the reference test scenario data 7, the part test data of the part 80g, and the part test of the part 80b. The data has been deleted.

The component test data of the component 80g includes the data of the coordinate position "x4, y2", the data of the attribute test contents of the states "operating state" and "being green", and the states "abnormal state" and "red". Includes data on the attribute test content of "Koto".

The data of the coordinate position "x4, y2" is the data acquired from the screen data 3, and the data of the attribute test contents of the states "operating state" and "being green", and the states "stop state" and "red". The data of the attribute test content of "being" is the data acquired from the default test scenario data 6.

In this way, when the test scenario generation unit 13 includes data indicating the attributes to be added to the difference data 5, the test scenario generation unit 13 adds the attribute data to be added to the reference test scenario data 7 read from the test scenario storage unit 24. Further, when the difference data 5 includes the component 80 or the data indicating the attribute to be deleted, the test scenario generation unit 13 has the component data or attribute to be deleted from the reference test scenario data 7 read from the test scenario storage unit 24. Delete the data.

For example, it is assumed that the difference data 5 is data indicating the addition of attribute data including the state "serious failure" and the state "minor failure". In this case, the test scenario generation unit 13 adds data indicating the attribute test contents of the state "serious failure" and the mode "gray" to the reference test scenario data 7 read from the test scenario storage unit 24, and the state "light". Add data showing the content of the attribute test of "Failure" and "Being orange".

Based on the difference data 5 generated by the difference data generation unit 12, the test scenario generation unit 13 uses the data of the portion changed from the reference test scenario data 7 as the data of the portion not changed from the reference test scenario data 7. Can be included in the overall test scenario data 8 so as to be distinguishable from.

FIG. 11 is a diagram showing another example of the overall test scenario data 8. As shown in FIG. 11, the entire test scenario data 8 includes data indicating the changes from the monitor screen 8 ₁ before the change. In the example shown in FIG. 11, data indicating that the component 80b at the coordinate position “x2, y2” has been deleted and data indicating that the component 80g at the coordinate position “x4, y2” has been added are included.

Therefore, it is possible to distinguish between the data of the portion changed from the reference test scenario data 7 and the data of the portion not changed from the reference test scenario data 7 by the data indicating the changed contents included in the overall test scenario data 8. .. Then, the attribute test contents can be highlighted or marked by the data indicating the changed contents "addition" and "deletion" and displayed on a display device (not shown).

In this way, the test scenario generation unit 13 adds the component 80 or the attribute defined in the difference data 5 to the reference test scenario data 7 based on the difference data 5, the default test scenario data 6, and the reference test scenario data 7. Alternatively, the overall test scenario data 8 can be generated by deleting it.

Next, an example of the generation process of the partial test scenario data 9 will be described. Of the difference data 5 shown in FIG. 7 generated by the difference data generation unit 12, the test scenario generation unit 13 changes the change content to the part type “solenoid valve 1” whose change content is set to “delete”. Is generated as test data of the component 80 to be deleted.

Further, the test scenario generation unit 13 has the attribute state in the component type “solenoid valve 2” whose change content is set to “addition” among the difference data 5 shown in FIG. 7 generated by the difference data generation unit 12. Data in which the change content "addition" is associated with the "operating state" and the "stopped state" is generated as the test data of the component 80 to be added.

The test scenario generation unit 13 generates partial test scenario data 9 including test data of the component 80 or attribute to be added and test data of the component 80 or attribute to be deleted. FIG. 12 is a diagram showing an example of partial test scenario data 9.

The partial test scenario data 9 shown in FIG. 12 includes data associated with coordinate positions, attribute test contents, and changes. Specifically, the partial test scenario data 9 includes data in which the coordinate position “x2, y2” is associated with the change content “deletion”. Further, the partial test scenario data 9 has an attribute test content indicating the state "operating state" and the mode "green" at the coordinate position "x4, y2", and the state "stopped state" and the mode "red". Includes data associated with the attribute test content indicating "" and the changed content "addition" and "addition".

Based on the partial test scenario data 9, the screen test of the changed monitoring screen 8 _{2 can be performed for the difference between the monitoring screens 8 1} and 8 _{2 before and after the change.} That is, the screen test can be performed only on the changes from the monitoring screen 8 ₁ before the change of the monitoring screen 8 _{2 after the change.}

In the example described above, the test scenario data 8,9 is the data defining the test contents about the status of each attribute of the component included in the monitoring screen _82, the test scenario generation unit 13, for each attribute of the state It is also possible to generate the whole test scenario data 8 or the partial test scenario data 9 of the above.

Specifically, the test scenario generation unit 13 has the overall test scenario data 8 or a part for each of the attribute states "operating state", "stopped state", "serious failure", "minor failure", and "opening". Test scenario data 9 can be generated. This makes it possible to perform screen tests for each attribute state, and by performing screen tests for multiple parts at once for each attribute state, screen tests can be performed for each of the multiple attribute states for each part. The time required for the screen test can be shortened as compared with the case of performing the screen test.

Next, the processing of the processing unit 10 described above will be described with reference to the flowchart. FIG. 13 is a flowchart showing an example of the processing of the processing unit 10 according to the first embodiment, and the processing is repeatedly executed by the processing unit 10.

As shown in FIG. 13, the difference data generation unit 12 of the processing unit 10 acquires the screen data 4 before the change from the screen data storage unit 21 (step S11), and further, after the change from the screen data storage unit 21. Screen data 3 is acquired (step S12).

Then, the difference data generator 12, a difference between the screen data 3 after the change as the screen data 4 before change, i.e., generates difference data 5 indicating the difference of the monitoring screen _81, 82 before and after the change ( Step S13).

The test scenario generation unit 13 of the processing unit 10 acquires the reference test scenario data 7 from the test scenario storage unit 24 (step S14). Then, the test scenario generation unit 13 executes a test scenario generation process for generating test scenario data 8 and 9 on the changed monitoring screen based on the reference test scenario data 7 and the default test scenario data 6 (step S15). ).

FIG. 14 is a flowchart showing an example of the test scenario generation process of step S15 shown in FIG. The test scenario generation process shown in FIG. 14 is a process for generating the overall test scenario data 8.

As shown in FIG. 14, the test scenario generation unit 13 determines whether or not the difference data 5 includes data indicating a component or attribute to be added (step S21). When the test scenario generation unit 13 determines that the difference data 5 has data indicating the parts or attributes to be added (step S21: Yes), the parts to be added or the parts to be added from the default test scenario data 6 based on the difference data 5 The default data indicating the attribute is acquired as the default data to be added (step S22).

The test scenario generation unit 13 adds the default data of the addition target acquired in step S22 to the reference test scenario data 7 acquired in step S14 (step S23).

When the process of step S23 is completed, or when it is determined that the difference data 5 does not have data indicating the component or attribute to be added (step S21: No), the test scenario generation unit 13 deletes the difference data 5. It is determined whether or not there is data indicating the part or attribute of (step S24).

When the test scenario generation unit 13 determines that the difference data 5 contains data indicating the parts or attributes to be deleted (step S24: Yes), the reference for acquiring the data indicating the parts or attributes to be deleted in step S14. It is deleted from the test scenario data 7 (step S25).

When the process of step S25 is completed, or when it is determined that the difference data 5 does not have data indicating the component or attribute to be deleted (step S24: No), the test scenario generation unit 13 processes the steps S23 and S25. The changed data of the reference test scenario data 7 according to the above is stored in the test scenario storage unit 24 as the overall test scenario data 8 (step S26).

FIG. 15 is a flowchart showing another example of the test scenario generation process of step S15 shown in FIG. The test scenario generation process shown in FIG. 15 is a process for generating partial test scenario data 9.

As shown in FIG. 15, the test scenario generation unit 13 determines whether or not the difference data 5 includes data indicating a component or attribute to be added (step S31). When the test scenario generation unit 13 determines that the difference data 5 has data indicating the parts or attributes to be added (step S31: Yes), the parts to be added or the parts to be added from the default test scenario data 6 based on the difference data 5 The default data indicating the attribute is acquired, and the test data of the component or attribute to be added is generated (step S32).

When the process of step S32 is completed, or when it is determined that the difference data 5 does not have data indicating the component or attribute to be added (step S31: No), the test scenario generation unit 13 deletes the difference data 5. It is determined whether or not there is data indicating the part or attribute of (step S33).

When the test scenario generation unit 13 determines that the difference data 5 contains data indicating the parts or attributes to be deleted (step S33: Yes), the test scenario generation unit 13 generates test data of the parts or attributes to be deleted based on the difference data 5. (Step S34).

When the process of step S34 is completed, or when it is determined that the difference data 5 does not have data indicating the component or attribute to be deleted (step S33: No), the test scenario generation unit 13 is based on the generated test data. The partial test scenario data 9 is generated and stored in the test scenario storage unit 24 (step S35).

FIG. 16 is a diagram showing an example of the hardware configuration of the test scenario generation device 1 according to the first embodiment. As shown in FIG. 16, the test scenario generator 1 is a computer including a processor 101, a memory 102, an HDD 103, and an interface circuit 104. The processor 101, the memory 102, the HDD 103, and the interface circuit 104 can send and receive data to and from each other by the bus 105. The storage unit 20 is realized by the memory 102 and the HDD 103.

The processor 101 executes the functions of the screen data acquisition unit 11, the difference data generation unit 12, and the test scenario generation unit 13 by reading and executing the OS and the processing program stored in the HDD 103. The processor 101 transmits an OS and a processing program from one or more storage media of a magnetic disk, a USB (Universal Serial Bus) memory, an optical disk, a compact disk, and a DVD (Digital Versatile Disc) via an interface (not shown). It can also be stored in the read-out HDD 103 and executed.

The processor 101 is an example of a processing circuit, and includes one or more of a CPU, a DSP (Digital Signal Processer), and a system LSI (Large Scale Integration). The memory 102 is a storage area used as a work area of the processor 101, and is a non-volatile or volatile semiconductor memory represented by a RAM (Random Access Memory).

As described above, the test scenario generation device 1 according to the first embodiment includes a difference data generation unit 12 and a test scenario generation unit 13. The difference data generating unit 12 generates a differential data 5 indicating the difference of the monitoring screen _81, 82 before and after the change when the monitor screen 8 ₁ is a graphic screen in which a plurality of components 80 are disposed is changed. The test scenario generation unit 13 is a graphic screen after the change based on the difference data 5 generated by the difference data generation unit 12 and the default test scenario data 6 which is the default test scenario data of the preset component 80. generating a test scenario data 8,9 is a data of the monitoring screen ₈₂ of test scenarios is.

Therefore, it is possible to generate a test scenario data 8,9 Monitoring window ₈₂ is a graphic screen that has changed automatically, compared with the case of creating a test scenario data 8,9 manually, the operator on the screen test It is possible to reduce the trouble of. _{In addition, since test scenario data 8 and 9 are generated from the differences between the monitoring screens 8 1} and 8 ₂ before and after the change, omission of addition and deletion of attribute test items can be suppressed, and screen tests can be performed efficiently. be able to. Furthermore, since the test content can be added from the default test scenario data 6, the test scenario data 8 with improved completeness by using the default test scenario data 6 as the attribute test content that is frequently used, 9 can be created.

Further, the difference data generator 12, the difference data including the difference between the information showing a part of attributes included in the monitoring screen ₈₂ after the updates and indicating the attribute of a component included in the monitoring screen ₈₁ before the change Generated as data 5. Test scenario generation unit 13, a monitoring screen 8 _second test scenario after the change, to generate a test scenario data 8,9 to test the components of the attributes in the monitoring screen _82. Therefore, the test scenario data 8,9 can be tested attributes of there is a change in the monitor screen ₈₂ parts can be produced automatically.

Further, the difference data generator 12 generates data including the difference between the monitor screen 8 _second image after the change the monitoring screen ₈₁ of the image before change as differential data 5. Test scenario generation unit 13, a monitoring screen 8 _second test scenario data after the change, to generate a test scenario data 8,9 to test the image in the monitoring screen ₈₂ after the change. Therefore, it is possible to generate a test scenario data 8,9 can be tested component image and the background image that have changed in the monitor screen ₈₂ automatically.

Further, the test scenario generation unit 13 includes a difference data 5, based on the default test scenario data 6 is a default test scenario data of the parts, by modifying the test scenario data of the monitoring screen ₈₁ before the change, changes The test scenario data 8 of the subsequent monitoring screen 8 _{2 is generated.} Therefore, it is possible to generate a test scenario data 8 can perform the entire test of the monitoring screen ₈₂ after the change, to a screen test, including the relationship between the altered portion and the unmodified portion Can be done.

Test scenario generation unit 13, among the plurality of test data included in the monitoring screen 8 _second test scenario data after the change, the difference between the test data, monitoring screen ₈₂ after distinguishable change other than the test data difference Included in the test scenario data 8 of. Therefore, in the test scenario data 8, the changed portion from the reference test scenario data 7 can be easily grasped, and the influence range of the test scenario data 8 can be easily extracted. Therefore, it is possible to prevent omission of change in the test scenario, and it is possible to easily modify the test scenario.

Further, the test scenario generation unit 13 changes the test scenario data for the differences between the _{monitoring screens 8 1} and 8 ₂ before and after the change based on the difference data 5 and the default test scenario data 6, and _{displays the monitoring screen 8 2} after the change. Generated as test scenario data 9. Therefore, only the changed portion can be tested, the time required for the screen test can be reduced, and the efficient screen test can be performed.

Embodiment 2.
In the second embodiment, in addition to the difference data 5 is data indicating the difference between the monitor screen 8 _1, 8 ₂ attributes before and after the change, addition, data indicating the difference before changing the monitoring screen _81, 82 of the image It differs from the first embodiment in that test scenario data is generated based on the above. In the following, components having the same functions as those of the first embodiment will be designated by the same reference numerals and description thereof will be omitted, and the points added from the test scenario generation device 1 of the first embodiment will be mainly described.

FIG. 17 is a diagram showing a configuration example of the test scenario generation device 1A according to the second embodiment. The test scenario generation device 1A shown in FIG. 17 includes a screen data acquisition unit 11, a difference data generation unit 12A, and a test scenario generation unit 13A. Further, the storage unit 20A includes a screen data storage unit 21A, a difference data storage unit 22A, a default test scenario storage unit 23A, and a test scenario storage unit 24A.

The screen data 3 and 4 are stored in the screen data storage section 21A, the monitoring screen _81, in addition to the _{8 2} of the component data, including image data of the monitoring screen _{81, 82.} Image data of the monitoring screen _{81, 82} is, for example, data of a screen shot of the monitoring screen _{81, 82.} The difference data storage unit 22A can store the difference data 5A in addition to the difference data 5. The test scenario storage unit 24A can store the reference test scenario data 7A and the test scenario data 8A and 9A in addition to the reference test scenario data 7 and the test scenario data 8 and 9.

In the test scenario generation apparatus 1A according to the second embodiment, although the test scenario data 8,8A or test scenario data 9,9A is data monitoring screen 8 _second test scenario after the change, the test scenario generation device 1A , Only test scenario data 8A, 9A can be generated.

Reference test scenario data 7A is a data for testing the monitoring screen ₈₁ of the part image and the background image before the change, the reference test for test the attributes of each component included in the monitoring screen ₈₁ before the change This data is different from the scenario data 7.

FIG. 18 is a diagram showing an example of the reference test scenario data 7A. The reference test scenario data 7A shown in FIG. 18 includes data in which the coordinate position of the component image or background image is associated with the component image or background image. The reference test scenario data 7A includes data in which the coordinate position “x1, y1” is associated with the image “image A”, data in which the coordinate position “x2, y2” is associated with the image “image B”, and the coordinate position. Includes data associated with "x3, y2" and image "image C".

Further, the reference test scenario data 7A includes data in which the coordinate position "x3, y3" is associated with the image "image D", data in which the coordinate position "x3, y4" is associated with the image "image C", and data in which the coordinate position "x3, y4" is associated with the image "image C". Includes data associated with the coordinate position "x3, y5" and the image "image D".

The difference data generating unit 12A, in addition to the processing of the differential data generating section 12, further acquires the image data of the monitoring screen ₈₂ before the change before the change of the monitoring screen ₈₁ of the image data, before and after the change monitoring screen The difference data 5A showing the difference between the images of is generated. Here, the difference data 5A, in the monitoring screen ₈₂ after the change, before change and data of the added image from the monitor screen 8 _1, of the data of the deleted image from the monitor screen 8 ₁ before the change Includes at least one.

FIG. 19 is a diagram showing an example of the difference data 5A. The difference data 5A shown in FIG. 19 includes data including coordinate positions "x0 to xn, y0 to yn", image information "image information N", and change contents "addition", coordinate positions "x2, y2", and image information. Includes data including "image information B" and "deleted" changes. Further, the difference data 5A includes data including the coordinate position “x4, y2”, the image information “image information B”, and the change content “addition”.

The test scenario generation unit 13A is based on the difference data 5A generated by the difference data generation unit 12A and the default test scenario data 6A stored in the default test scenario storage unit 23A, and the image included in the default test scenario data 6A. Among them, an image that matches the image information included in the difference data 5A is determined.

FIG. 20 is a diagram showing an example of default test scenario data 6A. The default test scenario data 6A shown in FIG. 20 includes data indicating a type and data indicating an image. In the example shown in FIG. 20, the default test scenario data 6A includes data including the type "automatic operation button" and the image "image A", data including the type "electromagnetic valve" and the image "image B", and the type "pump". And the data including the image "Image C" and the data including the type "Numeric Button" and the image "Image D". Although not shown, the default test scenario data 6A includes data including the type "background image" and the image "image N".

When there is an image that matches the image information included in the difference data 5A, the test scenario generation unit 13A extracts an image that matches the image information included in the difference data 5A from the default test scenario data 6A. The test scenario generation unit 13A adds the image extracted from the default test scenario data 6A and the coordinate position of the difference data 5A to the reference test scenario data 7A read from the test scenario storage unit 24A.

Here, it is assumed that the image information B of the difference data 5A shown in FIG. 19 matches the image “image B” shown in FIG. In this case, the test scenario generation unit 13A acquires the image "image B" from the default test scenario data 6A, and the data of the image "image B" is the coordinate position "x4, y2" of the image information B included in the difference data 5A. Is added to the reference test scenario data 7A read from the test scenario storage unit 24A.

Further, when the difference data 5A includes a background image, the test scenario generation unit 13A can add the background image included in the difference data 5A to the reference test scenario data 7A read from the test scenario storage unit 24A. For example, the image information A of the difference data 5A shown in FIG. 19 is a background image, and the test scenario generation unit 13A uses the data including the image information N and the coordinate positions “x0 to xn, y0 to yn” as a reference test. It can be added to the scenario data 7A.

Thus, the test scenario generation unit 13A, a reference to the image contained in the difference between the monitor screen 8 ₂ of the image data after the change before the change of the monitoring screen ₈₁ of the image data, read from the test scenario storage unit 24A The test scenario data 8A can be generated by adding to the test scenario data 7A or deleting it from the reference test scenario data 7A. The test scenario data 8A is test scenario data for performing a screen test of the entire monitoring screen after the change.

Figure 21 is a diagram showing an example of a monitoring screen 8 _second test scenario data 8A after the change. The test scenario data 8A shown in FIG. 21 includes data in which the coordinate positions “x0 to xn, y0 to yn” and the image “image N” are associated with each other, and the coordinate position “ The data in which "x4, y2" and the image "image B" are associated with each other are included. The image "image N" is the same as the image information "image information N". Further, in the test scenario data 8A, the data associated with the coordinate position "x2, y2" and the image "image B" is deleted from the test scenario data 7A.

In the example described above, the test scenario data 8A is not data included showing changes from the monitor screen 8 ₁ before the change, not limited to this example. Test scenario generation unit 13A, like the entire test scenario data 8 shown in FIG. 11, it is possible to include data indicating the changes from the monitor screen 8 ₁ before the change to the test scenario data 8A.

Further, the test scenario generation unit 13A performs a screen test on the difference between the screen data 4 before the change and the screen data 3 after the change among the monitoring screens after the change, similarly to the partial test scenario data 9 shown in FIG. Test scenario data 9A can be created. Again, the test scenario generation unit 13A, similarly to the partial test scenario data 9 shown in FIG. 12, it is possible to include data indicating the changes from the monitor screen 8 ₁ before the change.

Next, the processing of the processing unit 10A described above will be described with reference to the flowchart. FIG. 22 is a flowchart showing an example of the processing of the processing unit 10A according to the second embodiment, and is a flow chart before the processing of step S21 shown in FIG. 14 or between the processing of step S25 and the processing of step S26. It is a process to be done. The test scenario generation process shown in FIG. 22 is a process for generating the overall test scenario data 8A. The processing of the processing unit 10A according to the second embodiment includes the same processing as the processing of the processing unit 10 except for the processing of steps S13 and S14 shown in FIG.

Test scenario generation unit 13A in the process of step S13 shown in FIG. 13, in addition to the difference data 5, and generates the difference data 5A showing the difference of the monitoring screen _81, 82 of the image before and after the change. Further, in the process of step S14 shown in FIG. 13, the test scenario generation unit 13A acquires the reference test scenario data 7A in addition to the reference test scenario data 7 from the test scenario storage unit 24A.

As shown in FIG. 22, the test scenario generation unit 13A determines whether or not the difference data 5A has data indicating an image to be added (step S41). When the test scenario generation unit 13A determines that the difference data 5A has data indicating the image to be added (step S41: Yes), the test scenario generation unit 13A performs a default test on the data of the image matching the image to be added based on the difference data 5A. Obtained from scenario data 6A (step S42).

The test scenario generation unit 13A adds the image data acquired in step S42 to the reference test scenario data 7A acquired in step S14 (step S43).

When the process of step S43 is completed, or when the test scenario generation unit 13A determines that there is no data indicating the image to be added in the difference data 5A (step S41: No), the image to be deleted in the difference data 5A. It is determined whether or not there is data indicating (step S44). When the test scenario generation unit 13A determines that the difference data 5A contains data indicating the image to be deleted (step S44: Yes), the test scenario generation unit 13A deletes the image to be deleted from the reference test scenario data 7A acquired in step S14. (Step S45).

When the test scenario generation unit 13A has completed the process of step S45, or has determined that there is no data indicating the image to be deleted in the difference data 5A (step S44: No), the reference by the process of steps S43 and S45. The changed data of the test scenario data 7A is stored in the test scenario storage unit 24 as the overall test scenario data 8A (step S46).

FIG. 23 is a flowchart showing another example of the processing of the processing unit 10A according to the second embodiment, before the processing of step S21 shown in FIG. 14 or between the processing of step S25 and the processing of step S26. It is a process performed in. The test scenario generation process shown in FIG. 23 is a process for generating partial test scenario data 9A. In the process of generating the partial test scenario data 9, the process of step S14 shown in FIG. 13 is not performed.

As shown in FIG. 23, the test scenario generation unit 13A determines whether or not the difference data 5A includes data indicating an image to be added (step S51). When the test scenario generation unit 13A determines that the difference data 5A has data indicating the image to be added (step S51: Yes), the default test scenario data 6A matches the image to be added based on the difference data 5A. The default data of the image is acquired, and the test data of the image to be added is generated (step S52).

When the process of step S52 is completed, or when the test scenario generation unit 13A determines that the difference data 5A does not have data indicating the image to be added (step S51: No), the difference data 5A contains the image to be deleted. It is determined whether or not there is data indicating (step S53).

When the test scenario generation unit 13A determines that the difference data 5A has data indicating the image to be deleted (step S53: Yes), the test scenario generation unit 13A generates test data of the image to be deleted based on the difference data 5A (step S54). ).

When the process of step S54 is completed, or when it is determined that there is no data indicating the image to be deleted in the difference data 5A (step S53: No), the test scenario generation unit 13A at least one of steps S52 and S54. Partial test scenario data 9A is generated based on the test data generated in the above process, and is stored in the test scenario storage unit 24A (step S55).

When the difference data 5 contains data indicating the component to be added, the test scenario generation unit 13A acquires the data of the component type associated with the coordinate position of the component to be added from the screen data 3, and the acquired component. A part image associated with a part type that matches the type data can be obtained from the default test scenario data 6A. The test scenario generation unit 13A can add the acquired component image data to the reference test scenario data 7A acquired from the test scenario storage unit 24A. As a result, the test scenario data 8A can be generated with priority given to the difference data 5 over the difference data 5A.

For example, the coordinate position of the component to be added included in the difference data 5 is "x3, y4", and the component type associated with the coordinate position "x3, y4" in the screen data 3 is "pump 2". And. In this case, the test scenario generation unit 13A adds the part image "image C" associated with the part type "pump" in the default test scenario data 6 to the reference test scenario data 7A acquired from the test scenario storage unit 24A. Can be done. As a result, the test scenario data 8A can be generated without using the difference data 5A.

Further, when the difference data 5A contains data indicating the image to be added, the test scenario generation unit 13A acquires the data of the part type associated with the coordinate position of the image to be added from the screen data 3, and the acquired parts. The attribute test content associated with the part type that matches the type data can be obtained from the default test scenario data 6. The test scenario generation unit 13A can add the acquired attribute test content data to the reference test scenario data 7. As a result, the test scenario data 8 can be generated with priority given to the difference data 5A over the difference data 5.

For example, the coordinate position of the image to be added included in the difference data 5A is "x3, y4", and the component type associated with the coordinate position "x3, y4" in the screen data 3 is "pump 2". And. In this case, the test scenario generation unit 13A can add the attribute test content associated with the component type “pump” in the default test scenario data 6 to the reference test scenario data 7. As a result, the test scenario data 8 can be generated without using the difference data 5.

The hardware configuration example of the test scenario generation device 1A according to the second embodiment is the same as the test scenario generation device 1 shown in FIG. The processor 101 can execute the functions of the screen data acquisition unit 11, the difference data generation unit 12A, and the test scenario generation unit 13A by reading and executing the program stored in the memory 102 that functions as the storage unit 20A. can.

As described above, the test scenario generation device 1A according to the second embodiment includes a difference data generation unit 12A and a test scenario generation unit 13A. The difference data generation unit 12A is a difference data 5, showing the difference between _{the monitoring screens 8 1} and 8 ₂ before and after the change when the _{monitoring screens 8 1} and 8 ₂ which are graphic screens in which a plurality of parts 80 are arranged are changed. Generate 5A. The test scenario generation unit 13A is modified based on the difference data 5 and 5A generated by the difference data generation unit 12A and the default test scenario data 6 and 6A which are the default test scenario data of the preset component 80. after the graphic screen is a monitor screen _{81, 82} is the data of the _second test scenario test scenario data 8, 8A, to produce a 9, 9A.

Therefore, it is possible to generate a test scenario data 8,9 Monitoring window ₈₂ is a graphic screen that has changed automatically, compared with the case of creating test scenario data 8, 8A, a 9,9A manually screen It is possible to reduce the labor of the operator in the test. Also, the monitoring screen _81, 82 of the difference from the test scenario data 8,8A before and after the change, since it generates a 9, 9A, it is possible to suppress leakage of adding and deleting attributes test items, efficiently You can do a screen test. Furthermore, since the test contents can be added from the default test scenario data 6 and 6A, the test with improved completeness by using the default test scenario data 6 and 6A as the attribute test contents that are frequently used. It is possible to create scenario data 8, 8A, 9, 9A.

Further, the difference data generating unit 12A generates data including the difference between the monitor screen 8 _second image after the change the monitoring screen ₈₁ of the image before the change as the difference data 5A. Test scenario generation unit 13A, the test scenario data 8A, as 9A, to generate data defining a test contents of the image in the monitoring screen ₈₂ after the change. Thus, the test scenario data 8A which can be tested images that have changed in the monitor screen _82, it is possible to generate 9A automatically.

Embodiment 3.
In the third embodiment, in addition to the processing of the first and second embodiments, further, the editing process for generating screen data 3 by editing the screen data 3 _1, and the test scenario data 8, 8A, on the basis of the 9,9A It differs from the first and second embodiments in that an automatic test process for performing a screen test of the screen data 3 is added. The test scenario generation device according to the third embodiment is a data processing device that performs an editing process, a test scenario editing process, and an automatic test process.

In the following, components having the same functions as those of the second embodiment will be designated by the same reference numerals and description thereof will be omitted, and the points added from the test scenario generation device 1 of the second embodiment will be mainly described. , It can also be applied to the test scenario generator 1 of the first embodiment.

FIG. 24 is a diagram showing a configuration example of the test scenario generation device 1B according to the third embodiment. The test scenario generation device 1B shown in FIG. 24 includes a difference data generation unit 12A, a test scenario generation unit 13A, a display processing unit 14, a screen editing unit 15, and a screen test processing unit 16. Further, the storage unit 20A includes a screen data storage unit 21A, a difference data storage unit 22A, a default test scenario storage unit 23A, and a test scenario storage unit 24A.

The display processing unit 14, based on the screen data 3,4 stored in the screen data storage section 21A, an image can be displayed in the monitor screen 8 _1, 8 ₂ on the display device 50. _{A worker who creates a monitoring screen edits the monitoring screen 8 1} by inputting to the input device 40 while the image of the _{monitoring screen 8 1} is displayed on the display device 50, and displays the monitoring screen 8 ₂ . Can be created. Screen editing unit 15 based on the input operation of the input device 40, and stores the generated screen data storing unit 21A screen data 3 is data of the monitoring screen _82.

Further, the display processing unit 14 can make the display device 50 editably display the contents of the test scenario data 8, 8A, 9, 9A based on the input operation to the input device 40. FIG. 25 is a diagram showing an example of a test scenario editing screen. The test scenario editing screen 60 shown in FIG. 25 includes information indicating the coordinate positions of the parts, information indicating the state of the attribute test contents, information indicating the mode of the attribute test contents, and information indicating the changed contents.

Information indicating the change is information indicating the difference of the monitoring screen _81, 82 before and after the change, in the example shown in FIG. 25 including the characters and the character of "addition" of "Delete". Specifically, a character string indicating "delete" is associated with the state "operating state" and the state "stop state" in the component at the coordinate position "x2, y2", and the component at the coordinate position "x4, y2". A character string indicating "addition" is associated with the state "operating state" and the state "stopped state" in. Thus, the operator can easily grasp the difference between the monitor screen 8 _1, 8 _2.

In the test scenario editing screen 60 shown in FIG. 25, the information indicating the changed content is displayed separately from the information indicating the attribute test content, but the information indicating the attribute test content is highlighted or marked. Can also represent changes.

Further, on the test scenario editing screen 60 shown in FIG. 25, information indicating the state of the attribute test contents is displayed so as to be changeable in the input frames 61a to 61n. The processing unit 10B functions as a test scenario data editing unit, changes the information indicating the state of the attribute test contents in the test scenario data 8 based on the input operation to the input device 40, and stores it in the test scenario storage unit 24A. be able to.

Therefore, when the test scenario data 8 generated by the test scenario generation unit 13A has attribute test contents that need to be corrected, the operator can correct the test scenario data 8 by inputting to the input device 40. can. In the example shown in FIG. 25, the input frames 61a to 61n are displayed so that the information indicating the state of the attribute test contents can be changed. However, other information may be displayed in the input frame so that the information can be changed. You can also display a button to add information about.

Further, in the example shown in FIG. 25, the test scenario editing screen 60 for the test scenario data 8 is shown, but the display processing unit 14 also edits the test scenario editing screen for the test scenario data 8A, 9, and 9A. It can be displayed on the display device 50 in the same manner as the screen 60. The processing unit 10B functions as a test scenario data editing unit, changes information indicating the state of the attribute test contents in the test scenario data 8A, 9, and 9A based on the input operation to the input device 40, and changes the information indicating the state of the attribute test contents, and the test scenario storage unit. It can be stored in 24A.

The test scenario generation unit 13A can generate test scenario data 8, 8A, 9, 9A each time the screen data 3 is generated by the screen editing unit 15 based on the input operation to the input device 40. The screen test processing unit 16 performs a screen test of the screen data 3 based on the test scenario data 8, 8A, 9, 9A each time the test scenario data 8, 8A, 9, 9A is generated by the test scenario generation unit 13A. Can be done automatically. This makes it possible to perform a screen test of screen data 3 having high real-time performance.

Further, the screen test processing unit 16 can automatically perform a screen test of the screen data 3 based on the test scenario data 8, 8A, 9, 9A when there is a specific input operation from the input device 40. .. As a result, the processing load of the test scenario generator 1B can be reduced as compared with the case where the screen test is performed every time the test scenario data 8, 8A, 9, and 9A are generated.

Next, the processing of the processing unit 10B described above will be described with reference to the flowchart. FIG. 26 is a flowchart showing an example of the processing of the processing unit 10B according to the third embodiment, and the processing is repeatedly executed by the processing unit 10B. The processes of steps S61 to S65 shown in FIG. 26 are the same as the processes of steps S11 to S15 shown in FIG. 13, and the description thereof will be omitted below.

As shown in FIG. 26, a screen editing unit 15 based on the input operation of the input device 40, editing the screen data _{3 1} (step S60). Screen editing unit 15, when the screen data 3 ₁ is edited, stores screen data 3 ₂ is a result of editing the screen data 3 ₁ in the screen data storage section 21A. Also, the screen test processing unit 16, the test scenario data 8,8A generated by the test scenario generation unit 13A, based on 9, 9A, a screen test screen data _{3 2} automatically (step S66).

FIG. 27 is a flowchart showing an example of the process of step S60 shown in FIG. 26. As shown in FIG. 27, a screen editing unit 15 based on the input operation of the input device 40, or to remove additional or parts of components in the monitor screen 8 ₁ (step S70). Further, the screen editing unit 15 sets the attributes and images of the parts based on the input operation to the input device 40 (step S71). Screen editing unit 15 stores the screen data 3 is data of the monitoring screen ₈₂ after the change in the screen data storage section 21A (step S72), and ends the processing shown in FIG. 27.

The hardware configuration example of the test scenario generation device 1B according to the third embodiment is the same as the test scenario generation device 1 shown in FIG. The processor 101 reads and executes the program stored in the memory 102 that functions as the storage unit 20A, thereby causing the difference data generation unit 12A, the test scenario generation unit 13A, the display processing unit 14, the screen editing unit 15, and the screen test. The function of the processing unit 16 can be executed.

As described above, the test scenario generation apparatus 1B according to the third embodiment, the test scenario data 8, 8A, based on 9, 9A, automatically performs screen test processing screen test of the monitoring screen ₈₂ after the change A unit 16 is provided. Therefore, in the test scenario generator 1B, the screen test is automatically performed based on the test scenario data 8, 8A, 9, 9A automatically created, so that the load on the operator in the screen test is significantly reduced. be able to.

In the above-described first to third embodiments, the monitoring screens 8 ₁ and 8 ₂ have been described as an example of the graphic screen, but the test scenario generators 1, 1A and 1B are graphic screens in which a plurality of parts are arranged. It suffices if test scenario data can be generated. That is, the graphics screen is not limited to the monitoring screen _81, 82, may be a graphic screen in which a plurality of components are arranged.

The configuration shown in the above-described embodiment shows an example of the content of the present invention, can be combined with another known technique, and is one of the configurations without departing from the gist of the present invention. It is also possible to omit or change the part.

1,1A, 1B test scenario generator, 3,4 screen data, 5,5A difference data, 6,6A default test scenario data, 7,7A standard test scenario data, 8,8A, 9,9A test scenario data, 10 , 10A, 10B processing unit, 11 screen data acquisition unit, 12, 12A difference data generation unit, 13, 13A test scenario generation unit, 14 display processing unit, 15 screen editing unit, 16 screen test processing unit, 20, 20A storage unit , 21,21A screen data storage, 22,22A difference data storage, 23,23A default test scenario storage, 24,24A test scenario storage, 40 input device, 50 display device.

Claims (12)

A difference data generation unit that generates difference data indicating the difference between the graphic screens before and after the change when the graphic screen on which a plurality of parts are arranged is changed.
A test that generates test scenario data that defines the test content of the changed graphic screen based on the difference data generated by the difference data generation unit and the default test scenario data of the component set in advance. Scenario generator and
A test scenario generation device including a test scenario data editing unit that edits the test scenario data generated by the test scenario generation unit based on an input operation to the input device. A difference data generation unit that generates difference data indicating the difference between the graphic screens before and after the change when the graphic screen on which a plurality of parts are arranged is changed.
A test that generates test scenario data that defines the test content of the changed graphic screen based on the difference data generated by the difference data generation unit and the default test scenario data of the component set in advance. With a scenario generator,
The test scenario generator
Among the plurality of test data included in the test scenario data of a graphic screen after the change, the test data of the difference, characterized by inclusion in distinguishably the test scenario and test data other than the difference trial Experiment scenario generator. The difference data generation unit
Data including the difference between the information indicating the attribute of the component included in the graphic screen before the change and the information indicating the attribute of the component included in the graphic screen after the change is generated as the difference data.
The test scenario generator
The test scenario generator according to claim 1 or 2 , wherein as the test scenario data, data that defines the test content of the attribute of the component on the changed graphic screen is generated. The test scenario generator
The test scenario generator according to claim 3 , wherein the test scenario data is generated for each state of the attribute. The difference data generation unit
Data including the difference between the image of the graphic screen before the change and the image of the graphic screen after the change is generated as difference data.
The test scenario generator
The test scenario generator according to any one of claims 1 to 4 , wherein as the test scenario data, data that defines the test content of the image on the changed graphic screen is generated. The test scenario generator
Claims 1 to 5 are characterized in that the test scenario data of the graphic screen before the change is modified based on the difference data and the default test scenario data of the component to generate the test scenario data. The test scenario generator according to any one of the above. The test scenario generator
The present invention according to any one of claims 1 to 6, wherein data defining the test content of the difference is generated as the test scenario data based on the difference data and the default test scenario data. Test scenario generator. The test scenario generator according to any one of claims 1 to 7, further comprising a screen test processing unit that automatically performs a screen test of the changed graphic screen based on the test scenario data. .. This is a computer-based test scenario generation method.
A difference data generation step that generates difference data indicating the difference between the graphic screens before and after the change when the graphic screen in which a plurality of parts are arranged is changed, and a difference data generation step.
A test that generates test scenario data that defines the test content of the changed graphic screen based on the difference data generated by the difference data generation step and the default test scenario data of the component set in advance. Scenario generation steps and
A test scenario generation method including a test scenario data editing step in which the test scenario data generated by the test scenario generation step is edited based on an input operation to an input device. This is a computer-based test scenario generation method.
A difference data generation step that generates difference data indicating the difference between the graphic screens before and after the change when the graphic screen in which a plurality of parts are arranged is changed, and a difference data generation step.
A test that generates test scenario data that defines the test content of the changed graphic screen based on the difference data generated by the difference data generation step and the default test scenario data of the component set in advance. Including scenario generation steps and
The test scenario generation step is
Of the plurality of test data included in the test scenario data of the graphic screen after the change, the test data of the difference is included in the test scenario data so as to be distinguishable from the test data other than the difference.
A test scenario generation method characterized by this. A difference data generation step that generates difference data indicating the difference between the graphic screens before and after the change when the graphic screen in which a plurality of parts are arranged is changed, and a difference data generation step.
A test that generates test scenario data that defines the test content of the changed graphic screen based on the difference data generated by the difference data generation step and the default test scenario data of the component set in advance. Scenario generation steps and
A test scenario generation program comprising causing a computer to edit a test scenario data editing step in which the test scenario data generated by the test scenario generation step is edited based on an input operation to an input device. A difference data generation step that generates difference data indicating the difference between the graphic screens before and after the change when the graphic screen in which a plurality of parts are arranged is changed, and a difference data generation step.
A test that generates test scenario data that defines the test content of the changed graphic screen based on the difference data generated by the difference data generation step and the default test scenario data of the component set in advance. Let the computer perform the scenario generation steps,
The test scenario generation step is
Of the plurality of test data included in the test scenario data of the graphic screen after the change, the test data of the difference is included in the test scenario data so as to be distinguishable from the test data other than the difference.
A test scenario generation program characterized by this.

Images