JP2009271840A - Testing device, testing method, and test program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a testing device for verifying an application without updating a database. <P>SOLUTION: This testing device is provided with: an input data storage part 1 for storing an input data; an output data storage part 5 for storing test result information; an application program control part 3 for reading out the input data from the input data storage part 1, executing an application to be tested according to the input data, and outputting an execution result; and a database pseudo-control part 4 for converting content of the execution result into a database updating language, to update the database in a pseudo manner, and for returning the result to the application program control part 3. The application program control part 3 records the test result information in the output data storage part 5, based on the pseudo-updated result. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a test apparatus that executes an application test without updating a database, and a test method thereof.

  Conventionally, when an application test is performed, the result is reflected in the database each time the test is executed. Therefore, it is necessary to restore the database to re-execute.

  On the other hand, in the following Patent Document 1, a cache in which a copy of a part of a database is placed is provided, and an update operation is performed on the cache instead of an update operation on the database, so that the contents of the database are in an initial state. A technique for artificially updating the database while maintaining the above is disclosed.

JP-A-6-161858

  However, according to the above-described conventional technique, a copy of the database must be created on the cache each time a test is performed. In addition, since the copy on the cache is updated, there is a problem that it is not suitable for application when the same process is repeated many times.

  The present invention has been made in view of the above, and an object of the present invention is to obtain a test apparatus, a test method, and a test program capable of verifying an application without updating a database.

  In order to solve the above-described problems and achieve the object, the present invention is a test apparatus that tests an application, and includes input data storage means for storing test input data, and an execution result of the application. Output data storage means for storing test result information; business data control means for reading input data from the input data storage means, executing an application to be tested according to the input data, and outputting the execution result; When the execution result of the application is input from the business program control unit, the input content is converted into a language for updating the database, and then the database is updated in a pseudo manner. A database pseudo control that returns the update result to the business program control means. And the business program control means, based on the pseudo update result received from the database pseudo control means, the log including the input data, the form output data, and a record relating to the database update as the test result information It is recorded in the output data storage means.

  According to the present invention, it is possible to verify the application by referring to the stored result data without actually updating the database, and it is possible to repeatedly test in a state close to a real environment. .

  Embodiments of a test apparatus according to the present invention will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 is a diagram illustrating a configuration example of a test apparatus. The test apparatus includes an input data storage unit 1, an input data batch reading unit 2, a business program control unit 3, a database pseudo control unit 4, an output data storage unit 5, and a compare result batch output unit 6. I have.

  The input data storage unit 1 holds input data used for testing. The input data batch reading unit 2 reads test target data held in the input data storage unit 1 when performing a test. The business program control unit 3 controls execution of the business program and also controls the database pseudo control unit 4 to perform database pseudo update. Here, the pseudo update means that the database update command issued by the business program is converted into an actual language for updating the database, and update processing excluding confirmation (commit) is performed. The database pseudo control unit 4 performs pseudo update on the database to be updated in accordance with control by the business program control unit 3.

  The output data storage unit 5 holds result data such as log data and form data output by the business program to be tested. The compare result batch output unit 6 reads the result data from the output data storage unit 5, compares the results before and after updating the business program, and outputs the compare result list and the difference input data as files. The compare result list is a file in which the compared results are output as a list. The difference input data is a file to which corresponding input data is output when the result data are different.

  In FIG. 1, a business program 10 is representatively described as a test target business program, and a database 11 is representatively described as a database that the business program 10 performs update processing. The business program 10 is an executable object state.

  Next, the operation of the test apparatus configured as described above will be described in detail using actual data. Hereinafter, this test apparatus will be used for verifying the logic of the business program in the sales distribution module. The test is performed before and after the logic update. The test before the logic update is the first test, and the test after the logic update is the second test.

  FIG. 2 is a flowchart showing the operation of the test apparatus, that is, the application test process. When the test apparatus starts operation, the input data batch reading unit 2 reads in batch input data to be transferred to the business program 10 from the input data storage unit 1 (step S1). FIG. 3 is a diagram illustrating an example of input data. The “function number” in FIG. 3 is an ID that uniquely indicates the processing content, and is “001 (order received)” as an example here. “Orderer code” is the ID of the supplier, and “Product code” is the ID of the product. “Number of orders” is the quantity ordered.

  If there is one or more input data (step S2: Yes), the business program control unit 3 executes the business program 10 according to the input data (step S3). Here, the business program 10 allocates inventory for the order data, updates the inventory table, and outputs the allocation result in a form. When the database update process occurs, the business program 10 issues an update request together with the update content and passes it to the business program control unit 3. On the other hand, when there is no input data (step S2: No), the process is terminated.

  When the business program control unit 3 receives an update request from the business program 10, the business program control unit 3 passes the update contents to the database pseudo control unit 4. The database pseudo control unit 4 converts the update contents into a language for the database, and performs pseudo update of the database 11. FIG. 4 is a diagram illustrating an example of the format of the inventory table. In the inventory table of FIG. 4, “stock quantity” for “product code” is registered. In the database 11, a process of subtracting the order quantity “100” from the inventory quantity “10000” of the product code “BBB” to “9900” is performed. Then, the database pseudo control unit 4 receives a return of the update result from the database 11 and delivers the update result to the business program control unit 3.

  The business program control unit 3 stores the update result received from the database 11 and the created log in the output data storage unit 5 as result data (step S4). FIG. 5 is a diagram illustrating an example of a format of result data. As shown in FIG. 5, for example, the input data shown in FIG. 3 and the log and output form data regarding the processing performed on the input data are stored. FIG. 5 shows input data, logs, and form data in order from the top. Here, the inventory allocation result is output as the form data.

  Next, the business program control unit 3 determines whether or not the current test is a test for the business program after the logic update, based on parameters set at the start of the test. If the test is for a business program before the logic update (step S5: No), the process is terminated. In both cases of the first test and the second test, the test apparatus performs the processing of steps S1 to S4 and stores the result data in the output data storage unit 5.

  On the other hand, when the current test is a test for the business program after the logic update (step S5: Yes), the business program control unit 3 notifies the compare result batch output unit 6 to that effect. Upon receiving this, the compare result batch output unit 6 reads the result data of the first and second business programs 10 from the output data storage unit 5, and compares the result data (step S6). Then, the compare result batch output unit 6 identifies result data having a difference as a result of the comparison, and outputs a file as a compare result list (step S7). Further, the compare result batch output unit 6 extracts only the input data from the result data having a difference, and outputs a file as the difference input data (step S8).

  For example, when the logic update is a logic change or a defect correction, the result data differs before and after the update. Therefore, it is verified whether the result data is output as expected. If the result data is not as expected, solve the logic deficiency and test again using the difference input data.

  For example, it is assumed that the current logic change is a defect correction and a test is performed before and after the correction. FIG. 6 is a diagram illustrating an example of the format of the compare result list. As shown in FIG. 6, the input data and the result data of the first and second tests are shown. In the first test, the post-operation data for the operation table “inventory table” is “8800”. This result is incorrect because the order quantity “100” is subtracted from the original inventory quantity “10000” (see FIG. 4). On the other hand, since the post-operation data is “9900” in the second test, it can be seen that the logic update (correction) is as expected.

  In addition, for example, if the logic is “rewrite the same logic in a different language (change Cobol to C language, etc.)”, the result data should be the same before and after the logic update. . In this case, if the results are different, the update is incomplete. If any deficiencies are found in the update, the deficiencies in logic are resolved and a test is performed again using the difference input data 8.

  FIG. 7 is a diagram showing an example of the format of the difference input data, and only the input data listed in the compare result list is extracted. The difference input data has the same format as the input data of FIG. As described above, when the first and second test results should be the same, the test can be executed again using the difference input data. In addition, the test results of the first time and the second test should be different, but if it is not partly as expected, the necessary data can be selected from the difference input data and the test can be executed again.

  As described above, in the present embodiment, the database is artificially updated without committing the update process, and the form output and the log of the database update result are output. Thereby, the user can verify the application by referring to the stored result data without actually updating the database. Moreover, in order to avoid actual updating while accessing the actual database, it is possible to repeatedly test in a state close to the actual environment.

  In addition, the test apparatus according to the present embodiment is applied before and after changing the logic of the program, the result data are compared with each other, and the list is output when they are different. Thereby, the verification regarding the change of the program can be facilitated, and the obtained list can be used for the second test.

  Next, a computer system that operates as the test apparatus shown in the present embodiment and can realize the above-described test processing will be described.

  The computer system includes, for example, a control unit including a CPU, a memory unit, a display unit, an input unit, a CD-ROM drive unit, a disk unit, and an external I / F unit. Are connected via a system bus.

  The control unit executes processing performed by the input data batch reading unit 2, the business program control unit 3, the database pseudo control unit 4, and the compare result batch output unit 6, that is, the test program of the present invention. The memory unit is composed of various memories such as a RAM and a ROM including the input data storage unit 1 and the output data storage unit 5. The memory unit stores programs to be executed by the control unit, necessary data obtained in the course of processing, and the like. Remember. The display unit is composed of a CRT, LCD (Liquid Crystal Display Panel), etc., and displays various screens for the computer user. The input unit includes a keyboard, a mouse, and the like, and is used by a computer user to input various information. Here, it is assumed that a test program describing the processing of the present embodiment is stored in the CD-ROM.

  Here, an example of the operation of the computer until the test program can be executed will be described. First, in the computer system configured as described above, a test program is installed in a disk unit from a CD-ROM set in a CD-ROM drive unit. The program read from the disk unit is stored in the memory unit when the computer system is activated or when the program is executed. In this state, the control unit (CPU) executes an application test according to the program stored in the memory unit.

  In the present embodiment, a program in which the test process is described is provided on a CD-ROM. However, the recording medium of this program is not limited to this, and depends on the computer constituting the system. For example, other recording media such as a magnetic disk such as a floppy (registered trademark) disk, a magneto-optical disk, and a magnetic tape may be used. Moreover, it is good also as using the program provided by transmission media, such as an email and the internet.

  As described above, the test apparatus, test method, and test program according to the present invention are useful for verifying applications including database update processing, and are particularly suitable for verifying the validity of logic changes.

It is a figure which shows the structural example of a test apparatus. It is a flowchart which shows operation | movement of a test apparatus. It is a figure which shows an example of input data. It is a figure which shows an example of the format of an inventory table. It is a figure which shows an example of the format of result data. It is a figure which shows an example of a format of a comparison result list. It is a figure which shows an example of the format of difference input data.

Explanation of symbols

1 Input Data Storage Unit 2 Input Data Batch Reading Unit 3 Business Program Control Unit 4 Database Pseudo Control Unit 5 Output Data Storage Unit 6 Compare Result Batch Output Unit 10 Business Program 11 Database

Claims (7)

A test device for testing an application,
Input data storage means for storing test input data;
Output data storage means for storing test result information as an application execution result;
Business program control means for reading input data from the input data storage means, executing an application to be tested according to the input data, and outputting the execution result;
When the execution result of the application is input from the business program control unit, the input content is converted into a language for updating the database, and then the database is updated in a pseudo manner. Database pseudo control means for returning an update result to the business program control means;
With
The business program control means, based on the pseudo update result received from the database pseudo control means, the output data storage means as the test result information including the input data, the form output data, and a log including records relating to database update. Test equipment characterized by recording in The business program control means reads the test result information before and after the logic update recorded in the output data storage means by executing the application after the logic update after executing the application before the logic update according to the input data, Comparison result output means for comparing the read test result information and outputting the comparison result,
The test apparatus according to claim 1, further comprising: The comparison result output means further includes:
The test apparatus according to claim 2, wherein when the test result information before and after the logic update is different, input data used for execution of the application before and after the logic update is output. An application testing method,
An execution step of reading test input data from the input data storage unit and executing the test target application according to the input data;
A pseudo-update step of pseudo-update the database after converting the execution result of the application in the execution step into a language for updating the database;
A recording step of recording the input data, the form output data, and a log including a record relating to database update in the output data storage unit as test result information based on a pseudo update result which is a result of the update by the pseudo update step;
A test method characterized by comprising: A first test step for executing the execution step, the pseudo-update step, and the recording step for the application before the logic update;
A second test step for executing the execution step, the pseudo-update step, and the recording step for the application after the logic update;
A comparison result output step of reading test result information before and after logic update recorded in the output data storage unit by executing the first and second test steps, comparing the read test result information, and outputting the comparison result When,
The test method according to claim 4, further comprising: When the test result information before and after the logic update is different, an input data output step for outputting input data used for execution of the application before and after the logic update,
The test method according to claim 5, further comprising:   A test program for causing a computer to execute the test method according to claim 4.

Images