JPH0815281B2 - Abstract test case dividing device - Google Patents

Description

Detailed Description of the Invention

[0001]

The present invention relates to OSI (Open Systems).
Interconnection) TTC used in an interconnect test system for testing the interoperability of (N) services between two (N) layer protocol implementation information communication terminals of the reference model
N. GR (Tree and Tabular CombinedNotation, Graphi
Cal Form; ISO / IEC9646) It is related to the improvement of the abstract test case dividing device that divides the abstract test case for the entire test system for each tester.

[0002]

2. Description of the Related Art Conventionally, TTCN. A method of dividing an abstract test case by a GR description is disclosed in Japanese Patent Application No. 5-2214. According to this method, an abstract test case for the entire test system is divided for each tester, and a "pass (pass)" judgment is added to a sub-test case that has no judgment result.

In this method, since the events are simply separated, an inconsistent description may appear when a complicated abstract test case is processed. For example, a time-out event may repeatedly appear, or a block of the same event may repeatedly appear in the same indent. As described above, in the conventional abstract test case division method, the divided test cases are TTC.
N. There was a problem that the description was not always correct according to GR. Further, it may be possible to manually correct the test case after dividing the test case by the above method, but since it requires specialized knowledge, it is a troublesome work.

[0004]

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances. An object of the present invention is to provide an abstract test case dividing device for dividing an abstract test case of the entire test system described in GR and efficiently outputting a sub test case for each tester.

[0005]

In order to achieve the above-mentioned object, the present invention provides TTCN. It is characterized in that each event in the abstract test case described using GR is inspected, and the same indent event is extracted / deleted to divide into sub test cases having no contradiction.

[0006]

In the creation of the abstract test case for the interconnect test equipment for the (N) layer protocol implementation of the OSI reference model, the present invention provides TTCN. The sub test case is created efficiently by automatically generating a sub test case division for each tester from the abstract test case of the entire test system described in GR.

[0007]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a block diagram of an interconnect test system according to an embodiment of the present invention. In the figure, 10
Is TTCN. An abstract test case of the entire test system described in GR, 11 is an abstract test case dividing device according to the present invention, 12
a and 12b are sub-test cases [1] and [2] for testers [1] and [2], 13a and 13b are conformance test suite creation devices [1] and [2], 20 is a test manager, 2
1 is an execution type result determination table, 22 is a determination result output, 2
3 is a result determination table, 24a and 24b are communication units [1] and [2], 30a and 30b are testers [1],
[2], 31a and 31b are execution type sub test cases [1] and [2], 32a and 32b are tester [1],
The timers A, B, 40a, 40b for [2] are IUTs.
[1], [2], 50 are lower layers, and 60 is a test channel.

The abstract test case 10 of the entire test system is divided by the abstract test case dividing device 11 into a sub-test case [1] 12a for the tester [1] and a sub-test case [2] 12b for the tester [2], which are respectively adapted. Sex test suite creation device (see Japanese Patent Application No. 5-28912) [1] 13a
And the compatibility test suite creation device [2] 13b convert the execution type sub-test case [1] 31a and the execution type sub-test case [2] 31b, and arrange the tester [1] 30a and the tester [2] 30b. .

Tester [1] 30a and tester [2] 3
0b is IUT [1] 40a and IUT [2] 40 according to the test case according to the instruction from the test manager 20.
Run the test on b.

IUT [1] 40a and IUT [2] 40b
Establish a test channel 60 in the lower layer 50 and interoperate. After the test execution, the result of each test case is sent to the test manager 20 via the communication unit [1] 24a and the communication unit [2] 24b, and the determination result is output by the execution-type result determination table 21 according to the result determination table 23. 22 is output.

FIG. 2 shows an example of a method of dividing an abstract test case according to an embodiment of the present invention. In this example, a request for establishing a transport connection (T connection) from IUT [1] to IUT [2] is made. , A test case for testing response, TTCN. It is described in GR.

TTCN. The basic operation description method of GR is
This is to describe the exchange operation of service primitives in the order of (control / observation point) (discrimination between transmission and reception) (service primitive). "?" Represents reception, and "!" Represents transmission.
In this example, the control / observation point is the upper interface of IUT [1] (upper service access point (SAP) U1 and IU).
It is a higher-level interface U2 of T [2]. The service primitive is a standard under the layer to be tested, for example, IS of ISO.
(International Standard). In addition, Start (argument), Cancel for timer operation
There is (argument), and the type of timer is described as an argument. Another description is Timeout.

Further, in the column of the judgment result 102, the judgment results (Pass (pass), (Fail), (Inco
nc (indeterminate)). The operation description is described with an indent according to the time sequence in which the test event used for the test is executed. And if there can be more than one event at the same time,
Write multiple events at the same indent position.

Here, 100 is an abstract test case of the entire test system, 101 is a behavioral description, 102 is a determination result, 103 is a description of the operation content, 104 is a destination of the relevant line after separation into sub test cases, and 105 is a tester. The sub test cases for 1 [1] and 106 are sub test cases for the tester 2 [2]. The description 103 of the operation content and the destination 104 of the relevant line after separation into the sub test cases are added for the sake of explanation and may not be described in the original test case.

The method of generating each sub-test case from the abstract test case 100 of the entire test system is as follows: service primitives associated with each IUT, U1 relating to IUT [1] and U2 relating to IUT [2] in this example. , And separate for IUT [1] and IUT [2] respectively. Timer operations, in this example timer A is for IUT [1], timer B is for IUT [2], Start, Cancel, Tim
The description for eout is separated into sub test cases [1] and [2], respectively. Each separated sub-test case [1] describes the separated one without changing the original order of each line.
105 and [2] 106.

The judgment result of each sub-test case is described as it is in the original abstract test case, and all those not described in the original abstract test case in the reachable final state except timer operation are passed (Pass). ) Is added. In this example, the tester 2 sub test case [2] 10
The description of Pass (107) of No. 6 corresponds to this.

FIG. 3 is an example of an abstract test case of the entire test system according to an embodiment of the present invention. This example is IUT
A test case for establishing and releasing a transport connection (T connection) from [1] to IUT [2] is TTCN. It is described in GR.

FIG. 4 is an example in which the abstract test case of FIG. 3 according to one embodiment of the present invention is divided into sub test cases by the method shown in FIG. In this example, TTCN. An unnatural description appears as the GR description. In the sub test case [1] for tester 1, the Timeout event is 10
It is repeated as indicated by 7,108. Timeo
The ut event is not repeated because it is an event "The timer is reset at the same time as the timer times out." Also, in the tester 2 sub-test case [2], blocks of exactly the same event appear on the same indent as shown by 109 and 110. In other words, the event block 110 is an extra description.

FIG. 5 is an example in which the sub-test case of FIG. 4 according to an embodiment of the present invention is modified. That is, in FIG. 4, from the behavioral description of the sub test case [1] for the tester 1 to T
The time out events 107 and 108 are deleted, and the event block 110 is deleted from the behavioral description of the sub test case [2] for the tester 2.

FIG. 6 is a block diagram of an abstract test case dividing device according to an embodiment of the present invention. 70 in the figure
Is TTCN. Abstract test cases of the entire test system described in GR, 71 is tester information, 80 is an abstract test case dividing device, 81 is an event interpreting unit, 82a and 82b are tester [1] and [2] event extracting units, and 83a and 83b. Is St
art-received event related interpretation unit [1], [2], 84
a and 84b are indent changing parts [1], [2], 85
a and 85b are the same indent event inspection / deletion units [1] and [2], 86a and 86b are Timeout event inspection and deletion units [1] and [2], and 87a and 87b are determination result inspection and addition units [1]. , [2], 88a, 88b are sub-test case inspection parts [1], [2], 89a, 89b.
Are sub-test case output units [1], [2], 90a, 90
b is an abstract test case for testers [1] and [2], 91a,
91b are test case errors [1] and [2].

TTCN. The abstract test case 70 of the entire test system described in GR is input to the abstract test case dividing device 80, and first, the event interpreting unit 81 uses tester information (PCO name / timer type used in each tester) 71 to tester [1] event. , Tester [2] event.
From the output, the tester [1], [2] event extraction unit 82
a and 82b extract only the tester [1] and [2] events, and the Start-received event-related interpretation unit [1],
[2] Send to 83a and 83b. Start-Reception event related interpreting units [1], [2]
The received event corresponding to the art event is inspected, and based on the result, the indent replacement units [1], [2] 8
The indentation is changed at 4a and 84b. Same indent event inspection / deletion unit [1], [2] 85a, 85
In b, the same indent event is inspected, and if the same event is detected, the subsequent event is deleted. Also, Ti
meout event inspection / deletion unit [1], [2] 86
In a and 86b, the Timeout event is inspected, and when the Timeout event is repeated, the subsequent event is deleted. For the output, the determination result inspection / addition units [1], [2] 87a, 87b inspect the determination result, and among the final reception events excluding the Timeout event, the temporary "P" for the event without "Pass" determination.
"ass" determination is added.

After the above operation is completed, the sub test case inspection units [1], [2] 88a, 88b inspect the sub test case, and if there is no abnormality, the sub test case output units [1], [2]. 89a and 89b allow the tester [1],
It is output as the abstract test cases 90a and 90b for [2]. If there is an abnormality, test case error [1],
[2] Output 91a and 91b.

FIG. 7A shows an example of the tester information 71 shown in FIG. Based on this information, the abstract test case of the entire test system is divided for each tester. FIG. 7B shows the Start of FIG.
-Reception event-related interpretation unit [1], [2] 83a, 83
It is a processing flow of b. Here, the reception event corresponding to each Start event is detected, and when a plurality of events correspond, those events are detected as the same indent reception event.

FIG. 8 shows the indent replacement unit [1] of FIG.
[2] It is a processing flow of 84a, 84b. here,
Start-Reception event related interpretation unit [1], [2] 8
The indent is changed according to the same indent reception event detected in 3a and 83b. Indents are added one character at a time starting from the first event, and if there are events with the same indent, those indents are aligned and the indents of subsequent events are replaced.

FIG. 9 is a processing flow of the judgment result inspection / addition unit [1], [2] 87a, 87b of FIG. Here, a provisional "Pass" determination is added to a test case that does not have a "Pass" determination. The judgment result of the final reception event excluding the Timeout event of the test case without the "Pass" judgment is inspected, and all judgments are "Fail"
If so, the previous reception event is inspected. If all the judgments are not "Fail", the "Pass" judgment is added to all reception events other than "Fail".

FIG. 10 is a processing flow of the sub test case inspection units [1], [2] 88a, 88b of FIG. In the indent inspection, it is inspected whether or not the indent is correctly added, and if it is not correct, the processes from the indent replacement units [1], [2] 84a, 84b are re-executed. In the same indent check, it checks whether there is a contradictory description in the same indent, and if it is incorrect, it is output as an abstract test case error. In the timer check, check whether there is any inconsistency in the description of the timer event, and if it is not correct, output it as an abstract test case error. In the judgment result check, check whether the judgment result is given correctly. Inspection / addition unit [1],
[2] The processes from 87a and 87b are re-executed.

[0027]

As described above, according to the present invention, TT
CN. By automatically dividing the abstract test case of the entire test system described in GR for each tester, it is possible to effectively provide a test case that can be used in the interconnection test apparatus.

[Brief description of drawings]

FIG. 1 is a block diagram showing an interconnection test system according to an embodiment of the present invention.

FIG. 2 is an explanatory diagram showing an example of a method of dividing an abstract test case according to an embodiment of the present invention.

FIG. 3 is a configuration explanatory diagram showing an example of an abstract test case of the entire test system according to an embodiment of the present invention.

FIG. 4 is a structural explanatory view showing an example in which the abstract test case of FIG. 3 according to an embodiment of the present invention is divided into sub test cases by the method shown in FIG.

5 is a configuration explanatory view showing an example in which the sub-test case of FIG. 4 according to an embodiment of the present invention is modified.

FIG. 6 is a block diagram of an abstract test case dividing device according to an embodiment of the present invention.

FIG. 7 is a configuration explanatory diagram showing an example of tester information according to an embodiment of the present invention and a flowchart showing a processing flow of a Start-received event related interpretation unit.

FIG. 8 is a flowchart showing a processing flow of an indent replacement unit according to an embodiment of the present invention.

FIG. 9 is a flowchart showing a processing flow of a determination result inspection / addition unit according to an embodiment of the present invention.

FIG. 10 is a flowchart showing a processing flow of a sub test case inspection unit according to an embodiment of the present invention.

[Explanation of symbols]

10 ... TTCN. Abstract test case of the entire test system described in GR, 11 ... Abstract test case dividing device, 12a ... Sub test case [1] for tester [1], 12b ... Sub test case [2] for tester [2], 13a ... Compatibility test suite creation device [1], 13b ... Compatibility test suite creation device [2], 20 ... Test manager, 21 ... Execution type result judgment table, 22 ... Judgment result output, 23 ... Result judgment table, 24a ... Communication Section [1], 24b ... communication section [2], 30a ... tester [1], 30b ... tester [2], 31a ... executable sub test case [1], 31b
... Execution type sub test case [2], 32a ... Timer A, 3
2b ... timer B, 40a ... IUT [1], 40b ... IU
T [2], 50 ... Lower layer, 60 ... Test channel, 7
0 ... TTCN. Abstract test cases of the entire test system described in GR, 71 ... Tester information, 80 ... Abstract test case dividing device, 81 ... Event interpretation unit, 82a ... Tester [1] event extraction unit, 82b ... Tester [2] event extraction unit , 8
3a ... Start-interpretation unit related to received event [1], 8
3b ... Start-Reception event-related interpretation unit [2], 8
4a ... Indent replacement unit [1], 84b ... Indent replacement unit [2], 85a ... Same indent event inspection / deletion unit [1], 85b ... Same indent event inspection / deletion unit [2], 86a ... Timeout check Delete unit [1], 86b ... Timeout event check / Delete unit [2], 87a ... Judgment result check / Addition unit [1], 87b
... Judgment result inspection / addition unit [2], 88a ... Sub test case inspection unit [1], 88b ... Sub test case inspection unit [2], 89a ... Sub test case output unit [1], 89b
... Sub test case output unit [2], 90a ... Tester [1] abstract test case, 90b ... Tester [2] abstract test case, 91a ... Test case error [1], 91b ...
Test case error [2].

Claims (1)

[Claims] 1. OSI (Open Systems Interconnectio)
n) TTCN.2 used in the interconnection test system for testing the interoperability of the (N) service between the two (N) layer protocol implementation information communication terminals of the reference model. GR (Tree a
nd Tabular Combined Notation, Graphical Form; ISO / IE
In the abstract test case dividing device that divides the abstract test case for the entire test system described in C9646) for each tester, the method to change the indent without changing the order of the generated events and the event generated in the same indent. A means to detect unnecessary events and delete them, and a temporary "pass" for the test cases without "pass" judgment.
And a means for adding the determination of 1. to the abstract test case dividing device.