JP6610037B2 - Test execution apparatus, method, and program - Google Patents

Description

  The present invention relates to a test execution device, method, and program, and more particularly, to a test execution device, method, and program that require registration of input test data.

  Programs created for electronic computers are tested to see if they work as specified. This test is performed not only at the time of initial development but also at the time of specification change. This test includes tests for other functions as well as tests for changed specifications. This is because functions other than those whose specifications have been changed may be changed unintentionally. Such a test is called a regression test or a regression test.

  Patent Document 1 discloses an apparatus for automating a regression test of a program. This apparatus stores input test data and execution results when the previous test was performed. When the test is performed again, this apparatus automatically registers the input test data when the previous test was performed, executes the test, and compares the new execution result with the previous execution result. Thereby, this apparatus confirms whether functions other than the function whose specification has been changed have been changed unintentionally.

  As described above, in a program test including a regression test, it is generally necessary to register input test data in a test database for each test case. There is a problem that it takes time to register the input test data.

  Patent Document 2 discloses a method for shortening the registration (loading) time of the input test data. When a server device using this method continuously executes tests for a plurality of programs, the difference between the test data part updated in the previous test and the data part to be accessed in the next test is minimized. The test execution order is determined so that In addition, the server device performs partial load or full load of data accessed in the next test. The server device records data update information at the first execution of each test, and grasps the above-described difference using the information.

JP-A-4-172538 International Publication No. 2012/104991

  The method disclosed in Patent Document 2 loads at least a part of test data before performing a test. Therefore, in the test environment where it takes a long time to load the test data, the test data registration time is still insufficiently shortened. Furthermore, this method cannot be applied to tests in which the execution order is determined or tests that are executed for the first time.

  It is an object of the present invention to provide a test execution apparatus, method, and program that solve the above-described problems.

  The test execution apparatus according to an embodiment of the present invention includes input data storage means for storing first and second data patterns of transaction data, database storage means for storing a copy of the first data pattern, A database management unit that performs data access of the database storage unit, a first comparison between the first and second data patterns in the input data storage unit, a difference is extracted, and a copy of the first data pattern is used. After executing the first business process test, the database management means executes a difference reflection process for reflecting the difference in the first data pattern copy, and then uses the second data pattern copy. And test suite management means for executing the business process test.

  According to one embodiment of the present invention, the first and second data patterns of transaction data are stored in input data storage means, a copy of the first data pattern is stored in database storage means, and the input data The first and second data patterns in the storage means are compared to extract a difference, and after executing a first business process test using a copy of the first data pattern, the difference is converted to the first data pattern. A difference reflection process to be reflected in the copy of the data pattern is executed, and then a second business process test using the copy of the second data pattern is executed.

  A program according to an embodiment of the present invention includes a process for storing first and second data patterns of transaction data in input data storage means, and a process for storing a copy of the first data pattern in database storage means. A database management process for accessing data in the database storage means, and comparing the first and second data patterns in the input data storage means to extract a difference and using a copy of the first data pattern After executing the first business process test, a difference reflection process for reflecting the difference on the copy of the first data pattern is executed by the database management process, and then the copy of the second data pattern is used. The computer is caused to execute a test suite management process for executing the second business process test.

  The test execution apparatus according to the present invention can register test data of tests that are continuously performed at high speed.

FIG. 1 is a configuration diagram of a test execution device 30 according to the first embodiment. FIG. 2 is a configuration diagram of the computer device 40. FIG. 3 is a configuration diagram of test suite definition information stored in the test suite definition storage unit 33. FIG. 4 is a flowchart showing an outline of the operation of the test suite management unit 31. FIG. 5 is an operation flowchart of the master data registration process of the test suite management unit 31. FIG. 6 is an operation flowchart of transaction data registration processing of the test suite management unit 31. FIG. 7 is a diagram showing the configuration of the read management table 37. FIG. 8 is a diagram illustrating an example data pattern of transaction data. FIG. 9 is a configuration diagram of the test execution apparatus 30 according to the second embodiment.

  When performing a test of a program, for example, a regression test, it is necessary to newly store the original input test data, which is a precondition for executing the test, in the test system. If this is done for each test case, it takes time to store the input test data. The test system (test execution apparatus 30) according to the present invention speeds up test execution by minimizing the storage of input test data for each test case.

<First Embodiment>
<Configuration>
FIG. 1 is a configuration diagram of a test execution apparatus 30 according to the present embodiment. The test execution apparatus 30 includes a test suite management unit 31, a database management unit 32, a test suite definition storage unit 33, a test program storage unit 34, an input data storage unit 35, a database storage unit 36, and a read management table 37.

  The test suite definition storage unit 33 stores test suite definition information. The test suite definition information defines one or more test suites, and defines a plurality of test cases for each test suite. Furthermore, the test suite definition information defines the execution order of each test case in the test suite, the test data to be used, the test program to be used, and the like.

  The test program storage unit 34 stores a test program used in each test case.

  The input data storage unit 35 stores the original input test data used in each test case. The database storage unit 36 stores a copy of input test data used in a test case while a test case is being executed. In each test case, the test program accesses the input test data registered in the database storage unit 36 and performs the test.

  Input test data is roughly classified into two types. They are transaction data and master data. Master data is data common to a plurality of business processes, and transaction data is data specific to a certain business process. The master data is, for example, bank account information. The transaction data is, for example, online transaction transaction data, daily batch processing data, and monthly batch processing data.

  Of the input test data, transaction data needs to be newly registered in the database storage unit 36 for each test case for each test case. On the other hand, the master data does not necessarily have to be registered in the database storage unit 36 every test case.

  Note that transaction data is different for each test case, but only a part of the data is different. For example, if the transaction data is a collection of records, not all data items in each record are different, only a few data items are different, and other data items are the same. There are many cases.

  For example, transaction data used in a test case relating to a threshold value that causes a process to branch depending on whether a value of an integer data item is 100 or more includes two records having different values of the integer data item. These two records are, for example, a record in which the value of the integer data item is 100 and a record in 99. However, in the two records, only the integer data item has a different value, and there is often no difference in the values of the other data items.

  The test execution device 30 according to the present embodiment distinguishes the transaction data from the master data and uses this characteristic of the transaction data to efficiently register the test data in the database storage unit 36.

  The read management table 37 is a table in which input test data already registered in the database storage unit 36 is recorded. The input test data already registered in the database storage unit 36 is input test data used in a test case that has already been performed.

  The test suite management unit 31 executes each test case in the test suite designated by the user based on the test suite definition information. In other words, the test suite management unit 31 extracts the test case information from the test suite definition information of the specified test suite in the defined order, and registers a copy of the defined input test data in the database storage unit 36. . Thereafter, the test suite management unit 31 activates the defined test program. The test suite manager 31 may determine whether the test case is normal or abnormal based on predetermined result data when the execution of the test program is completed.

  The database management unit 32 receives an instruction from the test suite management unit 31 or the test program and accesses data in the database storage unit 36. The database management unit 32 is, for example, a relational database system. The database management unit 32 stores the update history of the data and the data before and after the update in a log file. In response to a request from the test suite management unit 31, it determines whether or not to update the data, provides information thereof, and updates the data. Process to restore.

  Here, the test suite management unit 31 and the database management unit 32 are configured by logic circuits. The test suite definition storage unit 33, the test program storage unit 34, the input data storage unit 35, and the database storage unit 36 are storage devices such as disk devices or semiconductor storage devices. The read management table 37 is stored in a semiconductor storage device such as a RAM (Random Access Memory).

  Note that the test execution device 30 may be realized by the computer device 40. FIG. 2 is a configuration diagram of the computer device 40.

  The computer device 40 includes a processor 41, a main storage unit 43, and an external storage device 42 that are connected to each other via a bus 44. The processor 41 reads and writes data from and to the main storage unit 43 and the external storage device 42 via the bus 44. Further, the processor 41 executes a program 45 stored in the main storage unit 43. The program 45 is initially stored in the external storage device 42, and the processor 41 may be loaded from the external storage device 42 into the main storage unit 43 when the computer device 40 is initially set.

  Here, the main storage unit 43 is a semiconductor storage device such as a RAM. The external storage device 42 is a storage device such as a disk device or a semiconductor storage device.

  The processor 41 functions as the test suite management unit 31 and the database management unit 32 by executing the program 45. That is, the processor 41 executes the process performed by the test suite management unit 31 and the database management unit 32 by executing the program 45. The external storage device 42 functions as a test suite definition storage unit 33, a test program storage unit 34, an input data storage unit 35, and a database storage unit 36. Further, the processor 41 creates a read management table 37 in the main storage unit 43.

  FIG. 3 is a configuration diagram of test suite definition information stored in the test suite definition storage unit 33. The test suite definition information includes, for example, a plurality of row records corresponding to test cases in the test suite. Each row record includes, for example, a test suite ID (Identification), a test case ID, an execution order, a transaction data definition, a master data definition, and a test program ID.

  The test suite ID and the test case ID are identification information of the test suite and the test case, respectively. The execution order defines the order in the test suite in which the test case is executed. The test program ID defines a test program used in the test case.

  The transaction data definition defines one or more transaction data used in the test case and its data pattern. The input data storage unit 35 stores original data of a plurality of data patterns for each transaction data.

  The first line of the test suite definition information example in FIG. 3 indicates that the test case A of the test suite T01 uses the data pattern AA of the transaction data A. The second row shows that the test case B of the test suite T01 uses the data pattern AB which is the same transaction data A but different pattern data. Further, the third row shows that the test case C of the test suite T01 uses the same transaction data A but the data pattern AC that is the third pattern data. Here, the patterns AA, AB, and AC of the transaction data A may be data that is mostly similar and only the values of some data items are different.

  The master data definition defines one or more master data used in the test case. Master data is data shared by a plurality of test cases. The input data storage unit 35 stores the original data corresponding to the master data.

  The first line of the test suite definition information example in FIG. 3 indicates that the master data X is used for the test case A of the test suite T01. The second row indicates that the test data B of the test suite T01 uses the master data X and Y. Further, the third row indicates that the master data Y is used for the test case C of the test suite T01.

<Operation>
The user of the test execution device 30 prepares test suite definition information and stores it in the test suite definition storage unit 33 before executing the test. At this time, the user defines the data to be input / updated by each test case by distinguishing whether the data is transaction data or master data.

  Further, the user prepares master data defined in the test suite definition information and stores it in the input data storage unit 35. Further, the user prepares each data pattern of transaction data defined in the test suite definition information and stores it in the input data storage unit 35.

  In addition, the user activates the test suite management unit 31 by specifying the ID of the test suite for performing the test. The user activates the test suite management unit 31 using a console device (not shown) connected to the test execution device 30.

  FIG. 4 is a flowchart showing an outline of the operation of the test suite management unit 31. The test suite management unit 31 sequentially extracts information on the test cases of the designated test suite from the test suite definition information (S1). The test suite management unit 31 extracts each test case in the order described in the test suite definition information.

  The test suite management unit 31 registers the master data used in the test case indicated by the master data definition in the database storage unit 36 (S2; details will be described later). Next, the test suite management unit 31 registers the data pattern of transaction data used in the test case indicated in the transaction definition in the database storage unit 36 (S3; details will be described later).

  After completing the registration of the input test data in the database storage unit 36, the test suite management unit 31 activates the test program used in the test case indicated by the test program ID. The test program executes the test while referring to or updating the input test data registered in the database storage unit 36 (S5). After execution of the test program, the test suite management unit 31 may determine whether the test is good or bad from the output value of the test program and the content of the input test data updated by the test program, and may output the determination result to the outside of the apparatus.

The test suite management unit 31 repeats the above operation until the test of all the test cases of the designated test suite is completed (Y in S5). FIG. 5 shows the master data registration process of the test suite management unit 31. It is an operation | movement flowchart. This process is executed in S2 of the flowchart of FIG.

  First, the test suite management unit 31 checks whether or not the master data of the test case to be implemented has already been registered in the database storage unit 36 (S11). This check is to check whether or not the master data of the test case to be executed has already been registered by the test case executed before. This check is performed with reference to the read management table 37.

  FIG. 7 is a diagram showing the configuration of the read management table 37. The read management table 37 records a flag indicating whether registration is already “completed” or “not” for each master data and transaction data registered in the test suite definition information. As soon as the test suite management unit 31 is activated (before S1), it generates and initializes the read management table 37. In the initial state, the flags of all master data and transaction data in the read management table 37 indicate a state of “No” (indicated by a blank in FIG. 7).

  FIG. 7A shows an initial read management table 37 based on the test suite definition information example shown in FIG. The read management table 37 indicates that both the transaction data A and B and the master data X and Y are unregistered.

  If the master data of the test case to be implemented is not yet registered (N in S11), the test suite management unit 31 reads the master data original in the input data storage unit 35 and registers it in the database storage unit 36. (S14). The test suite management unit 31 registers data in the database storage unit 36 using the database management unit 32. At this time, the test suite management unit 31 records in the read management table 37 that the registered master data has been registered.

  As described above, the test suite management unit 31 records the registration in the read management table 37 each time the transaction data A and B and the master data X and Y are registered for the first time.

  FIG. 7B shows master data of the test case (test suite T01, test case A) in the first line of the test suite definition information example of FIG. 3, and the read management table 37 after transaction data registration. In addition, each test case is implemented in the implementation order described in FIG. This read management table 37 indicates that master data X and transaction data A have been registered.

  FIG. 7C shows the master data of the test case (test suite T01, test case B) on the second line of the test suite definition information example of FIG. 3, and the read management table 37 after transaction data registration. This read management table 37 indicates that master data X and Y and transaction data A have been registered.

  Note that the master data of the test case (test suite T01, test case C) on the third line of the test suite definition information example of FIG. 3 and the read management table 37 after transaction data registration are also as shown in FIG. 7C). is there. This is because the master data X and transaction data A used in the test case are registered in the previous test case.

  FIG. 7D shows the master data of the test case (test suite T02, test case α) on the fourth line of the test suite definition information example of FIG. 3, and the read management table 37 after transaction data registration. Note that it is assumed that the test suite T02 is performed after the test suite T02. This read management table 37 indicates that master data X and Y and transaction data A and B have been registered.

  Returning to FIG. 5, if the master data of the test case to be implemented has already been registered (Y in S11), the test suite management unit 31 updates the database management unit 32 with whether or not the master data has been updated. Queries the availability of restoration. In other words, the test suite management unit 31 has changed whether or not the master data of the test case to be executed has been changed in the course of executing the test case that has been executed before, or can be restored if it has been changed. Is checked using the database management unit 32.

  When there is no update (N in S12), since the registered master data can be reused, the test suite management unit 31 ends the master data registration process.

  If there is an update (Y in S12) and update data can be restored (Y in S15), the test suite management unit 31 requests the database management unit 32 to restore the update data (S17). If the update data is restored, the registered master data can be reused, and the test suite management unit 31 ends the master data registration process.

  If there is an update (Y in S12) and the update data cannot be restored (N in S15), the test suite management unit 31 deletes the registered data from the database storage unit 36 (S16). Then, the test suite management unit 31 reads the master data original in the input data storage unit 35 and re-registers it in the database storage unit 36 (S18).

  When the master data registration process ends (Y in S12, S14, S17, and S18), the test suite management unit 31 has already registered all the master data of the test case to be implemented (S13). Y) The master data registration process is terminated. If there is unregistered master data of the test case to be executed from now (N in S13), the test suite management unit 31 performs the next master data registration process (returns to S11).

  FIG. 6 is an operation flowchart of transaction data registration processing of the test suite management unit 31. This process is executed in S3 of the flowchart of FIG.

  First, the test suite management unit 31 checks whether or not the transaction data of the test case to be implemented has already been registered in the database storage unit 36 (S21). At this time, the test suite management unit 31 checks whether the transaction data is registered, and does not check whether the data pattern to be registered is registered.

  This check is to check whether or not the transaction data of the test case to be executed has already been registered by the test case executed previously. This check is performed with reference to the read management table 37 described above.

  If the transaction data of the test case to be executed is not yet registered (N in S21), the test suite management unit 31 reads and registers the original transaction data data pattern of the test case to be executed (S28). . The test suite management unit 31 reads the data pattern from the input data storage unit 35 and registers it in the database storage unit 36.

  At this time, the test suite management unit 31 records the registered transaction data in the read management table 37. The test suite management unit 31 may record the data pattern of the registered transaction data in the read management table 37. By doing so, the test suite management unit 31 can easily know which data pattern is registered when transaction data is registered.

  If the transaction data of the test case to be executed has already been registered (Y in S21), the test suite management unit 31 determines whether or not the transaction data is updated and whether or not the update data can be restored. Inquire. In other words, the test suite management unit 31 determines whether the transaction data of the test case to be executed has been changed in the course of executing the test case that has been executed before, or can be restored if it has been changed. Check.

  If there is no update (N in S22), the test suite management unit 31 uses the already registered data pattern (hereinafter referred to as the previous pattern) as the data pattern (hereinafter referred to as the new data pattern) of the test case transaction data to be executed. Pattern). This process is called a difference reflection process.

  Even if there is an update (Y in S22), if the update data can be restored (Y in S29), the test suite management unit 31 requests the database management unit 32 to restore the update data (S31). If the update data is restored, the test suite management unit 31 executes a difference reflection process.

  For example, when registering the transaction data A of the test case (test suite T01, test case B) on the second line in the test suite definition information example of FIG. 3, the test suite management unit 31 changes the previous data pattern AA by the difference reflection process. Change to new data pattern AB.

  The transaction data is a set of a plurality of records, and each record includes a record ID and a plurality of data items.

  In the difference reflection process, the test suite management unit 31 accesses both the previous data pattern and the new data pattern in the input data storage unit 35. The test suite manager 31 obtains from the test suite definition information which data pattern is the previous data pattern and the new data pattern. The test suite management unit 31 may obtain from the read management table 37 which data pattern is the previous data pattern.

  Then, the test suite management unit 31 determines, for all record IDs included in one or both of them, whether the record of the ID is included in the previous or new data pattern (S23). The following processing is performed according to the result of the separation.

A: When the record of the ID is included in both the previous and new data patterns In this case, the test suite management unit 31 takes out the record of the same ID from each of the previous data pattern and the new data pattern, and both records Is compared with the data item unit. When the test suite management unit 31 detects a data item having a difference, the test suite management unit 31 sets the value of the data item of the record having the same ID in the database storage unit 36 with the value included in the new data pattern, and the database management unit 32 To replace (S24).

  Specific examples in this case are shown in A) and B1) of FIG. 8A shows a pre-data pattern in the input data storage unit 35. FIG. B1) in FIG. 8 is a new data pattern in the input data storage unit 35. Here, each record of ID01 to ID03 is included in both data patterns. In this case, the test suite management unit 31 compares the data of both records of ID01, and the value of data item 1 is “a” in the previous data pattern, but “d” in the new data pattern. Is detected. Then, the test suite management unit 31 updates the value of the data item 1 of the record of ID01 in the database storage unit 36 from “a” to “d”. Similarly, the test suite management unit 31 replaces the values of the data item 1 of the records of ID02 and ID003 in the database storage unit 36 with “e” and “f” from “b” and “c”.

B: When the record of the ID is included only in the previous data pattern In this case, the test suite management unit 31 deletes the record of the ID in the database storage unit 36 (S25).

  Specific examples in this case are shown in FIGS. 8A and 8B. 8A shows a pre-data pattern in the input data storage unit 35. FIG. B2) in FIG. 8 is a new data pattern in the input data storage unit 35. Here, the record of ID02 is included only in the previous data pattern. In this case, the test suite management unit 31 deletes the record of ID02 in the database storage unit 36.

C: When the record of the ID is included only in the new data pattern In this case, the test suite management unit 31 additionally registers a copy of the record of the ID in the input data storage unit 35 in the database storage unit 36 ( S26).

  Specific examples in this case are shown in A) and B3) of FIG. 8A shows a pre-data pattern in the input data storage unit 35. FIG. B3) in FIG. 8 is a new data pattern in the input data storage unit 35. Here, the record of ID04 is included only in the new data pattern. In this case, the test suite management unit 31 additionally registers a copy of the record with ID 04 in the input data storage unit 35 in the database storage unit 36.

  Returning to FIG. 6, when there is an update (Y in S22), and update data cannot be restored (N in S29), the test suite management unit 31 deletes the registered data from the database storage unit 36. (S30). Subsequently, the test suite management unit 31 reads a new original data pattern of transaction data in the input data storage unit 35 and registers it in the database storage unit 36 (S32).

  When the transaction data registration process ends, the test suite management unit 31 ends the transaction data registration process if all the transaction data of the test case to be executed has been registered (Y in S27). If any of the transaction data of the test case to be implemented is unregistered (N in S27), the test suite management unit 31 performs the next transaction data registration process (returns to S21).

<Effect>
The test execution device 30 according to the present embodiment can register test data of tests that are continuously performed at high speed.

  The first reason is that the test suite management unit 31 registers the data of the test case to be executed by reflecting the difference in the data pattern of the transaction data in the database storage unit 36.

  Transaction data is different for each test case, but it is often partial data. In a database system, particularly a relational database system, the cost of INSERT processing is generally higher than that of UPDATE processing. The reason is that the UPDATE process is less expensive to create an index than the INSERT process, and the number of data to be transferred is smaller than the INSERT process. For this reason, for example, when data that differs only partially is reinserted each time, such as in a regression test, transaction data registration can be speeded up by using UPDATE processing instead of INSERT processing.

  The second reason is that the data is not compared with the master data common to the test case because it is distinguished from the transaction data unique to the test case.

  Further, the test execution device 30 of the present embodiment does not place excessive restrictions on the input data access of the test program.

  This is because the test program can update the master data and the transaction in order to restore the update data. Before reflecting the difference in the data pattern of the transaction data in the database storage unit 36, the update data is restored, so that the difference in the database storage unit 36 is reflected based on the difference in the transaction data in the input data storage unit 35. Is possible.

<Modification>
The database management unit 32 may not be a relational database system. The database management unit 32 may be an index sequential file system or an in-memory database system. Similar effects can be obtained. The reason is that the two processes of deleting and adding records can be reduced to one process only for updating records.

<Second Embodiment>
FIG. 9 is a configuration diagram of the test execution apparatus 30 according to the second embodiment. The test execution device 30 includes a test suite management unit 31, a database management unit 32, an input data storage unit 35, and a database storage unit 36.

  The input data storage unit 35 stores first and second data patterns of transaction data. The database storage unit 36 stores a copy of the first data pattern. The database management unit 32 performs data access to the database storage unit 36.

  The test suite management unit 31 compares the first and second data patterns in the input data storage unit 35 and extracts a difference. Then, the test suite management unit 31 executes a first business process test using a copy of the first data pattern. Thereafter, the test suite management unit 31 executes a difference reflection process for causing the database management unit 32 to reflect the difference on the copy of the first data pattern, and a second business process test using the copy of the second data pattern Execute.

  The test execution device 30 according to the present embodiment can register test data of tests that are continuously performed at high speed.

  The reason is that the test suite management unit 31 registers the data of the test case to be executed by reflecting the difference in the data pattern of the transaction data in the database storage unit 36.

  While the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.

DESCRIPTION OF SYMBOLS 30 Test execution apparatus 31 Test suite management part 32 Database management part 33 Test suite definition storage part 34 Test program storage part 35 Input data storage part 36 Database storage part 37 Reading management table 40 Computer apparatus 41 Processor 42 External storage apparatus 43 Main storage part 44 bus 45 program

Claims (10)

Input data storage means for storing first and second data patterns of transaction data in which a predetermined execution order is predetermined ;
Database storage means for storing a copy of the first data pattern;
Database management means for accessing data in the database storage means;
The database management means after comparing the first and second data patterns in the input data storage means to extract a difference and executing a first business process test using a copy of the first data pattern Executing a difference reflection process for reflecting the difference to the copy of the first data pattern, and then executing a second business process test using the copy of the second data pattern; A test execution device comprising: The first and second data patterns include a plurality of records including identification information and a plurality of data items,
The test suite management means, when there is a difference in the value of the same data item in the record of the same identification information included in each of the first and second data patterns, of the record included in the second data pattern 2. The test execution apparatus according to claim 1, wherein the value of the data item is stored in a copy of the first data pattern in the database storage means. The database management means performs data pattern restoration processing for restoring data updated during execution of the first business process test out of the copy of the first data pattern,
The test execution apparatus according to claim 1, wherein the test suite management unit executes the difference reflection process for the copy of the first data pattern after the data pattern restoration process. The input data storage means further stores master data commonly used in the first and second business processes,
The database storage means further stores a copy of the master data;
The database management means performs a master data restoration process for restoring the data updated during the execution of the first business process test out of the copy of the master data,
The test suite management means executes a second business process test using the second data pattern after the master data restoration process and the difference reflection process for the copy of the first data pattern. 4. The test execution device according to any one of 1 to 3. Storing first and second data patterns of transaction data in which a predetermined execution order is predetermined in the input data storage means;
Storing a copy of the first data pattern in a database storage means;
The first and second data patterns in the input data storage means are compared to extract a difference, and after executing a first business process test using a copy of the first data pattern, the difference is A method of executing a difference reflection process to be reflected in a copy of the first data pattern, and thereafter executing a second business process test using the copy of the second data pattern. The first and second data patterns include a plurality of records including identification information and a plurality of data items,
When there is a difference in the value of the same data item of the record of the same identification information included in each of the first and second data patterns, the value of the data item of the record included in the second data pattern is 6. The method of claim 5, wherein the method is stored in a copy of the first data pattern in the database storage means. Performing a data pattern restoration process for restoring data updated during execution of the first business process test among copies of the first data pattern;
The method according to claim 5, wherein after the data pattern restoration process, the difference reflection process for the copy of the first data pattern is executed. In the input data storage means, further, master data commonly used in the first and second business processes is stored,
The database storage means further stores a copy of the master data,
Performing master data restoration processing for restoring data updated during execution of the first business process test among copies of the master data,
The second business process test using the second data pattern is executed after the master data restoration process and the difference reflection process for the copy of the first data pattern. Section method. A process of storing first and second data patterns of transaction data having a predetermined execution order determined in the input data storage means;
Storing a copy of the first data pattern in a database storage means;
A database management process for accessing data in the database storage means;
The database management process after comparing the first and second data patterns in the input data storage means to extract a difference and executing a first business process test using a copy of the first data pattern Performing a difference reflection process for reflecting the difference to the copy of the first data pattern, and then a test suite management process for executing a second business process test using the copy of the second data pattern; A program that causes a computer to execute. The first and second data patterns include a plurality of records including identification information and a plurality of data items,
Included in the second data pattern when there is a difference in the value of the same data item in the record of the same identification information included in each of the first and second data patterns in the test suite management process The program according to claim 9, wherein the value of the data item of the record is stored in a copy of the first data pattern in the database storage means.

Images