JP4769832B2 - Test support system and test support program for integration work system - Google Patents

Description

  The present invention relates to a test support system and a test support program in a computer system that performs an integration work related to a construction price and the like, and in particular, it is possible to automatically perform a confirmation test in an update operation of an integration standard or an integrated unit price that occurs periodically. The present invention relates to a test support system and a test support method.

In general, in a computer system that performs processing based on a program, it is necessary to perform a test to confirm that input or updated data is correct as various types of data are added or updated. The test for confirming the data content is originally performed by visually confirming the data content displayed on the display or printed by the operator.
The same applies to the test process at the time of adding / updating data in the computer system that performs the integration work that is the subject of the present invention.

However, when data is added or updated, it is difficult to reliably check the validity of the data contents only by relying on visual observation by the operator.
Therefore, in order to make the confirmation work by the operator easy and accurate, a technique has been proposed in which a check list corresponding to the data content of the test target is automatically generated and presented to the operator.
For example, in Patent Document 1, when correcting document data such as drawings and specifications in a database of a computer system, check contents and know-how input from the correction screen are taken in and a check list is automatically created. The technology is described.
JP 2004-303072 A

  In the integration work such as construction price, the integration standards such as conditions and unit price are officially announced, and the number of data items is an enormous number of hundreds to thousands. Even if the checklist automatic creation technology disclosed in Patent Document 1 is used for the correction / revision work of the integration reference data, the number of items to be checked is enormous, so that it alone is the work efficiency and accuracy. The effect of improvement is not so much.

  In addition, in the integration work, the integration criteria such as conditions and unit prices are regularly revised at a time, so a huge number of data items need to be revised at one time, and these data updates are performed. There is a very special technical problem that requires a certain short period of time without error.

  Even if the check list automatic creation method disclosed in Patent Document 1 is used in the revision work of the accumulation standard in such an accumulation work, the check list of the update target data is simply displayed. If you are dealing with an enormous amount of data that is subject to revision, it is not easy to identify whether the checklist is a display of revision work or a display for correcting errors in revision work. Will be confused.

SUMMARY OF THE INVENTION In view of these problems of the prior art, the object of the present invention is to reduce the burden on an operator and to easily handle an integration standard that requires a huge amount of data to be revised at a time. In particular, the present invention is to provide a test support system and a test support program for an integration work system that can automatically perform a data update confirmation test.

  As a result of earnest research in view of the above-mentioned problem, the inventor has determined whether or not the data revision work has been performed by referring to the data accumulated cumulatively before and after the revision for each data revision item specified in advance. By automatically confirming and generating and displaying the confirmation result as a checklist, it was conceived that the test can be performed efficiently without burden on the operator.

That is, according to the present invention, data related to unit prices and standards relating to business orders and data and data related to gradually revised unit prices and standards are stored and managed in a unit price standard database cumulatively with the application date or date of revision as a key . a system for supporting test data updating operation due to revision of the unit price and the reference of that totalized business system,
Check target item input means for accepting input of data items to be checked according to the revision,
For checked data item that is the input, whether the data updating operations definitive in the unit price reference database based on whether or not the latest version of the data and the previous version of the data matching in the unit price reference database is performed Unit price standard revision inspection means to inspect
Unit price standard revision instructing means for urging the operator to update the data for the check target data item for which data updating is not performed in the unit price standard database;
And the check target data item that is the input, first; and a checklist generation means for outputting information indicating whether a data item data updating is performed in the unit price reference database matches And

In addition, the present invention stores and manages data related to unit prices and standards related to business ordering and data and data related to gradually revised unit prices and standards in the unit price standard database cumulatively by using the application date or date of revision as a key. A system that supports testing of data update work associated with the unit price and standard revision of the integration work system,
  Check target item input means for accepting input of data items to be checked according to the revision,
  The latest version data in the unit price standard database is searched using the application date or date of revision included in the data item to be checked as a key, and whether or not the previous version data matches the data Unit price standard revision inspection means for inspecting whether or not data update work is performed in the unit price standard database;
  Unit price standard revision instructing means for urging the operator to update the data for the check target data item for which data updating is not performed in the unit price standard database;
  A check list generation unit that outputs information indicating whether or not the input data item to be checked matches a data item for which data update work has been performed in the unit price standard database. And

According to the test support system according to the first or second feature, it is possible to compare the data related to the old unit price and standard with the new version data, and to determine that the data update has been performed if they are different. By comparing whether or not the updated data item detected in this way matches the check target data item, it can be determined whether or not an appropriate update has been performed.
  A characteristic of the revision work of unit price / standard in accumulating work is that a large amount of data items are revised at one time. Focusing on this characteristic, the application date or date of revision is gradually revised. It can be treated as a standard version. This makes it possible to cumulatively maintain and manage the criteria that are gradually revised.

Further, the present invention provides the test support system according to any one of the above features , wherein the unit price reference revision instructing means includes the input check target data item and a data item for which data update work has been performed in the unit price reference database. A third feature is that the operator is continuously prompted to perform data update work until there is no match or mismatch.

In this way, it is possible to reliably and efficiently update all target data items without omission.

The present invention also stores and manages data related to business unit orders and standards and data related to gradually revised unit prices and standards in the unit price standard database by using the application date or date of revision as a key. A computer test support program for supporting a test of data update work accompanying the revision of the unit price and standard of an integration business system,
  In the computer,
  Check target item input step for accepting input of data items to be checked according to the revision,
  Whether the data update operation in the unit price standard database is performed based on whether the latest version data in the unit price standard database matches the data of the previous version for the input check target data item Unit price standard revision inspection step to be inspected,
  A unit price standard revision instruction step for prompting an operator to update data for a data item to be checked that is not subjected to data update work in the unit price standard database;
  A fourth feature is that the step of outputting information indicating whether or not the input data item to be checked matches a data item for which data update work has been performed in the unit price standard database is executed. .

In addition, the present invention stores and manages data related to unit prices and standards related to business ordering and data and data related to gradually revised unit prices and standards in the unit price standard database cumulatively by using the application date or date of revision as a key. A computer test support program for supporting a test of data update work accompanying the revision of the unit price and standard of an integration business system,
  In the computer,
  Check target item input step for accepting input of data items to be checked according to the revision,
  The latest version data in the unit price standard database is searched using the application date or date of revision included in the data item to be checked as a key, and whether or not the previous version data matches the data Unit price standard revision inspection step for inspecting whether or not data update work is being performed in the unit price standard database;
  A unit price standard revision instruction step for prompting an operator to update data for a data item to be checked that is not subjected to data update work in the unit price standard database;
  And executing a check list generation step of outputting information indicating whether or not the input data item to be checked matches a data item for which data update work has been performed in the unit price standard database. Features.

According to the present invention, in the test support program according to the fourth or fifth feature, a unit price standard revision instruction step is performed on the computer, and the data update operation is performed on the input check target data item and the unit price standard database. The sixth feature is that the operator is continuously prompted to perform the data update operation until there is no coincidence with the performed data item.

  As described above, according to the test support system and the test support program of the integration work system of the present invention, in the revision operation of the integration standard in which a huge amount of data revision work must be performed at one time, It is possible to automatically perform a data update confirmation test with an easy operation without burden and efficiently. Therefore, it is possible to reduce the work burden for the data revision work test of the integration work system and improve the quality of the test.

  Hereinafter, the configuration, operation, and effect of the best embodiment of the test support system and test support program of the integration business system of the present invention will be described in detail with reference to the accompanying drawings.

[1] System Configuration FIG. 1 is a diagram schematically showing an overall configuration of a test support system for an integration business system according to an embodiment of the present invention.
In FIG. 1, the present system is configured to include a standard check target item table DB 101, a reference table DB 102, a unit price table DB 103, a unit price revision information table DB 105, and a standard revision information table DB 106 with a check list generation device 104 as a center.

FIG. 2 is a diagram schematically showing an internal configuration of the check list generation device 104.
In FIG. 2, a check list generation device 104 includes a CPU 203 that controls the operation of each member described below according to a predetermined program, a device volatile or non-volatile memory 201, a printer 202 that prints a display screen and predetermined information, and an operation A display device 204 that displays predetermined information for a user, an input device 205 that receives an operation input from an operator, and an external storage device 206 that stores and reads the predetermined information. The check list generation device 104 can be configured as a general computer device in which a necessary program for realizing a predetermined function to be described later is installed.

  FIG. 3 is a flowchart schematically showing a flow of checklist generation processing by the checklist generation apparatus 104. Each process illustrated in FIG. 3 is defined by a check list generation program installed in the check list generation apparatus 104 in advance. Details of each process will be described later together with the handling of each data to be processed.

[2] Data Configuration The table and data held by the standard check target item table DB 101, the standard table DB 102, the unit price table DB 103, the unit price revision information table DB 105, and the standard revision information table DB 106 shown in FIG. An example will be described.

  The standard check target item table DB 101 stores information on data items to be checked in the standard revision work of the integration work. Specifically, as shown in Fig. 4, the standard check target item table includes the classification of the standard revision, the new application month version, the old application month version, name, and unit of the standard code subject to the standard revision. Furthermore, the types of tables to be revised are defined as a management table, a condition table, a breakdown table, and a chart of progress. Each item for each table to be revised has two data, an input value and a collected value. These data are input by the operator using the input device 205 of the check list generation device 104 or generated by external data capture every time the standard is revised.

  The unit price list DB 103 cumulatively stores information related to unit prices of construction and the like updated by the revision of the standard of the integration work. Specifically, as shown in FIGS. 5 and 6, there are new and old unit price tables before and after the revision of the standard, and each unit price table includes the unit price application date, unit price code, unit price name, unit. Etc. are defined. These data are input by the operator using the input device 205 of the check list generation device 104 or generated by external data capture every time the standard is revised.

  The unit price revision information table DB 105 stores information (unit price revision information) related to the difference in data contents in the unit price table DB 103 between the new and old application years generated by the unit price revision generated by the check list generation device 104. Specifically, as shown in FIG. 7, the unit price revision information table defines the application date, unit price code, update category, unit price name, unit, etc. for the difference between the new and old application dates. .

The reference table DB 102 cumulatively stores information related to integration standards that are updated as a result of the revision of the standards for integration operations. Information relating to the integration criteria is held in four tables: a management table, a condition table, a breakdown table, and a chart.
As shown in FIGS. 11 and 12, the management table defines the application date, the reference code, the reference name, the unit, the amount of rebate, and the like.
As shown in FIG. 13 and FIG. 14, an application date, a reference code, a condition name, a condition value, and the like are defined in the condition table.
As shown in FIGS. 8 and 9, the breakdown table defines application date, reference code, breakdown line, breakdown code, and the like. Alternatively, as shown in FIG. 15 and FIG. 16, an application date, a reference code, a breakdown number, a breakdown code, a breakdown progress, and the like may be defined in the breakdown table.
As shown in the figure and figure, the application date, reference code, yield value or code is defined in the progress chart.

  The reference revision information table DB 106 stores information (reference revision information) regarding the difference in data contents in the reference table DB 102 between the new and old application dates generated by the unit price revision and the standard revision, which is generated by the checklist generation device 104. . Specifically, as shown in FIG. 10, application date, reference code, update classification, table classification, check item, flag, check item value, and the like are defined in the reference revision information.

[3] The processing flow of the checklist generation for specification revision process of the integration operational by processing test support system integrated business system shown in flow diagram 1, reference to the operation flow chart of the check list generating apparatus 104 shown in FIG. 3 While explaining.

  First, standard check target items are input to the system (step 301). The operator looks at the standard check target item table screen (screen displaying a table as shown in FIG. 4) displayed on the display device 204 of the check list generation device 104, and uses the input device 205 to check the revision target. Enter information about new application date, old application date, standard code, table to be revised, etc. Or it is good also as taking in and inputting standard check object item data from the outside. The input information constitutes the standard check target item table (FIG. 4) and is stored in the standard check target item table DB 101.

At this time, the combination of the new application date and the old application date must be the same for each standard code. In the example shown in Fig. 4, the standard code 001 is 200707 for the new application date and 200704 for the previous application date, and the management table name, unit, condition table, and breakdown table are subject to revision. It is shown that. The values of name 001 and unit 001 are the new application month and standard code as key items when the revised category is changed and new, and the old application date and standard code as key items when the revised category is deleted. Can be obtained from the management table of the reference table DB 102 (401).
The input value in the table takes a value of 1 for an item that has been input as a revision target, and the collected value takes a value of 1 for an item for which the revision has been reflected in the DB.

  Next, the check list generation device 104 generates unit price revision information before and after the reference revision based on the data stored in the unit price list DB 103 (step 302). The unit price revision information is generated by comparing the unit price table of the new application month version (FIG. 5) and the unit price table of the old application month version (FIG. 6) using the unit price code as a key item. In the example shown in FIGS. 5 and 6, the unit price code 102 is changed from the unit 102 in the old application date version (601) to the unit 102 ′ in the new application date version (501). Regarding the unit price code 106, a record that did not exist in the old application date version is added in the new application date version (502). These comparison results are stored in the unit price revision information table DB as a unit price revision information table (701, 702 in FIG. 7).

  Next, the check list generation device 104 generates reference revision information before and after the revision of the reference based on the data stored in the reference table DB 102 (step 303). First, based on the unit price revision information generated in step 302, a revision of information related to the breakdown of the unit price revision in the reference table DB 102 is searched, and the reference revision information is generated based on the search result. Specifically, in the unit price revision information table of the unit price revision information table DB 105 in FIG. 7, each of the unit price code 102 (701) and the unit price code 106 (702) to be revised and the application date are set as key items. A breakdown table in the reference table DB 102 is searched. Here, the date of application coincides with the breakdown table of the new application date (Fig. 8). In this breakdown table, the reference code and the breakdown line are acquired from the record having the unit price code 102 (801) and the unit price code 106 (802). Furthermore, using the acquired standard code 001 and breakdown line 02 and each of breakdown line 02 as key items, the old applicable month version breakdown table (Figure 9) is searched, and the new applied month version breakdown table and the old application Information on the difference from the year / month version breakdown table is stored in the standard revision information table DB 106 (FIG. 10) as standard revision information.

  In addition, the following other standard revision information is added to the standard revision information table of FIG. 10 one after another, and finally the standard revision information table as shown in FIG. 19 is obtained. Two records in the reference revision information table of FIG. 10 remain as records 1903 and 1904 in the reference revision information table of FIG.

  Subsequently, in the standard table DB 102, the management table of the new application date version (FIG. 11) and the management table of the old application date version (FIG. 12) are compared using the reference code as a key item, and information on the difference is used as a reference The revision information is stored in the standard revision information table DB 106. Specifically, when the management table of the new application date in FIG. 11 and the management table of the old application date in FIG. 12 are compared, for the standard code 001, the new application date (1101) and the old Since the standard name and unit are different in the applicable date (1201), the result is the standard revision information. Regarding the standard code 003, since the amount of rebate differs between the new application date (1102) and the old application date (1202), the result is used as the reference revision information. These reference revision information is stored as a record of the reference revision information table in the reference revision information table DB 106 (1901 and 1908 in FIG. 19).

Subsequently, in the standard table DB 102, the standard code is used as a key item, the new applied month version condition table (FIG. 13) is compared with the old applied month version condition table (FIG. 14), and information on differences is used as a reference. The revision information is stored in the standard revision information table DB 106. In particular,
Comparing the new application date version in Fig. 13 and the old application date version in Fig. 14, the criteria code 001 is subject to the conditions of the new application date version (1301) and the old application date version (1401). Since the condition value 1 of 2 is different, the result is used as the reference revision information. Regarding the standard code 003, since the condition name of condition 1 is different between the new application date version (1302) and the old application date version (1402), the result is used as the reference revision information. The reference revision information is stored as a record of the reference revision information table in the standard revision information table DB 106 (1902 and 1909 in FIG. 19).

  Subsequently, in the standard table DB 102, the new applied month version breakdown table (FIG. 15) and the old applied month version breakdown table (FIG. 16) are compared using the reference code and breakdown number as key items, and the difference is related. The information is stored in the standard revision information table DB 106 as standard revision information. Specifically, comparing the new application date version in FIG. 15 and the old application date version in FIG. 16, with respect to the breakdown number 02 of the standard code 002, the new application date version (1501) and the old application date version Since the breakdown code is different in the applicable date (1601), the result is used as the standard revision information. The breakdown number 03 of the reference code 002 exists only in the old application date (1602) and has been deleted from the new application date, so the result is used as the reference revision information. These standard revision information is stored as a record of the standard revision information table in the standard revision information table DB 106 (1905 and 1906 in FIG. 19).

  Subsequently, in the reference table DB 102, the new application month version of the cash flow chart (FIG. 17) and the old application date version of the cash flow chart (FIG. 18) are compared using the reference code and the cash chart number as key items. Then, the information regarding the difference is stored in the standard revision information table DB 106 as the standard revision information. Specifically, when the new application date version of FIG. 17 is compared with the old application date version of FIG. Since the value in the first row and third column is different between the previous application date (1801), the result is used as the standard revision information. In addition, regarding the chart number 01 of the standard code 003, since the second row is deleted in the new application date (1702), the result is used as the standard revision information. The reference revision information is stored as a record of the reference revision information table in the standard revision information table DB 106 (1907 and 1910 in FIG. 19).

  Next, the check list generation device 104 performs the standard revision information table (stored in the standard revision information table DB 106) generated in step 303 for the standard check target item (stored in the standard check target item table DB 101) input in step 301. By applying the (stored) data, a new standard check target item table is generated and displayed on the screen (step 304).

  20 and 21 are diagrams exemplifying standard check target item tables generated based on the data examples shown in FIGS. In these figures, when it is confirmed by the unit price revision information generation step 302 and the standard revision information generation step 303 that the revision target items in the standard table DB 102 and the unit price table DB 103 have been revised appropriately, The collected value is 1.

  Here, in the standard check target item table shown in FIG. 20, with respect to the name of the reference code 002, the input value is 1 but the collected value is 0 (2001). There is a discrepancy that the collected value is 1 even though the input value is 0 (2002). On the other hand, the operator re-enters the standard check target item or corrects the data update operation of each table so as to eliminate the inconsistency so that the two match.

  As a result, as shown in FIG. 21, when the input value and the collected value match for all revision target items in the standard check target item table (step 305), the check list generation device 104 generates a check list and generates the check list. The checked list is output (step 306). FIG. 22 is a diagram illustrating an example of a generated check list. As described above, the check list is generated by adding the collation result between the input value and the collected value in step 304 to the reference revision information table shown in FIG.

  The operator can check the output checklist and confirm that all necessary items have been completed without fail.

  As described above, the test support system and the test support program of the integration business system of the present invention have been described with specific embodiments, but the present invention is not limited to these. Those skilled in the art can make various changes and improvements without departing from the scope of the present invention.

  As shown in FIG. 1 and FIG. 2, the test support system and test support program of the integration business system of the present invention are constructed on hardware resources including a computer CPU, memory, auxiliary storage device, display, input device and the like. The above-described hardware processing is realized by an OS, an application, a database, a network system, and the like. Since it is specifically realized by using hardware resources, it corresponds to the technical idea using the laws of nature and can be used in the software industry and the like.

1 is a diagram schematically showing an overall configuration of a test support system for an integration business system according to an embodiment of the present invention. FIG. It is a figure which shows schematically the internal structure of the check list production | generation apparatus in the test assistance system of the integrating | accumulating business system shown in FIG. It is a flowchart which shows roughly the flow of the process of the check list production | generation by the check list production | generation apparatus in the test assistance system of the integrating | accumulating business system shown in FIG. It is a figure which shows the specific example of the table and data which standard check object item table | surface DB hold | maintains in the test support system of the integrating | accumulating business system shown in FIG. It is a figure which shows the specific example of the table and data which a unit price list DB in the test support system of the integrating | accumulating business system shown in FIG. It is a figure which shows the specific example of the table and data which a unit price list DB in the test support system of the integrating | accumulating business system shown in FIG. It is a figure which shows the specific example of the table and data which a unit price revision information table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 hold | maintains. It is a figure which shows the specific example of the table and data which the breakdown table of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 holds. It is a figure which shows the specific example of the table and data which the breakdown table of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 holds. It is a figure which shows the specific example of the table and data which the reference | standard revision information table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 hold | maintains. It is a figure which shows the specific example of the table and data which the management table | surface of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. It is a figure which shows the specific example of the table and data which the management table | surface of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. It is a figure which shows the specific example of the table and data which the condition table | surface of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 holds. It is a figure which shows the specific example of the table and data which the condition table | surface of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 holds. It is a figure which shows the specific example of the table and data which the breakdown table of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 holds. It is a figure which shows the specific example of the table and data which the breakdown table of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 holds. It is a figure which shows the specific example of the table and data which the scale table of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 hold | maintains. It is a figure which shows the specific example of the table and data which the scale table of reference | standard table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 hold | maintains. It is a figure which shows the specific example of the table and data which the reference | standard revision information table DB in the test support system of the integrating | accumulating business system shown in FIG. 1 hold | maintains. It is a figure which illustrates the standard check object item table | surface produced | generated based on the example of data shown in FIGS. 4-19 by the check list production | generation part in the test assistance system of the integrating | accumulating business system shown in FIG. It is a figure which illustrates the standard check object item table | surface produced | generated based on the example of data shown in FIGS. 4-19 by the check list production | generation part in the test assistance system of the integrating | accumulating business system shown in FIG. It is a figure which shows the example of the check list produced | generated by the check list production | generation apparatus in the test assistance system of the integrating | accumulating business system shown in FIG.

Explanation of symbols

101 Standard check target table DB
102 Standard table DB
103 Price list DB
104 Checklist generation device 105 Unit price revision information table DB
106 Standard revision information table DB
201 Memory 202 Printer 203 CPU
204 Display device 205 Input device 206 External storage device

Claims (6)

Is the data and gradually revised related bids and standards for business ordering the revised data on the unit price and the reference application date or apply date cumulatively held unit price reference database totalized operational systems are managed as a key A system that supports testing of data update work accompanying revision of unit price and standards,
Check target item input means for accepting input of data items to be checked according to the revision,
For checked data item that is the input, whether the data updating operations definitive in the unit price reference database based on whether or not the latest version of the data and the previous version of the data matching in the unit price reference database is performed Unit price standard revision inspection means to inspect
Unit price standard revision instructing means for urging the operator to update the data for the check target data item for which data updating is not performed in the unit price standard database;
A test support system comprising: a check list generation unit that outputs information indicating whether the input check target data item matches a data item for which data update work has been performed in the unit price standard database. Is the data and gradually revised related bids and standards for business ordering the revised data on the unit price and the reference application date or apply date cumulatively held unit price reference database totalized operational systems are managed as a key A system that supports testing of data update work accompanying revision of unit price and standards,
Check target item input means for accepting input of data items to be checked according to the revision,
The latest version data in the unit price standard database is searched using the application date or date of revision included in the data item to be checked as a key, and whether or not the previous version data matches the data and bid specification revision inspection means data updating operations definitive unit price reference database checks whether being performed,
Unit price standard revision instructing means for urging the operator to update the data for the check target data item for which data updating is not performed in the unit price standard database;
A test support system comprising: a check list generation unit that outputs information indicating whether the input check target data item matches a data item for which data update work has been performed in the unit price standard database.   The unit price standard revision instructing means continues to prompt the operator to perform a data update operation until there is no match / mismatch between the input check target data item and the data item for which the data update operation has been performed in the unit price standard database. The test support system according to claim 1 or 2, characterized by the above. Is the data and gradually revised related bids and standards for business ordering the revised data on the unit price and the reference application date or apply date cumulatively held unit price reference database totalized operational systems are managed as a key A computer test support program for supporting a test of data update work accompanying revision of unit price and standard,
In the computer,
Check target item input step for accepting input of data items to be checked according to the revision,
For checked data item that is the input, whether the data updating operations definitive in the unit price reference database based on whether or not the latest version of the data and the previous version of the data matching in the unit price reference database is performed A unit price standard revision inspection step for inspecting
A unit price standard revision instruction step for prompting an operator to update data for a data item to be checked that is not subjected to data update work in the unit price standard database;
A test support program for executing the step of outputting information indicating whether or not the input data item to be checked matches a data item for which data update work has been performed in the unit price standard database. Is the data and gradually revised related bids and standards for business ordering the revised data on the unit price and the reference application date or apply date cumulatively held unit price reference database totalized operational systems are managed as a key A computer test support program for supporting a test of data update work accompanying revision of unit price and standard,
In the computer,
Check target item input step for accepting input of data items to be checked according to the revision,
The latest version data in the unit price standard database is searched using the application date or date of revision included in the data item to be checked as a key, and whether or not the previous version data matches the data and bid specification revision checking step that the data updating operations definitive unit price reference database checks whether being performed,
A unit price standard revision instruction step for prompting an operator to update data for a data item to be checked that is not subjected to data update work in the unit price standard database;
A test support program for executing a check list generation step for outputting information indicating whether or not the input data item to be checked matches a data item for which data update work has been performed in the unit price standard database.   In the computer, the unit price standard revision instruction step performs the data update operation to the operator until there is no match / mismatch between the input data item to be checked and the data item for which the data update operation has been performed in the unit price standard database. 6. The test support program according to claim 4 or 5, which continues to be urged.