JP2000284952A - Software generation test linking mechanism - Google Patents

Abstract

PROBLEM TO BE SOLVED: To generate and execute plural pieces of software and corresponding test suits according to the constitutional information. SOLUTION: This mechanism is provided with a software constitution setting means 2 which prepares software constitutional information 102, a software generating means 3 which generates software 104 based on the software constitutional information 102, a test program database 105 which stores a test program, and a test executing means 4 which executes the test of the software generated by the software generating means 3 by using test suits generated by connecting plural corresponding test programs with plural software modules indicated by the software constitutional information 102 based on a test program correspondence chart 106 indicating the correspondence of software modules to test programs, and which prepares the tested result information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to software generation and testing. More specifically, the present invention relates to a software generation / test cooperation mechanism for generating a plurality of software according to the configuration information and generating and executing a test suit according to the configuration information.

[0002]

2. Description of the Related Art Conventionally, in software generation and test work, each software is generated in accordance with its specification information, and then a test suit (a program group for implementing a software test) corresponding to each software is generated. And
The test is performed. Generally, most of software generation and test operations are performed manually, but the following methods are employed in order to improve work efficiency and prevent erroneous operations.

FIG. 35 shows, for example, Japanese Patent Application Laid-Open No. 6-274336.
1 is a software test environment construction apparatus shown in FIG. The software test environment construction device is a software test environment construction device for constructing a test environment program group for testing software incorporated in any of a plurality of subsystems constituting a system. System configuration specification information creation support processing 20
When the hardware specification information 202 is input, the user 1 inputs the subsystem definition information 203 through dialogue with the user based on the hardware specification information 202, and creates the system configuration specification information 204. When the system configuration specification information 204 is input, the test environment generation processing 205 causes the user to input the specification 206 under test based on the dialogue with the user based on the system configuration specification information 204, and the MPU (Micr) prepared in the simulator library 207.
o Processing Unit) simulator to generate a test environment program group 208. As a result, the software test environment construction equipment supports the user in collecting the information for constructing the test environment program group from the hardware specifications of the test target system, and based on the collected information, the test environment program By automatically generating groups, the work load on the user is reduced.

[0004]

However, in the conventional example,
For software, a test suite consisting of a group of programs required to implement software testing can be automatically generated according to the difference in hardware configuration. For such software, the test suit cannot be automatically generated according to the difference in the configuration of the software. The difference in software configuration is a difference between software modules of software components or a difference between attribute values corresponding to the software modules. Therefore, when software of various configurations, that is, a plurality of types of software having different configurations is generated, a test suit corresponding to the software cannot be easily automatically generated, resulting in a problem of low work efficiency. there were. Further, in the conventional example, there is a mechanism for generating a test suit, but there is no mechanism for generating software, and software generation and testing cannot be performed by the software test environment construction apparatus. However, there is a problem that work from software generation to test execution cannot be performed in a unified environment, resulting in poor operability and poor work efficiency.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems, and it is an object of the present invention to implement a test on software composed of a plurality of software modules in accordance with a difference in software configuration. It is another object of the present invention to realize a software generation test cooperation mechanism that generates a test suit including a plurality of programs.
Thus, when software of various configurations is generated, a test suit composed of one or a plurality of programs for realizing a test corresponding to the software can be easily automatically generated, and a user can generate test suits. The aim is to improve efficiency. In a unified user operation environment, a plurality of software is automatically generated according to the configuration information, and the corresponding test suit is automatically generated and executable according to the configuration information. It is an object of the present invention to assist a user in generating software and automating test work, and to improve work efficiency by reducing a work load and reducing erroneous operations. The unified user operation environment referred to here is, for example, an environment in which a series of work of software generation, test suit generation, and software test can all be performed by a menu selection operation on one screen such as a WWW browser. That is.

[0006]

The software generation test coordination mechanism of the present invention is characterized in that a software generation test coordination mechanism that performs software generation and test in cooperation with each other includes the following components. (A) a user interface for displaying information for supporting the generation and testing of software and receiving a request from a user; (b) a software component relating to a software module which is a component of the software and an attribute value corresponding to the software module A software component list file for storing information; and (c) displaying the software component information stored in the software component list file on the user interface, and specifying predetermined software component information from the software component information on the user interface. ,
Software configuration setting means for creating software configuration information including specified software component information and a value corresponding to the software component information,
(D) a software module database that stores software modules indicated by software component information stored in the software component list file; and (e) a plurality of software modules indicated by software component information included in the software configuration information. Software generating means for acquiring from a database, reflecting a value corresponding to the software component information included in the software configuration information in the software module, and combining the software modules to generate software; (f) the software component list file Test program data for storing a test program for implementing the functional test of each software module shown in Base, (g) test program correspondence table showing the correspondence between the test program stored in the software module and the test program database shown in the software component list file,
(H) acquiring from the test program database a plurality of test programs for implementing functional tests respectively corresponding to the plurality of software modules indicated in the software configuration information based on the test program correspondence table;
Test execution means for generating a test suit by combining a plurality of acquired test programs and executing a test of the software generated by the software generation means using the generated test suit to generate test result information.

The software generation test cooperation mechanism includes a software configuration information database storing a plurality of pieces of software configuration information, and the software configuration setting means converts software configuration information designated on the user interface from the software configuration information database. It is characterized by selecting and setting the software configuration based on the selected software configuration information.

The software configuration setting means searches the software configuration information database for software configuration information including a software component specified on the user interface, and searches for software corresponding to the software configuration information by software generation means. It is characterized in that the generation and the test by the test execution means are collectively executed.

[0009] The software generation test cooperation mechanism may include a software configuration including at least one of a rule regarding a combination of software modules indicated in the software component list file and a rule regarding setting of an attribute value corresponding to the software module. The software configuration setting means holds a rule and checks whether a configuration of software input from the user interface does not violate the software configuration rule.

The software generation test cooperation mechanism further stores software component information relating to a software module of the generated software and an attribute value corresponding to the software module in the software component list file, and stores the software module in the software module. Component management means is provided for storing the generated software and a plurality of test programs corresponding to the generated software in a test program correspondence table stored in a database.

[0011] The software generation test cooperation mechanism further includes a software database for storing the software generated by the software generation means, specifies the software on the user interface, and acquires the specified software from the software database. And a software management means for acquiring the information on a user interface.

The software generation test cooperation mechanism has a software configuration information correspondence table that associates software configuration information in the software configuration information database with software in the software database.
The software management means causes a software component to be specified on the user interface, and searches software configuration information corresponding to software in a software database including the specified software component from the software configuration information correspondence table. The software configuration information in the software configuration information database is searched based on the searched software configuration information, the software in the software database is extracted based on the searched software configuration information, and the software is tested by a test execution unit. It is characterized by being executed collectively.

The software generation test cooperation mechanism includes a first computer having the software configuration setting means, the software generation means, and the test execution means, and a second computer having the user interface. The first and second computers are connected by communication means.

[0014] The software generation test cooperation mechanism further includes a user for determining whether the first computer is permitted to use at least one of the software configuration setting means, the software generation means, and the test execution means. Holding account information, and determining whether or not the use request is permitted based on the user account information in response to a use request from the second computer connected to the first computer by the communication means. I do.

The software generation test cooperation mechanism includes a software generation computer for generating software and a test suite, and a software test computer for testing software, and connects both computers via a network. Remote execution request means for sending a software test execution request to the software test computer together with the attribute value indicated in the software configuration information to the software generation computer via the network, and the software test and the software test suite via the network First file transfer means for sending to the software test computer, the software generation computer based on the software test execution request sent from the software generation computer by the remote execution request means to the software test computer. Remote execution executing means for executing a software test using the software and the test suite sent from the first computer by the first file transfer means to create test result information, and a test executed by the remote execution executing means And a second file transfer means for sending the result information to the software generating computer via the network.

A computer-readable recording medium according to the present invention is characterized by recording a program for causing a computer to function as the above-described software generation test cooperation mechanism.

[0017]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Embodiment 1 Hereinafter, a software generation test cooperation mechanism that generates software and a test suit according to software configuration information and automatically performs a software test will be described with reference to the drawings.

FIG. 1 is a configuration diagram of a software generation test cooperation mechanism showing an embodiment of the present invention. In FIG. 1, a user interface 1 is an operation interface for a user to perform software configuration setting, software generation, and software testing. The software configuration setting unit 2 converts the software component information from the software component list file 101 storing software component information including a name list of software modules which are components of the software and a name list of attribute values corresponding to the software module to the user interface 1. , And input information selected from the displayed software component information, and software configuration information including a list of software module names input from the user interface 1, names of attribute values corresponding to the software modules, and their value definitions 102. In response to a software generation request input from the user interface 1, the software generation means 3 converts software configuration information 102 from software module database 103 in which all software modules indicated in software component list file 101 are stored.
Is a means for selecting the software module shown in (1), reflecting the attribute value shown in the software configuration information 102 on the corresponding software module, and combining the software modules to generate software 104.
The test execution means 4 holds one or a plurality of test programs for realizing a functional test corresponding to each software module included in the software module database 103 in the test program database 105, and stores the software module database in the test program correspondence table 106. Manages the correspondence between each software module in the test program 103 and one or more test programs in the test program database 105;
2, a corresponding test program shown in the test program correspondence table 106 is selected from the test program database 105 from the software module shown in FIG. 2, and the test programs are combined to generate a test suit 107;
The software 104 is started, and the software configuration information 1
By passing the attribute value name and its value list shown in FIG. 02, the test suit 107 is started, the test of the software 104 is executed, and the test result information 108 created by the test suit 107 is displayed on the user interface 1 by the means. is there. By combining the test program, the test suit 10
Generating 7 means to combine a plurality of test programs selected from the test program database into one program that can be executed continuously.

An example of the difference in the software configuration will be described with reference to FIG. The difference in the software configuration means that the software component of the software component or the attribute value corresponding to the software module is different. For example, as shown in FIG. 2, in the case of a μ kernel-based OS (Operating System), a configuration by selecting function sets A to N including one or a plurality of software modules as constituent elements of the OS, setting attribute values, and the like. It is necessary to generate an OS based on the same configuration,
The purpose of this mechanism is to automatically generate and test software according to the difference in the components of such software (for example, OS).

FIG. 3 shows an example of the software component information 130 stored in the software component list file 101 and displayed on the user interface 1. In the figure, software module name 131
Column holds a list of names of each software module included in the software module database 103. The column of the attribute value name 141 holds a list of attribute value names that define the function details of each software module corresponding to each software module. A component corresponds to a component of software, and an attribute value corresponding to a software module is also a component. In addition, a function may be a component without a combination of software modules.

FIG. 4 shows an example of the software configuration information 102. In the figure, the software component list file 101
Holds a list of software module names that are software components shown in FIG. 6. The column of attribute values 161 lists attribute names corresponding to each software module and a list of values of software modules selected as software components. Hold and
The column of presence / absence 171 holds whether each software module is selected as a component (o) or not (x).

FIG. 5 shows an example of the test program correspondence table 106. In the figure, the column of the software module name 181 holds the name of each software module included in the software module database 103, and the column of the test program name 191 contains, for each software module, the number required for the function test of each software module. Holds the names of one or more test programs.

Next, the operation will be described. FIG. 6 is a flowchart showing a flow of user operation. FIG. 7 is a diagram showing a display example on the user interface 1 of this embodiment. FIG. 8 is a diagram showing a display example on the user interface 1 of this embodiment. FIG. 9 is a diagram showing a display example on the user interface 1 of this embodiment.
First, a flow of user operation on the user interface 1 will be described with reference to FIG. It is assumed that the display example shown in FIG. 7 is displayed on the screen. In S1, for example, by selecting 801 in FIG. 7, a configuration setting request of software (S / W) to be tested is input. S
2, a plurality of software module names 811, 81
A list of software components including 2,821,819 and the attribute value names 821,822,823 corresponding to the software modules is displayed on the user interface 1. In S3, as a software configuration,
The names of a plurality of software modules selected from the displayed software component list and the names and values of attribute values corresponding to the software modules are input to define components. As the input operation at this time, for example, a check box corresponding to the name of the software module as indicated by 810 in FIG. 7 is checked. Also, attribute values are input as shown at 831 to 833. In S4, the user selects 802 and inputs a software generation request. In S5, the end of software generation is displayed as shown in FIG. In S6,
7 is selected, and a software test execution request is input. In S7, a software test result is displayed as shown in FIG.

Next, the internal operation of the mechanism corresponding to the flow of the user's operation shown in FIG. 6 will be described. First,
FIG. 10 shows the internal operation of the software configuration setting process.
This will be described with reference to FIG. In S101, a software configuration setting request is input on the user interface 1.
In S102, the software configuration setting means 2 which is a program is activated from the user interface 1. S10
In step 3, the software configuration setting means 2 retrieves the software component information from the software component list file 101 storing the software component information 130 including the names of a plurality of software modules and the names of attribute values corresponding to the software modules. Display on interface 1.
In S104, a plurality of software module names and the names of attribute values corresponding to the software modules and their values are input on the user interface 1 from the software component information displayed on the user interface 1. In S105, the software configuration setting means 2
In step (1), software configuration information 102 is created from a plurality of software module names input from the user interface 1, names of attribute values corresponding to the software modules, and a software configuration including the values. S
In 106, the software configuration setting means 2 as a program ends the processing.

Next, the internal operation of the software generation processing will be described with reference to FIG. In S201,
A software generation request is input on the user interface 1. In S202, the software generation means 3 which is a program is activated from the user interface 1.
In S203, the software generation unit 3 converts a plurality of software modules shown in the software configuration information 102 created by the software configuration setting unit 2 from the software module database 103 storing all the software modules shown in the software component list file 101. Get a software module. In S204, the software generation unit 3 reflects the attribute value indicated in the software configuration information 102 on the corresponding software module acquired in S203. In S205, the software generation unit 3
In step S204, a plurality of software modules reflecting the attribute values are combined into one to generate software 104. In S206, the software generation unit 3 notifies the user interface 1 of the end of software generation.
Display to In S207, the software generation means 3 of the program ends the processing.

Next, the operation of the test execution processing of this embodiment will be described with reference to FIG. In S301, a test execution request is input on the user interface.
In S302, the program of the test execution means 4 is started from the user interface. In S303, the test execution means 4 selects a test program corresponding to the software module indicated in the software configuration information 102 from the test program database 105. S30
In 4, the test execution means 4 combines the test programs selected in S304 into one to generate the test suit 107. In S305, the test execution means 4 executes the software 104. In S306, the test execution means 4 activates the test suit 107 by passing the attribute value indicated in the software configuration information 102. S3
In the test suit 107, the software 1
The function test of step 04 is performed. In S308, the result of the test executed in the test suit 107 is stored in the test result information 10
Create as 8. In S309, the test suit ends the program processing. In S310, the test execution means 4 stores the test result information 108 in the user interface 1
(Test result display column 862 in FIG. 9). S311
Then, the test execution means 4 ends the program processing.

As described above, in this embodiment, the software component list in which the software component information including the software module name list as the component of the software and the attribute value name list corresponding to the software module is stored From the file, the software component information is displayed on the user interface, and a plurality of software module names which are components of software specified on the user interface, and attribute value names corresponding to the software modules and software configuration information including the values are displayed. Created and obtained according to the software configuration information from the software module database that stores the software modules indicated in the software component list file From the test program database in which the software is generated from the software module and a test program for realizing the functional test of each software module shown in the software component list file is stored, the software module and each software module shown in the software component list file are stored. Based on a test program correspondence table indicating correspondence with a test program for realizing the functional test, one or more programs for realizing a functional test corresponding to the software module indicated in the software configuration information are acquired, and A software that combines a test program to generate a test suit, executes a functional test of the software using the test suit, and outputs test result information created by the test to a user interface. It was described hardware generated test cooperation mechanism.

The software generation test cooperation mechanism of this embodiment has the following components. A user interface that displays information for supporting software generation and test operations and receives requests from users. The software component information is displayed on the user interface from the software component list file storing the software component information including the software module name list which is a component of the software and the attribute value name list corresponding to the software module. Software configuration setting means for creating software configuration information including a plurality of software module names specified by the above, the names of attribute values corresponding to the software modules, and the values. Obtain a plurality of software modules indicated by software configuration information created by software configuration setting means from a software module database storing software modules which are components of software indicated in the software component list file, and Software generation means for reflecting the definition of the attribute value of the module in the software module and combining the software modules to generate software. A test program database in which a test program for realizing the function test of each software module shown in the software component list file is stored, and a test program for realizing the function test of each software module and each software module shown in the software component list file. It has a test program correspondence table indicating the correspondence with the test program, and based on the test program correspondence table, a plurality of programs for implementing the functional test corresponding to the software module indicated by the software configuration information created by the software configuration setting means. To obtain from the test program database, generate a test suit by combining the test program, execute the software test generated by the software generating means using the test suit, Test execution means for outputting the test result information generated to the user interface by test run.

As described above, according to the software generation test cooperation mechanism of this embodiment, a test suit according to the configuration can be automatically generated for a plurality of software, and the test suit generation work can be performed. Efficiency can be improved. In a unified user operation environment,
A plurality of software is automatically generated according to the configuration, and a test suit corresponding to the software is automatically generated according to the configuration of the software, and a test is executed. Can be automated, and the work efficiency can be improved by reducing the work load and the number of erroneous operations.

In the above example, a test suit 107 is generated by combining test programs selected from the test program database 105 based on the test program correspondence table 106 in accordance with the software configuration information 102, and the test is performed. However, a test suite generated by combining all the programs that implement the tests corresponding to the software modules shown in the software component list file 101 is held in advance, and the test suite is displayed in the software configuration information 102 when the test is executed. Even if only a test corresponding to the software module is performed, the same effect as described above can be obtained.

Embodiment 2 In the first embodiment,
Based on the software component information 130 stored in the software component list file 101, the software configuration information 102 is created from the software configuration specified on the user interface. Next, an embodiment will be described in which the created software configuration information is stored in the software configuration information database, and the software configuration is set based on the specified software configuration information in the software configuration information database.

FIG. 13 is a configuration diagram of the second embodiment.
In the figure, a user interface 1, software generation means 3, software component list file 1
01, software configuration information 102, software module database 103, software 104, test program database 105, test program correspondence table 106, test suit 107, and test result information 108 are the same as those in FIG. The software configuration setting unit 122 stores the created software configuration information 102 in response to a request from the user interface 1 in a software configuration information database 109 that stores the software configuration information 102 in addition to the functions of the first embodiment. This is a means for displaying the contents of the specified software configuration information in the configuration information database 109 on the user interface 1 and enabling the software configuration to be set on the user interface based on the software configuration information.

Next, the operation of this embodiment will be described. The flow of user operation, software generation processing, and software test execution processing according to the present embodiment are described in Embodiment 1.
Therefore, the description is omitted. The operation of the software configuration setting process according to the present embodiment will be described with reference to FIG. Steps S101, S102, and S103 are the same as those in the first embodiment. In S120, it is specified whether to set the software configuration based on the existing software configuration information stored in the software configuration information database 109 on the user interface 1. S120
When it is specified not to use the existing software configuration information (NO) in S104, as in the first embodiment,
The process of S105 is performed. If it is specified in S120 that the existing software configuration information is to be used (YES), the processes in S121, S122, and S123 are performed, and then the processes in S104 and S105 are performed. S12
In 1, the software configuration setting unit 122 displays a list of software configuration information names stored in the software configuration information database 109 on the user interface 1. In S122, from the list of software configuration information names displayed on the user interface 1,
The software configuration information name is specified. In S123,
The software configuration setting unit 122 displays the contents of the software configuration information specified by the software configuration information name on the user interface 1. After that, the software configuration information 102 is created in S104 and S105 as in the first embodiment.

In this case, in S104, the user may set the same content as the software configuration information stored in the software configuration information database on the user interface, or may set the partially changed content. You may. It is assumed that the user can edit the software configuration information with desired contents. In S105, the software configuration information 102 is newly created, and the software configuration information in the software configuration information database 109 on which the software configuration information is based is not changed. When the new software configuration information 102 is created based on the stored software configuration information, in S124, it is designated whether to save the newly created software configuration information 102 on the user interface 1. If it is determined in S124 that the software configuration information 102 is not to be saved, the result is NO, and the process proceeds to S124 as in the first embodiment.
In 106, the software configuration setting means ends the processing of the program. If it is determined in S124 that the software configuration information 102 is to be stored, the result is YES, and in S125, the software configuration setting unit 122 stores the software configuration information 102 in the software configuration information database 109 under the name specified on the user interface 1. I do. Next, in S106, the software configuration setting unit 122 ends the processing of the program.

As described above, in this embodiment, in the software configuration setting means of the above-described embodiment,
Providing a software configuration information database for storing one or more software configuration information, in response to a user request from a user interface, storing the created software configuration information in the software configuration information database,
A software generation test cooperation mechanism characterized in that software configuration information specified on a user interface is selected from the software configuration information database and the software configuration can be reset based on the software configuration information .

As described above, in this embodiment, the efficiency of the user's software configuration setting work can be improved by storing and reusing the software configuration information once set by the user. it can.

Embodiment 3 In Embodiment 2 described above,
The software configuration information created by the software configuration setting means is stored in a software configuration information database so that it can be reused. Next, software configuration information including software modules of software components specified on a user interface is stored. An embodiment will be described in which the software is extracted from a software configuration information database and automatically generates and tests software corresponding to the software configuration information in a lump.

The configuration of the present embodiment is the same as that of the second embodiment, and the description is omitted.

Next, the operation of this embodiment will be described. The software configuration setting process, the software generation process, and the software test execution process of the present embodiment are the same as those of the first embodiment, and a description thereof will be omitted. The batch automatic generation test processing of software including the designated component will be described with reference to FIG. In step S141, a batch automatic generation test request for the designated component use software is input on the user interface 1. In S142, based on the batch automatic generation test request in S141, the software configuration setting unit 122
Start the program. In S143, the user specifies the software module name of the software component on the user interface 1. S14
In step 4, the software configuration setting unit 122 checks the contents of the software configuration information stored in the software configuration information database 109 and extracts all software configuration information including the specified software module name. In S 145, the software configuration information selected by the software configuration setting unit 122 from the one or more pieces of software configuration information extracted in S 144 in order from the software configuration information 10 of the same content.
Create 2. In S146, the software generation unit 3
(Program of) is started, and the software 104 corresponding to the extracted software configuration information is generated by performing the processing of S201 to S207 of the first embodiment. S1
In step 47, the test execution means 4 is started, and the S
A test of software corresponding to the software configuration information extracted by performing the processing from S301 to S311 is executed. In S148, it is determined whether all the software corresponding to the software configuration information extracted in S144 has been generated and tested. If there is unprocessed software configuration information in S148, the process proceeds to S145, one piece of unprocessed software configuration information is selected, and the process proceeds to S145.
145, S146, and S147 are repeated to generate and test software. When there is no unprocessed software configuration information in S148, the software configuration setting means of the program ends the process in S149.

As described above, in this embodiment, in the software configuration setting means of the above-described embodiment,
Searches software configuration information including software components specified on a user interface from a software configuration information database in which software configuration information is stored, and automatically generates and tests software corresponding to the software configuration information collectively The software generation test cooperation mechanism characterized in that it is performed has been described.

As described above, in this embodiment, software configuration information including software components (here, software modules) specified on the user interface is extracted from the software configuration information database, and By automatically executing the generation and testing of the corresponding software in a batch, it is possible to generate and test software that focuses on components, and to improve the efficiency of software generation and test work when replacing software components. Can be improved.

Embodiment 4 In the first embodiment, the software configuration setting unit immediately generates software configuration information in response to an input from the user interface, and can generate and test software.
Next, the software configuration setting means holds the software configuration rules, checks whether the software configuration input from the user interface is inconsistent with the software configuration rules, and if so, outputs the software configuration information. An embodiment in which creation of functionally incomplete software is prevented in advance by not creating the software will be described.

FIG. 16 shows a configuration diagram of the present embodiment. In the figure, the configuration other than the software configuration setting unit 32 and the software configuration rule 110 is the same as that of the first embodiment, and thus the description is omitted. Software configuration setting means 32
Is a software configuration rule 110 storing rules of a software configuration method in addition to the functions of the first embodiment.
Is a means for checking whether or not the software configuration input from the user interface 1 does not violate the software configuration rule 110, and creating the software configuration information 102 only when the configuration does not violate the software configuration rule 110.

Next, FIG. 17 shows an example of the software configuration rule 110. Column 21 of software module name
1 is a software component list file 101
Holds the software module name shown in. As rules of the software configuration method, each software module has a column 221 for software modules that must be combined, a column 231 for software modules that cannot be combined, and a column 241 for attribute value rules. The list of software modules required for combination 221 holds a list of software module names that must be used together as components. The list of software modules that cannot be combined holds a list of software modules that cannot be used together. The attribute value rule column 241 holds the name of the attribute value and the range of the value that can be set as the attribute value.

Next, the operation of this embodiment will be described. The flow of user operation, software generation processing, and software test execution processing according to the present embodiment are described in Embodiment 1.
Therefore, the description is omitted. Based on FIG.
The software configuration setting process will be described. S10
Steps 1 to S104 are the same as those in the first embodiment, and a description thereof will be omitted. In S150, the software configuration setting unit 3
2, referring to the software configuration rule 110,
It is checked whether the input software configuration does not violate the software configuration rules 110. S151
Then, the result of the inspection in S150 is determined. If it is determined in S151 that the software configuration is correct (Y
ES), the processes in S105 and S106 are performed as in the first embodiment. If it is determined in S151 that the software configuration is invalid (NO), it is shown in S152 that the configuration of the software input to the user interface 1 is invalid, and the process returns to S104 to return the software from the user. Wait for the configuration to be re-entered.

As described above, in this embodiment, in the software configuration setting means of the above-described embodiment,
Holds software configuration rules including the rules for setting combinations of software modules and attribute values corresponding to the software modules indicated in the software component list file, and the configuration of software input from the user interface is contrary to the software configuration rules. A description has been given of the software generation test coordination mechanism, which checks whether or not there is an invalid configuration and prevents setting of an invalid configuration.

As described above, in the present embodiment, the software configuration setting means holds the software configuration rule, checks whether the configuration of the software input from the user interface is inconsistent with the software configuration rule, and checks the software configuration rule. In such a case, the software configuration information is not created, so that the generation of functionally incomplete software is prevented in advance, and the efficiency of software generation and test work can be improved.

Embodiment 5 FIG. In the first embodiment, software is configured using software modules registered in the software component list file in advance, and generation and test are performed. In the present embodiment, the software is generated by this mechanism and the test is performed. A case will be described in which large-scale software generation and test operations are performed stepwise by enabling registered software to be registered as a software module that is a component of new software.

The configuration of the present embodiment will be described with reference to FIG. In the figure, the components other than the component management means 5 are the same as those of the first embodiment, so that the description will be omitted. The component management means 5 is a means for adding the generated software 104 to the software component list file 101 as a software module of a new software component in accordance with a request from the user, and storing the software module 104 in the software module database 103. A test program corresponding to each software module included in the software module database is registered in the test program correspondence table 106 in advance. Test program information corresponding to the software module of the component of the software 104 is obtained from the test program correspondence table 106.

Next, the operation of this embodiment will be described. User operation flow, software configuration setting process,
Since the software generation processing and the test execution processing are the same as those in the first embodiment, the description is omitted. A process of registering the software 104 as a new component after the generation and the test of the software 104 are completed will be described with reference to FIG. In step S401, a request for registering software components is input on the user interface 1. S
At 402, the program of the component management means 5 is started from the user interface 1. In S403,
In the component management means, the software module name of the software 104 and the software configuration information 102 are stored in the software component list file 101.
The attribute value name list corresponding to the software module acquired from the above is additionally recorded. In S404, the component management unit 5 stores the software module 104 in the software module database 103. In S405, in the component management means,
A test program list corresponding to the software module of the component of the software 104 acquired from the test program correspondence table 106 based on the software module name of the software 104 and the software configuration information 102 is additionally recorded in the test program correspondence table 106. In S406, the component management means 6 ends the program processing.

As described above, in this embodiment, in the software generation test cooperation mechanism of the above-described embodiment, the component management means is provided, and in response to a user request from the user interface, the component management means is used. In order to register the software generated by the mechanism as a new software component, a software component list file records a software module name of the software and a corresponding attribute value name list, stores the software module in a software module database, The software generation test cooperation mechanism characterized in that the correspondence between the software and one or a plurality of test programs corresponding to the software is recorded in a test program correspondence table.

As described above, in the present embodiment, the software generated by the present mechanism and subjected to the test can be registered as a new software component, and the large-scale software generation and test operations are performed step by step. In this case, the efficiency of software generation and test work can be improved.

Embodiment 6 FIG. In the second embodiment, the software configuration information is stored and can be reused.
In the present embodiment, the software generated by this mechanism is stored and managed, and the software specified on the user interface can be obtained on the user interface. Without the need to get it easily.

A configuration diagram of the present embodiment will be described with reference to FIG. In the figure, software generation means 123,
Software management means 6, software database 1
Components other than the software configuration information correspondence table 112 are the same as those in the second embodiment, and thus description thereof is omitted.
The software generating means 123 is a means for storing the generated software 104 in response to a request from the user interface 1 in the software database 111 for storing and managing the software generated by the present mechanism, in addition to the function of the second embodiment. . Software management means 6
Holds the correspondence between the software configuration information stored in the software configuration information database 109 and the software stored in the software database 111 in a software configuration information correspondence table 112, and stores the software specified on the user interface 1 in the software database 111 From the user interface 1 so that a file can be obtained on the user interface 1.

Next, FIG. 22 shows an example of the software configuration information correspondence table 112. Column 251 of software configuration information name
Holds a software configuration information name list that is the name of software configuration information stored in the software configuration information database 109. The software name column 261 holds software names in the software database corresponding to each software configuration information name.

Next, the operation will be described. The flow of the user's operation, the software configuration setting process, and the test execution process are the same as those in the second embodiment, and thus description thereof is omitted. The software generation processing will be described with reference to FIG. Steps S201 to S206 are the same as those in the first embodiment, and a description thereof will not be repeated. In S220, it is specified on the user interface 1 whether to save the software. If it is not specified in S220 that the software is to be stored (NO), the program processing of the software generating means 123 is terminated in S207. If it is specified in S220 that the software is to be stored (YES), the software generation unit 123 stores the generated software 1 in the software database 111 that stores and manages the software in S221.
04, and the program processing ends in S207.

Next, a process for acquiring software stored and managed in the present mechanism will be described with reference to FIG. In step S501, a software acquisition request is input on the user interface 1. In S502, the program of the software management means 6 is started from the user interface 1. In S503, the software management unit 6 displays a list of software names stored in the software database 111. In S504, a software name is specified on the user interface. In step S505, the software management unit 6 acquires a software file having the designated software name from the software database 111 and causes the software file to be acquired on the user interface. In S506, the software management means ends the program.

As described above, in this embodiment, in the software generation test cooperation mechanism of the above-described embodiment, a software database for storing software generated by software generation means is provided, and in response to a request from a user interface. Storing the software generated by the software generation means in a software database, further providing software management means, and acquiring the software specified on the user interface from the software database by the software management means, and obtaining the software on the user interface. The software generation test cooperation mechanism characterized by the following has been described.

As described above, in the present embodiment, the software generated by the present mechanism is stored and managed, and the software specified on the user interface can be obtained on the user interface. Make it easier to get the software when needed without having to regenerate it. As a result, software corresponding to a plurality of pieces of software configuration information can be stored, and acquisition of software designated by the user and display and acquisition of software including software modules designated by the user can be performed. Therefore, the operation of regenerating software is reduced, and the efficiency of software generation operation can be improved.

Embodiment 7 FIG. In the sixth embodiment, the software generated by the present mechanism is stored and managed, and the software specified on the user interface can be obtained on the user interface. Of these, software including components specified on the user interface is extracted, and the tests of the software are collectively performed, so that the retest can be easily performed collectively without regenerating the software. .

A configuration diagram of the present embodiment will be described with reference to FIG. In the figure, the components other than the software management means 26 are the same as those in the sixth embodiment, and the description is omitted. The software management unit 26 includes a software configuration information database 109 in addition to the functions of the sixth embodiment.
The correspondence between the software configuration information stored in the software configuration information and the software stored in the software database is stored in the software configuration information correspondence table 112, and the software configuration information stored in the software configuration information database 109 is specified on the user interface 1. This is a means for extracting software configuration information including the software module obtained and automatically executing a test of the software collectively. The software configuration information correspondence table 112 is the same as that in FIG. 21 of the sixth embodiment.

Next, the operation will be described. User operation flow, software configuration setting processing,
Since the software generation processing and the test execution processing are the same as those in the second embodiment, the description will be omitted. FIG. 26 shows batch test processing of software including a specified component.
It will be described based on.

At S521, a batch test request for software using the designated component is input on the user interface 1. In S522, the program of the software management means 6 is started from the user interface 1. In S523, the software configuration information in the software configuration information database 109 is displayed on the user interface 1, and the name of the software module which is a component of the software is designated. S52
In step 4, the software management unit 26 extracts software configuration information including the specified software module from the software configuration information in the software configuration information database 109. In S525, the software management unit 26 sequentially sets the extracted software configuration information as the software configuration information 102 to be tested. In S526, the software management unit 2
In 6, the software name corresponding to the set software configuration information 102 is acquired based on the software configuration information correspondence table 112, and the software in the software database is identified by the software name in S50 of FIG.
5 is acquired in the same manner as in the processing of step 5
Set as 4. In S527, the test execution means is started. In step S528, the test execution unit performs a software test by the processes in steps S301 to S311 described in the first embodiment. In S529, it is determined whether all the software tests corresponding to the extracted software configuration information have been performed. If it is confirmed in S529 that there is an unprocessed test, the result is NO, and S5
25, select the unprocessed software configuration information,
The processing from S525 to S529 is repeated. If it is confirmed in S529 that there is no unprocessed test, YES
Then, in S530, the software management unit 26 ends the program processing.

As described above, in this embodiment, the software management means of the above-described embodiment has a software configuration information correspondence table for associating software configuration information in the software configuration information database with software in the software database. Searching for software configuration information corresponding to software in the software database including the software component specified on the user interface from the software configuration information database, and automatically executing the tests of the software in the software database collectively. The feature of the software generation test cooperation mechanism, which is a feature, has been described.

As described above, in the present embodiment, software including components specified on the user interface is extracted from the software stored in the mechanism, and the tests of the software are collectively performed. By doing so, software testing focused on components,
The software can be easily and collectively performed without regenerating the software, and the efficiency of the software generation test operation can be improved.

Embodiment 8 FIG. In the first embodiment, the software configuration setting unit, the software generation unit, and the test execution unit are started from the user interface, and the user interface can be interacted with the user by directly cooperating with the user interface. In the embodiment, a communication unit and a communication server are provided between a user interface and each of the units, the communication unit and the communication server perform communication via a network, and the user interface includes a communication unit.
By cooperating with the above-described units via a network and a communication server, only the user interface can be mounted on a computer different from the computer that generates and tests the software, and the software generation test work can be remotely performed from the computer. The operation of can be performed.

FIG. 27 shows a configuration diagram of the present embodiment. In the figure, software component list file 1
01, the software configuration information 102, the software module database 103, the software 104, the test program database 105, the test program correspondence table 106, the test suit 107, and the test result information 108 are the same as those in the first embodiment, and thus the description is omitted. The user interface-equipped computer 20 includes the user interface 1 and the communication unit 7, is connected to the software generation test computer 21 via the network 22, communicates with the software generation test computer 21 via the network 22, and interacts with the user. Is a computer that enables a software generation test operation via the network 22 according to the present invention.
The software generation test computer 21 includes a software configuration setting unit 2, a software generation unit 3, a test execution unit 4, a software component list file 101,
Software module database 103, test program database 105, test program correspondence table 10
6. Equipped with a communication server 8, performs a cooperative operation with the user interface-equipped computer 20 via communication via the network 22, and causes the user interface 1 on the user interface-equipped computer 20 to display information necessary for supporting the software generation test work. , Software configuration information 10
2. Generate software 104, test suit 107,
This is a computer that performs a test of the software 104 using the test suit 107, creates test result information 108, and displays it on the user interface 1.

The network 22 is, for example, a LAN (Local Area N) connecting the computer 20 with a user interface and the computer 21 for software generation test.
communication means 7 and the communication server 8 are T
CP / IP (Transmission Control)
l Protocol / Internet Proto
col) protocol to transmit and receive data via the LAN. The user interface 1 is a means for receiving an instruction from a user, notifying each processing request to the communication means 7, and displaying a processing result returned from the communication means 7. The communication unit 7 is a unit that receives a request from the user interface 1 and transmits the request to the communication server 8 on the software generation test computer 21 via the network 22. The communication server 8 receives each request from the communication unit 7 on the user interface-equipped computer 20 and activates any one of the software configuration setting unit 2, the software generation unit 3, and the test execution unit 4 that performs a corresponding process. This is a means for receiving a processing result from each means and transmitting the processing result to the communication means 7. Each unit of the software configuration setting unit 2, the software generation unit 3, and the test execution unit 4 is started by the communication server 8, and operates in cooperation with the user interface 1 via the communication unit 7, the network 22, and the communication server 8, and The same processing as in the first embodiment is performed. In this embodiment, since the point is to enable remote operation, it is assumed that the communication portion via the network takes any configuration using existing technology. It does not limit the method of realizing the part.

Next, the operation of this embodiment will be described. The flow of the user's operation is the same as that of the first embodiment, and the description is omitted. The software configuration setting process will be described with reference to FIG. In S101, a request for software configuration setting is input on the user interface 1 on the user interface-equipped computer 20.
In S160, the communication means 7
Sends a software configuration setting request to In S161, the communication unit 7 receives the request from the user interface 1 and sends the request to the communication server 8 on the software generation test computer 21 via the network 22. In S162, the communication server 8 receives the request from the communication unit 7, and starts the program of the software configuration setting unit 2. In step S163, the software configuration setting unit 2 transmits the software component information from the software component list file 101 storing the software component information including the names of the plurality of software modules and the names of the attribute values corresponding to the software modules. Send to 8. In S164, the communication server 8 sends the software component information to the communication unit 7.
In S165, the communication means 7 displays the software component information received from the communication server 8 on the user interface 1 via the network 22. S1
In 04, the names of a plurality of software modules which are components of the software, the names of attribute values corresponding to the software modules, and the configuration of the software including the values are input on the user interface 1. S16
At 6, the software configuration is sent from the user interface 1 to the communication means 7. In S167, the communication unit 7
Sends the software configuration to the communication server 8 via the network 22. In S168, the communication server 8
, The configuration of the software received from the communication unit 7 is sent to the software configuration setting unit 2. In S105, the software configuration setting unit 2 creates software configuration information from the configuration of the software input to the user interface 1. In S106, the software configuration setting means 2 ends the program processing.

Next, regarding the software generation processing,
This will be described with reference to FIG. In the figure, in S201, a software generation request is input on the user interface 1 on the user interface-equipped computer 20. In S230, a software generation request is sent from the user interface 1 to the communication unit 7. In S231, the communication unit 7 receives the request from the user interface 1 and sends the request to the software generation test computer 21.
The request is sent to the communication server 8 via the network 22. In S232, the communication server 8 receives the request from the communication means 7 and starts the software generation means 3 program. In S203, the software generation unit 3 acquires the software module indicated in the software configuration information 102 from the software module database 103. In S204, the software generating means 3 causes the software configuration information 1
The attribute value of the software module indicated by 02 is reflected on the software module. In S205, the software generating unit 3 combines the software modules to generate software 104. S233
Then, the software generation means 3 notifies the communication server 8 to display the end of software generation on the user interface 1. In S207, the software generation means 3 ends the program processing. In S234, the communication server 8 transmits the received request to the network 22.
Via the communication means 7 In S235, the communication means 7 displays the end of software generation on the user interface 1.

Next, the software test execution processing will be described with reference to FIG. In S301, a software test execution request is input on the user interface 1 on the user interface-equipped computer 20. S
At 320, a test execution request is sent from the user interface 1 to the communication means 7. In S321, the communication unit 7 receives the test execution request and sends the request via the network 22 to the communication server 8 on the software generation test computer 21. In S322, the communication server 8 receives the request from the communication means 7 and activates the test execution means 4. Steps S303 to S309 are the same as in the first embodiment, and a description thereof will not be repeated. In S323, the test execution means 4 notifies the communication server 8 to display the test result information 108 on the user interface 1. In S311, the test execution means 4 ends the program processing. In S324, the communication server 8 sends the test result information 108 to the communication means 7 via the network 22. In S325, the communication means 7 displays the test result information 108 received from the communication server 8 on the user interface 1.

As described above, in this embodiment, in the software generation test cooperation mechanism of the above-described embodiment, communication is performed between the user interface and each of the software configuration setting means, software generation means, and test execution means. Means and a communication server, the communication means and the communication server are connected via a network, the communication means and the communication server communicate via the network, and the user interface is a software configuration setting means via the communication means, the network and the communication server By cooperating with the software generation means and the test execution means, the user interface can be implemented on a remote computer different from the computer that generates and tests the software, and the software generation and test operation can be performed remotely. Software generation test characterized by: It was described cellular mechanism.

As described above, in the present embodiment, the communication means and the communication server are provided between the user interface and each of the software configuration setting means, software generation means, and test execution means. Since the communication is performed via the network, the user interface cooperates with the above-described units via the communication unit, the network, and the communication server, so that only the user interface is on a computer different from the computer that generates and tests the software. Be able to mount. Therefore, the user can remotely perform the operation of the software generation test operation, so that the convenience of the user can be improved.

In the above example, the network 22 is a LAN, and the communication means 7 and the communication server 8 communicate with each other using the TCP / IP protocol. Server 8 is T
The above effect can be obtained even if communication is performed using a protocol other than the CP / IP protocol.

In the above-described example, the computer 20 is equipped with the user interface-equipped computer 20 and the software generation test computer 21. However, among the software generation test computers, the test execution means is further shifted to another computer. The above-mentioned effect can be obtained even if the computer is installed and the computer and the software generation test computer are further connected via a network such as a LAN.

In the above example, the test result information 108 is displayed on the user interface 1. However, the test result information 108 is displayed on the software generation test computer 21.
By storing the test result information 108 in a file and transferring the file to the user interface-equipped computer 20, the above effect can be obtained even if the test result information 108 can be obtained as a file on the user interface 1.

Embodiment 9 In the eighth embodiment, a communication unit and a communication server are provided between the software configuration setting unit, the software generation unit, and the test execution unit and the user interface, and the communication unit and the communication server perform communication via a network. By linking the user interface with each of the above means via a communication means, a network, and a communication server, only the user interface can be mounted on a computer different from the computer that generates and tests the software. In the embodiment, a user interface is provided on a plurality of computers at the same time, user account information indicating a list of available users is held in the communication server, and the user account information is stored in the communication server in response to a use request from the user interface. Confirm the user based on the As the number of users can not be operated, a plurality of computing machine to perform operations of generating test work software remotely.

This is because, when a plurality of users try to perform a software generation test with the same configuration at the same time, inconsistency occurs in data and processing handled internally. In order to prevent inconsistency. In the case where the parallel operation is partially enabled in the mechanism according to the processing content, a plurality of users may be allowed to use the function at the same time.

The configuration of the present embodiment will be described with reference to FIG. Computers 20a, 20 with user interface
, 20n and the user interface 1a, 1
, 1n and communication means 7a, 7b, ..., 7n
Is provided with a plurality of user interface-equipped computers 20, user interfaces 1, and communication means 7 in the eighth embodiment. The communication server 8 includes computers 20a, 20b,.
, 1n from each of the communication means 1a, 1b,..., 1n, and receives user account information 113 holding an account list of users who are permitted to use the mechanism. It is determined whether or not the user is available based on the user. If the user is available, it is further determined based on the user information 114 currently in use whether or not another user is in use. When there is no user in the system, use is permitted, and the name of the use start user is registered in the user information 114.
And the communication means 7a, 7b,.
n, the user name being used is deleted from the user information 114, and the next communication means 7a, 7
b,..., 7n.
Although illustration is omitted in the user account information 113,
Maintains a list of user account information consisting of pairs of names and passwords of users who are permitted to use this mechanism. The user information 114 indicates the name of the user currently using the mechanism, and the communication server 8 registers and deletes the user name. The other components are the same as those in the first embodiment, and a description thereof will not be repeated.

Next, the operation of this embodiment will be described. Software configuration setting processing, software generation processing,
The software test execution processing is the same as in the eighth embodiment, and a description thereof will not be repeated. User interface 1a,
The operation flow of the user on 1b,..., 1n is common, and the flow will be described with reference to FIG. In S20, a use request of the software generation test mechanism is input together with user information (user name and password). S21
Then, a use request including the user information sent from the user interface is sent from the communication means 7 to the communication server 8 via the network 22, and the communication server uses the set of the name and password of the user who can use the software generation test mechanism. Based on the user account information 113 that holds a list of user account information, the name of the user who made the use request is included in the user account information 113, and the password of the user is included in the user account information 113 in the password of the user. Is checked to see if they match, and if both conditions are satisfied, the determination is YES and the process proceeds to S22. If it is determined in S21 that the user cannot use the service, the result is NO, and the user operation is terminated. In S22, the communication server 8 further checks whether the user name in use is registered in the user information 114. If the user name is not registered, the user name is registered in the user information 114, The same processing as in the eighth embodiment can be performed. If the user in use has already been registered in S22, the result is NO, and the user's operation is terminated. If the user does not exist in S22 and the use of this mechanism is permitted (YES),
The operations from S1 to S7 are performed in the same manner as in the first embodiment. In S23, a request to end use of this mechanism is input, and the request sent from the user interface to the communication means 7 is sent to the communication server 8 via the network 22, and the communication server 8 outputs the user information in use. Deletes the user's registration from and prepares for the next use request.

As described above, in this embodiment, the user interface is mounted on a plurality of computers different from the computer that generates and tests the software in the software generation test cooperation mechanism of the above-described embodiment. The communication server holds user account information for identifying and managing users who are permitted to operate by this mechanism, and based on a user-specified use request issued at the start of operation by this mechanism from the user interface,
Operation to perform software generation test work in the communication server, which is a user registered in the user account information and permits use when there is no other user, and does not allow multiple users to use it at the same time A software generation test cooperation mechanism characterized in that the software generation test can be performed remotely from a plurality of computers has been described.

As described above, in this embodiment, a plurality of computers equipped with a user interface are provided at the same time, the user is confirmed in the communication server in response to a use request from the plurality of user interfaces, and a plurality of computers are simultaneously provided. A user is prevented from operating, and remote operation of software generation test work can be performed from a plurality of computers. As a result, users of the present mechanism can be limited, and by limiting users of the present mechanism to only registrants, users who perform unauthorized operations on the present mechanism can be eliminated, and occurrence of operation failures of the present mechanism can be suppressed. Can be supported so that the user can operate smoothly. Further, for example, since the present mechanism can be shared by a plurality of users on computers at different remote locations, joint development of software by a plurality of persons is enabled, and user convenience can be improved.

Embodiment 10 FIG. In the first embodiment, the software generation, the test suit generation, and the software test execution are performed on the same computer. However, in the present embodiment, the computer and the software that generate the software and the test suit are generated. A computer for performing the test is provided separately, the two computers are connected via a network, and the two computers cooperate with each other via the network so that the software test can be remotely executed. For example, it is assumed that the computer targeted for the test does not have a disk or memory of a capacity necessary to generate software and a test suite in this mechanism, and the computer targeted for the test is a test target. It can be implemented as long as it has only the necessary hardware specifications.

FIG. 33 shows the structure of this embodiment. In the figure, test execution means 4, software 104a, 10
4b, test suit 107a, 107b, test result information 1
08a, 108b, remote execution request means 9, file transfer means 10a, 10b, remote execution execution means 11, software generation computer 23, software test computer 2
Since the fourth embodiment is the same as the first embodiment except for the network 22, the description is omitted. The software 104a is software generated by the software generating means 3 as in the first embodiment, and is
Transferred to The software 104b is obtained by transferring the software 104a to the software test computer 24. The test suit 107a is the software 1 generated by the test execution means 4 as in the first embodiment.
This is a test suit for performing a functional test 04a, and is transferred to the software test computer 24. Test suit 1
Reference numeral 07b denotes the test suit 107a transferred to the software test computer 24. Test result information 10
8a is a file in which the file of the test result information 108b created on the software test computer 24 is transferred. The test result information 108b is transmitted to the software 10 by the test suit 107b on the software test computer 24.
4b is a file of test result information created as a result of the test of FIG. 4b. The remote execution request unit 9 is started after the test suit is generated by the test execution unit 4, and the software 104a and the test suit 10 are used by the file transfer unit 10a.
7a is sent to the software test computer 24, the attribute value indicated in the software configuration information 102 is acquired, and the software test request is sent to the network 2 together with the attribute value.
This is a means for sending to the remote execution means 11 via 2 and receiving a test end notification from the remote execution means to end the program processing. The file transfer unit 10a is a unit that transmits and receives a file to and from the file transfer unit 10b on the software test computer 24 via the network 22.

The file transfer means 10b is a means for transmitting and receiving files via the network 22 to and from the file transfer means 10a on the software generating computer 23. Upon receiving the software test request from the remote execution requesting means 9, the remote execution execution means 11 uses the test suite 107 b on the software test computer 24 to execute the software 10.
4b is a means for executing the test of 4b. The software generation computer 23 is connected to the software test computer 24 via the network 22, and performs a software configuration setting, software generation, generation of a test suit for realizing a software functional test, and software test through interaction with a user. This is a computer to be executed on the software test computer 24. The software test computer 24 is a computer that is connected to the software generation computer 23 via the network 22, receives a request from the software generation computer 23, and executes a software test. The network 22 is a LAN that connects the software generation computer 23 and the software test computer 24. The remote execution request unit 9, the remote execution unit 11, the file transfer unit 10a, and the file transfer unit 10b are, for example, T
Data is transmitted and received via the LAN using the CP / IP protocol.

Next, the operation of this embodiment will be described. The flow of the user's operation, the software configuration setting process, and the software generation process are the same as those in the first embodiment, and a description thereof will be omitted. The software test execution processing will be described with reference to FIG. S301 to S
The steps up to 304 are the same as those in the first embodiment, and a description thereof will be omitted.

In S340, the test execution means 4
Activate the remote execution request means 9. In S341, the remote execution request unit 9 sends the software 104a and the test suit 107a to the software test computer 24 via the network 22 using the file transfer unit 10a. In S342, the file transfer unit 10b receives the file sent from the file transfer unit 10a in the software test computer 24, and
The test suit 107b is stored on the software test computer 24. In S343, the remote execution request unit 9 acquires the attribute value indicated in the software configuration information 102. In S344, the remote execution requesting means 9
A request for remote execution of the test of the software 104a is issued in S343.
Are sent to the remote execution unit 11 via the network 22 together with the attribute values obtained in Step 2. In S345, the remote execution executing means 11 activates the software 104b on the software test computer 24. In step S346, the remote execution execution unit 11 activates the test suit 107b by passing the attribute value of the software received from the remote execution request unit. Steps S307 to S309 are the same as those in the first embodiment, and a description thereof will be omitted.

In S347, the remote execution executing means 11 causes the file transfer means 10b to execute the test result information 1
08b is sent to the software generating computer 23 via the network 22. In S348, the file transfer means 10a on the software generation computer 23 receives the file, and stores the test result information 108a on the software generation computer 23. In S349, the remote execution performing unit 11 notifies the remote execution requesting unit 9 on the software generating computer 23 of the end of the test via the network 22. In S350, the remote execution requesting means 9 ends the program processing. Steps S310 and S311 are the same as those in the first embodiment, and a description thereof will be omitted.

As described above, in this embodiment, in the software generation test cooperation mechanism of the above-described embodiment, the software is tested separately from the software generation computer for generating the software and the test suit. A software test computer is provided, both computers are connected via a network, a software test remote execution request means and a file transfer means are provided on the software generation computer, and a software test remote test means is provided on the software test computer. An execution execution unit and a file transfer unit are provided. After the test suite is generated by the test execution unit on the software generation computer, the software and the test suite are sent to the software test computer via the network by the file transfer unit on the software generation computer. ,
A request for software test execution is sent from the remote execution requesting means to the remote execution execution means along with the attribute value indicated in the software configuration information via the network, and the remote execution execution means on the software test computer sends the request from the software generation computer. Software test using the software and the test suite, and after the test is executed, a file of the test result information created on the software test computer is sent to the software generation computer via the network by the file transfer means, The software generation test cooperation mechanism characterized in that the test result information is displayed on the user interface by the test execution means on the software generation computer has been described.

As described above, in the present embodiment, a computer that generates software and a test suit (having hardware specifications necessary for processing) and performs test execution of software (necessary for test execution). A computer (with only hardware specifications) is provided separately, the two computers are connected by a network, and the two computers cooperate with each other via the network so that the software test can be executed remotely. As a result, software tests on computers with hardware specifications that make it difficult to generate software and test suits can be easily performed remotely,
Convenience at the time of software testing can be improved.

In the above example, the network 22 is a LAN, and the remote execution requesting means 9 and the remote execution executing means 11, and the file transfer means 10a and the file transfer means 10b
Communication was performed using the P / IP protocol.
The communication means 7 and the communication server 8 are configured by TCP / WAN.
The effect described above can be obtained even if communication is performed using a protocol other than the IP protocol.

In the above example, the file transfer means 10a and 10b are provided on the software generation computer 23 and the software test computer 24, respectively.
A file is transmitted and received between the network and the file transfer means 10b via a network. However, a network file sharing function (existing technology, for example, UNIX NFS (Ne) developed by Sun Microsystems, USA)
work file system) and US Micr
Windows NT (W
The above effects can also be obtained by performing file transfer between the software generation computer 23 and the software test computer 24 by using a network shared file of Windows New Technology).

In the above example, the remote execution requesting means 9 requested to execute the remote test of the software from the test executing means 4 transfers the software 104a and the test suit 107a, executes the software test, and acquires the test result information. A series of operations are performed by file transfer means 10a, 10b,
This processing is performed by using the remote execution unit 11, but this processing is performed by the test execution unit 4 first by the file transfer unit 10a.
Transmits the software 104a and the file of the test suit 107a to the file transfer means 10b, and then causes the remote execution request means 9 and the remote execution execution means 11 to execute the software test on the software test computer 24,
After the test is completed, the above effect can be obtained even if the file of the test result information 108b is acquired on the software generation computer using the file transfer means 10a and 10b.

[0094]

According to the present invention, software and a test suit are generated according to software configuration information,
Software testing can be performed automatically to reduce the workload and reduce erroneous operations.

Further, according to the present invention, the efficiency of the user's software configuration setting operation can be improved.

Further, according to the present invention, it is possible to improve the efficiency of software generation and test work when replacing software components.

According to the present invention, the generation of functionally incomplete software can be prevented in advance, and the efficiency of software generation and test work can be improved.

Further, according to the present invention, large-scale software generation and test operations can be easily performed step by step, so that the efficiency of software generation and test operations can be improved.

Further, according to the present invention, the task of regenerating software is reduced, and the efficiency of the task of generating software can be improved.

Further, according to the present invention, software tests focused on components can be easily and collectively performed without regenerating software, and the efficiency of software generation test work can be improved.

Further, according to the present invention, since the user can remotely perform the operation of the software generation test work, the convenience for the user can be improved.

Further, according to the present invention, it is possible to eliminate a user who performs an unauthorized operation on the present mechanism, suppress the occurrence of operation failure of the present mechanism, and assist the user to operate the present mechanism smoothly. Further, for example, since the present mechanism can be shared by a plurality of users on computers at different remote locations, joint development of software by a plurality of persons is enabled, and user convenience can be improved.

Further, according to the present invention, the convenience at the time of software testing can be improved.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

FIG. 2 is a diagram illustrating a difference in software configuration.

FIG. 3 is a diagram illustrating an example of software component information.

FIG. 4 is a diagram illustrating an example of software configuration information.

FIG. 5 shows an example of a test program correspondence table.

FIG. 6 is a flowchart showing a flow of a user operation.

FIG. 7 is a diagram illustrating a display example on the user interface 1 according to the present embodiment.

FIG. 8 is a diagram showing a display example on the user interface 1 of the present embodiment.

FIG. 9 is a diagram showing a display example on the user interface 1 of the embodiment.

FIG. 10 is a diagram showing an internal operation of the software configuration setting processing.

FIG. 11 is a diagram showing an internal operation for software generation processing.

FIG. 12 is a diagram illustrating an operation of a test execution process according to the present embodiment.

FIG. 13 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

FIG. 14 is a diagram illustrating an operation of a software configuration setting process according to the present embodiment.

FIG. 15 is a diagram illustrating batch automatic generation test processing of software including a specified component.

FIG. 16 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

17 is a diagram illustrating an example of a software configuration rule 110. FIG.

FIG. 18 illustrates a software configuration setting process according to the present embodiment.

FIG. 19 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

FIG. 20 is a diagram showing processing for registering software 104 as a new component.

FIG. 21 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

FIG. 22 is a diagram illustrating an example of a software configuration information correspondence table.

FIG. 23 illustrates software generation processing.

FIG. 24 is a diagram showing an acquisition process of software stored and managed in the present mechanism.

FIG. 25 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

FIG. 26 is a diagram illustrating batch test processing of software including a specified component.

FIG. 27 is a configuration diagram of a software generation test cooperation mechanism of the present embodiment.

FIG. 28 illustrates a software configuration setting process.

FIG. 29 is a diagram illustrating a software generation process.

FIG. 30 is a diagram showing test execution processing of software.

FIG. 31 is a diagram showing a configuration of a software generation test cooperation mechanism of the present embodiment.

FIG. 32 is a diagram showing a flow of a user operation on a user interface.

FIG. 33 is a diagram showing a configuration of a software generation test cooperation mechanism of the present embodiment.

FIG. 34 is a diagram illustrating test execution processing of software.

FIG. 35 is a diagram showing a conventional software test environment construction device.

[Explanation of symbols]

1 user interface, 2 software configuration setting means, 3 software generation means, 4 test execution means,
5 component management means, 6 software management means, 9 remote execution request means, 10a, 10b file transfer means, 11 remote execution execution means, 22 software configuration setting means, 26 software management means, 32 software configuration setting means, 101 software component list File, 102 software configuration information, 103 software module database, 1
04, 104a, 104b software, 105 test program database, 106 test program correspondence table, 107, 107a, 107b test suit, 10
8, 108a, 108b test result information, 109 software configuration information database, 110 software configuration rules, 111 software database, 112
Software configuration information correspondence table.

Claims (11)

[Claims] 1. A software generation / test coordination mechanism for performing software generation and testing in cooperation with each other, comprising the following components: (a) Supporting software generation and testing (B) a software component list file that stores software component information relating to software modules that are components of software and attribute values corresponding to the software modules, and ) The software component information stored in the software component list file is displayed on the user interface, and predetermined software component information is obtained from the software component information. It was specified on the user interface,
Software configuration setting means for creating software configuration information including specified software component information and a value corresponding to the software component information,
(D) a software module database that stores software modules indicated by software component information stored in the software component list file; and (e) a plurality of software modules indicated by software component information included in the software configuration information. Software generating means for acquiring from a database, reflecting a value corresponding to the software component information included in the software configuration information in the software module, and combining the software modules to generate software; (f) the software component list file Test program data for storing a test program for implementing the functional test of each software module shown in Base, (g) test program correspondence table showing the correspondence between the test program stored in the software module and the test program database shown in the software component list file,
(H) acquiring from the test program database a plurality of test programs for implementing functional tests respectively corresponding to the plurality of software modules indicated in the software configuration information based on the test program correspondence table;
Test execution means for generating a test suit by combining a plurality of acquired test programs and executing a test of the software generated by the software generation means using the generated test suit to generate test result information. 2. The software generation test cooperation mechanism according to claim 1,
A software configuration information database storing a plurality of software configuration information; the software configuration setting means selects software configuration information specified on the user interface from the software configuration information database; The software generation test cooperation mechanism according to claim 1, wherein a software configuration is set for the software generation test and the software configuration. 3. The software configuration setting means searches the software configuration information database for software configuration information including software components specified on the user interface, and responds to the software configuration information by software generation means. 3. The software generation test cooperation mechanism according to claim 2, wherein the software generation and the test by the test execution means are collectively executed. 4. The software generation test cooperation mechanism according to claim 1,
The software configuration setting unit holds a software configuration rule including at least one of a rule regarding a combination of software modules indicated in the software component list file and a rule regarding setting of an attribute value corresponding to the software module. 2. The software generation test cooperation mechanism according to claim 1, wherein a check is made as to whether the configuration of the software input from the user interface does not violate the software configuration rules. 5. The software generation test cooperation mechanism according to claim 1,
Further, the software component information on the software module of the generated software and the attribute value corresponding to the software module is stored in the software component list file, the software module is stored in the software module database, and the generated software is stored in the software module database. 2. The software generation test cooperation mechanism according to claim 1, further comprising component management means for recording a correspondence relationship between the generated software and a plurality of test programs in a test program correspondence table. 6. The software generation test cooperation mechanism according to claim 1,
Further, a software database for storing software generated by the software generating means is provided, and software is designated on the user interface, the designated software is acquired from the software database, and software management means for acquiring the software on the user interface The software generation test cooperation mechanism according to claim 1, further comprising: 7. The software generation test cooperation mechanism according to claim 1,
The software configuration information in the software configuration information database and a software configuration information correspondence table for associating software in the software database, the software management means, the software interface on the user interface to specify the component of the software,
The software configuration information corresponding to the software in the software database including the specified software component is searched from the software configuration information correspondence table, and the software configuration information in the software configuration information database is searched based on the searched software configuration information. 7. The software generation test according to claim 6, wherein software is extracted from the software database based on the searched software configuration information, and a test is executed by the test execution means in a batch. Cooperation mechanism. 8. The software generation test cooperation mechanism,
A first computer provided with the software configuration setting means, the software generation means, and the test execution means; and a second computer mounted with the user interface, wherein the first and second computers are communicated with each other. 2. The software generation test cooperation mechanism according to claim 1, wherein the connection is established by a connection. 9. The software generation test cooperation mechanism according to claim 1,
Further, the first computer holds user account information for judging whether or not use of at least one of the software configuration setting means, the software generation means, and the test execution means is permitted, and the first computer 9. The software generation test cooperation mechanism according to claim 8, wherein whether or not the use request is permitted or not is determined based on the user account information in response to a use request from the second computer connected by the communication means. . 10. The software generation test cooperation mechanism includes a software generation computer that generates software and a test suit, and a software test computer that performs software testing, and connects both computers via a network. Remote execution request means for sending a software test execution request to the software test computer together with the attribute value indicated in the software configuration information to the software generation computer via the network, and the software and the test suite via the network. First file transfer means for sending to the software test computer, wherein the software test computer receives the software test execution request from the software generation computer by the remote execution request means. Remote execution executing means for executing a software test using the software and the test suite sent from the generating computer by the first file transfer means to generate test result information, and the remote execution executing means generates the test result information. 2. The software generation test cooperation mechanism according to claim 1, further comprising: second file transfer means for transmitting test result information to said software generation computer via said network. 11. A computer-readable recording medium on which a program for realizing the software generation test cooperation mechanism according to claim 1 is recorded.