JP2001256078A - Test support equipment - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To make it possible to input a task of creating a test sequence for testing a target system smoothly and without errors in software development. SOLUTION: A state transition table (101) including a next transition state and an event causing the state transition,
An event state extraction unit (701) for extracting the state and the event included in the state transition table, and generating an event state definition table defining the contents of the event based on the extracted state and the event And an event state definition generation unit (702).

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a test support apparatus for supporting the generation of a test sequence from a state-based specification and the generation of an event definition as input data to an automatic state-based specification test execution system. Things.

[0002]

2. Description of the Related Art In the development of a system in which software, hardware, or a mixture of both are used, in order to determine the specifications of a system to be developed quickly and without errors, development is performed using a state-based specification description such as a finite state machine. It is widely practiced to analyze / define the specifications of how the target system operates. FIG. 21 shows a conventional test support device based on a state transition specification disclosed in Japanese Patent Application Laid-Open No. 63-148747. The state / event search unit 2002 extracts a state and an event immediately after the state from the input state transition diagram 2001. Next, the simultaneous operation extraction unit 2003 searches the simultaneous operation extraction rule 2005 for each of the extracted states and events to check a combination of events that can be a simultaneous operation. The state of the result is obtained. Thus, the state transition diagram 200
The results obtained by performing the above processing for all the states and events in 1 are output as a test item table 2006 of the simultaneous operation test by the test item table creation unit 2004.

[0003]

The conventional test support apparatus shown in FIG. 21 targets all states included in the state transition diagram and state transitions exiting from the state transition target according to the simultaneous operation test rule. A state transition is selected, and from the selected state transition, a list of events that cause the transition and states after the transition are displayed in a table format. From a test support device based on the conventional state transition specification, an occurrence event for each state and a transition destination which is an expected value for the state are output as test items. Such a conventional test support apparatus has the following problems. (1) Since the specifications are based on a state transition diagram, only events that cause a transition to a state are described, and combinations of states and events are not exhaustive. (2) In order to test all output test items, it is necessary to first set a system state in each state and then input an event that causes a state transition.
Since this setting is very troublesome, a test sequence for sequentially following a plurality of state transitions must be generated again before the test is performed.

An automatic test execution apparatus is an apparatus that inputs a test sequence and an event / state table defining events and states used in the test sequence, executes the test sequence, and reports a result. The event / definition table describes the meaning of the events and states used in the test sequence for the program under test (for example, when a certain memory value reaches a certain value or when the program is executed). It is a table that defines the position. Usually, the event / state definition table requires manual input, so this work takes time,
There is a case where the test / sequence does not exist in the event / state definition table even though it is used in the test sequence, and the test cannot be automatically executed.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-described problems. In software development, it is necessary to smoothly input the operation of creating a test sequence for testing a target system without error. The purpose is to make test sequence change work more efficient with respect to specification changes.

[0006]

According to a first aspect of the present invention, there is provided a state transition table including a next transition state and an event causing the state transition, and the state and the event included in the state transition table. An event state extraction unit for extracting
An event status definition generating unit that generates an event status definition table defining the contents of the event based on the extracted status and the event is provided.

A second invention is an event state definition file in which the contents of an event causing a state transition are defined in advance by a system, and whether an event extracted by the event state extraction unit exists in the event state definition file. And an event state matching unit for checking whether or not the event state is checked.

According to a third aspect of the present invention, when the event extracted by the event status extracting unit does not exist in the event status definition file, the content of the extracted event is checked by the event status checking unit. Is added to the event state definition file.

[0009]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 FIG. 1 shows a functional configuration diagram of the test support device according to the first embodiment of the present invention. In FIG. 1, reference numeral 101 denotes a state transition table which is an input of the test support apparatus, and 102 denotes a state transition table input unit which inputs the state transition table 101 and outputs an internal state transition table 103. Reference numeral 104 denotes a transition table display unit that inputs the internal state transition table 103 and displays it in a table format. 105 interprets the operation of the user selecting a cell in the state transition table 101,
This is a test sequence generation unit that sequentially generates test items corresponding to the selected cells. FIG. 2 shows a state transition table 10
1 is an example. The state transition table 101 is matrix data in which a system state is taken as a row and an input event to the system is taken as a column (the row and the column may be reversed).
In the cell specified by one state and one event, the next transition state and the action executed at the moment of the transition are described. In FIG. 2, the syntax rules are as follows. Transition destination state / action A portion where "-" is designated as the transition destination state means that there is no transition and no action is executed. Diagonally lined cells represent improbable transitions. The remaining cells excluding this cell are called valid cells. The internal state transition table 103 is obtained by adding, in addition to the input state transition table 101, a data area indicating the current state and a candidate for the next input event to the entire table, and a data area indicating the number of passes to each cell. . A valid cell whose passing number is 0 in a certain current state is referred to as a candidate cell.

FIG. 3 is a flowchart showing the operation of the first embodiment. The operation of the first embodiment will be described based on this flowchart. First, the transition table input unit 102 reads the state transition table 101 (301) and outputs it to the internal state transition table 103. At this time, the valid times of all cells are set to zero. The transition table display unit 104 displays the internal state transition table 103 (302). Thereafter, the end is designated by the user, or the number of passes of all valid cells is 1
Until the above, the test sequence generation unit 105 repeats the test sequence creation processing (303). In the test sequence creation process (303), first, an input of an initial state from the user is waited (304). At this time, an initial state with no candidate cell is not selected. If a certain initial state of the candidate cell can be input, the input result is substituted for the current state. Otherwise, end. The input initial state is output as follows (305). Initial state Next, the initial state is substituted for the current state (306), and test item processing (3) is performed until there are no candidate cells for the current state.
07) is repeated. In the test item processing (307), the candidate cell is highlighted (308), and the process waits for cell selection (309). When the user selects one of the candidate cells, the next output is performed based on the description of the cell (3).
10). (Input event, transition destination state, action) Next, the value of the current state is set as the transition destination state (311), the number of passages of the selected cell is increased by one (312), and the process returns to the test item process (307) to repeat this process. repeat.

FIG. 4 is an explanatory diagram for explaining the flow of the operation of the first embodiment. The transition table display section 104 is on the left side of FIG.
9 shows a screen image of the internal state transition table 103 displayed by the に よ っ て. The internal state transition table 103 shown on the left side of FIG.
Are copied from the state transition table 101. On the right side of FIG. 4, the internal data of the internal state transition table 103 corresponding to the left screen is shown. The internal data includes a current state, a candidate cell, the number of passes, and a test sequence output at that time. For example, output = s
1-> (e1, s2, a1)-> (e1, s2,-)
Is "Starting from the initial state s1 and input event e1
Comes, the next state becomes s2 as an expected value, and a1 is output as an action. Next, when the input event e1 comes, the next state is s2, and no action is output as an expected value. Also, the number of passes = (1,0,1,0) is the number of passes of the cell 11 (meaning the cell in the first row and the first column: corresponding to the state s1-the event e1)
1, the number of passages through cell 12 = 0, the number of passages through cell 21 =
1, meaning that the number of times of passage through the cell 22 = 0.

In FIG. 4, reference numeral 201 denotes an initial screen.
S1 is designated as an initial state, and cell 1 is designated as a candidate cell.
1 is highlighted. Reference numeral 202 denotes a screen showing a result after the user selects the cell 11 on the initial screen. On the screen 202, the cell 11 is marked, and the current state is s2, which is the transition destination state shown in the cell 11, and s2
Cell 21 and cell 22, which are candidate cells for No. 2, are highlighted. The screen 203 is a screen showing the result when the user selects the cell 21 from the screen 202. On the screen 203, the current state does not change, and the cell 2
1 is marked, and cell 22 is the only candidate cell. The screen 204 is a screen showing the result when the user selects the cell 22 from the screen 203. Since there is no candidate cell for the current state s1, this test sequence ends here. Since there are no more candidate cells, the process ends.

As described above, according to the present embodiment, when a test sequence is created based on a state transition table, the next transition destination state of one test item matches the current state of the next test item. However, since the candidate cells for the current state are shown and the operator is sequentially input and guided, a test sequence can be created without error. Also, candidate cells that have passed in the already generated test sequence are not highlighted, thereby preventing selection of duplicate test items. Furthermore, since the cells already selected as test items are displayed, it is possible to grasp what remains as test items, and to efficiently create a test sequence while creating all test items. This solves the problem of the conventional example that the coverage of the test items is not guaranteed and that the test item generation and the test sequence generation are different operations.

In the present embodiment, the state transition table shown in FIG. 2 is used. However, even in a state transition table using hierarchical states, a state higher than a certain current state is included. If a candidate cell is created, it can be handled in the same manner as in the present embodiment. Further, in the description of the operation of the present embodiment, the highlight display and the mark display are performed as shown in FIG. 4, but it is of course possible to use another method that the operator can understand.

Embodiment 2 FIG. 5 shows a functional configuration diagram of the test support device according to the second embodiment of the present invention. In FIG. 5, reference numerals 101 to 104 are the same as the functional blocks shown in FIG. Reference numeral 403 denotes a test sequence file including a plurality of test sequences that describe the content of the following format as one test sequence unit. * Represents repetition. Test sequence = initial state + test item * test item = (input event, transition destination state, action) 401 is a test sequence trace unit with error judgment, reads the test sequence file 403 and transitions each test sequence to the internal state. By tracing on table 103, discrepancies between system specifications and test sequences are reported.

Next, the operation of the second embodiment will be described. FIG. 6 is a flowchart showing the operation of the test sequencer with error determination 401 when the internal state transition table 103 has already been initialized by the transition table input unit 102. In FIG. 6, first, the test sequence trace unit 401 with error judgment reads the test sequence file 403 (601). As long as there is a test sequence, a sequence number is assigned as a unique number to each test sequence, and the test sequence processing ( 602) is repeated. Test sequence processing (6
02), it is checked whether or not the initial state of the target test sequence is in the internal state transition table 103 (60).
3) If not in the internal state transition table 103, the next message is output in the error report 1 (607), and the test sequence processing (602) is performed for a new test sequence. Sequence number: state name: initial state does not exist If the state exists on the internal state transition table 103, the current state in the internal state transition table 103 is read as (6)
04), test item processing (60
Perform 5). Here, the test item to be processed is called a target test item.

Next, it is checked whether or not an input event of the target test item exists in the candidate cell in the current state (606). If the input event is not in the candidate cell, the next message is output in the error report 2 (612), and the test sequence processing (602) is performed for a new test sequence. Sequence number: Current state name: Input event name: No input event exists If an input event exists in a candidate cell, the candidate cell is set as a selected cell, and the action in the target test item and the action in the selected cell Are compared (608).
If the actions are different, error report 3 (613)
, The next message is output, and the process of (609) is executed. Sequence number: current state name: input event name: action name: different actions If the actions are the same, the processing of (609) is executed without doing anything. At (609), the transition destination state of the target test item is compared with the transition destination in the selected cell. When the transition destination is different, in error report 4 (614),
The next message is output, and test sequence processing (602) is performed for the new test sequence. Sequence number: current state name: input event name: destination state name: destination is different When the destination is the same, the current state is set to the destination state (610), and the next test item is set as the target test item Test item processing (605) is performed.

As described above, according to the present embodiment, when creating a test sequence based on the state transition table, the test sequence group described in the test sequence file is compared with the internal state transition table which is a specification. Since the difference can be reported, an error in the test sequence created manually by the creator can be detected. Furthermore, since it is possible to check whether or not the existing test sequence conforms to the new specification in response to the change to the specification itself, it is possible to efficiently re-create the test sequence according to the change in the specification.

In this embodiment, an error message is output as text in a certain format.
The same information can be presented to the operator in different formats. For example, it is possible to show the error position on the state transition table displayed by the transition table display unit 104 shown in FIG.

Embodiment 3 FIG. 7 shows a functional configuration diagram of the test support device according to the third embodiment of the present invention. 7, 101, 102 and 104 are the same as the functional blocks shown in FIG. Reference numeral 1703 denotes an internal state transition table, which is obtained by adding the following change to the internal state transition table 103 shown in the first embodiment. When marking each cell in the internal state transition table 103, only the number of passes is stored. However, the internal state transition table 103 has a data area of a number list for recording the number of the passed test sequence group. 1701 is
A test sequence trace unit with a mark that inputs the test sequence file 403 and marks the trace result in the internal state transition table 1703 while tracing the test sequence. Reference numeral 1702 denotes a duplication determination unit that analyzes the internal state transition table 1703 on which the trace result is reflected by the test sequence trace unit with marking 1701 and determines duplication of test items.

Next, the operation of the third embodiment will be described. FIG. 8 is a flowchart showing the operation of the test sequence tracing unit with marking 1701, and the internal state transition table 170 is output by the transition table input unit 102 shown in FIG.
3 has already been initialized.
FIG. 8 shows an error report 1 (607), an error report 2 (612), an action (608), an error report 3 (613) from the flowchart of the test sequence tracing unit 401 with error judgment shown in FIG.
Delete each process such as error report 4 (614) and (2
201) is added to mark the cell.
At (2201), the sequence number of the passed test sequence is added to the number list of the target cell.

FIG. 9 is a flowchart showing the operation of the duplication judgment section 1702. The duplication determination unit 1702 performs processing in a state where the processing of the test sequence trace unit with marking 1701 has been completed. In FIG. 9, duplication determination processing (2401) is performed using all cells in the internal state transition table 1703 as target cells. Duplicate judgment processing (240
In 1), when the number list of the target cell has two or more numbers (2402), the next error message is output (2403). Cell number: Sequence number list: Duplicate test items

As described above, according to the present embodiment, when creating a test sequence based on the state transition table, the test sequence group described in the test sequence file is compared with the internal state transition table which is a specification. Since the redundancy of the test sequence can be reported, the creator can find a redundant portion of the test sequence manually created using a text editor or the like.

In this embodiment, an error message is output as text in a certain format.
The same information can be presented to the operator in different formats. For example, it is also possible to show an error position on the displayed state transition table.

Embodiment 4 FIG. 10 shows a functional configuration diagram of the test support device according to the fourth embodiment of the present invention. FIG.
At 0, 101, 102, 104, 1701, 17
03 is the same as the functional block shown in FIG. 1
Reference numeral 802 denotes a test sequence trace unit 1 with a marking.
Reference numeral 701 denotes an internal state transition table 170 reflecting a trace result.
3 is an insufficiency judging unit that judges the shortage of test items by analyzing No.

Next, the operation of the fourth embodiment will be described. FIG. 11 is a flowchart illustrating the operation of the shortage determination unit 1802. The shortage determination unit 1802 performs the processing in a state where the processing of the test sequence trace unit with marking 1701 has been completed. In FIG. 11, shortage determination processing (2501) is performed with all cells in the internal state transition table 1703 as target cells. In the shortage determination process (2501), when the number of elements in the number list of the target cell is 0 (2
502), and outputs the next error message (240)
3). Cell number: Test item is missing

As described above, according to the present embodiment, when creating a test sequence based on the state transition table, the test sequence group described in the test sequence file is compared with the internal state transition table which is a specification. You can report the lack of test sequences,
The creator can find the missing part of the test sequence created manually. Embodiment 1
In addition to the above, it is possible to assist the operator in replenishing the test sequence while indicating the shortage to the operator.

In this embodiment, an error message is output as text in a certain format.
The same information can be presented to the operator in different formats. For example, it is also possible to show an error position on the displayed state transition table.

Embodiment 5 FIG. 12 shows Embodiment 2
4 is a diagram showing what kind of check is performed between an internal state transition table as a specification and a test sequence to be inspected. FIG. In FIG. 12, the test objects are test sequence 1 (504) and test sequence 2 (50).
5), and the specification is the internal state transition table 506. In the second embodiment, the action a4 of the third test item (e2, s1, a4) of the test sequence 1 (504)
Is different from the action a3 on the internal state transition table 506, the following error message is output (501). 1: e2: s1: a4: different actions In the third embodiment, since the test sequence 1 (504) and the test sequence 2 (505) overlap in the cell 22, the following error message is displayed (50).
3). 22: 1, 2: Duplicate test items In the fourth embodiment, since the test sequence 1 (504) and the test sequence 2 (505) do not pass through the cell 12, the following error message is displayed. 12: Insufficient test items

Note that Embodiments 2 to 4 may be used in any combination.

Embodiment 6 FIG. FIG. 13 shows a functional configuration diagram of the test support device according to the sixth embodiment of the present invention. FIG.
3, reference numeral 101 is the same as the state transition table 101 shown in FIG. Reference numeral 701 denotes an event state extraction unit that inputs the state transition table 101 and extracts events and states included in the state transition table 101. Reference numeral 702 denotes an event state extraction unit that inputs the extracted events and states, and An event state definition generation unit that generates a template. 704
Is an event state definition editor for editing the generated event state definition.

The event state definition table 703 includes a logical name, I
It is a table having four items of D, event state type, and definition. Conventionally, in a test automatic execution system for inputting a test sequence and automatically testing a program, this event status definition table 703 is input to determine correspondence between a real address in a program, an event and a status in the test sequence. taking it. The definition is expressed by a logical operation of an arithmetic (inequality) equation using a macro identifier. The definition example is shown below. Example 1) Event "Initialization" is the label M in the program
Define when the program reaches _10. Initialization, 1, EVENT,! M_10 Example 2) The event “value change” is when the content of the variable macro name INP is written and becomes OH or more and 5H or less by byte length comparison. Value change, 2, EVENT, 0H ≦ (INP, BYTE)
≦ 5H Example 3) The state “changing” is when the second bit of the variable macro name INP is ON. During change, 3, STATE, (INP, BIT, 2) = 1

Next, the operation of this embodiment will be described. FIG. 14 is a flowchart showing the operation of the present embodiment. First, the event state extraction unit 701 inputs the state transition table 101, and extracts all events and states in the table (901). Next, the event state definition generation unit 70
2 assigns 1 to the sequence number, and performs an event ID addition process (90 for each extracted event and state).
After repeating step 2), an output (907) to the event state definition table 703 is performed. In the ID adding process (902), the sequence number is added to the event and the state (9
03), increments the sequence number by one (9)
05).

FIG. 15 is an example for explaining the operation of the present embodiment. In FIG. 15, reference numeral 801 denotes an input state transition table, and reference numeral 802 denotes a template of an output event state definition table. In the state transition table 801, events and states are e1, e2, s1, and s2, and the logical name, ID, and event state type are output to 802. The definition is output as UNDEF. FIG.
8 is a screen example of the event state definition editor 704 immediately after inputting the template 802 of the event state definition table shown in FIG.
Using the event state definition editor 704, the operator can input the definition of each event and state.

As described above, according to the present embodiment, when creating an event state definition as input data to the automatic test execution system based on the state transition table, the event and the state in the state transition table, which are specifications, are defined. Since the operator is forced to give the definitions of the event and the status to the test sequence defined by using the same, there is an advantage that errors are hardly mixed.

Embodiment 7 FIG. 17 shows a functional configuration diagram of the test support device according to the seventh embodiment of the present invention. FIG.
7, 101, 701 and 703 are the same as those shown in FIG. Reference numeral 1001 denotes an output from the event state extraction unit 701 and an event state definition file 70.
5 is an event state collating unit for collating the output from 5. 1
Reference numeral 002 denotes an error report indicating an output result of the event state matching unit 1001.

Next, the operation of this embodiment will be described. FIG. 18 is a flowchart showing the operation of the present embodiment. First, the event state extraction unit 701 inputs the state transition table 101, and extracts all events and states in the table (901). After that, the event state matching unit 10
01 performs a matching process (1201) using the event and state extracted from the state transition table 101 as target events / states, performs an event state definition check (1208) on all event state definition columns, and outputs an error message ( 1212), and the processing ends. Checking process (120
In 1), individual collation processing (1202) is performed for all event state definition columns. Individual collation processing (120
In 2), if the event state extracted from the state transition table 101 exists in the event state definition file 705 (1203), the column of the event state definition file 705 is marked (1204), and the next collation processing (1201)
Perform If not, the individual comprehensive processing is performed again.
If no match is found as a result of checking all the event state definition columns, the next error message is created in error message creation 1 (1206). Event status definition: ID: No event status is defined. Further, in the event status definition check (1208) for the event status check, it is checked whether or not there is a mark in the target event status definition column. If there is no mark, the next error message is created in error message creation 2 (1210). Event state definition: ID: No definition of event state in transition table In the output of error message (1212), the error message created in error message creation 1 (1206) and error message creation 2 (1210) Output as an error report (1002).

As described above, according to the present embodiment, when creating a test sequence based on the state transition table, the events and states used in the state transition table, which is the specification, and the events defined in the event state definition table Since it is possible to check the excess or deficiency of the status, it is possible to define the event status definition necessary for interpreting the test sequence that is the input to the automatic test execution system without errors, and to perform the automatic test execution smoothly. It becomes possible.

Embodiment 8 FIG. FIG. 19 shows a functional configuration diagram of the test support device according to the eighth embodiment of the present invention. FIG.
9, 101, 704 and 705 are the same as those shown in FIG. Reference numeral 1301 denotes an output from the event state extraction unit 701 and the event state definition file 70.
5 is an event state collating unit for collating the output from 5. 1
Reference numeral 302 denotes an error report indicating an output result of the event state matching unit 1301. An event state definition generation unit 1303 adds a new event state definition template to the event state definition file 705 based on the event state name output from the event state matching unit 1301.

Next, the operation of this embodiment will be described. FIG. 20 is a flowchart showing the operation of the present embodiment. In FIG. 20, (901) performs the same processing as that shown in the flowchart of FIG. In the matching process (1201) performed by the event state matching unit 1301, the event matching unit 1001 shown in FIG.
8 is the same as that of FIG. 8 except that a process of generating a new event state definition of (1301) is added to the matching process (1201).
In (1301), the event state definition column that does not exist in the transition table is output to the event state definition generation unit 1303 as a new event state definition. further,
(1209) to (1212) are completely the same as those in FIG. 18. In (1302), a number obtained by adding 1 to the maximum value of the ID number in the event state definition table is substituted for the sequence number, and the ID addition processing is performed. (902) and output to the event state definition table (907). Steps (902) and (907) are exactly the same as those shown in FIG.

As described above, according to the present embodiment, when creating a test sequence based on the state transition table, the event state definition table is compared with the specification state transition table. If the specification changes frequently, the test sequence that has already been created and the event state definition used there must be consistent with the specification because the specification can be changed frequently. Will be easier to keep.

[0042]

【The invention's effect】

According to the first aspect, a state transition table including a next transition state and an event causing the state transition, and an event for extracting the state and the event included in the state transition table By providing a state extraction unit and an event state definition generation unit that generates an event state definition table that defines the contents of the event based on the extracted state and the event, the operator can determine whether the event is A definition of the state can be given.

According to the second invention, the contents of the event causing the state transition are defined in the event state definition file by the system, and the event extracted by the event state extraction unit exists in the event state definition file. With the provision of the event state collating unit for checking whether or not to perform the test, it is possible to define the event state definition necessary for interpreting the test sequence as an input to the automatic test execution system without error.

According to the third aspect, when the event extracted by the event status extracting unit does not exist in the event status definition file by the check of the event status checking unit, the extracted event is output. When the specification changes frequently, the event sequence definition is added to the event status definition file. If the specification frequently changes, the test sequence that has already been created matches the event status definition used in the specification with the specification. It is easy to maintain the performance.

[Brief description of the drawings]

FIG. 1 is a functional configuration diagram of a test support device according to Embodiment 1 of the present invention.

FIG. 2 is a diagram illustrating an example of a state transition table.

FIG. 3 is a flowchart showing the operation of the first embodiment of the present invention.

FIG. 4 is an example showing a specific image of test sequence generation support according to the first embodiment of the present invention.

FIG. 5 is a functional configuration diagram of a test support device according to a second embodiment of the present invention.

FIG. 6 is a flowchart showing an operation of the second embodiment of the present invention.

FIG. 7 is a functional configuration diagram of a test support device according to Embodiment 3 of the present invention.

FIG. 8 is a flowchart illustrating an operation of a test sequence trace unit with marking according to Embodiment 3 of the present invention;

FIG. 9 is a flowchart showing the operation of the third embodiment of the present invention.

FIG. 10 is a functional configuration diagram of a test support device according to Embodiment 4 of the present invention.

FIG. 11 is a flowchart showing an operation of the fourth embodiment of the present invention.

FIG. 12 is a diagram showing an example of a test sequence evaluation according to the fifth embodiment of the present invention.

FIG. 13 is a functional configuration diagram of a test support device according to Embodiment 6 of the present invention.

FIG. 14 is a flowchart showing the operation of the sixth embodiment of the present invention.

FIG. 15 is a diagram showing an input / output example according to a sixth embodiment of the present invention.

FIG. 16 is a screen example of an event state definition editor according to Embodiment 6 of the present invention.

FIG. 17 is a functional configuration diagram of a test support device according to Embodiment 7 of the present invention.

FIG. 18 is a flowchart showing the operation of the seventh embodiment of the present invention.

FIG. 19 is a functional configuration diagram of a test support device according to an eighth embodiment of the present invention.

FIG. 20 is a flowchart showing the operation of the eighth embodiment of the present invention.

FIG. 21 is a functional configuration of a conventional test case generation device according to the present invention.

[Explanation of symbols]

101 state transition table, 102 state transition table input section, 10
3 internal state transition table, 104 transition table display section, 105
Test sequence generation unit, 401 Test sequence trace unit with error judgment, 403 test sequence file, 701 event state extraction unit, 702 event state definition generation unit, 703 event state definition table, 704
Event status definition editor, 705 Event status definition file, 1001 Event status collation unit, 1002
Error report, 1301 Event status collation unit, 13
02 error report, 1303 event state definition generation unit, 1701 test sequence trace unit with marking, 1702 duplication judgment unit, 1802 shortage judgment unit.

Claims (3)

[Claims] A state transition table including a state to be transitioned next and an event causing the state transition; an event state extraction unit that extracts the state and the event included in the state transition table; A test support device comprising: an event state definition generation unit that generates an event state definition table that defines the contents of an event based on the extracted state and the event. 2. An event state definition file in which the contents of an event causing a state transition are defined in advance by a system, and whether or not the event extracted by the event state extraction unit exists in the event state definition file is checked. 2. The test support apparatus according to claim 1, further comprising: an event state matching unit that performs the operation. 3. When the event extracted by the event status extraction unit does not exist in the event status definition file according to a check of the event status collation unit, the content of the extracted event is converted to the event status. 3. The test support apparatus according to claim 2, further comprising an event state definition adding unit that adds the event state definition to the definition file.