JP2010262376A - Test distribution method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To equalize the labors of an operator by rearranging a plurality of test cases by test execution conditions when executing a test by a plurality of operators. <P>SOLUTION: In a test distribution device 1, one test object test case stored in a test case table 300 is classified into a system test case and a non-system test case based on an execution test condition table 500. Then, the test case is classified according to a test execution priority order into a test case whose test execution priority is high, a test case whose test execution priority is low, and the other test cases based on test order condition tables 600/700. Then, on the basis of a test execution standard time table 800 and a test switching operation time table 900, the system test case or the non-system test case is distributed to operators whose number is specified in a test execution condition table 400 so that the test execution time or labors are made uniform for each classification corresponding to each test execution priority order. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to a method for creating a test item list when software is operated on a computer to test a device (hereinafter referred to as a software test, and a device to be tested is referred to as a device to be tested). It is related with the test distribution method at the time of carrying out the scheduling which can perform the test of such a test object apparatus efficiently.

  In software testing, it is necessary to efficiently digest multiple test cases within a limited period. Therefore, it is effective to use a test combination generation tool that reduces the number of test cases while ensuring the completeness of the test cases for the test target device. As typical tools, an orthogonal table (Non-patent Document 1) and an All-Pair method (Patent Document 1) are used.

  Non-Patent Document 1 describes a method for effectively extracting test items from the total number of test items. Patent Document 1 describes a table creation device that can easily create a test item list even when a test item list is recreated a plurality of times.

  For example, software test items when an embedded device is used as a test target device are classified into two types: a real machine test using an actual machine or prototype hardware, and a non-real machine test using a development environment or simulator on a personal computer. Sometimes.

  And since the cost of the actual equipment used for testing is high, there are many cases where there are few actual machines that can be secured for testing. Therefore, it is necessary to avoid the duplication of the use of actual machines among workers and to be able to carry out efficiently.

JP 2008-209993 A Masaaki Akiyama “Efficient software testing using orthogonal tables” [online] July 15, 200 [Search October 29, 2008], Internet <UTR: http://jasst.jp/archives/jasst05w/ pdf / S4-1.pdf>

  However, since the output test cases do not take into consideration that the actual machine tests do not overlap among a plurality of workers, they have been rearranged manually. This manual rearrangement has a problem that it takes time to test because the number of test cases to be output is large, and further, it is difficult to guarantee the accuracy due to manual work.

  The purpose of the present invention is to eliminate such problems and to sort the test cases according to the test execution conditions when testing by a plurality of workers, and to equalize the workload of the workers and the time required for the tests. It is to provide a test distribution method that makes it possible.

  In order to achieve the above object, the present invention relates to a device to be tested, and relates to a test distribution method for distributing a plurality of test cases set for testing to a plurality of workers. Are classified into real test cases that are tested using actual machines and non-real machine test cases that are tested without using real machines, and the test execution priority is assigned to each of the actual test cases and non-real machine test cases. A second step of classifying into a corresponding group, and a third step of determining a test case to be assigned to each worker for each group classified in the second step with respect to the actual machine test case and the non-real machine test case; The fourth process distributes the test cases assigned in the third process to the respective workers.

  Further, according to the present invention, each test case is composed of a combination of a plurality of factor values, and each test case has a different combination of factor values, and the first step requires an actual machine for the test. Based on the actual machine test condition table that specifies the value of the factor to be used, classify the test cases having the value of the factor that requires the actual machine test, which is a test using the actual machine, into the actual machine test case table as an actual machine test case, Other tests are classified as non-real machine tests, and non-real machine test cases are classified as non-real machine test cases in a non-real machine test case table.

  In the present invention, the second step is a test table having a high execution priority as a test order condition table in which values of factors having a high test execution priority are defined, and a factor value having a low test execution priority. Based on the test order table with low execution priority as the test order condition table that stipulates the test order condition table, execution priority is given to the real machine test cases that have the factor values specified in the test table with high execution priority in the real machine test case table Classify actual test cases with higher ranks, classify actual test cases with factor values specified in test tables with lower execution priorities into actual test cases with lower execution priorities, and do not match test order condition tables Classifying test cases into real machine test cases with medium execution priorities, real machine test case tables with high execution priorities, real machine test case tables with low execution priorities, The non-real machine test cases that are stored in the real machine test case table that does not correspond to the strike order condition table and have the values of the factors specified in the test table with the high execution priority in the non-real machine test case table have the execution priority Classify as non-real machine test cases, classify non-real machine test cases with factor values specified in test table with low execution priority as non-real machine test cases with low execution priority, and do not hit test order condition table Categorize non-real machine test cases into non-real machine test cases with medium execution priority that do not match the test order condition table, and non-real machine test cases with high execution priority and non-real machine test cases with low execution priority And a non-real machine test case table that does not correspond to the test order condition table.

  Further, according to the present invention, the third step is a test execution standard time table that defines a test execution standard time for a real machine test and a test execution standard time for a non-real machine test, and a test switching operation time between values of the same factor. Based on the test switching operation time table that stipulates, the actual machine test case table with high execution priority, the real machine test case table with low execution priority, and the real machine test case table that does not correspond to the test order condition table Actual test cases for each non-real machine test case table that sets the test execution time of the case and has a high execution priority, non-real machine test case table with low execution priority, and non-real machine test case table that does not fall under the test order condition table The test execution time is set.

  In addition, the test execution time is an added value of the test execution standard time of the actual machine test and the test switching operation time for the actual machine test case.

  In addition, the fourth step is the test execution time of the actual machine test case for each of the actual machine test case table having a high execution priority, the actual machine test case table having a low execution priority, and the actual machine test case table not corresponding to the test order condition table. Non-real machine test case table with high execution priority, with real machine test cases distributed to each worker according to test allocation execution time per worker calculated from total test execution time, with total as total test execution time For each non-real machine test case table that does not correspond to the non-real machine test case table and the test order condition table with low execution priority, the total test execution time is calculated from the total test execution time as the total test execution time. Non-real machine test cases are distributed to each worker according to the test allocation execution time per worker. A non-actual test cases, and storing, in the output table after test case distribution of workers applicable.

  Further, the present invention is characterized in that the distribution of the test cases to the output table after the distribution of the test cases starts from the actual machine test cases in the actual machine test case table having a high execution priority.

  Further, according to the present invention, when the number of actual machines is m and the number of workers is n (where m <n) as defined in the actual machine test condition table, the output after distributing the test cases assigned to m workers. In the table, the real machine test case group distributed from the real machine test case table having the highest execution priority is stored in order, and the output table after the distribution of these test cases is the real machine test case table having the high execution priority. The real machine test cases of the real machine test case group having a high execution priority distributed in the order are stored in order from the top storage position, and then the test cases assigned to the remaining (nm) workers are distributed. In the output table, the real machine test case group distributed from the real machine test case table having the highest execution priority is stored in order, and the real machine test is immediately before the output table after the test case distribution. Characterized in that the storage of over scan group are stored from a storage position corresponding to the next storage location of the stored storage location in the actual test case group at the output table after test case distribution ended.

  According to the present invention, when a test is executed by a plurality of workers on the same test object, the test case list is rearranged according to the test execution conditions so that the utilization rate of the real machine and the non-real machine is maximized. Since the test cases are distributed to each worker, the time and burden required for the worker's test can be made uniform, and the time required for the entire test can be minimized.

FIG. 3 is a diagram illustrating an embodiment of a test distribution method according to the present invention. It is a block block diagram which shows one specific example of the test distribution apparatus as a test case rearrangement means in FIG. 1 for performing embodiment shown in FIG. It is a block diagram which shows one specific example of said value definition table for producing the test case table | surface 100 in FIG. It is a figure which shows one specific example of the test case table | surface 300 in FIG. It is a figure which shows one specific example of the test execution condition table | surface 400 in FIG. It is a figure which shows one specific example of the real machine test condition table | surface 500 in FIG. It is a figure which shows one specific example of the test table 600 with high execution priority as the test order condition table in FIG. It is a figure which shows one specific example of the test table | surface 700 with low execution priority as the test order condition table | surface in FIG. FIG. 9 is a diagram showing a specific example of the test execution standard time table 800 in FIG. FIG. 10 is a diagram showing a specific example of the test switching operation time table 900 in FIG. It is a flowchart which shows the flow of the whole test case rearrangement process of embodiment shown in FIG. 12 is a flowchart illustrating a specific example of step S100 in FIG. 11. It is a figure which shows one specific example of the real machine test case table | surface 1000 obtained by the process shown in FIG. It is a figure which shows one specific example of the non-real machine test case table 1100 obtained by the process shown in FIG. 12 is a flowchart showing a specific example of step S101 related to an actual machine test case in FIG. FIG. 16 is a diagram showing a specific example of an actual machine test case table 1200 created in step S303 in FIG. 15 and having a high execution priority. FIG. 16 is a diagram showing a specific example of an actual machine test case table 1300 having a low execution priority created in step S307 in FIG. FIG. 16 is a diagram showing a specific example of an actual machine test case table 1400 that does not correspond to the test order condition table 600/700 created in step S309 in FIG. 12 is a flowchart showing a specific example of step S101 related to a non-real machine test case in FIG. 19 is a flowchart showing a specific example of step S102 in FIG. 11 for calculating the test execution times stored in the test execution time columns 1201, 1301, 1401 in FIGS. It is a figure which shows one specific example of the output table 1500 after test case distribution for one worker in FIG. 11 distributes the real machine test cases 1202 in the real machine test case table 1200 having a high execution priority shown in FIG. 16 to the number of workers specified in the number of workers column of the test execution condition table 400 shown in FIG. It is a flowchart which shows one specific example of the process of step S103-S105. Based on the flowchart shown in FIG. 22 of the real machine test cases from the real machine test case table 1200 having a high execution priority shown in FIG. 16 and the corresponding non-real machine test cases from the non-real machine test case table having a high execution priority not shown. It is a figure which shows a distribution process and its result.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 is a diagram showing an embodiment of a test distribution method according to the present invention. 100 is a test work table, 300 is a test case table, 400 is a test execution condition table, 500 is an actual machine test condition table, and 600 is a test order. A test table with high execution priority as a condition table, 700 is a test table with low execution priority as a test order condition table, 800 is a test execution standard time table, and 900 is a test switching operation time table.

  In this figure, in this embodiment, the test work table 100 prepared for the test of the test target device is processed by the test case rearranging means, that is, the test distribution device 1 to test the test target device. A plurality of test cases of the test target apparatus are distributed to a plurality of workers to be executed, and a test case work table 1500 for each worker is created.

  That is, the test cases in the test case table 300, which is a list of a plurality of test cases created for the test of the test target device, are divided into the test execution condition table 400, the actual machine test condition table 500, and the execution priority. Test order condition table (a test table 600 having a high execution priority and a test table 700 having a low execution priority, which are collectively referred to as a test order condition table 600/700) and a test execution standard time table 1300 and the test switching operation time table 1400 are distributed to each worker who executes the test specified in the test execution condition table 400.

  Therefore, the distribution device 1 as the test case rearrangement device sorts the test cases in the test case table 300 into a test case using an actual machine and a test case using a non-real machine based on the actual machine test condition table 500. The real machine test case table 1000 and the non-real machine test case table 1100 are created, and further executed for each of the real machine test case table 1000 and the non-real machine test case table 1100 based on the test order condition table 600/700. The test cases are rearranged into a test case table 1200 having a high priority, a test case table 1300 having a low execution priority, and a test case table 1400 not corresponding to the test order condition table. 1000, test order table 1100 having a low execution priority, and test order condition table The test case table 1200 each test case that does not, and performs reordering to assign is the per worker tests specified in Test Requirements table 400. As a result, an output table 1500 of test cases assigned for each worker is obtained.

  The actual machine test is a test of the test target apparatus performed using the test target apparatus itself or a prototype (prototype hardware) of the apparatus, and the non-real machine test is a test of the test target apparatus on a personal computer. This is a test of the test target device performed using a development environment or a simulation. Usually, a non-real machine test is performed. If this cannot be performed smoothly, a real machine test is performed.

  In addition, there are various methods (test methods) for testing the device. Each of these methods is called a test case. Usually, a plurality of test cases are set for testing the same test target device. When multiple workers perform multiple test cases set on the same test target device, each of these workers is given a test case mainly, so that the burden on these workers and the time required for the test are equalized. The main object of the present invention is to create a test case output table 1500 for each worker distributed in this way.

  FIG. 2 is a block diagram showing a specific example of the test distribution device as the test case rearranging means in FIG. 1 for executing the embodiment shown in FIG. Central processing unit: 3 is a main storage device, 4 is an external storage device, 5 is a reading device, 6 is an input / output device, 7 is a communication device, and 8 is a portable storage medium.

  In this figure, the test distribution device 1 includes a CPU 2, a main storage device 3, an external storage device 4 such as an HDD (hard disk drive), and a portable portable storage medium 8 such as a CD-ROM or DVD-ROM. It comprises a general computer equipped with a reading device 5 for reading information, an input / output device 6 such as a display, a keyboard, a mouse, and a printer, and a communication device 7 such as a NIC (Network Interface Card) for connection to a communication network. Is.

  The test case table 300 of the test target device in FIG. 1 is created by the CPU 2 and stored in the external storage device 4 under the operation of the input / output device 6 by the operator. The test case table 300 is created by processing of the CPU 2 in accordance with an operator's instruction input operation on the input / output device 6 based on a value definition table 200 described later set for each test target device.

  In addition, in order to create the test case output table 1500 for each worker for this test target device, the test execution condition table 400 created by another device and stored in the portable storage medium 8 or the actual machine test The condition table 500, the test order condition table 600/700, the test execution standard time table 800, and the test switching operation time table 900 are read by the reading device 5 and stored / saved in the main storage device 3.

  Thereafter, under the operation of the input / output device 6 by the operator, the CPU 2 reads the test case table 300 from the external storage device 4 and stores the test execution condition table 400 and the actual machine test conditions stored in the main storage device 3. Using the table 500, the test order condition table 600/700, the test execution standard time table 800, and the test switching operation time table 900, the test case rearrangement process is performed in the test case table 300, and the test for each worker is performed. Case distribution processing is performed to create a test case output table 1500 for each worker. The generated test case output table 1500 is displayed on the display of the input / output device 6 or printed by a printer.

  Next, this embodiment will be described in detail.

  FIG. 3 is a block diagram showing a specific example of the above value definition table for creating the test case table 300 in FIG. 1, wherein 200 is a value definition table, 201 is a factor column, and 202 is a value column. .

  In the figure, a value definition table 200 defines the values of factors used in the test case. The factor column 201 defines the factors that form the test case of the test target device. Possible values are specified.

  Here, the “factor” is a parameter of the test case, and is information for giving an operating condition of the program when testing. For example, if a printer is taken as an example of the test target device, factors include output paper size, paper orientation, output color, printing method, page layout, and the like.

Also, the “value” is a value that can be taken by a factor, and when a printer is taken as an example of a test target device,
The value of the factor “output paper size” is the paper size A4, A5, B4, B5, A3.
The value of the factor “paper direction” is the vertical direction, which is the print direction, the value of the factor “output color” is black and white, color, gray scale The value of the factor “printing method” is single-sided printing, double-sided printing factor “1 page The value of “Layout” is 1 page, 2 pages,
That means 4 pages and 8 pages.

  In the factor column 201, information (variable names) for identifying factors is set as “factor A”, “factor B”, “factor C”,... Necessary for the test, and in the value column 202, The values are set for each of these “factor A”, “factor B”, “factor C”,. For example, in the case of “Factor A”, the values are a1, a2, a3,..., And in the case of “Factor B”, the values are b1, b2, b3,. Note that the number of values set in the factor depends on the factor and varies.

  The value definition table 200 is stored in the external storage device 4 of the test distribution device 1 (FIG. 2), and the CPU 2 displays the screen on the display in accordance with an instruction operation by the operator at the input / output device 6. Through this process, the test case table 300 (FIG. 1) is created based on the test case generation method such as the orthogonal table or the All-pair method. The created test case table 300 is stored in the main storage device 3 in the test distribution device 1.

  4 is a diagram showing a specific example of the test case table 300 in FIG. 1, in which 301 is a test case column, 302a, 302b, 302c,... Are factor columns, and 303a to 303i are test cases.

  In the figure, a test case table 300 is created based on the value definition table 200 (FIG. 3) and shows a list of test cases 303a to 303i. Here, these test cases 303a to 303i are: The All-pair method disclosed in the above-mentioned Patent Document 1 is used, and is created so that the two factors of the value definition table 200 are covered.

  Test cases 303a to 303i have a test case number column 301 and factor columns 302a, 302b, 302c,. The test case numbers assigned to the test cases are set in the test case number column 301, and the factor columns 302a, 302b, 302c,. For example, the factor column 302a contains the selected value of factor A in the value definition table 200, the factor column 302b contains the selected value of factor B in the value definition table 200, and the factor column 302c contains the value definition. The selected value of the factor C in the table 200 is set in the factor column 302d, and the selected value of the factor D in the value definition table 200 is set. The same applies hereinafter.

  Here, when creating a test case from the value definition table 200 based on the test case generation method such as the All-pair method in Patent Document 1 above, it is created so that the two factors in the value definition table 200 are covered. In this case, these two factors are designated as factors A and B, and in the value definition table 200 shown in FIG. 3, the value of factor A is three as a1, a2 and a3 as shown in the figure. If there are three values of B1, b2, and b3, these two factors A and B are covered by obtaining all combinations of these values a1, a2, and a3 and values b1, b2, and b3. Therefore, nine test cases 303a to 303i from test case number 1 to test case number 9 are created as test cases to be created.

  According to the example shown in the figure, the test case 303a with the test case number 1 has a value a1 as a factor A and a value b1 as a factor B, a value c3 as a factor C, and a value d2 as a factor D, respectively. Yes. That is, the test case 303a is composed of a factor A having a value a1, a factor B having a value b1, a factor C having a value c3, and a factor D having a value d2. The same applies to the other test cases 303b to 303i.

  FIG. 5 is a diagram showing a specific example of the test execution condition table 400 in FIG. 1, wherein 401 is a real machine number column, 402 is a non-real machine number column, and 403 is an operator number column.

  In this figure, a test execution condition table 400 is a table that defines the number of actual machines to be used, the number of non-real machines, and the number of workers performing the test, with respect to tests to be performed on the test target apparatus to be used for testing. A number column 401, a non-real machine number column 402, and a worker number column 403 are provided.

  For example, here, the actual machine number column 401 stores the actual machine number used for the actual machine test using the actual machine or the prototype hardware as, for example, “one”. In the non-real machine number column 402, the number of non-real machines used for the non-real machine test performed in the development environment on the personal computer or in the simulator is stored as, for example, “three”. In the number of workers column 403, the number of workers performing the test is stored as, for example, “3 people”.

  FIG. 6 is a diagram showing a specific example of the actual machine test condition table 500 in FIG. 1, in which 501 is an actual machine information column, 502 is a factor column, and 503 is a value column.

  In the figure, an actual machine test condition table 500 is a table showing factors that require an actual machine test among the factors defined in the factor column 201 of the value definition table 200 (FIG. 3). A real machine information column 501, a factor column 502, and a value column 503 are created.

  The actual machine information column 501 stores information on the actual machine used for the actual machine test (for example, the name and ID of the actual machine), and the factor column 502 includes the factors defined in the value definition table 200. The name of the factor that requires the actual machine test is stored, and the value column 503 stores a value necessary for the actual machine test for the factor stored in the factor column 502.

  The test case 303 in the test case table 300 having the value stored in the value column 503 is tested with an actual machine.

  Here, as an example, values C1 and C2 of the factor C are stored. In this case, an actual machine test is required for the values C1 and c2 of the factor C.

  FIG. 7 is a diagram showing a specific example of the test table 600 having a high execution priority as the test order condition table in FIG. 1, in which 601 is a factor column and 602 is a value column.

  In the figure, a test table 600 having a high execution priority is a table showing values of factors having a high execution priority of tests among the factors stored in the value definition table 200 (FIG. 3). 601 and a value column 602 are provided.

  The factor column 601 stores a factor having a high test execution priority among the factors defined in the value definition table 200, and the value column 602 stores the factor for each factor stored in the factor column 601. A value having a high test execution priority is stored. Among the test cases 303 in the test case table 300, the test case 303 having a factor value whose value is stored in the value column 602 of the test table 600 having a high execution priority is a test case having a high test execution priority. It turns out that.

  Here, as an example, the value al of the factor A is stored, and the test case 303 having the factor A having the value a1 is a test case having a high test execution priority.

  Note that test cases with a high execution priority include test cases for which the test results are desired to be obtained quickly, and test cases that need to be performed first before executing the tests.

  FIG. 8 is a diagram showing a specific example of the test table 700 having a low execution priority as the test order condition table in FIG. 1, wherein 701 is a factor column and 702 is a value column.

  In the figure, a test table 700 having a low execution priority is a table that represents the values of factors having a low test execution priority among the factors stored in the value definition table 200 (FIG. 3). 701 and a value column 702 are provided.

  In the factor column 701, factors having a low test execution priority among the factors defined in the value definition table 200 are stored, and in the value column 702, each factor stored in the factor column 701 is stored. A value with a low test execution priority is stored. Among the test cases 303 in the test case table 300, the test case 303 having a factor value whose value is stored in the value column 702 of the test table 700 having a low execution priority is a test case having a low test execution priority. It turns out that.

  Here, as an example, the value b2 of the factor B is stored, and the test case 303 having the factor B of the value b2 is a test case having a low test execution priority.

  Test cases with low test execution priority include tests with low necessity for test execution, test cases that do not need to know the results quickly, and test cases with functions that are not very important or rarely used. .

  As described above, the test case 303 having the value factor stored in the test table 600 having a high execution priority is set as a test case having a high test execution priority, and is stored in the test table 700 having a low execution priority. A test case 303 having a factor with a certain value is a test case with a low execution priority of the test, and a test with a value factor stored in the test table 600 having a high execution priority and a low execution priority. A test case 303 that does not have any of the value factors stored in the table 700 is a test case that does not correspond to the test order condition table (medium execution priority of the test).

  FIG. 9 is a diagram showing a specific example of the test execution standard time table 800 in FIG. 1, in which 801 is a real machine test standard time column and 802 is a non-real machine test standard time column.

  In the figure, a test execution standard time table 800 is a table showing standard test execution times for real machine tests and non-real machine tests, and includes a real machine test standard time field 801 and a non-real machine test standard time field 802. Here, the test execution standard time is an average execution time of the test execution times of the real machine test or the non-real machine test.

  The real machine test standard time column 801 stores a standard time for executing the real machine test, and the non-real machine test standard time column 802 stores a standard time for executing the non-real machine test. Here, as an example, “30 seconds” is set in the actual machine test standard time field 801, and “10 seconds” is set in the non-actual machine test standard time field 802.

  FIG. 10 is a diagram showing a specific example of the test switching operation time table 900 in FIG. 1, in which 901 is a factor column, 902 is a value column, 903 is a factor column, 904 is a value column, and 905 is a test switching operation time column. It is.

  When testing a test target device, a plurality of test cases set in this are sequentially tested by the operator's operation, but the test is completed from the test case (hereinafter referred to as the preceding test case) to the next test. When a test is switched to a test of a case (hereinafter referred to as a subsequent test case), if the preceding test case and the subsequent test case have the same factor, the operation performed by the operator if the values of these factors are the same Although there is no change, if there is a difference in the value of the factor, the operator needs to perform an operation for that, and operation time is required for switching the test for the factor. For example, the preceding test case has a factor A having a value a1 (for example, the output paper size A4 by taking the previous printer as an example), and the subsequent test case in which the test is performed subsequently has the same factor A value. Assuming that a1 (output paper size A4), in this case, the factor A can be kept in the same state as the preceding test case with respect to the subsequent test case, and the operator does not need to change the factor A. On the other hand, for example, when the value of the factor A of the preceding test case is a1 (output paper size A4) and the value of the factor A of the subsequent test case is different from a2 (for example, output paper size A5), the subsequent In order to perform the test of the test case, an operator's operation is required to switch the value A1 from the value a1 to a2 (the output paper size A5 can be tested). The operator's operation time required for this switching is the test switching operation time.

  In FIG. 10, a test switching operation time table 900 is a table showing a list of test switching operation times, which are operator operation times required for test switching with the same factors, and is created for each factor. The factor column 901 of the test case before the test switching operation, the factor value column 902 of the factor column 901, the factor column 903 of the test case after the test switching operation, the factor value column 904 of the factor column 903, And a test switching operation time column 905. If the test operation is changed when the operator tests the next test case (that is, the value of the same factor is changed), the set time required for this test switch is set to this test switch operation. Obtained from the timetable 900.

  Here, “factor A” is shown as an example, and “factor A” is set in the factor column 901 as the factor of the test case before the test switching operation, and those values are set in the value column 902. ing. Similarly, “factor A” is set in the factor column 903 as the factor of the test case after the test switching operation, and those values are set in the value column 904. However, these factors and values are based on the value definition table 200 shown in FIG.

  In the test switching operation time column 905, the test case factor after the test switching operation for each of the values a1, a2, a3,..., An set in the factor A value column 902 of the test case before the test switching operation. The time required for the test switching operation to the respective values a1, a2, a3,... An set in the A value column 904 is stored.

  For example, the time required for the test switching operation from the value a1 of the factor A of the test case before the test switching operation to the column a2 of the factor A of the test case after the test switching operation is 10 seconds, and the test switching to the column a3 is also performed. The time required for the operation is 5 seconds. The time required for the test switching operation from the value a2 of the test case factor A before the test switching operation to the column a1 of the test case factor A after the test switching operation is 5 seconds, and the test switching to the column a3 is also performed. The time required for the operation is 7 seconds.

  If test switching of the same value of the same factor is performed in test switching from the test case before the test switching operation to the test case after the test switching operation, the time required for the test switching operation at that time is 0 second. It is. For example, the time required for the test switching operation from the value a3 of the test case A before the test switching operation to the factor a column a3 of the test case after the test switching operation is 0 second.

  In the test distribution apparatus 1 as the test case rearranging means shown in FIG. 1, the above test execution condition table 400, actual machine test condition table 500, test table 600 with high execution priority, test table 700 with low execution priority, test The execution standard time table 800 and the test switching operation time table 900 are read from the portable storage medium 8 by the reading device 5 and stored in the main storage device 3, and stored in the external storage device 4 based on these by the CPU 2. The rearrangement process of the test cases 303 of the test case table 300 being performed is performed.

  FIG. 11 is a flowchart showing the overall flow of the test case rearrangement process of this embodiment.

  In the figure, based on the real machine test condition table 500 (FIG. 6), the test cases in the test case table 300 (FIG. 4) are divided into test cases of real machine tests and non-real machine tests. In this case, the test cases 303 having the values of the factors stored in the actual machine test condition table 500 are classified as actual machine test cases (hereinafter referred to as actual machine test cases), and the other test cases 303 are non-real machine test cases. A test case (hereinafter referred to as a non-real machine test case) is classified (step S100).

  Next, the actual machines classified based on the test order condition table 600/700 (FIG. 1), that is, the test table 600 having a high execution priority (FIG. 7) and the test table 700 having a low execution priority (FIG. 8). “Test cases with high test execution priority”, “Test cases with low test execution priority”, and “Test cases that do not meet the test order condition table” The test cases are classified into the test cases corresponding to the three test order conditions (step S101).

  Then, for each condition of the real machine test case and the non-real machine test case, the test execution time is calculated based on the test case execution standard time table 800 (FIG. 9) (step S102). The test cases are distributed to all workers defined in the test execution condition table 400 (FIG. 5).

  That is, the real machine test case and the non-real machine test case having a high execution priority are distributed to all workers (step S103), and the real machine test case and the non-real machine test case that do not satisfy the test order condition are distributed to all workers. (Step S104) The real machine test cases and the non-real machine test cases having low execution priorities are distributed to all workers (Step S105).

  Thereby, an output table 1500 of the test cases for each worker is created and displayed on the display of the input / output device 6 (step S106).

  Next, a specific example of each step in FIG. 11 and a specific example of a table obtained thereby will be described.

  FIG. 12 is a flowchart showing a specific example of step S100 in FIG.

  In the figure, one unprocessed test case 303, for example, the test case 303a with the test case number “1” is acquired from the test case table 300 (FIG. 4) (step S200). The acquired test case 303 is hereinafter referred to as an acquired test case.

  Next, for one factor set in the actual machine test condition table 500 (FIG. 6) in FIG. 6, one value, for example, the value c1 of the factor C is acquired (step S201), and the acquired factor C is acquired. It is determined whether or not the value c1 matches the value of any factor in the acquired test case 303 (here, the test case 303a) (step S202). If there is a matching factor value (“YES” in step S202), this acquired test case 303 is stored as an actual machine test case in the later-described actual machine test case table 1000 (step S203). Thereafter, when such processing has not been performed for all unprocessed test cases (“NO” in step S206), the process returns to step S200, and the next test case 303 is obtained from the test case table 300 (FIG. 4). The above process is repeated for this test case 303.

  If the acquired test case 303 does not have a factor value that matches the factor value acquired in step S201 (“NO” in step S202), the determination process in step 204 is performed, and the value column of the actual machine test condition table 500 One next value stored in 503 is acquired (step S201), and it is determined whether or not a factor value that matches the factor value exists in the acquired test case (step S203). If the process of step S201 → S202 → S204 → S201 is repeated and the value of the factor acquired in step S201 is found to be in the acquired test case (“YES” in step S202), the acquired test case 303 Are stored in the actual machine test case table 1000 as actual machine test cases (step S203).

  Here, step S204 is a determination process for determining whether or not the determination process of step S202 has been performed for all factor values stored in the actual machine test condition table 500 for the acquired test case. When the value of the factor that has not been subjected to the determination process in step S202 related to the condition table 500 remains ("NO" in step S204), the process proceeds to step S201 and the value of the next factor in the actual machine test condition table 500 is determined. The determination in step S202 is performed, but the determination process in step S202 is performed for all factor values stored in the actual machine test condition table 500, and the last factor value also matches the factor that matches this. If there is no value in the acquisition test case 303, this acquisition test case 303 is set as a non-real machine test case. Stored in the non-real machine test case table 1100 (step S205). Thereafter, when such processing has not been performed for all unprocessed test cases (“NO” in step S206), the process returns to step S200, and the next test case 303 is obtained from the test case table 300 (FIG. 4). The above process is repeated for this test case 303.

  In this manner, when the classification of one acquired test case 303 into the above-described real machine and non-real machine test cases is completed, when an unprocessed test case 303 remains in the test case table 300 (FIG. 4) ( Returning to step S200, the next unprocessed test case 303 is acquired from the test case table 300, and the above processing is performed using this as the acquired test case. When the above processing is performed for all unprocessed test cases 303 in the test case table 300, all these test cases 303 are either the actual machine test case table 1000 or the non-executed test case table 1100, respectively. ("YES" in step S206), the classification process ends.

  FIG. 13 is a diagram showing a specific example of the actual machine test case table 1000 obtained by the processing shown in FIG. 12, wherein 1001a to 1001f are actual machine test cases, and parts corresponding to those in FIG. Therefore, duplicate explanations are omitted.

  Referring to FIG. 12, the actual machine test case table 1000 includes actual machine test cases 1001a to 1001f determined to perform the actual machine test among the non-processed test cases in the test case table 300 (FIG. 4). Is stored. These actual machine test cases 1001a to 1001f also have the test case configuration in the test case table 300 (FIG. 4), and are composed of a test case number column 301 and factor columns 302a, 302b, 302c, 302d,. Is.

  Here, as an example, test cases 303b, 303c, 303d, 303f, 303g, and 303h with test case numbers “2”, “3”, “4”, “6”, “7”, and “8” are shown in FIG. The actual machine test cases 1001a, 1001b, 1001c, 1001d, 1001e, and 1001f are determined by the processing shown in FIG.

  FIG. 14 is a diagram showing a specific example of the non-real machine test case table 1100 obtained by the processing shown in FIG. 12, in which 1101a to 1101c are non-real machine test cases, and parts corresponding to those in FIG. A duplicate description is omitted.

  In the figure, the non-real machine test case table 1100 includes a non-real machine test case that is determined not to perform the real machine test among the non-process test cases in the test case table 300 (FIG. 4) by the process of FIG. 1101a to 1101c are stored. These non-real machine test cases 1101a to 1101c are also the same as the test case configuration in the test case table 300 (FIG. 4), from the test case number column 301 and the factor columns 302a, 302b, 302c, 302d,. It will be.

  Here, as an example, the test cases 303a, 303e, and 303i with the test case numbers “1”, “5”, and “9” are determined as non-real machine test cases 1101a, 1101b, and 1101c by the processing shown in FIG. It is stored in the non-real machine test case display 1101.

  FIG. 15 is a flowchart showing a specific example of step S101 regarding the actual machine test case in FIG. This specific example is stored in the actual test case table 1000 (FIG. 13) based on the test table 600 (FIG. 7) having a high test execution priority and the test table 700 (FIG. 8) having a low test execution priority. The actual test case that has been executed is a test case with a high test execution priority, a test case with a low test execution priority, and a test case that does not fall into any of these (ie, does not fall under the test order condition table 600/700) It is classified into and.

  In the figure, one of the actual machine test cases 1001 (generic name of the actual machine test cases 1001a to 1001f) is acquired from the actual machine test case table 1000 (FIG. 13) (step S300). Here, as an example, it is assumed that the test case 1001a having the test case number “2” in the actual machine test case table 1000 (FIG. 13) is acquired.

  Next, one value is acquired from one factor value column 602 of the factor column 601 of the test table 600 (FIG. 1) having a high execution priority (step S301), and the factor in the test case 1001a acquired in step S300 is obtained. It is confirmed whether or not there is a value that matches the factor value acquired in step S301 (step S302). If there is a matching value (“YES” in step S302), this actual machine The test case 1001a is stored as a real machine test case having a high execution priority in the test in the real machine test case table 1200 having a high execution priority, which will be described later (step S303). Thereafter, the process returns to step S300, the next real machine test case 1001 is obtained from the real machine test case table 1000 (FIG. 13), and the above-described processing is repeated for this real machine test case 1001.

  When the actual machine test case 1101a does not have a value that matches the factor value acquired in step S301 (“NO” in step S302), the actual machine test table 600 having a higher execution priority has values of unacquired factors. In the case (“NO” in step S304), the process returns to step S301, the next value of the same factor (the value of the next factor if there is no such) is obtained from the test table 600 having a high execution priority, and the process of step S302 is performed. Do.

  For all values of all factors in the test table 600 having a high execution priority, when there is no factor value that matches any of these in the actual machine test case 1101a (“NO” in step S302 and step S304). “NO”), one of the factor values stored in the test table 700 (FIG. 8) having a low execution priority is acquired (step S305), and the factor value matching the factor value is the actual test case. It is confirmed whether or not it exists in 1101a (step S306). If the actual machine test case 1101a has a factor value that matches this ("YES" in step S306), the actual machine test case 1101a is an execution priority to be described later as an actual machine test case having a low test execution priority. The data is stored in the test case table 1300 having a lower rank (step S307).

  If the actual machine test case 1101a does not have a factor value that matches the factor value acquired from the test table 700 having a low execution priority ("NO" in step S306), the test case has a low execution priority. If there is a value of another factor not acquired in the table 1300 (“NO” in step S308), the process returns to step S305 to acquire the next value of the same factor or the value of the next factor from the test table 700 having a low execution priority. Then, the determination process of step S306 is performed. If there is a factor value that matches the acquired factor value (“YES” in step S306), this real machine test case 1101a has a low execution priority, which will be described later, as an actual machine test case with a low test execution priority. Although stored in the test case table 1300 (step S307), if there is no match, a series of processing of steps S305 → S306 → S308 → S305 is repeated, and the value of any factor in the actual machine test case 1101a is given priority to execution. If it does not match the value of any factor in the low-rank test table 700 (“YES” in step S308), the actual machine test case 1101a will be described later as a test case that does not correspond to the test order condition table 600/700. That do not fall under the test order condition table (that is, the execution priority is medium) As strike case, stored in the actual test case table 1400 which does not correspond to the test sequence condition table (step S309).

  When the real machine test case 1101a is stored in any of the real machine test case table 1200 having a high execution priority, the test case table 1300 having a low execution priority, and the real machine test case table 1400 not corresponding to the test order condition table, the real machine test case When there is a further actual machine test case 1001 in the table 1000 (“NO” in step S310), the process returns to step 300, and the same processing is performed for the next actual machine test case 1001 in the actual machine test case table 1000.

  When such processing is performed for all the actual machine test cases 1001 in the actual machine test case table 1000 (“YES” in step S310), the actual machine test case table 1200 having a higher execution priority, the test having a lower execution priority. The distribution is stored in either the case table 1300 or the actual machine test case table 1400 that does not correspond to the test order condition table, and the distribution process for the actual machine test case ends.

  FIG. 16 is a diagram showing a specific example of the real machine test case table 1200 created in step S303 in FIG. 15 and having a high execution priority, where 1201 is a “test execution time” column, and 1202a and 1202b are test executions. This is a real machine test case having a high priority, and the same reference numerals are given to portions corresponding to those in FIG.

  In FIG. 7, an actual machine test case table 1200 having a high execution priority has a value of one of the factors in the actual machine test case 1001 in the actual machine test case table 1000 shown in FIG. 13. Is stored as a real machine test case 1202 having a high execution priority (generic name of real machine test cases 1202a and 1202b having a high execution priority). Here, as an example, the real machine test cases 1001a and 1001b (FIG. 13) with the test case numbers “2” and “3” are determined as the real machine test cases with high execution priority (step S303 in FIG. 15). ).

  The real machine test case 1202 having a high execution priority has the same configuration as the test case 303 shown in FIG. 4, but the time required for executing the test of the real machine test case 1202 having a high execution priority (test execution) A “test execution time” column 1201 in which (time) is stored is added. This test execution time is the time from the start of the test set to the actual machine in the test execution standard time table 800 shown in FIG. 9 to the end of the test (for example, “30 seconds” is set). The time required for the test switching operation from the value of the tested factor set in the test switching operation time table 900 shown in FIG. 10 to the same factor value to be tested next is added.

  For example, when the test is switched from the real machine test case 1001a with the test case number “2” to the real machine test case 1001b with the test case number “3” in the real machine test case table 1000 (FIG. 13) having a high completion priority, the factor A requires a switching operation from value al to value a1, factor B from value b2 to value b3, factor C from value c2 to value cl, and factor D from value d1 to value d1. The test switching operation time at the test execution time of the actual machine test case 1001a of the case number “2” is the test switching operation time table 900 corresponding to each of these factors A, B, C, and D (however, here, FIG. 10 shows only the test switching operation time table for the factor A), and the test switching operation time is obtained and added. The result obtained by adding the test time of the actual machine test case in the test execution standard time table 800 shown in FIG. 9 to the added value is the “test execution time” column of the actual machine test case table 1200 shown in FIG. 1201 is a test execution time stored in 1201.

  Therefore, in the real machine test case table 1200 having a high execution priority shown in FIG. 16, for example, the test execution time stored in the “test execution time” column 1201 in the real machine test case 1202a having a high execution priority is the real machine test case. This is the time required from 1202a to the end of the test after the start of the test until the operation for switching to the real machine test case 1202a with the next higher execution priority is completed.

  FIG. 17 is a diagram showing a specific example of the actual machine test case table 1300 created in step S303 in FIG. 15 and having a low execution priority. 1301 is a “test execution time” column, and 1302 is a test execution priority. This is a real machine test case, and parts corresponding to those in FIG.

  Referring to FIG. 8, an actual machine test case table 1300 having a low execution priority has a value of any of the actual machine test cases 1001 in the actual machine test case table 1000 shown in FIG. The real machine test case 1001 that matches the value of the factor in the test table 700 with a low is stored as the real machine test case 1302 with a low execution priority. Here, as an example, it is assumed that an actual machine test case 1001f (FIG. 13) with the test case number “8” is determined as an actual machine test case having a low execution priority (step S307 in FIG. 15).

  Such a real machine test case 1302 having a low execution priority has the same configuration as the test case 303 shown in FIG. 4, but further, the time required for executing the test of the real machine test case 1302 having a low execution priority (test execution) A “test execution time” column 1301 in which (time) is stored is added. This test execution time is also the same as that in the real machine test case table 1200 having a high execution priority. The test execution time is from the start of the test set for the real machine in the test execution standard time table 800 shown in FIG. Time (for example, “30 seconds” is set) and from the value of the tested factor set in the test switching operation time table 900 shown in FIG. 10 to the value of the same factor to be tested next The time required for the test switching operation is added.

  FIG. 18 is a diagram showing a specific example of the actual machine test case table 1400 that does not correspond to the test order condition table 600/700 created in step S303 in FIG. 15. 1401 is a “test execution time” column, 1402a, 1402b and 1402c are actual machine test cases that do not correspond to the test order condition table 600/700 (the execution priority is medium), and parts corresponding to those in FIG.

  In FIG. 7, in the actual machine test case table 1400 that does not correspond to the test order condition table 600/700, the value of any factor in the actual machine test case 1001 in the actual machine test case table 1000 shown in FIG. A real machine test case 1001 that does not match the factor values of the test table 600 having a high execution priority shown in FIG. 8 or the test table 700 having a low execution priority shown in FIG. 8, that is, a real machine test case table 1200 having a high execution priority shown in FIG. In addition, an actual machine test case 1001 that is not stored in the actual machine test case table 1300 having a low execution priority shown in FIG. 17 is an actual machine test case 1402 (test order condition table 600/700) that does not correspond to the test order condition table 600/700. As a generic name of actual machine test cases not corresponding to 700). Here, as an example, the actual machine test cases 1001c, 1001d, and 1001e (FIG. 13) of the test case numbers “4”, “6”, and “7” are not included in the test order condition table 600/700, respectively. , 1402b, 1402c and stored (step S309 in FIG. 15).

  An actual machine test case 1402 that does not correspond to the test order condition table 600/700 has the same configuration as the test case 303 shown in FIG. 4, but further, an actual machine test case 1402 that does not correspond to the test order condition table 600/700. A “test execution time” column 1401 for storing the time required to execute the test (test execution time) is added. This test execution time is also the same as that of the real machine test case table 1200 having a high execution priority and the real machine test case table 1300 having a low execution priority, and is compared with the real machine in the test execution standard time table 800 shown in FIG. The time from the start of the set test to the end of the test (for example, “30 seconds” is set) and the tested factors set in the test switching operation time table 900 shown in FIG. The time required for the test switching operation from the value to the value of the same factor to be tested next is added.

  As described above, the real machine test case 1001 in the real machine test case table 1000 shown in FIG. 13 corresponds to the execution priority of the test, and the execution priority shown in FIG. The real machine test case table 1300 having a lower rank and the real machine test case table 1400 not corresponding to the test order condition shown in FIG. 18 are distributed to the non-real machine test case table 1100 shown in FIG. The same applies to.

  FIG. 19 is a flowchart showing a specific example of step S101 relating to the non-real machine test case in FIG. 11, and the execution shown in FIG. 7 is the same as in the real machine test case 1001 in the real machine test case table 1000 shown in FIG. Based on the test table 600 having a high priority and the test table 700 having a low execution priority shown in FIG. 8, the non-real machine test case 1101 in the non-real machine test case table 1100 shown in FIG. A non-real machine test case table having a high execution priority similar to the real machine test case table 1200 having a high execution priority and a non-real machine test case table having a low execution priority similar to the real machine test case table 1300 having a low execution priority shown in FIG. Actual machine test cases that do not correspond to the test order conditions shown in FIG. It is intended to distribute the strike case table. Note that illustration of a non-real machine test case table having a high execution priority for a non-real machine test case, a non-real machine test case table having a low execution priority, and a non-real machine test case table not corresponding to the test order condition are omitted.

  The flowchart shown in FIG. 19 is the flowchart shown in FIG. 15 for the actual machine test case except that the test case to be distributed is the non-real machine test case 1101 in the non-real machine test case table 1100 shown in FIG. Therefore, the processing steps corresponding to FIG. 15 are given the same number with a dash “′”, and the description thereof will be omitted because it is redundant. The non-real machine test case 1101 is represented as a real machine test case table 1200 ′ having a high execution priority, a real machine test case table 1300 ′ having a low execution priority, and a real machine test case table 1400 ′ not corresponding to the test order condition. These have the same configuration as the tables shown in FIGS. 16, 17, and 18, respectively.

  As described above, the real machine test case 1001 stored in the real machine test case table 1000 (FIG. 13) and the non-real machine test case 1101 stored in the non-real machine test case table 1100 (FIG. 14) are tested. Are classified into a test case having a high execution priority, a test, a test case having a low execution priority, and a test case not corresponding to any of them (that is, not corresponding to the test order condition table 600/700).

  FIG. 20 is a flowchart showing a specific example of step S102 in FIG. 11 for calculating the test execution times stored in the test execution time columns 1201, 1301, 1401 in FIGS.

  The test execution time is a real machine test case table 1200 having a high execution priority shown in FIG. 16, a real machine test case table 1300 having a low execution priority shown in FIG. 17, and a real machine test case not corresponding to the test order condition table shown in FIG. Although calculated for each of the tables 1400, here, an actual machine test case table 1200 having a high execution priority shown in FIG. 16 will be described as an example. Although not shown, a non-real machine test case table having a high execution priority similar to FIG. 16, a non-real machine test case table having a low execution priority similar to FIG. 17, and an order condition table similar to FIG. The same applies to the actual machine test case table.

  20, in the real machine test case table 1200 having a high execution priority shown in FIG. 16, two real machine test cases 1202 with test case numbers “m” and “n” arranged in succession (hereinafter, these are executed tests). Case “m” and “n” are acquired) (step S400). As an example of the actual machine test case 1202 to be acquired, for example, m = 2 and n = 3, the actual machine test case number “2” (actual machine test case 1202a) and the real machine test case “3” (actual machine test case 1202b) are used. .

  Next, the test switching operation time between the same factors of the acquired actual machine test cases “m” and “n” is acquired from the test switching operation time table 900 shown in FIG. 10 (step S401).

  As described above, the test switching operation time table 900 is created individually for each factor, and stores the time (test switching operation time) required for the test switching operation from the value to the value for this factor. Yes. The test switching operation time table 900 shown in FIG. 10 relates to the factor A, and stores the test switching operation time from all the values of the factor A defined in the value definition table 200 shown in FIG. 3 to all these values. Has been. However, the test switching operation time between the same values is 0 (seconds).

  Therefore, if the real machine test case table having a high execution priority as a target at this time is described as the high real machine test case table 1200 shown in FIG. 16 below, in step S401, factor columns 302a, 302b, The test switching operation time is obtained in the order... First, the factor in the first factor column 302a, that is, the test switching operation time of the value of the factor A is obtained. In this case, since the value of the factor A of the actual machine test case “2” is a1 and the value of the factor A of the actual machine test case “2” is also a1, this is a test switching operation from the value al to the value al. The switching operation time corresponds to the value a1 in the test case value column 902 before the test switching operation and the value a1 in the test case value column 904 after the test switching operation in the test switching operation time table 900 of FIG. It is obtained from the storage location of the test switching operation time column 905. In this case, the test switching operation time is 0 (seconds) (step S401).

  The acquired test switching operation time is stored as the test execution time t in the test execution time column 1201 of the real machine test case “2” in the real machine test case table 1200 having a high execution priority shown in FIG. 16 (step S402).

  Next, for the factor B in the next factor column 302b of the actual machine test case table 1200 having a high execution priority shown in FIG. In this case, the test switching operation from the value b2 to the value b3 is performed, and the test switching operation time is obtained from the test switching operation time table (not shown) for the factor B (step S403). Then, the obtained test switching operation time is added to the test execution time t stored in the test execution time column 1201 of the real machine test case “2” in the real machine test case table 1200 having the high execution priority shown in FIG. Then, the added value is stored as a new test execution time t in the test execution time column 1201 of the real machine test case “2” in the real machine test case table 1200 having a high execution priority shown in FIG. 16 (step S404).

  Further, when there is a value of the factor C of the actual machine test cases “2” and “3” having the higher execution priority in the next factor column 302c of the actual machine test case table 1200 having the higher execution priority shown in FIG. ("NO" in step S405), the process from step S403 is repeated for this factor C. Thereafter, the same process is performed for sequential factors, and the obtained test switching operation times are sequentially shown in FIG. This is added to the test execution time t stored in the test execution time column 1201 of the real machine test case “2” in the real machine test case table 1200 having a high execution priority.

  When the test switching operation time for all factors is obtained for the same set of real machine test cases, in this case, real machine test cases “2” and “3” (“YES” in step S405), the real machine test case “2” As the test execution time t, the total test switching operation time to the real machine test case “3” is the real machine test case “2” in the real machine test case table 1200 shown in FIG. ) In the test execution time column 1201.

  Next, the standard time required to execute the real machine test stored in the real machine test standard time column 80 of the test execution standard time table 800 shown in FIG. 9 is acquired, and this is the real machine test with the high execution priority shown in FIG. The actual test case “2” in the case table 1200 is added to the test execution time t stored in the test execution time column 1201 (step S406), and the added value is used as a new test execution time t, and the execution shown in FIG. Stored in the test execution time column 1201 of the real machine test case “2” in the real machine test case table 1200 having a high priority (step S407).

  As a result of the above processing, this test after the actual machine test case “2” starts the test in the test execution time column 1201 of the actual machine test case “2” in the actual machine test case table 1200 shown in FIG. Is stored as the test execution time t until the test switching operation to the next actual machine test case “3” is completed.

  When the test execution time t of one real machine test case is obtained as described above, the next set of real machine test cases from which the test execution time t is obtained has the execution priority shown in FIG. If it is in the high actual machine test case table 1200 (“NO” in step S408), m = m + 1 and n = n + 1 are selected as the next set of actual machine test cases 1202 (step S409). The processing from S401 is performed, and the test execution time t of the next actual machine test case is obtained. Further, when the next set of actual machine test cases 1202 is eliminated (“YES” in step S408), the processing is terminated.

  For example, in the actual machine test case table 1202 shown in FIG. 16 where only the actual machine test cases 1202a and 1202b are stored in the actual machine test case table 1200, the next actual machine test case is as follows. In the case of a real machine test case that does not exist and cannot form a set of real machine test cases for the above processing, although not shown, after this real machine test case 1202 is selected as m = m + 1 in step S409 ( Since there is no next execution test case, it is not possible to set n = n + 1 and this is determined (not shown), but the process proceeds to step S406, where the actual machine test of the test execution standard time table 800 shown in FIG. The standard time required to execute the actual machine test stored in the standard time column 80 is the test execution time t. It is stored in the test execution time column 1201. Then, assuming that the processing of all the real machine test cases 1202 in the real machine test case table 1200 having a high execution priority shown in FIG. 16 is completed (“YES” in step S408), the test execution time t of the real machine test case 1202 is obtained. The process ends.

  In this way, the test execution time t is obtained for all the real machine test cases 1202 in the real machine test case table 1200 shown in FIG. 16 having the high execution priority, but the real machine test having the low execution priority shown in FIG. The same applies to all real machine test cases 1302 in the case table 1300 and all execution test cases 1402 in the real machine test case table 1400 that do not correspond to the test order condition shown in FIG. The test execution time t is stored in 1401. Further, for non-real machine test cases, a non-real machine test case table having a high execution priority, a non-real machine test case table having a low execution priority, and a test order condition are used. In the test execution time column of the non-real machine test case table that does not apply, the test Execution time t is stored sought.

  The actual machine test case 1201 in the real machine test case table 1200 having a high execution priority shown in FIG. 16 and the real machine test case 1301 in the real machine test case table 1300 having a low execution priority shown in FIG. The actual machine test case 1401 in the actual machine test case table 1400 that does not correspond to the test order condition table shown in FIG. 18, and the non-real machine test case table in the same non-real machine test case table for the non-real machine test case are tested. Test cases for each worker are distributed to the number of workers specified in the number of workers column of the condition table 400 so that the time required for each worker's test and the burden of the test work are equalized. An output table 1500 (FIG. 1) after distribution is created.

  FIG. 21 is a diagram showing a specific example of the output table 1500 after the distribution of test cases for one worker. 1501 is a “worker” column, 1502 is a “test execution time” column, and 1503 is a “real machine / non-working” column. .., “Distinguish between real machines”, 1504a, 1504b,... Are distributed test cases, and the portions corresponding to those in FIG.

  In the figure, an output table 1500 after test case distribution includes a “worker” column 1501 in which information identifying the worker such as the name and ID of the worker to whom the output table 1500 is provided is stored. For this worker, the real machine test case 1201 distributed from the real machine test case table 1200 having a high execution priority shown in FIG. 16 and the real machine test case table 1300 having a low execution priority shown in FIG. The actual machine test cases 1401, distributed from the actual machine test case table 1400 not corresponding to the test order condition table shown in FIG. 18, are stored as distributed test cases 1504a, 1504b, 1504c, 1504d,. Yes.

  Here, these distribution test cases 1504 (generic names of distribution test cases 1504a, 1504b, 1504c, 1504d,...) Are similar to the test case 303 shown in FIG. 4 in the “test case number” column 301 and “factor” column 302a. , 302b, 302c, 302d,..., But the “execution priority” column 1201 of the real machine test case table 1200 having a high execution priority shown in FIG. 16 and the execution priority shown in FIG. Stored in the “test execution time” column 1301 of the actual machine test case table 1300 and the test execution time t stored in the “test execution time” column 1401 of the actual machine test case table 1400 not corresponding to the test order condition table shown in FIG. In addition, a “test execution time” column 1502 and a “distinguish between real and non-real machine” column 1503 are provided.

  In the “Distinction between actual machine / non-real machine” column 1503, when the distribution test case 1504 is an actual machine test case distributed from any one of the actual machine test case tables 1200, 1300, and 1400 shown in FIGS. Information indicating that it is a real machine test case (indicated as “real” in FIG. 21) is stored, and if it is a non-real machine test case distributed from the same non-real machine test case table, it is a non-machine test case Is stored (indicated in FIG. 21 by “non-”).

  FIG. 22 is a diagram for distributing the actual machine test cases 1202 in the actual machine test case table 1200 shown in FIG. 16 having a high execution priority to the number of workers specified in the number of workers column of the test execution condition table 400 shown in FIG. 11 is a flowchart showing a specific example of the processing of steps S103 to S105 in FIG. Hereinafter, step S103 in FIG. 11 for distributing the real machine test cases 1202 in the real machine test case table 1200 having a high execution priority shown in FIG. 16 will be described as an example.

In FIG. 16, the actual machine test total time as the sum of all the test execution times t stored in the test execution time column 1201 of all the actual machine test cases 1202 in the actual machine test case table 1200 shown in FIG. Σt is obtained, and this actual machine test total time Σt is divided by the number of workers specified in the test execution condition table 400 shown in FIG. 5 to obtain the test execution time T of the actual machine test case per worker.
In addition, among the actual machine test cases that have been distributed from the actual machine test case table 1200 having a high execution priority shown in FIG. 16 to the output table 1500 after the test case distribution of each worker as shown in FIG. showing a test case 1504, that is, any actual test test case pointer that indicates whether it has distributed to the case 1504 (hereinafter, TC pointer that) the P _TC, been made to start in the future distribution, distribution already actual test case _Therefore , P _TC = 0. In the actual machine test case table 1200 having a high execution priority shown in FIG. 16, P _TC = 0 represents the illustrated position.
Also, a copy offset P _CF indicating a distribution destination of the output table 1500 after the test case distribution shown in Figure 21 of the actual test case 1504 has execution priority shown in FIG. 16 becomes a distribution target of the high actual test case table 1200, P _CF = 0. In the output table 1500 after test case distribution shown in FIG. 21, P _CF = 0 represents the position shown in the figure.
The above is the initial setting process of step S500.

  Next, since the worker number i representing the worker who is the distribution destination of the actual machine test case 1202 is the first worker here, i = 1 is set (step S501), and the execution priority shown in FIG. The distribution counter j representing the number of workers who distributed the actual machine test case 1202 from the high actual machine test case table 1200 is set to j = 0 since the number of distributed workers is 0 (step S502).

As described above, distribution of the actual machine test case 1202 to the first worker to the actual machine test case table 1200 having the high execution priority shown in FIG. 16 of the first worker is started. TC in the actual machine test case table 1200 is started. From the position of the pointer P _TC = 0, the total of the test execution times t stored in the “test execution time” column 1201 in FIG. 16 is closest to the test execution time T of the actual machine test case per worker. A number of actual machine test cases 1202 are selected as distribution-target actual machine test cases 1202 and are sequentially stored from the position of copy offset P _CF = 0 in the output table 1500 after test case distribution shown in FIG. Here, only the first real machine test case 1202a with the test case number = 1 from the real machine test case table 1200 having a high execution priority shown in FIG. 16 is the real machine test case 1202 to be distributed, and after the test case distribution shown in FIG. It is assumed that it is stored at the head of the output table 1500 (step S503).

  In this way, the actual machine test cases 1202 are distributed (rearranged) from the “test execution time” column 1201 in FIG. 16 to the output table 1500 after the test case distribution shown in FIG. 21 of the first worker.

Thereafter, the worker number i is set to i = i + 1 (step S504), the distribution counter j is set to j = j + 1 (step S505), and an output table 1500 after test case distribution as shown in FIG. The TC point P _TC is designated as P _TC = P _TC + N _T (step S506: where N _T is the number of actual test cases 1202 closest to the test execution time T), and the execution priority shown in FIG. Initial setting for distribution of the actual machine test case 1202 from the high actual machine test case table 1200 to the output table 1500 after the test case distribution shown in FIG. 21 of the next worker is performed. Here, since N _T = 1, in the real machine test case table 1200 having a high execution priority shown in FIG. 16, as shown in the figure, P _TC = 1 represents the position of the first real machine test case 1202a. become.

Then, the distribution counter j, which is the number of workers who performed the distribution, is compared with the actual number of machines set in the test execution condition table 400 shown in FIG. 5 (step S507), and if the distribution counter j is less than the actual number of machines. ("YES" in step S507), the actual machine test case 1202 is distributed to the output table 1500 after the test case distribution of the next worker initially set in steps S504 to S506 as shown in FIG. if the distribution counter j actual number more ( "NO" in step S507), the copy offset P _CF at the output table 1500 after the test case distribution shown in FIG. 21 and _{P CF = P CF + N T} ( step S508) Further, the distribution counter j, which is the number of workers who have distributed, is compared with the number of workers set in the test execution condition table 400 shown in FIG. If the distribution counter j is less than the number of workers (“YES” in step S509), the process returns to step S503, as shown in FIG. 21 of the next worker initially set in steps S504 to S506. The actual test case 1202 is distributed to the output table 1500 after the distribution of the test cases. In this case, the storage start position of the real machine test case 1202 distributed from the real machine test case table 1200 having a high execution priority shown in FIG. 16 in the output table 1500 after test case distribution as shown in FIG. 21 is shown in step S509. are stored from the set next storage location of the storage position indicated by the copy offset P _CF.

Here, according to the test execution condition table 400 shown in FIG. 5, the actual number of machines is three, and the number of workers is three. In this case, when the distribution of the actual test case 1202 to the output table 1500 after the test case distribution as shown in FIG. 21 of the first worker is completed (only the actual test case 1202a of the test case number “2” is distributed). Step S503), the distribution counter j becomes j = 1 (Step S505), “NO” in Step S507, and the output table 1500 after the test case distribution as shown in FIG. copy offset P _CF is specified in _{P CF = P CF + N T} ( step S508), further, because it is "YES" in step S509, the output after the test case distribution as shown in Figure 21 of this next worker from the next storage location of the storage position designated by the copy offset P _CF table 1500 execution priority shown in FIG. 16 higher actual test cases The test case 1202 to be distributed next in the process table 1200 is stored.

  As described above, a series of processes of steps S503 to S509 are repeated based on the actual number of machines and the number of workers in the test execution condition table 400 shown in FIG. The actual machine test cases 1202 having a high execution priority are distributed to the output table 1500 after the test case distribution as shown in FIG.

When the distribution of the actual machine test case 1202 in the actual machine test case table 1200 in the actual machine test case table 1200 shown in FIG. 16 to the output table 1500 after the test case distribution ends, the execution priority shown in FIG. Distribution of the non-real machine test cases in the non-real machine test case table having a high execution priority regarding the non-real machine test cases similar to the real machine test case table 1200 having a high rank is performed in the same manner according to the flowchart shown in FIG. Test cases as shown in FIG. 21 of the respective workers in the actual machine test case table and the non-real machine test case table as shown in FIG. 18 and the test cases in the real machine test case table and the non-real machine test case table as shown in FIG. Distribution to the output table after distribution is performed. However, in the sequential distribution of test cases in the test case table, the distribution process is started from step S500 in FIG. 22. At the start, the output after the distribution of the test cases as shown in FIG. for Table 1500, the holding is set in step S508 at the end of the distribution process from the test case table as shown in the previous 16 to 18 are copies offset P _CF is a buffer on a CPU 2 (Fig. 2) is, the next test case to be dispensed from the test case table as shown in FIGS. 16 to 18 will be stored from the next position of the copy offset P _CF which is the holding.

  FIG. 23 shows a real machine test case from the real machine test case table 1200 having a high execution priority shown in FIG. 16 and a non-real machine test case from the non-real machine test case table having a high execution priority (not shown) corresponding thereto. FIG. 11 is a diagram showing a distribution process based on the flowchart and the result, where 1600 is a non-real machine test case table having a high execution priority, and RT1 to RT3 are workers in the real machine test case table 1200 having a high execution priority shown in FIG. A group of actual machine test cases of test execution time T of actual machine test cases per person (assigned per worker), NRT1 to NRT3 are per worker in the non-real machine test case table with high execution priority. Of non-real machine test cases (assigned per worker) of non-real machine test cases with test execution time T. They are assigned the same reference numerals to corresponding parts to.

FIG. 23A shows a case where the number of actual machines is one and the number of workers is three, and each worker a, b, c uses the actual machine by shifting the test execution time per person. In order to be able to do this, the output table 1500a after the test case distribution of the first operator a is changed from the next storage position (first storage position) of the copy offset P _CF = 0 to the actual test case table 1200. stores actual test case group RT1 (step S503 in FIG. 22), the copy offset P _CF to the number of actual test cases actual test case group RT1 N _T (1) only by adding copy offset P _CF (1) (= P _CF + N _T (1)) is created (step S508 in FIG. 22), and the next storage of the position of this copy offset P _CF (1) is stored in the output table 1500b after the test case distribution of the second worker b. Stores actual test case group RT2 of actual test case table 1200 from the position (step S503 in FIG. 22), thereafter, further, the number of actual test cases copy offset P _CF (1) on a real machine test case group RT2 N _T (2) is added to create P _CF (2) (= P _CF (1) + N _T (2)) (step S508 in FIG. 22), and after the test case distribution of the next third worker c The actual machine test case group RT3 of the actual machine test case table 1200 is stored in the output table 1500c from the storage position next to the position of the copy offset P _CF (2) (step S503 in FIG. 22). Then, the copy offset P _CF (3) by adding the number of actual test cases actual test case group RT3 N _T (3) to copy offset _{P CF (2) (= P} CF (2) + N T (3)) Is formed (step S508 in FIG. 22).
As a result, the distribution of the actual machine test cases in the actual machine test case table 1200 to the output tables 1500a, 1500b, and 1500c after the distribution of the test cases of the workers a, b, and c ends. Copy offsets P _CF (1), P _CF (2), and P _CF (3) are held for the output tables 1500a, 1500b, and 1500c, respectively.

  Then, the non-real machine test cases in the non-real machine test case table 1600 having the highest execution priority are distributed to the output tables 1500a, 1500b, and 1500c after the test cases are distributed to the workers a, b, and c.

This, first, the above initial setting in step S500~S502 of FIG. 22 is performed, in this case, only the copy offset P _CF at step 500, the output table 1500a after the test case the distribution of the first operator a Is set to the copy offset P _CF (1) that is held. As a result, in the output table 1500a after the distribution of the test cases, the execution priority is higher from the storage position next to the position specified by the copy offset P _CF (1) (following the actual test case group RT1). The non-real machine test case group NRT1 of the real machine test case table 1600 is stored. When this storage is completed, the number N _T (1 ′) of non-real machine test cases in the non-real machine test case group NRT1 is added to the copy offset P _CF (1) to obtain P _CF (1 ′) (= P _CF ( _{1) + N T (1 '} )) is generated (step S508 in FIG. 22), as to define the next storage starting position of the output table 1500a after the test case distribution, output table 1500a after the test case distribution Saved against.

At the same time, in step S508 of FIG. 22, the non-real machine test case group NRT2 of the non-real machine test case table 1600 having a high execution priority to the output table 1500b after the test case distribution of the next worker b is stored. for this test a copy of the stored for output table 1500b of the case after dispensing offset P _CF (2) is set, the copy offset P _CF at the output table 1500b post test case distribution (2) The non-real machine test case group NRT2 of the non-real machine test case table 1600 having a higher execution priority is stored from the storage position next to the position specified in (Step S503 in FIG. 22). When the storing process is completed, the number N _T of the non-real machine test case in the non-real machine test case group NRT2 this copy offset _{P CF (2) (2 '} ) is added copied offset P _CF (2') (= P _CF (2) + N _T (2 ′)) is created and stored in the output table 1500b after the test case distribution as defining the next storage start position in the output table 1500b after the test case distribution. Is done.

At the same time, in step S508 of FIG. 22, the non-real machine test case group NRT3 of the non-real machine test case table 1600 having a high execution priority to the output table 1500c after the test case distribution of the next worker c is stored. for, this copy of the stored for output table 1500c after test cases distributed offset P _CF (3) is set, the copy offset P _CF at the output table 1500c after test case distributor (3) The non-real machine test case group NRT3 of the non-real machine test case table 1600 having a higher execution priority is stored from the storage position next to the position specified in (Step S503 in FIG. 22). When the storing process is completed, the number N _T of the non-real machine test case in the non-real machine test case group NRT3 this copy offset _{P CF (3) (3 '} ) is added copied offset P _CF (3') (= P _CF (3) + N _T (3 ′)) is created and stored in the output table 1500c after test case distribution as defining the next storage start position in the output table 1500c after test case distribution Is done.

  In the same manner, an actual machine test case table 1400 that does not correspond to the test order condition table shown in FIG. 18, a non-real machine test case table that does not correspond to the similar test order condition table, and an actual machine test case table with low execution priority shown in FIG. Each of the actual machine test cases and non-real machine test cases in the non-real machine test case table 1300 and similar non-real machine test case tables are repeated in the order of the real machine test case and the non-real machine test case. The output tables 1500a, 1500b, and 1500c after the case distribution are sequentially distributed and stored.

  FIG. 23B shows a case where the number of actual machines is two and the number of workers is three, and two of the workers a, b, and c perform separate actual machine tests at the same time. As can be done, the actual test cases and the non-real test cases are distributed and stored in the output tables 1500a, 1500b, 1500c after the distribution of the respective test cases.

  22, the real machine test case group RT1 of the real machine test case table 1200 is stored in the output table 1500a after the test case distribution of the worker a from the top storage position, and step S504 of FIG. 22 is performed. Through the processing of ~ S506, the output table 1500b after the test case distribution of the next worker b and the real machine test case group RT2 of the real machine test case table 1200 are designated. At this time, since the number of actual machines (= 2)> distribution counter j (= 1) (“YES” in step S507 in FIG. 22), the actual machine test case group RT2 in the actual machine test case table 1200 is the output after the test case is distributed. It is stored in the table 1500b from the first storage position (step S503 in FIG. 22).

When the output table 1500c after test case distribution for the next worker c and the actual machine test case group RT3 in the actual machine test case table 1200 are designated in the processing of steps S504 to S506 in FIG. 22, the number of actual machines (= 2) )> Distribution counter j (= 2) (“NO” in step S507 of FIG. 22), the actual test case group is set to the copy offset P _CF (= 0) set at this time by the processing of step S508. the number of RT1 test cases N copies plus _T (1) offset _{P CF (1) (= P} CF + N T (1)) and by adding the number of test cases in actual use test case group RT2 N _T (2) A copy offset P _CF (2) (= P _CF + N _T (2)) is created, and these copy offsets P _CF (1) and P _CF (2) are respectively distributed to the test cases. It is held with respect to the output tables 1500a and 1500b after the distribution of the test cases as defining the next storage start position in the subsequent output tables 1500a and 1500b.

Further, the copy offset P _CF (2) created for the output table 1500b after the test case distribution is further added to the actual machine test case of the actual machine test case table 1200 in the output table 1500b after the test case distribution of the next worker c. be those used to define the storage start position when storing the group RT3, actual test cases actual test case table 1200 from the next storage position of the position designated by the copy offset P _CF (2) The group RT3 is stored (step S503 in FIG. 22).

  In this way, as shown in FIG. 23B, the output tables 1500a and 1500b after the test case distribution of the two workers a and b are respectively displayed in the actual test case table 1200 from the initial storage position. Although the actual machine test case groups RT1 and RT2 are stored, the output table 1500c after the test case distribution for the remaining worker c follows the storage position of the actual machine test case group RT2 in the output table 1500b after the test case distribution. The actual machine test case group RT3 is stored from the storage position corresponding to the position.

Next, the non-real machine test cases in the non-real machine test case table 1600 having the highest execution priority are distributed to the output tables 1500a, 1500b, and 1500c after the test cases are distributed to the workers a, b, and c. The process is the same as the process shown in FIG. 23A, and after distributing the test case based on the held copy offsets P _CF (1), P _CF (2), and P _CF (3). In the output table 1500a, the non-real machine test case group NRT1 is stored after the real machine test case group RT1, and in the output table 1500b after the distribution of the test cases, the non-real machine test case group NRT2 is stored after the real machine test case group RT2. In the output table 1500c after the test case distribution, the non-real machine test case group NRT3 is stored after the real machine test case group RT3.

  In the same manner, an actual machine test case table 1400 that does not correspond to the test order condition table shown in FIG. 18, a non-real machine test case table that does not correspond to the similar test order condition table, and an actual machine test case table with low execution priority shown in FIG. Each of the actual machine test cases and non-real machine test cases in the non-real machine test case table 1300 and similar non-real machine test case tables are repeated in the order of the real machine test case and the non-real machine test case. The output tables 1500a, 1500b, and 1500c after the case distribution are sequentially distributed and stored.

  In the above, the number of actual machines is one or two and the number of workers is three as test execution conditions. However, these are shown as an example, and in this embodiment, the number of workers is limited to these. It is not something. That is, when the actual number of machines is m and the number of workers is n (where m <n) as test execution conditions, the output table after the distribution of the test cases assigned to m workers (output in FIG. 23) (Corresponding to Tables 1500a and 1500b), the real machine test case group (real machine test case group RT1 in FIG. 23) distributed in order from the real machine test case table (real machine test case table 1200 in FIG. 23) having the highest execution priority. RT2, RT3) are stored, and in the output table after the distribution of the test cases, the real machine test cases of the real machine test case group having the high execution priority distributed from the real machine test case table having the high execution priority are displayed. The data are stored in order from the first storage position (the output tables 1500a and 1500b in FIG. 23B correspond to this).

Thereafter, in the output table after distribution of the test cases (corresponding to the output table 1500c) assigned to the remaining (n−m) workers (corresponding to the worker b in FIG. 23 (b)), the execution is sequentially performed. The actual test case group stored from the high-priority actual test case table is stored, and in the output table after the distribution of the test cases, the test case distribution after the storage of the actual test case group is completed. Stored from the storage position corresponding to the storage position next to the stored storage position of the actual test case group in the output table. Although not shown in FIG. 23B, the output table 1500d after the test case distribution of the next worker d corresponds to the copy offset P _CF (3) of the output table 1500c after the test case distribution of the worker b. The next real machine test case group distributed from the real machine test case table 1200 having a higher execution priority is stored from the next storage position. As described above, in the output table after the distribution of the test cases assigned to the remaining (nm) workers, the storage start positions of the actual machine test case groups distributed from the actual machine test case table 1200 having a high execution priority. However, the number of test cases in the actual machine test case group shifts sequentially.

  As described above, in this embodiment, the test cases of the real machine test cases and the non-real machine test cases are equally distributed to the respective workers with respect to the test priorities, and are required for the tests of the respective workers. Even when testing is performed with appropriate test conditions and with multiple workers, the test cases that efficiently and efficiently equalize the work burden on the workers and the time required for testing are equivalent. Can be assigned.

  In addition, the real machine test cases with the highest test execution priority are placed at the top, the real machine and the non-real machine test cases are distributed in the descending order of the test execution priority, and stored in the test distribution output table 1500 of each worker. Therefore, the operator can easily confirm the test cases that should be executed in advance, and between the test distribution output table 1500 of each operator according to the actual number of machines. Since the storage start position of the actual machine test case having a high test execution priority is shifted, it is possible to grasp the order of starting the use of the actual machine test of the actual machine test case.

  In addition, this invention is not limited only to the said embodiment, A various deformation | transformation and application are possible.

  For example, in the above embodiment, each process (process for classifying test cases into real machine tests and non-real machine tests (FIGS. 13 and 14), and executing real machine test cases and non-real machine test cases for each test order condition. Processing for classifying into priority order (FIGS. 16 to 18), processing for calculating test execution time (FIG. 20), classifying real machine test cases and non-real machine test cases classified into three execution priorities into a plurality of workers The processing to be performed (FIGS. 21 and 22) is realized by the general computer shown in FIG. 2. For example, each of the above processing is distributed to a plurality of devices via a network. It may be.

1: Test distribution device 2: CPU 3: Main storage device 4: External storage device 5: Reading device 6: Input / output device 7: Communication device 8: Portable storage medium 100: Test work table 200: Value definition table 201: “ “Factor” column 202: Value column 300: Test case table 301: “Test case” column 302a, 302b, 302c: “Factor” column 303a to 303i: Test case 400: Test execution condition table 401: “Number of actual machines” column 402 : "Non-real machine number" column 403: "Number of workers" column 500: Actual machine test condition table 501: "Real machine information" column 502: "Factor" column 503: "Value" column 600: Execution priority as test order condition table Test table with higher rank 601: “Factor” column 602: “Value” column 700: Test table with lower execution priority as a test order condition table 701: “Factor” column 7 2: “Value” column 800: Test execution standard time table 801: “Real machine test standard time” column 802: “Non-real machine test standard time” column 900: Test switching operation time table 901: “Factor” column 902: “Value” Field 903: “Factor” field 904: “Value” field 905: “Test switching operation time” field 1000: Real machine test case table 1001a to 1001f: Real machine test case 1100: Non-real machine test case table 1101a to 1101c: Non-real machine test case 1200: Real machine test case table with high execution priority 1201: “Test execution time” column 1202a, 1202b: Real machine test case with high test execution priority 1300: Real machine test case table with low execution priority 1301: “Test execution time” ”Column 1302: Actual machine test case 1400 having low test execution priority Actual test case table 1401 which does not correspond to the test sequence Conditions Table: "Test Run Time" column 1402a, 1402b, 1402c: the test sequence condition table 600/700
Unmatched real machine test case 1500: Output table after test case distribution 1501: “Worker” column 1502: “Test execution time” column 1503: “Distinction between actual and non-real machine” columns 1504a, 1504b: Distribution test case 1600: Execution Non-real machine test case table with high priority

Claims (8)

In a test distribution method for distributing a plurality of test cases set for the test to a plurality of workers with respect to a device to be tested,
A first step of classifying the plurality of test cases into a real machine test case to be tested using a real machine and a non-real machine test case to be tested without using a real machine;
A second step of classifying the actual test case and the non-real machine test case into groups according to test execution priorities;
A third step of determining the test case to be assigned to each of the workers for each group classified in the second step for the real machine test case and the non-real machine test case;
And a fourth step of distributing the test case assigned in the third step to each of the workers. In claim 1,
Each of the test cases is composed of a combination of a plurality of factor values, and the combination of the factor values is different for each test case,
In the first step, the test having the value of the factor requiring the actual machine test, which is a test using the actual machine, based on the actual machine test condition table defining the value of the factor requiring the actual machine for the test. Cases are classified as actual machine test cases in the real machine test case table, other tests are classified as non-real machine tests, and non-real machine test test cases are classified as non-real machine test cases in the non-real machine test case table. A test distribution method characterized by that. In claim 2,
The second step includes
A test table having a high execution priority as a test order condition table that defines the values of the factors having a high test execution priority, and an execution as a test order condition table having the values of the factors having a low test execution priority. Based on the low priority test table,
A test table in which the real machine test cases having the values of the factors defined in the test table having a high execution priority in the real machine test case table are classified into real machine test cases having a high execution priority, and the execution priority is low. The real machine test cases having the values of the factors defined in (1) are classified into real machine test cases with a low execution priority, and the real machine test cases that do not fall under the test order condition table have a medium execution priority. Are stored in a real machine test case table having a high execution priority, a real machine test case table having a low execution priority, and a real machine test case table not corresponding to the test order condition table,
And classifying the non-real machine test cases having the values of the factors defined in the test table having a high execution priority in the non-real machine test case table into non-real machine test cases having a high execution priority, The non-real machine test cases having the values of the factors specified in the test table with low rank are classified into non-real machine test cases with low execution priority, and the non-real machine test cases not corresponding to the test order condition table are classified into the test The non-real machine test case table having a high execution priority, the non-real machine test case table having a low execution priority, and the test order are classified into non-real machine test cases having a medium execution priority not corresponding to the order condition table. A test distribution method characterized by storing in a non-real machine test case table that does not fall under the condition table. In claim 3,
The third step includes
A test execution standard time table defining the test execution standard time of the real machine test and a test execution standard time of the non-real machine test, and a test switching operation time table defining the test switching operation time between values of the same factor Based on
The test execution time of the actual machine test case is set for each of the actual machine test case table having a high execution priority, the actual machine test case table having a low execution priority, and the actual machine test case table not corresponding to the test order condition table,
The test execution time of the actual machine test case is set for each of the non-real machine test case table having a high execution priority, the non-real machine test case table having a low execution priority, and the non-real machine test case table not corresponding to the test order condition table. A test distribution method characterized by: In claim 4,
The test execution method is characterized in that, for the actual machine test case, the test execution time is an added value of the test execution standard time of the actual machine test and the test switching operation time. In claim 4 or 5,
The fourth step includes
For each of the actual machine test case table having the higher execution priority, the actual machine test case table having the lower execution priority, and the actual machine test case table not corresponding to the test order condition table, the total test execution time of the actual machine test case is totaled. As the test execution time, the actual machine test cases are distributed to the respective workers by the test allocation execution time per worker obtained from the total test execution time,
The non-real machine test case table having a high execution priority, the non-real machine test case table having a low execution priority, and the non-real machine test case table not corresponding to the test order condition table, the test of the non-real machine test case. The total test execution time is defined as the total test execution time, and the non-real machine test cases are distributed to the respective workers by the test allocation execution time per worker obtained from the total test execution time,
The test distribution method characterized by storing the distributed real test case and the non-real test case in an output table after the test case distribution of the worker. In claim 6,
2. The test distribution method according to claim 1, wherein the distribution of the test cases to the output table after the distribution of the test cases is started from an actual machine test case in the actual machine test case table having a high execution priority. In claim 7,
When the number of actual machines is m and the number of workers is n (where m <n) as defined in the actual machine test condition table,
In the output table after the distribution of the test cases assigned to m workers, the real machine test case groups distributed from the real machine test case table having the higher execution priority are stored in order, and these tests are performed. In the output table after case distribution, the real machine test cases of the real machine test case group with the high execution priority distributed from the real machine test case table with the high execution priority are stored in order from the first storage position,
Thereafter, in the output table after the distribution of the test cases assigned to the remaining (nm) workers, the actual test case group distributed from the real machine test case table having the higher execution priority in order. In the output table after the storage of the test cases, and the storage of the actual test case group in the output table after the distribution of the test case that has been stored immediately before, The test distribution method is characterized in that data is stored from the storage position corresponding to the next storage position.

Images