JPH03216739A - Random execution system for test item - Google Patents

Abstract

PURPOSE:To easily execute a systematic error detection by imparting an execution ID to a test unit, registering the execution ID in a sequential, random or a designated order into an execution order registration table, and referring to this for the repeated execution of an applicable test unit. CONSTITUTION:Corresponding to a mode designation, the execution ID which is random, sequential or designated is registered to an execution order registration table 3. When testing, the execution ID is taken out from this execution order registration table 3, a unit table 2 is referred, the execution of an applicable test unit 1 is repeatedly executed, and the testing of a device to be tested is executed. Thus, the systematic error detection can be executed easily by executing the test with many combination orders. etc.

Description

[Detailed Description of the Invention] [Summary] Regarding the random execution method for randomly executing tests on test items, Execute on test units! Sequential by adding D,
Register the execution ID in the execution order registration table using a random number or a specified order, refer to this and repeatedly execute the corresponding test unit, perform tests in many combination orders, etc. to detect errors system-wide. With the aim of making it possible to perform A random number, sequential, or specified execution ID is registered in the execution order registration table according to the mode specification, and the execution order is registered from this execution order registration table at the time of testing. The configuration is configured so that the device under test is tested by extracting the above UniSoto table and re-executing the corresponding test UniSoto. [Industrial Application Field] The present invention relates to a random execution method for randomly executing tests on test items. [Prior Art and Problems to be Solved by the Invention] Conventionally, a test program for testing a development device (device under test IF) is run in the test uninote 2l in the order registered in advance in the unisoto table 22, as shown in FIG. are executed sequentially to test the corresponding test items one by one. In this way, the test units 12 were executed in a fixed order in the order registered in advance in the test unit 21, so for example, the first test unit, area X, was used, and then the second test unit used the same area When using , there is a problem with the first post-processing and an error occurs.
When tests depend on relationships, there is a problem in that errors cannot be detected if tests are performed sequentially and in a fixed order. The invention is carried out to test Unisoto! D is added and real 1 test ID is registered in the execution order registration table in sequential, random number, or specified order, and by referring to this, the corresponding test unit is repeatedly executed, and tests are performed in many combination orders. The purpose is to easily detect errors systematically. [Means for solving the problem] Means for solving the problem will be explained with reference to FIG.

In FIG. 1, test unit 1 is a unit that tests test items on the device under test. Unit table 2 is a table that stores execution IDs assigned to test units 1. The execution order registration table 3 is a table in which the execution order of the execution IDs stored in the unit table 2 is registered. r effect] As shown in FIG. 1, the present invention can perform random number, sequential, or specified execution in response to mode specification! Register D in the execution order registration table 3 and execute from this execution order registration table 3 during testing! D is taken out, the test unit 1 is repeatedly executed by referring to the unit table 2, and the device under test is tested. Therefore, by assigning an execution ID to a test UNISOTO, registering the execution ID in the execution order registration table using a sequencer, random number, or specified order, and repeatedly executing the corresponding test UNISOTO by referring to this, it is possible to create a large number of combinations. It becomes possible to easily detect errors systematically by testing in order. [Embodiment] Next, the configuration and operation of an embodiment of the present invention will be explained in detail using FIGS. 1 to 5. In Figure 1,
The test unit 1 is a unit that tests test items on the device under test, and includes an initial setting processing unit that performs initial settings, a test unit that tests various test items, and a test unit that performs The unit table 2 is a table that stores the execution 10 assigned to the test unit L and the address (start address) of the test unit 1 in association with each other. The order registration table 3 is a table for registering the execution order for the execution IDs stored in the unit table 2, and is a table for storing execution IDs in sequential, random number, or specified order.Here, test unit 1 If there is something that must be executed first when executing (for example, if there is an initialization processing section)
, this is fixedly registered at the beginning, etc., and the execution is generated using random numbers only for the other test unit 10 execution IDs! Restrict to registering D. Execution order setting processing unit 4
is to set the execution It) in the execution order registration table 3 as sequential, random number, and specified order. The control unit 5 performs various controls. FIG. 2 shows an example of a uninote table according to the present invention. Here, run I
D is an identifier given to the test unit 7 as described above. The Unisoto address is the start address of the corresponding test unit 1. The test item name is the name of the test item on which the execution ID test unit tests the device under test. As shown in execution ID 3, storing the addresses of two units in one execution ID is 1.
There are test units that must be executed together when executing one test unit, so these are executed together. FIG. 3 shows an example of an execution order registration table according to the present invention. Here, the number of tests is the number of times the test is performed,
The test is created up to the number of times specified in advance by the tester (it is created up to the number of tests corresponding to the number of repetitions entered in Figure 4 @). The execution order is registered in the mode specified by the test taker.
The example in the figure is when random number mode is specified (see Figure 4 [Phase]
), the first time is registered sequentially, and from the second time onwards, the first 1 (execution IDI, first a
Setting processing section) and using random numbers, set as shown. In addition, in the case of sequential mode, settings are made for the second and subsequent times in the same order of execution ID as the first time. In addition, in the case of specified mode (when attempting to re-authorize by repeatedly executing in the order in which errors were detected),
Set the specified number of times to repeat. Also, the presence or absence of an error indicates whether or not an error was detected as a result of testing by executing the test unit corresponding to the execution ID in the order of the first, second, third, etc. It is something. Next, the operation of the configuration shown in FIG. 1 will be explained in detail using the flowchart shown in FIG. In Fig. 4, ■ is the initial setting. ■Enter the number of repetitions. The tester registers this in the execution order registration table 3 in the system and inputs the number of times to repeat the test for the VTT to be tested. 0 enters the execution mode. Then, the tester specifies the execution mode by inputting one of the following numbers: 1: sequential 22 random (random number) 3: operator input. [phase]
determines whether the number of repetitions has been satisfied. This determines whether or not the steps after ■ have been repeated for the number of repetitions input in ■.If YES, it ends (E
ND). If No, execute ■. [Phase] executes UniSoto. This executes one test unit 1 registered in the execution order registration table 3 according to the flowchart in FIG. 5, which will be described later. [Phase] determines whether the test mode is 1, 2, or 3. O is a process to be executed when the test mode is "l" (sequential), which refers to Uninote table 2, stores it in an array, and sets the execution order (Unit table 2 which is the contents of the array) in [Stock]. The order of execution!D stored in ) is registered in the execution order registration table 3. This results in
In the execution order registration table 3, the execution IDs are stored in the order stored in the Unisoto table 2.
It will be registered in 0 is the process to be executed when the test mode is "2" (random, random number), which generates random numbers, stores the random numbers in an array with [phase], and sets the execution order (array contents) with [stock]. (order of random number execution ID) is registered in the execution order registration table 3. As a result, in the execution order registration table 3,
Run in random order! D will be registered in the execution order registration table 3. ■ is the process to be executed when the test mode is "3" (operator input). Enter the number of months, and use @ to check whether the input is 0 (zero, displaying the history of execution order layers up to the previous time). If YES, display the registration table (contents of execution order registration table 3) with [Phase] and exit; if No, press O to refer to the registration table and store it in the array, and press [Phase]. ] to register the execution order (the order of the execution IDs specified by the operator) in the execution order registration table 3. As a result, the execution TDs are registered in the execution order registration table 3 in the order of the same number of executions specified by the operator]D. As mentioned above, in response to specifying sequential, random (random number), or operator input depending on the execution mode, execute in this order in the execution order registration table 3! D, and execute the test unit l in the order of the registered execution ID to test the device under test 1.
By detecting an error, there are sequential tests in a fixed order, tests in a random number order that systematically detects errors, and operator input that repeats and confirms the number of times an error was detected when an error is detected. Test the device under test by a
It becomes possible to efficiently and systematically detect errors that occur due to combinations without missing detection. FIG. 5 shows a flowchart of the test unisoto execution of the present invention. This shows the unit execution process in Figure 4 (■). In FIG. 5, [phase] determines whether the unit is finished or not. This determines whether or not all executions of the corresponding test unit 1 have been completed for one execution ID registered in the execution order registration table 3 in FIG. YES
In this case (when all executions of Test Unisoto 1 for one execution ID have been completed), EXIT is executed (finish the step ■ in Figure ↓ and execute the next [phase]). If No {if the execution of the test unit l with the execution ID for one run has not finished}, perform the steps after [stock]. ■ refers to the registration table and extracts the execution ID number; @ executes the unit. These [phase] and [share] are, for example, taken out from the execution order registration table 3 in FIG.
Execute and test the applicable test items of the device under test. [Phase] determines whether or not there is an error, YF. In the case of S, press ■ to display the error message, and press [Stock] to display the registration table (
Display the contents of execution order registration table 3) and exit (
END). On the other hand, if No, repeat [phase]. Through the above processing, the execution IDs of the predetermined number of times registered in the execution order registration table 3 are taken out one by one from the beginning, the corresponding test unit 1 is executed, and the device under test is tested to detect errors. This makes it possible to efficiently and systematically detect errors in the 100 execution orders specified in the execution order registration table 3 by sequential, random, or operator input through simple operations. [Effects of the Invention] As explained above, according to the present invention, the test unit l is executed! Add D and execute sequentially, randomly or in a specified order! D is registered in the execution order registration table 3, and the corresponding test unit 1 is repeatedly executed with reference to this, so the system can be tested by testing the device under test in many combinations of test items. Error detection can be done with simple operations. This makes it possible to detect failures related to error post-processing, area initialization, etc. with high accuracy in a system with simple operations, especially in abnormal system tests.

[Brief explanation of drawings]

FIG. 1 is a configuration diagram of one embodiment of the present invention, FIG. 2 is an example of a unit table according to the present invention, FIG. 3 is an example of an execution order registration table according to the present invention, and FIG. 4 is a flowchart explaining the operation of the present invention. FIG. 5 shows a test unisoto execution flowchart of the present invention, and FIG. 6 shows an explanatory diagram of the prior art. In the figure, l is a test unit, 2 is a unit table, and 3 is a test unit.
4 represents an execution order registration table, and 4 represents an execution order setting processing unit.

Claims (1)

[Claims] In a random execution method that randomly tests test items, there is provided a test unit (1) that tests a test item on a device under test, and an execution ID assigned to this test unit (1). A unit table (2) to store and an execution order registration table (3) to register the execution order for the execution IDs stored in this unit table (2).
), and registers a random number, sequential, or specified execution ID in the execution order registration table (3) above according to the mode specification, and extracts the execution ID from this execution order registration table (3) at the time of testing and executes the above execution ID. A method for randomly executing test items, characterized in that a device under test is tested by repeatedly executing the corresponding test unit (1) with reference to a unit table (2).