JPH04236636A - Check method for interactive system - Google Patents

Abstract

PURPOSE:To improve the check efficiency by eliminating omission of check of an interactive application. CONSTITUTION:A command of the interactive application is expressed by a state transition diagram 1, and this diagram is converted to a state transition file 3 by a state transition diagram converting part 2. Meanwhile, an event generating part 5 automatically generates an event. When receiving the event, an event processing part 6 calls a command processing part 7 for the event to perform the processing. A state value changing part 8 changes the state value in a state value storage part 9 by processing contents of the command processing part 7. A state transition verifying part 10 verifies whether the state transition of the command understood by the state value before event generation, the event, and the state value in the state value storage part coincides with contents of an independently read state transition file or not. If they do not coincide with each other, a warning is given. All events are automatically generated for all states in the event generating part to automatically check all states of the application.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an interactive system testing method, and more particularly to an interactive system testing method for testing an event-driven interactive application.

0002

[Background Art] In a conventional inspection method for interactive systems, an inspector refers to a flowchart while running an application program to check whether there are any errors in the type of event from the outside and the change in state at that time. was inspected.

0003

[Problems to be Solved by the Invention] In the above-mentioned method of testing an interactive system, the tester generates all possible events while running an application program, and identifies the type and status of each event that has occurred. Since it is necessary to compare the check with the flowchart and verify whether it matches, human errors such as omissions in checking all events in all states and mistakes in checking against the flowchart occur. There was a problem with that.

An object of the present invention is to provide an interactive system testing method that can eliminate omissions in testing interactive applications and improve testing efficiency.

[0005]

[Means for Solving the Problems] The interactive system inspection method of the present invention includes a file conversion means for converting a state transition diagram of an event-driven interactive application into a state transition file, and a method for automatically converting all events in all states. a state value changing means that directly changes the internal state value of the command of the interactive application of the event, and a state that changes depending on the type of event is the same as the event state described in the state transition file. This configuration includes a state transition verification means for verifying whether or not the state transition is the same.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be explained with reference to the drawings.

FIG. 1 is a block diagram of one embodiment of the present invention.

The method for testing the interactive system shown in FIG.
A state transition diagram 1 that shows state transitions of an interactive application; a state transition converter 2 that converts the state transition diagram 1 into a file in a format that the interactive application can read; and a state transition diagram 1 that converts the state transition diagram 1 into a format that the interactive application can understand. an interactive system 4 to be inspected; an event generation unit 5 that reads the state transition file 3 and automatically generates all events for all states;
An event processing unit 6 that accepts an event to the interactive system and calls the next process, a command processing unit 7 that processes the command called by the event processing unit 6, and a status value of the command output by the command processing unit 7. The state value change unit 8 that directly changes the state value, the state value storage unit 9 that stores the state value of the changed command, and the state value storage unit 9 that checks whether the state value of the changed command matches the contents of the state transition file 3. This is realized by a state transition verification section 10 that outputs mismatch information when there is no match, and a warning generation section 11 that receives the mismatch information from the state transition verification section 10 and generates a warning.

Next, the operation will be explained.

The state transition diagram 1 is converted into a state transition file 3 by a state transition change unit 2. The event generation unit 5 receives the output of the state transition file 3 and generates one of the events that may occur in the current state. The event processing unit 6 that receives one of the events outputs a command corresponding to the event to the command processing unit 7. The command processing unit 7 processes the command and outputs the status value of the command to the status value changing unit 8. The state value changing section 8 rewrites the state value of the command in the state value storage section 9 to the state value of the command changed by the event. Next, the state transition verification section stores the state value a of the command before changing the state, the type b of the event, the state value c of the command in the state value storage section 9, and three data that can express the state transition of the command. Send to 10. The state transition verification unit 10 reads the state transition file 3 and verifies whether the state transition of the command and the state transition file 3 match, and if they do not match, sends mismatch information to the warning generation unit 11. Generates a warning. In this way, the event generation unit 5 is operated so that all events occur repeatedly in all states, and the comparison between the state value c and the state transition file 3 is automatically performed, which greatly reduces inspector errors. can be done.

[0011]

[Effect of the invention] The method for testing an interactive system of the present invention is as follows:
By automatically generating all events in all conditions, it is possible to eliminate omissions in inspections. Furthermore, if a state that does not match the state transition diagram occurs, a warning is issued, which has the effect of greatly increasing inspection efficiency.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of one embodiment of the present invention.

[Explanation of symbols] 1. State transition diagram 2　　　　State transition diagram conversion section 3. State transition file 4 Interactive system 5 Event occurrence part 6 Event processing section 7 Command processing section 8 Status value change section 9 Status value storage section 10　　　　State transition verification section 11 Warning section a Status value before status value change b Event type c Status value of status value storage section

Claims (1)

[Claims] 1. File conversion means for converting a state transition diagram of an event-driven interactive application into a state transition file; event generation means for automatically generating all events in all states; The present invention is characterized by comprising a state value changing means for directly changing the internal state value of a command, and a state transition verification means for verifying whether the state changed depending on the type of event is the same as the event state described in the state transition file. How to test interactive systems.