JPH0779373B2 - Compatibility test suite creation device - Google Patents

Description

Detailed Description of the Invention

[0001]

The present invention relates to OSI (Open Systems).
Interconnection) Conformance test suite creation apparatus for generating an executable test suite for use in a conformity test apparatus that tests conformity to a conforming standard for (N) layer packaging manufactured based on the standard Is.

[0002]

2. Description of the Related Art FIG. 12 is a block diagram showing a configuration example of a compatibility test apparatus.

In order to ensure the interoperability of the information communication terminals implementing the (N) layer of the OSI reference model created in conformity with the OSI protocol specifications and the OSI standard 110 concerning the service definition, the OSI reference of each information communication terminal is performed. There is a conformance test as a test for determining whether or not the (N) layer implementation of the model properly complies with the compliant OSI standard. (ISO / IEC 9646)

The implementation of the (N) layer by a program or a logic circuit is called mounting. In particular, the target implementation of the conformance test apparatus 140 is tested target implementation (IUT: Implementation).
Under Test) 150.

The compatibility test apparatus 140 comprises a test execution control section 141, a lower tester 142, an upper tester 143 and a test result judgment output section 144. The IUT 150 and the lower-order tester 142 of the compatibility test apparatus use the lower layer service of OSI, that is, the (N-1) service (hereinafter referred to as the lower layer) 160, to the (N-1) connection 16
Establish 1. Based on the execution-type test case 131, the test execution control unit 141 controls the upper tester 143 and the lower tester 14
IUT150 while controlling 2 and harmonizing the operation of both
I add an action to and observe the reaction event
Test operation of UT 150. The control of the upper tester 143 establishes the test management connection 162 between the test execution control unit 141 and the upper tester 143, and the test execution control unit 1
41 does.

Control the IUT 150, control the point of observation
Observation point (PCO: Point of Control and Observation)
Say The test case describes the specifications of data exchange in the PCO. In the example of FIG. 12, PCO is a point L corresponding to the lower interface of the IUT 150,
There are three points, a point U corresponding to the host interface and a point M corresponding to the test management connection. The test case describes the test operation by appropriately combining these three PCO points. In general, the upper tester 143 and the IUT 150 are often incorporated in the same device, and form a system under test (SUT) 170.

The test case, which is a document describing the test specifications of the conformance test, is an OS to which the test target implementation conforms.
As the abstract test case 121 based on the I international standard 110, for example, TTCN. GR (Tree and Tabular Combi
ned Notation, Graphical Form; ISO / IEC9646) is used to describe in human-readable form. There are usually multiple test cases, and the entire set of test cases is called a test suite. Based on this abstract test case 121, an executable test case 131 in a format that the compatibility test apparatus 140 can execute is generated. Using this, the conformity testing apparatus executes a test, controls and observes the operation of the IUT 150, and from the result, judges the conformity of the IUT to the OSI standard. 120 is an abstract test suite, and 130 is an execution test suite.

By comparing the result of controlling and observing the operation of the test object mounting with the operation described in the test case based on the provisions of the OSI standard, the test object mounting passes (pass) or fails (test) for each test case. fail), indeterminate (in
One of the determinations of "conclusive" is performed.

In the conventional conformance test apparatus, generation of an execution type test case from an abstract test case is performed by, for example, TTCN. The test specifications are described in GR, and the TTC is used as an execution type test case by the language conversion device.
N. MP (Tree and Tabular Combined Notation, Machi
ne Processable form) was generated and mounted on the conformance test equipment to operate the test equipment.

TTCN. MP has relatively low human comprehension as a language and requires specialized knowledge to understand it, so once the TTCN. GR to TTCN. M
When it is converted to P, the comprehension of what kind of test the test case does is significantly deteriorated, so that there is a problem that the debugging work of whether or not the execution test case is correctly generated becomes inefficient. .

On the other hand, an example of a conformity testing apparatus that uses a state transition table format as an execution type test case is disclosed in Japanese Patent Application No.
As disclosed in Japanese Patent No. 35386, TTCN. A method of generating a state transition table format execution type test case from GR can also be used, but conventionally,
It was a very laborious and difficult task because there was only a manual method.

[0012]

SUMMARY OF THE INVENTION The present invention has been made in view of the above points and has been proposed as an abstract test suite for TTC.
N. An object of the present invention is to provide a conformance test suite creation device for efficiently creating a state transition table format execution type test suite for conformity tests from those described in GR.

[0013]

SUMMARY OF THE INVENTION In order to solve the above problems, the present invention is directed to TTCN. Based on the abstract test case described using GR, the vertical axis indicates the creation of the execution test case in the state transition table format, the vertical axis is the state number and the reception instruction action description column,
The horizontal axis consists of input events, and in the box that describes the operation contents, the operation consisting of the state transition table management action, the test operation action, and the next state number is used as a table description to perform the operation. Is.

Further, in the above case, when a test case in the state transition table format is first created with ruled lines for human debugging, and then developed into an execution type test suite to be mounted on the compatibility test apparatus. Is characterized in that it is recorded in a format in which ruled lines, which are unnecessary for the test execution by the compatibility test apparatus, are removed.

[0015]

According to the present invention, in the creation of a test suite for a conformance test apparatus for the (N) layer implementation of the OSI reference model, TTCN. This is to efficiently create an execution type test suite by automatically generating an execution type test suite in the state transition table format from the abstract test suite described in GR.

[0016]

Embodiments of the present invention will now be described in detail with reference to the drawings.

FIG. 1 is a block diagram of a conformance test suite creating apparatus according to an embodiment of the present invention. In the figure, 10 is TTCN. Abstract test suite described in GR, 20 is a conformance test suite creating device, 30 is TTC
N. GR syntax interpretation unit, 31 is an input event extraction unit, 3
2 is a hierarchy decision unit for input events, 33 is an inter-transition-table input event setting unit and a comparison result input event setting unit for exchanging test operations between layers of the state transition table,
34 is an output action extraction unit, 35 is a hierarchy determination unit for output actions, 40 is a horizontal axis generation unit, and 41 is (N-
1) service primitive input event creation unit, 42 (N) PDU input event creation unit, 43 (N) service primitive input event creation unit, 50 vertical axis and box description creation unit, 51 box description creation unit, 5
2 is an (N-1) service primitive output action creation unit, 53 is an (N) PDU output action creation unit, 54
Is an (N) service primitive output action creation unit,
Reference numeral 55 is a state number management / assignment unit of the state transition table, 56 is a reception instruction action generation unit, 60 is a state transition table format execution type test suite synthesis unit, 61 is a ruled line (N-1) service primitive state transition table, 62 Is a ruled (N) PDU state transition table, 63 is a ruled (N) service primitive state transition table, 70 is a ruled line removal circuit, 80 is a text file output section, 90 is a ruled state transition table format execution type test suite display Part 100 is a state transition table format execution type test suite (no ruled lines).

TTCN. The abstract test suite 10 described in GR is sequentially input to the conformance test suite creating device 20 for each test case, and first, the syntax interpreting unit 30 inputs an event, an output action, and an event exchange between layers (inter-transition table input event). , Corresponding to the comparison result input event). Input event extractor 3 from the output
1 extracts only the input event and sends it to the hierarchy determining unit 32. The horizontal axis of the state transition table to be created is the input event sequence, and the horizontal axis creating unit 40 creates and creates the horizontal axis by recording and processing the next input event sent for each layer. Further, the input event for describing the interaction of the test operation between the transition tables sent from the transition table input event setting section and the comparison result input event setting section 33, for example, the result of the test operation in the lower transition table is correct ( ANS-OK) or illegal (ANS
-NG) is added to the horizontal axis to complete the horizontal axis.

On the other hand, the output action extraction unit 34 uses the TTC
N. From the description of each line of GR, a line corresponding to an output action, which has a "!" Symbol and a line which has neither "?" Nor "!", Is extracted, the hierarchy determination unit 35 determines the hierarchy of the state transition table, and the box It is sent to the description creating section 51. However, "?"
The state transition table 1 is used for the hierarchy of the row having neither "" nor "!". In the box description creating unit 51, an output action is generated for each layer and the state number management / assignment unit 55 causes the TTCN. A state number is given to each line of the GR having a "?" Symbol. At the same time, describe the next state number in the box description.

The reception instruction action generation unit 56 uses the TTC
N. Using the output of the GR syntax interpreting unit 30 as an input, the spontaneous action is "N", TTCN. If the GR description has a "?" Symbol, it means "?" As the input event waiting state, the result of the process of the box description creating unit 51 indicates a response from the lower hierarchy of the state transition table, or an event that has already been input. When determining the horizontal axis of the transition table again, the reception instruction action is described by the section of "S".

The state transition table format execution type test suite synthesizing unit 60 includes a horizontal axis generating unit 40, a box description creating unit 51, a state number managing / assigning unit 55, and a reception instruction action generating unit 5.
The output from 6 is used as an input to generate a ruled line state transition table. This is the ruled line (N-1) service primitive state transition table 61 (layer 1), the ruled line (N) PDU state transition table 62 (layer 2), the ruled line (N) service primitive state transition table 63 (layer 3). ) Consists of three layers.

State transition table format The output of the execution type test suite synthesizing unit 60 is passed to the ruled line removal circuit 70, the ruled lines are removed, and the state transition table format which can be used by the compatibility test apparatus via the text file output unit 80 is provided. Execution type test suite 1
It is output as 00.

The output of the state transition table format execution type test suite combining section 60 is displayed and output as a ruled line execution type test suite by the ruled line state transition table format execution type test suite display section 90.

The output state transition table format execution type test suite 100 is the logic circuit memory of the conformity testing apparatus as disclosed in, for example, Japanese Patent Application No. 4-35386 "Execution Method of Conformance Test". Is used for conformity testing, but if it is developed and used in this logic circuit memory, if it is a ruled state transition table format execution type test suite, it is difficult to expand it to the logic circuit memory as it is. Is generally. To solve this,
It is necessary to add a circuit for interpreting the structure of the state transition table and correctly expanding only the data of the part excluding the ruled lines into the logic circuit memory, but add this to the test equipment that requires high-speed processing. Is not efficient. However, on the other hand, when the operator of the conformance test suite creating device debugs whether the generated state transition table format execution test suite is correct, the contents of the generated test suite should be kept highly understandable. In order to improve efficiency, it is also necessary to output a ruled state transition table format execution type test suite. Therefore, the conformance test suite creating apparatus 20 can perform both display output of the ruled line state transition table format execution type test suite from the display unit 90 and output of the ruled line state transition table format execution type test suite 100. effective. FIG. 2 is a diagram showing the structure of a state transition table format execution type test suite according to an embodiment of the present invention.

The test suite consists of a plurality of test cases, for example M test cases. The execution test suite in the state transition table format includes (N-1) service primitives (state transition table 1 (tier 1)), (N) PDUs (state transition table 2 (tier 2)), (N). 2) For the service primitive (state transition table 3 (layer 3)), a three-layer structure is adopted, and FIG.
The structure is as shown in. The structure of each state transition table is shown in FIG.
An example is shown in. The horizontal axis indicates the input event, and the vertical axis includes the state number and the description field of the reception instruction action. The reception instruction action is for describing the reception instruction operation for the input event on the horizontal axis (see FIG. 4). The intersection of the input event and each status number is called a box and describes the action to be executed and the next status number. FIG. 3 is a description method of a state number of a state transition table format execution type test case according to an embodiment of the present invention.
Is the current state number, and (b) is the next state number.

The current state number is, for example, "0" as an initial value.
It is assumed that 0 is displayed with an appropriate number of digits such as "00", and thereafter, any numerical value in ascending order is taken. State number is TTC
N. Each time a "?" Symbol appears in the description of each line of GR, it is given corresponding to that line.

As an exception, the first spontaneous action includes, for example, the "!" Symbol and does not include "?", Which is the initial value 000 of the current state number. In addition, when the result of the action of the upper layer of the state transition table is passed to the lower layer (indicated by "DOWN" at the end of the action of the box) and the result evaluated by the lower layer is returned to the upper layer,
The state for waiting for this is provided by interrupting in the ascending order. The reception instruction action in this case is described as S (see FIG. 4). The input event waiting in this state is an answer from a lower hierarchy, such as ANS-OK and A.
Described as NS-NG. The next state number is the state number to be transitioned to next after executing the action in the box, and is described at the bottom left of the box. If the final state is reached after execution of an action, the next state number is "E
It is described as ND "to indicate the end.

FIG. 4 is a description method of the output action and the reception instruction action of the state transition table format execution type test case according to the embodiment of the present invention. There are two types of actions, an output action and a reception instruction action.

The reception instruction action is for describing the reception instruction operation for the input event on the horizontal axis.
The operation state immediately after the state transition is shown. Describe on the vertical axis of the state transition table, to the right of the state number. The type is “?” That indicates waiting for an input event, “S” that waits for a response from the lower state transition table, or “S” that determines the horizontal axis of the transition table again according to the events that have already been input. Is “N”.

The output action is described in the box and indicates the output operation. It consists of a state transition table management action for controlling the state transition table and a test operation action that describes an action for causing the conformance testing device to perform an operation according to the test target protocol.

FIGS. 5A and 5B are description examples of arguments of the state transition table management action of the state transition table format execution type test case according to the embodiment of the present invention. The state transition table management action has an argument. Arguments start with {, concatenate with +, and end with}. For example, the argument of RESULT, which is an action indicating the determination of the test result, is TTCN. GR
As shown in Fig. 5 (b), PASS, FA
IL, INCONCLUSIVE, and ABORT.
The conformance tester controls and observes the IUT to check the arrived box of the state transition table from the final input event,
The judgment of the test result is obtained from the argument of the result RESULT described therein. ABORT is used to forcibly cancel the execution of the test due to a system abnormality.

FIG. 6 shows a TTC according to an embodiment of the present invention.
N. It is a method to create the horizontal axis from the GR description, (a)
Is TTCN. Example of description contents of GR input event, (b)
Is TTCN. It is a flowchart which produces | generates the horizontal axis of a state transition table from GR. TTCN. The process for creating the horizontal axis is performed on the line with the "?" Symbol in GR. In FIG. 1, the processing is performed by the horizontal axis creating unit 40.

First, TTCN. Input events are extracted for each layer from the GR description. This is done for all test cases, ie the entire test case. The result of the processing is recorded, and finally the processing results are appropriately arranged, and the transition table input event and the comparison result input event are added to this to create the horizontal axis.

7 and 8 show a TTCN. This is a method of generating an output action and a next state number from GR, and FIG. Output action from GR, example entry contents of next state number, FIG. 7B shows TTCN. In the description of GR, an output action for a line without the symbols "!" Or "?", An example of the entry contents of the next state number, and FIG. 7C shows TTCN. An example of entry of the output action of the result judgment from GR, FIG. 8 shows TTCN. It is a flow diagram which produces the output action of a state transition table, and the next state number from GR.

TTCN. The process for creating the output action is sequentially performed on the line having the symbol "!" From the beginning of the GR (see FIG. 7A). In FIG. 1, it is processed by the box description creating unit 51. The symbol "!",
A line without any "?" Is processed by the (N-1) service primitive output action creation unit 52. The state number management / assignment unit 55 in FIG. 1 creates a state number from the overall syntax interpretation result and assigns the next state number in the box. TTCN. In the GR description, for lines that do not have the symbols "!" And "?", The process for creating a sequential output action is performed (see FIG. 7B). Here, the output action in the box is TTCN. Each line of the GR description is processed in order from the head side and arranged in order for each layer. Within one box is TTCN. Describe the output action that is the result of processing up to the line immediately before the line with "?" Next appears in the GR description. Figure 7 shows the test results.
As shown in (c), TTCN. It is described in the box from the GR description.

FIG. 9 shows a method of generating a reception instruction action according to an embodiment of the present invention. (A) shows TTCN. Example in which there is a "?" Symbol on the line following the GR description line, (b)
Is a voluntary operation, and (c) is switching of the hierarchy of the state transition table to be processed.

TTCN. When there is a "?" Symbol in the GR line, the reception instruction action of the state number indicated by the next state number of the output action immediately before it is "?" Indicating that it waits for an input event. The reception instruction action of the spontaneous action is represented by “N”. When switching the hierarchy of the state transition table to be processed, the receive instruction action is
It is represented by "S". FIG. 10 is a flowchart showing a method of creating a state transition table format execution type test suite according to an embodiment of the present invention. FIG. 11 is a flowchart showing a method of creating the vertical axis and box description of the state transition table format execution type test case according to the embodiment of the present invention.

[0038]

As described above, according to the present invention, the TTCN. By automatically creating an execution type test case in the state transition table format based on the abstract test case described in GR, there is an advantage that a test suite that can be used by the conformance test apparatus can be effectively provided.

Furthermore, the test case in the state transition table format can be displayed with a ruled line suitable for human understanding, which has a great effect that the debugging work of the execution type test case is facilitated and the reliability is improved.

[Brief description of drawings]

FIG. 1 is a block diagram showing an apparatus for creating a compatibility test suite according to an embodiment of the present invention.

FIG. 2 is an explanatory diagram showing a structure of a state transition table format execution type test suite according to an embodiment of the present invention.

FIG. 3 is an explanatory diagram showing a method of describing a state number of a state transition table format execution type test case according to an embodiment of the present invention.

FIG. 4 is an explanatory diagram showing a description method of an output action and a reception instruction action of a state transition table format execution type test case according to an embodiment of the present invention.

FIG. 5 is an explanatory diagram showing a description example of arguments of a state transition table management action of a state transition table format execution type test case according to an embodiment of the present invention.

FIG. 6 shows a TTCN. It is explanatory drawing which shows the method of creating a horizontal axis from the description of GR.

FIG. 7 shows a TTCN. It is explanatory drawing which shows the output action and the generation method of the next state number from GR.

FIG. 8 shows a TTCN. It is explanatory drawing which shows the flow of output action and generation of the next state number from GR.

FIG. 9 is an explanatory diagram showing a method of generating a reception instruction action according to an embodiment of the present invention.

FIG. 10 is a flowchart showing a method of creating a state transition table format execution type test suite according to an embodiment of the present invention.

FIG. 11 is a flowchart showing a method of creating a vertical axis and a box description of a state transition table format execution type test case according to an embodiment of the present invention.

FIG. 12 is a block diagram showing a configuration example of a compatibility test apparatus.

[Explanation of symbols]

10 ... TTCN. Abstract test suite written in GR, 2
0 ... Compatibility test suite creation device, 30 ... TTCN. G
R syntax interpreting unit, 31 ... Input event extracting unit, 32 ... Hierarchy determining unit for input event, 33 ... Transition table input event setting unit for exchanging test operation between layers of state transition table, and comparison result input event Setting unit, 34 ...
Output action extraction unit, 35 ... Hierarchy determination unit for output action, 40 ... Horizontal axis creation unit, 41 ... (N-1) Service primitive input event creation unit, 42 ... (N) P
DU input event creating unit, 43 ... (N) Service primitive input event creating unit, 50 ... Vertical axis and box description creating unit, 51 ... Box description creating unit, 52 ... (N
-1) Service primitive output action creation unit, 5
3 ... (N) PDU output action creation unit, 54 ... (N)
Service primitive output action creation unit, 55 ... State number management / granting unit of state transition table, 56 ... Reception instruction action generation unit, 60 ... State transition table format execution type test suite combining unit, 61 ... Ruled line (N-1) Service primitive state transition table, 62 ... Ruled line (N) PDU state transition table,
63 ... Ruled (N) service primitive state transition table,
70 ... Ruled line removal circuit, 80 ... Text file output section,
90 ... Ruled line state transition table format execution type test suite display section, 100 ... State transition table format execution type test suite (no ruled line).

Claims (2)

[Claims] 1. Open system interconnection (OSI: Op
TTC for use in conformance testing equipment for (N) layer implementations of the en Systems Interconnection reference model
N. GR (Tree and Tabular Combined Notation, Graph
ical form; ISO / IEC9646) is used to create an executable test suite that can be executed by the conformance test equipment from the abstract test suite. It consists of the state number and the receive instruction action description field shown, the horizontal axis is the input event that describes the external input in each state, and the box field that describes the operation content for the input event is the state transition table management action, A conformance test suite creation device for an execution type test suite in the form of a state transition table that describes an action consisting of a test action action and the next state number. 2. When the test suite in the state transition table format is first created with ruled lines to facilitate its creation and then expanded to the execution type test suite to be mounted on the compatibility test apparatus, the compatibility is set. 2. The suitability test suite creating apparatus according to claim 1, wherein the test file is output in a text file format in which ruled lines that are unnecessary for executing a test in the test apparatus are removed.