WO2018066040A1 - Ordinateur de gestion et procédé de détermination d'environnement de test - Google Patents

Ordinateur de gestion et procédé de détermination d'environnement de test Download PDF

Info

Publication number
WO2018066040A1
WO2018066040A1 PCT/JP2016/079330 JP2016079330W WO2018066040A1 WO 2018066040 A1 WO2018066040 A1 WO 2018066040A1 JP 2016079330 W JP2016079330 W JP 2016079330W WO 2018066040 A1 WO2018066040 A1 WO 2018066040A1
Authority
WO
WIPO (PCT)
Prior art keywords
test
test environment
environment
information
test case
Prior art date
Application number
PCT/JP2016/079330
Other languages
English (en)
Japanese (ja)
Inventor
敬太 嶋田
裕教 江丸
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2016/079330 priority Critical patent/WO2018066040A1/fr
Priority to JP2018543496A priority patent/JP6695437B2/ja
Publication of WO2018066040A1 publication Critical patent/WO2018066040A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Preventing errors by testing or debugging software

Definitions

  • the present invention relates to a test environment management technique for performing a test defined by one or more test cases.
  • system development such as DevOps
  • DevOps requires a rapid and continuous release of applications, so a huge amount of regression testing is performed using multiple test environments.
  • Patent Document 1 In response to a request for efficient system development, the technology described in Patent Document 1 is known.
  • Patent Document 1 “In the retest method for judging the test comprehensiveness of a program, the retest range at the time of module correction is extracted based on the test data and the relevant information of the test target module, and the extracted test The data is re-executed, and the executed test result for the test data is compared with the current test result for verification ”.
  • the execution cost of system development includes an operation cost such as a usage fee, a management cost such as a user operation, and a processing cost such as a load on a computer when a test case is executed.
  • an operation cost such as a usage fee
  • a management cost such as a user operation
  • a processing cost such as a load on a computer when a test case is executed.
  • test contents and test environment status is enormous, and it is a burden on the user to determine a test environment that meets the user requirements. Therefore, there is a problem that the management cost increases.
  • test cases with a high load are concentrated in one test environment, and processing cost increases.
  • the present invention realizes a system and method for automatically determining a test environment that matches a user request in consideration of the content of the test and the state of the test environment.
  • a typical example of the invention disclosed in the present application is as follows. That is, a management computer connected to a computer system in which a plurality of test environments for executing a test case group including one or more test cases is constructed, the computer system including a plurality of computers, and the management computer includes: , A processor, a memory connected to the processor, a network interface connected to the processor, and candidates determined based on identification information of the test case group and characteristics of the test cases included in the test case group Group information including an entry composed of test environment identification information, and condition information including a dynamic condition that is a condition related to the state of the test environment, and the processor executes the first test case group When an opportunity is detected, the first information is referenced with reference to the group information.
  • a candidate test environment of the test case group is identified, status information indicating a status of the candidate test environment is acquired, and the first test case group is selected from the candidate test environments based on the condition information and the status information It is characterized by determining an execution test environment for executing.
  • FIG. 1 is a block diagram illustrating an example of a computer system according to a first embodiment.
  • FIG. 4 is a diagram illustrating an example of test case information according to the first embodiment. It is a figure which shows an example of the condition information of Example 1. It is a figure which shows an example of the test environment information of Example 1.
  • FIG. 4 is a diagram illustrating an example of license information according to the first embodiment. It is a figure which shows an example of the group information of Example 1.
  • FIG. 6 is a diagram illustrating an example of test execution queue information according to the first embodiment. It is a sequence diagram explaining the flow of the process which the management server of Example 1 performs. It is a sequence diagram explaining the flow of the process which the management server of Example 1 performs.
  • 6 is a flowchart illustrating an example of group generation processing executed by a group generation module according to the first embodiment. It is a flowchart explaining an example of the group evaluation process which the group evaluation module of Example 1 performs.
  • 6 is a flowchart illustrating an example of a dynamic classification process executed by the dynamic classification module according to the first embodiment. 6 is a flowchart illustrating an example of a dynamic classification process executed by the dynamic classification module according to the first embodiment. 6 is a flowchart illustrating an example of processing executed by the information acquisition module according to the first embodiment. It is a flowchart explaining an example of the process which the cost calculation module of Example 1 performs.
  • the identification information used for the table used in the embodiment may omit the identification information column if the table entry can be specified using one or more columns in the table.
  • the identification information may be automatically assigned identification numbers in ascending order. In each figure, the same reference numerals are given to common configurations.
  • a configuration and processing when a user request is a reduction in operation cost will be described.
  • the operation cost can be reduced by using a test environment with a low usage fee or shortening the usage time of the test environment.
  • a method and a system for realizing a reduction in operation cost by using a test environment with a low usage fee will be described. It should be noted that similar functions and effects can be realized with the same configuration for other user requests.
  • FIG. 1 is a block diagram illustrating an example of a computer system according to the first embodiment.
  • the computer system includes a management server 100, an on-premises system 101, and a cloud system 102, and is connected to each other via a management network 103.
  • the management network 103 may be divided into a network connected to the on-premises system 101 and a network connected to the cloud system 102.
  • the test is performed by the test environment executing one or more test cases.
  • the test case is information defining test contents including pre-execution conditions, input values, expected results, post-execution conditions, and the like.
  • the test environment is an environment for performing a test.
  • the on-premises system 101 and the cloud system 102 are systems that realize a test environment.
  • two types of test environments a staging environment and an alternative environment, are constructed on each system.
  • the staging environment is an environment that uses commercial software and is equivalent to the production environment.
  • the alternative environment is an environment using OSS.
  • the production environment is an environment where the system actually operates.
  • the on-premises system 101 is a system operated by a company to which a system developer belongs.
  • the cloud type system 102 is a system operated by a cloud service provider.
  • the on-premises system 101 and the cloud system 102 each include a plurality of computers, a plurality of storage devices, a plurality of network devices, and the like.
  • the test environment may be a test environment that uses a physical device itself as a resource, or may be a test environment that uses a virtual device as a resource.
  • a process for a test environment constructed on the cloud system 102 will be described.
  • a process for a test environment constructed on two systems will be described in a second embodiment.
  • Management server 100 determines a test environment for executing a test case.
  • the hardware configuration and software configuration of the management server 100 will be described.
  • the management server 100 includes a CPU (Central Processing Unit) 111, a memory 112, a network interface 113, and an IO interface 114. Each hardware mentioned above is mutually connected via an internal bus.
  • CPU Central Processing Unit
  • the CPU 111 executes a program stored in the memory 112.
  • the CPU 111 operates as a module that realizes a predetermined function by operating according to a program stored in the memory 112.
  • the CPU 111 functions as the information acquisition module 126 by operating according to the information acquisition program. The same applies to other programs.
  • the memory 112 stores programs executed by the CPU 111 and information.
  • the memory 112 also includes a work area that is temporarily used by the program. Programs and information included in the memory 112 will be described later.
  • the network interface 113 is an interface for communicating with an external device via an IP network or the like.
  • the IO interface 114 is an interface connected to the input device 104 and the display device 105.
  • the IO interface 114 may be connected to an external storage medium such as a USB memory and an external storage device.
  • the input device 104 is a device for inputting data to the management server 100.
  • a keyboard, a mouse, a touch panel, or the like can be used as the input device 104.
  • the display device 105 is a device for displaying the processing result of the management server 100 and the like.
  • a display, a touch panel, or the like can be used as the display device 105.
  • the number of each hardware is one, but may be two or more.
  • the management server 100 when the management server 100 is connected to a plurality of networks, the management server 100 may have a plurality of network interfaces 113 connected to each network.
  • the memory 112 stores a program for realizing the control module 120 and a management information group 130.
  • the control module 120 is a module that controls the entire management server 100, and includes a plurality of modules. Specifically, the control module 120 includes a test execution module 121, a static classification module 122, a dynamic classification module 123, a group generation module 124, a group evaluation module 125, an information acquisition module 126, and a cost calculation module 127.
  • the test execution module 121 executes a test case in the determined test environment in cooperation with each module.
  • the static classification module 122 selects a test environment candidate for executing each test case based on the test contents defined by the test case and the condition information 132.
  • the dynamic classification module 123 determines a test environment for executing a test case based on the test environment state and condition information 132 such as the test environment operating state. In the following description, the contents of the test defined by the test case are described as test case characteristics.
  • the group generation module 124 generates a test case group composed of one or more test cases. In this embodiment, a test is performed in units of test case groups.
  • the group evaluation module 125 selects a test environment candidate for executing the test case group based on the processing result of the static classification module 122. In the following description, test environment candidates for executing test case groups are described as candidate test environments.
  • the information acquisition module 126 acquires state information indicating the state of the test environment.
  • the cost calculation module 127 calculates an execution cost for system development. In this embodiment, the cost calculation module 127 calculates a usage fee for the test environment.
  • the management information group 130 includes test case information 131, condition information 132, test environment information 133, license information 134, group information 135, and test execution queue information 136. Details of each information will be described with reference to FIGS.
  • the programs and information stored in the memory 112 are non-transitory storage media that can be read by a computer such as HDD (Hard Disk Drive), SSD (Solid State Drive), non-volatile memory, IC card, SD card, and DVD. Alternatively, it may be stored in an external storage device. In this case, the CPU 111 reads a program and information from an external storage device or the like, and loads the program and information into the memory 112.
  • FIG. 2 is a diagram illustrating an example of the test case information 131 according to the first embodiment.
  • the test case information 131 is divided into two tables in consideration of the space of the drawing, but in reality, it is managed as one table.
  • the test case information 131 is information for managing a test case, and is a test case ID 201, automation 202, performance 203, unique function 204, importance 205, precondition 206, alternative environment 207, execution environment 208, error 209, prediction time.
  • 210 includes an entry composed of 210, system ID 211, use case / function 212, and grouping 213. The entry may include columns other than those described above.
  • Test case ID 201 stores identification information for identifying a test case.
  • the test case ID 201 is also used as identification information for identifying the entry of the test case information 131.
  • the automation 202 stores information indicating whether the test case can be automated.
  • the automation 202 stores either “possible” or “impossible”.
  • Performance 203 stores information indicating whether the test defined in the test case is a performance test.
  • the performance 203 stores either “YES” or “NO”.
  • the performance test is performed for the purpose of measuring the performance of the system in the production environment. Therefore, the performance test needs to be performed in a staging environment equivalent to the production environment. As a test that needs to use a staging environment, a test or the like can be considered for the purpose of confirming security.
  • the unique function 204 stores information indicating whether or not the test defined in the test case is a test for confirming the unique function of the commercial software.
  • the unique function 204 stores either “YES” or “NO”.
  • the importance 205 stores importance indicating the test case execution order (test execution order) and the like.
  • the importance level represents the high occurrence rate of bugs or the influence level of the entire system.
  • an integer of “1” or more is stored in the importance degree 205. In this embodiment, the closer the value is to 1, the higher the importance.
  • a value set by the user may be set as the importance level 205, or a value calculated based on the dependency between test cases may be set as the importance level 205. For example, a method of setting a value based on the number registered in the precondition 206 can be considered.
  • the precondition 206 stores identification information of a test case that needs to be executed before executing the test case corresponding to the entry. Note that if there is no test case that needs to be executed in advance, the precondition 206 is blank. For example, if there is a first test case that defines a test for adding records in the database and a second test case that defines a test for deleting records added in the first test case, the second test The case is premised on the first test case. Therefore, the identification information of the first test case is stored in the precondition 206 of the entry corresponding to the second test case.
  • the alternative environment 207 stores information indicating whether or not the test case can be executed in the alternative environment 207.
  • the alternative environment 207 stores either “possible” or “impossible”.
  • the execution environment 208 stores the identification information of the test environment that executed the test case last time.
  • the execution environment 208 stores identification information set in a test environment ID 401 (see FIG. 4) described later.
  • the error 209 stores information indicating whether or not the test result is an expected result in the test case. If the test result is not the result expected in the test case, “error” is stored in the error 209, and if the test result is the result expected in the test case, the error 209 is blank.
  • the predicted time 210 stores a predicted value of the test execution time defined by the test case.
  • the execution time of the test executed last time may be stored in the prediction time 210, and the statistical value of the execution time of the test executed so far may be stored in the prediction time 210.
  • the statistical value indicates an average value, a maximum value, a median value, and the like.
  • the system ID 211 stores identification information of a system or software that is a test target defined in the test case.
  • the use case / function 212 stores identification information such as a specific function to be a test target defined in the test case.
  • the grouping 213 stores information indicating whether the entry has been processed by the group generation module 124.
  • the grouping 213 stores either “executed” or “not executed”.
  • the automation 202, performance 203, unique function 204, importance 205, and precondition 206 are used as test case characteristics.
  • FIG. 3 is a diagram illustrating an example of the condition information 132 according to the first embodiment.
  • the condition information 132 is information for managing a condition for determining a test environment for executing a test case group, and includes an entry including a condition ID 301, a condition type 302, an item 303, and a condition 304.
  • the entry may include columns other than those described above.
  • the condition ID 301 stores identification information for uniquely identifying the condition.
  • the condition type 302 stores information indicating the type of condition.
  • the condition type 302 stores either “static” or “dynamic”.
  • “Static” is a condition used by the static classification module 122
  • “Dynamic” is a condition used by the dynamic classification module 123.
  • Static conditions are conditions such as parameters that do not depend on time.
  • Conditions regarding the test case characteristics are mainly set as static conditions.
  • the dynamic conditions are conditions such as time-dependent parameters.
  • Conditions regarding the state of the test environment are mainly set as dynamic conditions.
  • Item 303 stores information indicating the name and type of the condition.
  • the item 303 is displayed on a GUI or the like for the user to input a user request.
  • the condition 304 stores the content of a specific condition.
  • the condition is described as a character string for explanation, but data other than the character string such as a conditional expression may be stored.
  • the numerical value set in the condition 304 may be determined by the user.
  • FIG. 4 is a diagram illustrating an example of the test environment information 133 according to the first embodiment.
  • the test environment information 133 is information for managing the configuration of the test environment, the state of the test environment, and the like. Contains an entry consisting of The entry may include columns other than those described above.
  • the test environment ID 401 stores identification information for uniquely identifying the test environment.
  • the test environment type 402 stores information indicating the type of test environment. In the test environment type 402 of this embodiment, either “staging” or “alternative” is stored.
  • Configuration 403 stores configuration information of the test environment.
  • the type of OS (Operating System) operating in the test environment is stored in the configuration 403.
  • the configuration 403 may store the hardware configuration and software configuration of the test environment.
  • the replacement target software 404 stores commercial software to be replaced with OSS or OSS identification information.
  • the replacement target software 404 stores identification information of commercial software to be replaced with the OSS.
  • the substitution target software 404 stores OSS identification information.
  • the CPU usage rate 405 stores the usage rate of the CPU included in the server or the like constituting the test environment. For example, when the server is a physical server, the usage rate of the physical CPU is stored in the CPU usage rate 405, and when the server is a VM, the usage rate of the virtual CPU is stored in the CPU usage rate 405.
  • the memory usage rate 406 stores the usage rate of the memory included in the server or the like constituting the test environment. For example, when the server is a physical server, the physical memory usage rate is stored in the memory usage rate 406, and when the server is a VM, the virtual memory usage rate is stored in the memory usage rate 406.
  • FIG. 5 is a diagram illustrating an example of the license information 134 according to the first embodiment.
  • the license information 134 is information for managing the license fee of the software used in the test environment, and includes an entry composed of a license ID 501, software 502, usage state 503, test environment ID 504, and fee 505.
  • the entry may include columns other than those described above.
  • the license ID 501 stores identification information for uniquely identifying the license.
  • the software 502 stores software identification information included in the licensed test environment.
  • the software 502 stores service identification information.
  • the usage state 503 stores information indicating whether or not the license is being used.
  • the usage state 503 stores either “in use” or “unused”.
  • Test environment ID 504 stores the identification information of the test environment targeted for the license.
  • the test environment ID 504 stores identification information set in the test environment ID 401.
  • Fee 505 stores the usage fee for the licensed test environment.
  • FIG. 6 is a diagram illustrating an example of the group information 135 according to the first embodiment.
  • the group information 135 is information for managing the test case group generated by the group generation module 124, and includes an entry including a group ID 601, a group importance 602, an alternative environment 603, and a test case 604.
  • the entry may include columns other than those described above.
  • the group ID 601 stores identification information for uniquely identifying the test case group.
  • the group importance 602 stores the importance of the test case group.
  • the group importance 602 is used to determine the execution order between test case groups.
  • the alternative environment 603 stores information indicating whether or not the alternative environment can be used as a test case group.
  • the alternative environment 603 stores either “possible” or “impossible”.
  • the value set in the alternative environment 603 is determined based on the alternative environment 207 of the test case included in the test case group. In this embodiment, since the type of test environment is used as information for specifying a candidate test environment, the entry includes an alternative environment 603.
  • Test case 604 stores the identification information of the test cases that constitute the test case group. There are as many columns in the test case 604 as the number of test cases included in the test case group. In each column of the test case 604, identification information set in the test case ID 201 is stored. In this embodiment, test cases are executed in order from the left of the test case 604.
  • FIG. 7 is a diagram illustrating an example of the test execution queue information 136 according to the first embodiment.
  • Test execution queue information 136 is information for managing a test execution queue for registering a test case, and includes an entry including a queue ID 701, a test case ID 702, a group ID 703, and an execution environment ID 704.
  • the entry may include columns other than those described above.
  • the queue ID 701 stores identification information for uniquely identifying the queue.
  • Test case ID 702 stores the identification information of the test case put in the queue.
  • the test case ID 702 stores the identification information set in the test case ID 201.
  • the group ID 703 stores the identification information of the test case group to which the test case submitted to the queue belongs. In the group ID 703, identification information set in the group ID 601 is stored.
  • the execution environment ID 704 stores identification information of a test environment that executes a test corresponding to the test case. In the execution environment ID 704, identification information set in the test environment ID 401 is stored.
  • 8A and 8B are sequence diagrams illustrating the flow of processing executed by the management server 100 according to the first embodiment.
  • test execution module 121 When the test execution module 121 detects the start timing of the test (test case group) (step S801), the test execution module 121 transmits a start command to the static classification module 122 (step S802). Further, the test execution module 121 displays a screen for inputting a budget to the user, and accepts an input of the budget.
  • the test execution module 121 may detect a test start instruction input by the user as a test start trigger. Further, the test execution module 121 may determine that the test has started when the time set in the execution schedule has elapsed or when the system to be tested commits the source to the version management software. .
  • a screen for inputting a budget may not be displayed.
  • the static classification module 122 executes a static classification process (step S803).
  • the static classification module 122 selects an executable test environment for each test case based on the test case characteristics. Details of the static classification processing will be described with reference to FIG.
  • the static classification module 122 transmits a completion notification to the test execution module 121 after the static classification processing is completed (step S804).
  • test execution module 121 When the test execution module 121 receives the completion notification from the static classification module 122, the test execution module 121 transmits a start command to the group generation module 124 (step S805).
  • the group generation module 124 When the group generation module 124 receives a start command from the test execution module 121, the group generation module 124 executes a group generation process (step S806). In the group generation process, the group generation module 124 generates a test case group. Details of the group generation processing will be described with reference to FIG.
  • the group generation module 124 transmits a completion notification to the test execution module 121 after the group generation processing is completed (step S807).
  • test execution module 121 When the test execution module 121 receives the completion notification from the group generation module 124, the test execution module 121 transmits a start command to the group evaluation module 125 (step S808).
  • the group evaluation module 125 When the group evaluation module 125 receives a start command from the test execution module 121, the group evaluation module 125 executes a group evaluation process (step S809). In the group evaluation process, the group evaluation module 125 selects a candidate test environment. Details of the group evaluation process will be described with reference to FIG.
  • the group evaluation module 125 transmits a completion notification to the test execution module 121 after the group evaluation process is completed (step S810).
  • test execution module 121 When the test execution module 121 receives the completion notification from the group evaluation module 125, the test execution module 121 transmits a start command to the dynamic classification module 123 (step S811).
  • the dynamic classification module 123 executes a dynamic classification process when receiving a start command from the test execution module 121 (step S812).
  • the dynamic classification module 123 determines a test environment for executing the test case group based on the state of the candidate test environment. Further, the dynamic classification module 123 registers the test cases included in the test case group in the test execution queue. Details of the dynamic classification processing will be described with reference to FIGS. 12A and 12B.
  • the dynamic classification module 123 transmits a completion notification to the test execution module 121 after the dynamic classification process is completed (step S813).
  • the test execution module 121 refers to the test execution queue information 136 and executes the test case put in the test execution queue (step S814).
  • test case group can be executed in an appropriate test environment.
  • FIG. 9 is a flowchart for explaining an example of the static classification process executed by the static classification module 122 of the first embodiment.
  • the static classification module 122 starts a test case loop process (step S901).
  • the static classification module 122 refers to the test case information 131 and selects one target test case. In addition, the static classification module 122 acquires an entry in which “static” is set in the condition type 302 from the condition information 132.
  • the target test case may be selected from all the test cases registered in the test case information 131, or the target test case may be selected from the test cases related to the changed software. Also good.
  • the processing load can be reduced by narrowing down to only test cases related to the changed software.
  • the static classification module 122 selects a test environment that can execute the target test case based on the static condition.
  • the static classification module 122 refers to the test case information 131 and determines whether or not the entry automation 202 corresponding to the target test case is “possible” (step S902).
  • the static classification module 122 proceeds to step S910. In this case, “impossible” is set in the alternative environment 207 of the entry.
  • the static classification module 122 determines whether or not the target test case can be executed in the alternative environment (step S903). Specifically, the following processing is executed.
  • the static classification module 122 determines whether or not the performance 203 of the entry corresponding to the target test case is “YES”.
  • the static classification module 122 determines that the target test case cannot be executed in the alternative environment.
  • the static classification module 122 determines whether or not the unique function 204 of the entry is “YES”.
  • the static classification module 122 determines that the target test case cannot be executed in the alternative environment. If it is determined that the unique function 204 of the entry is “NO”, the static classification module 122 determines that the target test case can be executed in the alternative environment. The above is the description of the process in step S903.
  • the static classification module 122 sets “impossible” in the alternative environment 207 of the entry corresponding to the target test case (step S909). Thereafter, the static classification module 122 proceeds to step S910.
  • the static classification module 122 executes the test case in each of the staging environment and the alternative environment (step S904).
  • the static classification module 122 transitions to a waiting state until test results are output from the staging environment and the alternative environment.
  • the static classification module 122 determines whether or not it is necessary to review the test case based on the test result (step S905).
  • the static classification module 122 determines whether an expected result in the test case has been output.
  • the static classification module 122 proceeds to step S910. In this case, no value may be set in the alternative environment 207 of the entry.
  • the static classification module 122 determines whether the test results of the staging environment and the alternative environment match (step S906). It should be noted that the test result does not have to be a complete match, but may be a similar result.
  • the static classification module 122 sets “impossible” in the alternative environment 207 of the entry (step S909). Thereafter, the static classification module 122 proceeds to step S910.
  • the static classification module 122 sets “possible” to the alternative environment 207 of the entry (step S907). Thereafter, the static classification module 122 proceeds to step S910.
  • step S910 the static classification module 122 determines whether the processing has been completed for all selectable test cases (step S910).
  • the static classification module 122 returns to step S901, selects a new target test case, and executes the same processing.
  • the static classification module 122 ends the test case loop processing and transmits a completion notification to the test execution module 121 (step S911). Thereafter, the static classification module 122 ends the static classification process.
  • the static classification module 122 selects a test environment capable of executing a test case based on the test case characteristics. In the present embodiment, the static classification module 122 performs control so that the alternative environment is preferentially selected. This can reduce the operating cost of the test case.
  • the static classification module 122 selects either the staging environment or the alternative environment, but the present invention is not limited to this. By changing the conditions set in the condition information 132, the static classification module 122 can select a test environment based on various viewpoints.
  • FIG. 10 is a flowchart illustrating an example of group generation processing executed by the group generation module 124 according to the first embodiment.
  • the group generation module 124 sets “not executed” in the grouping 213 of all entries of the test case information 131 (step S1001).
  • the group generation module 124 specifies a test case that is not registered in the precondition 206 (step S1002).
  • the group generation module 124 refers to the precondition 206 of each entry and identifies a test case that is not registered in the precondition 206 of any entry.
  • the test case that is not registered in the precondition 206 corresponds to the test case that is executed last in the test case group.
  • the group generation module 124 starts loop processing of the specified test case (step S1003).
  • the group generation module 124 selects one test case from the specified test cases, and executes the processing from step S1004 to step S1011.
  • the group generation module 124 sets the selected test case as a target test case (step S1004), and generates a test case group including the target test case (step S1005).
  • the group generation module 124 adds an entry to the group information 135 and sets identification information in the group ID 601 of the added entry.
  • the group generation module 124 adds a column to the test case 604 and sets target test case identification information.
  • the group generation module 124 refers to the test case information 131 and sets “executed” in the grouping 213 of the target test case entry.
  • the group generation module 124 determines whether there is a test case having a dependency relationship with the target test case (step S1006).
  • the group generation module 124 searches for an entry in which the target test case identification information is stored in the precondition 206. If the entry does not exist, the group generation module 124 determines that there is no test case having a dependency relationship with the target test case.
  • the group generation module 124 adds the searched test case to the test case group (step S1007).
  • the group generation module 124 acquires the test case identification information searched in step S1006 from the test case information 131.
  • the group generation module 124 adds the test case identification information acquired to the test case 604 of the entry added to the group information 135 in step S1005.
  • the test case identification information is set in order from the right. That is, the identification information of the newly set test case is set on the rightmost side.
  • the group generation module 124 refers to the test case information 131 and sets “executed” in the grouping 213 of the target test case entry (step S1008). If the grouping 213 is already “executed”, this step can be omitted.
  • the group generation module 124 sets the test case searched in step S1007 as a new target test case (step S1009). Thereafter, the group generation module 124 returns to step S1006 and executes the same processing.
  • step S1006 when it is determined that there is no test case having a dependency relationship with the target test case, the group generation module 124 refers to the test case information 131 and displays “executed” in the grouping 213 of the target test case entry. Is set (step S1010). If the grouping 213 is already “executed”, this step can be omitted.
  • the group generation module 124 calculates the importance of the test case group generated in step S1005 (step S1011). Specifically, the following processing is executed.
  • the group generation module 124 acquires test case identification information included in the test case group from the test case 604 of the entry added to the group information 135.
  • the group generation module 124 refers to the test case information 131 to search for an entry that matches the identification information of the test case for which the test case ID 201 is acquired, and acquires a value from the importance 205 of the searched entry.
  • the group generation module 124 calculates the importance of the test case group using the acquired value. For example, the total value, average value, maximum value, minimum value, etc. of the importance of the test case are calculated as the importance of the test case group.
  • the group generation module 124 sets the importance calculated in the group importance 602 of the entry added to the group information 135. The above is the description of the process in step S1011.
  • the group generation module 124 determines whether or not processing has been completed for all the test cases specified in step S1002 (step S1012).
  • step S1002 When it is determined that the processing has not been completed for all the test cases specified in step S1002, the group generation module 124 returns to step S1003, selects a new test case from the specified test cases, A similar process is executed.
  • the group generation module 124 ends the test case loop processing and transmits a completion notification to the test execution module 121 (step S1013). Thereafter, the group generation module 124 ends the group generation process.
  • test case information 131 shown in FIG. 2 “TC2”, “TC3”, and “TC5” are specified in step S1002.
  • the test case group of “TC2” includes “TC2” and “TC1”, the test case group of “TC3” includes only “TC3”, the test case group of “TC5” includes “TC1”, “TC4”, and Includes “TC5”.
  • “TC1” is included in two test case groups.
  • group generation module 124 may set the grouping 213 to “unexecuted” only for test case entries related to the changed software.
  • the group generation module 124 can generate a test case group including one or more test cases based on the dependency relationship between the test cases.
  • FIG. 11 is a flowchart illustrating an example of the group evaluation process executed by the group evaluation module 125 according to the first embodiment.
  • the group evaluation module 125 starts loop processing of the test case group (Step S1101).
  • the group evaluation module 125 refers to the group information 135 and selects one target test case group.
  • the group evaluation module 125 determines whether or not a test case that can be executed only in the staging environment is included in the target test case group (step S1102). Specifically, the following processing is executed.
  • the group evaluation module 125 refers to the group information 135 and acquires test case identification information from the test case 604 of the target test case group entry.
  • the group evaluation module 125 refers to the test case information 131 and searches for an entry whose test case ID 201 matches the acquired test case identification information.
  • the group evaluation module 125 refers to the alternative environment 207 of the searched entry, and determines whether there is an entry for which the alternative environment 207 is “impossible”. If there is an entry in which the alternative environment 207 is “impossible”, the group evaluation module 125 determines that the target test case group includes test cases that can be executed only in the staging environment. The above is the description of the processing in step S1102.
  • the group evaluation module 125 When it is determined that a test case that can be executed only in the staging environment is not included in the target test case group, the group evaluation module 125 refers to the group information 135 and displays “possible” in the alternative environment 603 of the target test case group entry. Is set (step S1103). That is, the alternative environment is selected as a candidate test environment for the target test case group. Thereafter, the group evaluation module 125 proceeds to step S1105.
  • the group evaluation module 125 When it is determined that a test case that can be executed only in the staging environment is included in the target test case group, the group evaluation module 125 refers to the group information 135 and displays “impossible” in the alternative environment 603 of the target test case group entry. Is set (step S1104). That is, the staging environment is selected as a candidate test environment for the target test case group. Thereafter, the group evaluation module 125 proceeds to step S1105.
  • step S1105 the group evaluation module 125 determines whether or not processing has been completed for all test case groups (step S1105).
  • the group evaluation module 125 When it is determined that the processing has not been completed for all the test case groups, the group evaluation module 125 returns to step S1101, selects a new target test case group, and executes the same processing.
  • the group evaluation module 125 ends the test case group loop processing, and transmits a completion notification to the test execution module 121 (step S1106). Thereafter, the group evaluation module 125 ends the group evaluation process.
  • 12A and 12B are flowcharts for explaining an example of the dynamic classification process executed by the dynamic classification module 123 of the first embodiment.
  • the dynamic classification module 123 rearranges the entries of the group information 135 in descending order of group importance (step S1201). In this embodiment, the smaller the value is, the higher the importance is. Therefore, the entries are rearranged in order of increasing group importance 602 value.
  • the process in step S1201 is a process for preferentially executing a test case having a high degree of importance.
  • the dynamic classification module 123 starts a loop process for the test case group (step S1202).
  • the dynamic classification module 123 refers to the group information 135 and selects one target test case. Further, the dynamic classification module 123 acquires an entry in which “dynamic” is set in the condition type 302 from the condition information 132.
  • the dynamic classification module 123 determines a test environment for executing the selected test case group based on the dynamic conditions.
  • the dynamic classification module 123 refers to the group information 135 to determine whether or not the alternative environment 603 of the entry corresponding to the target test case group is “possible” (step S1203). That is, it is determined whether or not the alternative environment is a candidate test environment.
  • This process is a process for specifying a candidate test environment.
  • the dynamic classification module 123 refers to the test environment information 133 and sets the staging environment for executing the target test case group. Determination is made (step S1205). Thereafter, the dynamic classification module 123 proceeds to step S1211. Specifically, the following processing is executed.
  • the dynamic classification module 123 refers to the test environment information 133 and searches for an entry whose test environment type 402 is “staging”.
  • the dynamic classification module 123 acquires the CPU usage rate 405 and the memory usage rate 406 of the retrieved entry.
  • the dynamic classification module 123 identifies a staging environment that satisfies the dynamic condition in which the item 303 is “operating state” based on the acquired CPU usage rate and memory usage rate.
  • the dynamic classification module 123 selects a staging environment with the lowest CPU usage rate from among the specified staging environments.
  • the dynamic classification module 123 determines the selected staging environment as a staging environment for executing the selected test case group. Note that the processing described above is an example, and the present invention is not limited to this. The above is the description of the processing in step S1205.
  • the dynamic classification module 123 determines whether or not the alternative environment can be used (step S1204).
  • the dynamic classification module 123 refers to the condition information 132, and substitutes based on the schedule set in the condition 304 of the entry whose condition type 302 is “dynamic” and the item 303 is “schedule”. Determine whether the environment can be used. For example, the dynamic classification module 123 can determine whether the alternative environment can be used by comparing the current time or the scheduled start time of the test case group with the schedule.
  • the dynamic classification module 123 determines an alternative environment for executing the target test case group (step S1206).
  • the dynamic classification module 123 refers to the test environment information 133 and searches for an entry whose test environment type 402 is “alternate”.
  • the dynamic classification module 123 selects an alternative environment having the smallest CPU usage rate 405 or memory usage rate 406 value of the retrieved entry.
  • the dynamic classification module 123 determines the selected alternative environment as an alternative environment for executing the target test case group. The above is the description of the processing in step S1206.
  • the dynamic classification module 123 determines whether or not resources necessary for the test exist in the determined alternative environment (step S1207).
  • the dynamic classification module 123 refers to the test environment information 133 and acquires the values of the CPU usage rate 405 and the memory usage rate 406 of the entry corresponding to the determined alternative environment. The dynamic classification module 123 determines whether or not the dynamic condition that the item 303 is “operating state” is satisfied based on the acquired CPU usage rate and memory usage rate. When the dynamic condition in which the item 303 is “operating state” is not satisfied, the dynamic classification module 123 determines that the resource necessary for the test does not exist in the determined alternative environment.
  • the dynamic classification module 123 proceeds to step S1211.
  • the dynamic classification module 123 calls the cost calculation module 127 (step S1208). At this time, the dynamic classification module 123 inputs the identification information of the target test case group to the cost calculation module 127. The dynamic classification module 123 shifts to a waiting state until a response including a usage fee is received from the cost calculation module 127. Processing executed by the cost calculation module 127 will be described with reference to FIG.
  • the dynamic classification module 123 determines whether or not the configuration of the alternative environment can be added within the budget (step S1209).
  • the dynamic classification module 123 determines whether or not the usage fee is below the budget. If the usage fee is less than or equal to the budget, the dynamic classification module 123 determines that an alternative environment can be added within the budget.
  • step S1211 If it is determined that the alternative environment cannot be added within the budget, the dynamic classification module 123 proceeds to step S1211.
  • the dynamic classification module 123 adds a test environment (step S1210), and the added test environment is changed to a test environment that executes the selected test case group. decide. Thereafter, the dynamic classification module 123 proceeds to step S1211. Since a known technique may be used for adding a test environment, a description thereof will be omitted.
  • the alternative environment is usually generated in step S1210.
  • the dynamic classification module 123 determines a test environment in which the test case group is executed based on the dynamic condition.
  • step S1211 the dynamic classification module 123 starts loop processing of test cases included in the target test case group (step S1211).
  • the dynamic classification module 123 refers to the group information 135 and selects one test case identification information (target test case) set in the test case 604 of the target test case group entry. At this time, the dynamic classification module 123 selects test case identification information in the execution order of the test cases. That is, test case identification information is selected in order from the left. This is because test cases are set in the test case 604 in the reverse order of the test case execution order.
  • the dynamic classification module 123 registers the target test case in the test execution queue information 136 (step S1212).
  • the dynamic classification module 123 adds an entry to the test execution queue information 136 and sets identification information in the queue ID 701 of the added entry.
  • the dynamic classification module 123 sets target test case identification information in the test case ID 702 and sets target test case group identification information in the group ID 703. Further, the dynamic classification module 123 sets the identification information of the determined test environment in the execution environment ID 704 of the added entry.
  • the dynamic classification module 123 determines whether or not the processing has been completed for all the test cases included in the target test case group (step S1213).
  • the dynamic classification module 123 When it is determined that the processing has not been completed for all the test cases included in the target test case group, the dynamic classification module 123 returns to step S1211, selects a new target test case, and executes the same processing. To do.
  • the dynamic classification module 123 determines whether the processing has been completed for all the test case groups (step S1214).
  • the dynamic classification module 123 returns to step S1202, newly selects a target test case group, and executes the same processing.
  • the dynamic classification module 123 transmits a completion notification to the test execution module 121 (step S1216). Thereafter, the dynamic classification module 123 ends the dynamic classification process.
  • the dynamic classification module 123 can determine the test environment for actually executing the test case group based on the dynamic condition.
  • FIG. 13 is a flowchart illustrating an example of processing executed by the information acquisition module 126 according to the first embodiment.
  • the information acquisition module 126 starts processing described below periodically or when a start command is received from the test execution module 121.
  • the information acquisition module 126 starts loop processing of the test environment (step S1301).
  • the information acquisition module 126 refers to the test environment information 133 and selects one target test environment.
  • the information acquisition module 126 acquires state information indicating the operating state of the test environment from the target test environment (step S1302).
  • test environment status indicates CPU usage rate, memory usage rate, network bandwidth, IO performance, etc. Since the method for acquiring the status information is known, detailed description thereof is omitted.
  • the information acquisition module 126 registers the acquired state information in the test environment information 133 (step S1303).
  • values are set in the CPU usage rate 405 and the memory usage rate 406 of the target test environment entry.
  • the information acquisition module 126 determines whether or not the processing has been completed for all test environments (step S1304).
  • step S1301 selects a new target test environment, and executes similar processing.
  • the information acquisition module 126 ends the processing.
  • the information acquisition module 126 can acquire the status information of the test environment.
  • FIG. 14 is a flowchart illustrating an example of processing executed by the cost calculation module 127 according to the first embodiment.
  • the cost calculation module 127 calculates the usage fee (operation cost) of the alternative environment for executing the target test case group selected in step S1202 (step S1401). Specifically, the following processing is executed.
  • the cost calculation module 127 refers to the group information 135, and acquires test case identification information from the test case 604 of the test case group entry selected in step S1202.
  • the cost calculation module 127 refers to the test case information 131 and acquires the value of the predicted time 210 of the entry that matches the identification information of the test case from which the test case ID 201 is acquired.
  • the cost calculation module 127 calculates the predicted time of the test case group by summing the acquired values.
  • the cost calculation module 127 refers to the license information 134 and acquires the value of the charge 505 for each entry.
  • the cost calculation module 127 calculates the usage fee for each test environment by multiplying the fee per unit time by the predicted time. The above is the description of the processing in step S1401.
  • the cost calculation module 127 selects the test environment with the lowest usage fee, and outputs the identification information and usage fee of the selected test environment to the dynamic classification module 123 (step S1402). Thereafter, the cost calculation module 127 ends the process.
  • the dynamic classification module 123 can add a test environment having the same configuration as the determined test environment based on the test environment identification information.
  • the management server 100 can change the test environment determined according to the user request. Information and processing contents when generalized will be described.
  • the alternative environment 207 of the test case information 131 is replaced with the selected test environment ID.
  • the selected test environment ID stores identification information of a test environment that can execute the test case.
  • the alternative environment 603 of the group information 135 is replaced with a candidate test environment ID.
  • the candidate test environment ID stores specific test environment identification information or test environment type.
  • the group evaluation module 125 selects a candidate test environment from the test environments set in the selected test environment ID instead of steps S1102 to S1104. Further, the group evaluation module 125 sets the identification information of the selected candidate test environment as the candidate test environment ID of the group information 135. For example, in the case of a user request for the purpose of reducing processing costs, a test environment that can execute all test cases and has the smallest CPU usage rate is selected.
  • the dynamic classification module 123 refers to the group information 135 and identifies a candidate test environment. In step S1206, the dynamic classification module 123 searches the test environment other than the candidate test environments based on the dynamic condition, and determines the execution test environment from the searched test environments.
  • the management server 100 sets the alternative environment as a candidate test environment, and selects two alternative environments that use a low amount of resources from the candidate test environment.
  • the software name or function type may be set as a static condition.
  • a test environment having designated software or function can be set as a candidate test environment.
  • the management server 100 selects a candidate test environment for executing the test case group based on the test contents, and further executes the test case group based on the state of the test environment and the user request.
  • the environment can be determined.
  • the management server 100 can quickly determine the test environment. Further, the management server 100 can determine a test environment that matches the user request according to the state of the test environment.
  • the management server 100 selects an alternative environment.
  • the management server 100 selects a test environment with a small amount of resources used or a test environment with a low load.
  • the second embodiment is different in that a test environment is generated in each of the on-premises system 101 and the cloud system 102.
  • Test case information 131 The configuration of the computer system and the configuration of the management server 100 in the second embodiment are the same as those in the first embodiment.
  • Test case information 131, license information 134, group information 135, and test execution queue information 136 are the same as those in the first embodiment.
  • condition information 132 and the test environment information 133 are different.
  • a system type column is newly added to the test environment information 133. For example, either “on-premises” or “cloud” is stored in the column. As a result, it is possible to identify on which system the test environment is generated.
  • “on-premises” is set as the static condition in the condition information 132. This is because the charge can be reduced by using the on-premises system 101.
  • each module of the second embodiment is the same as that of the first embodiment. However, the processes executed by the static classification module 122 and the dynamic classification module 123 are partially different.
  • the static classification module 122 selects a test environment on the on-premises system 101 as a candidate test environment. Further, the dynamic classification module 123 determines a test environment for executing the test case group from the test environments on the on-premises system 101. When the test environment on the on-premises system 101 is insufficient, the dynamic classification module 123 determines a test environment for executing the test case group from the test environments on the cloud system 102.
  • the dynamic classification module 123 determines whether or not the on-premises system 101 can generate a test environment that satisfies the dynamic condition that the item 303 is “operating state”. Determine.
  • step S1211 the dynamic classification module 123 proceeds to step S1211. If the determination result is NO, the dynamic classification module 123 proceeds to step S1209. At this time, the dynamic classification module 123 inputs the system type “cloud” to the cost calculation module 127.
  • Example 2 has the same effect as Example 1.
  • this invention is not limited to the above-mentioned Example, Various modifications are included. Further, for example, the above-described embodiments are described in detail for easy understanding of the present invention, and are not necessarily limited to those provided with all the described configurations. In addition, a part of the configuration of the embodiment can be added to, deleted from, or replaced with another configuration.
  • each of the above-described configurations, functions, processing units, processing means, and the like may be realized by hardware by designing a part or all of them with, for example, an integrated circuit.
  • the present invention can also be realized by software program codes that implement the functions of the embodiments.
  • a storage medium in which the program code is recorded is provided to the computer, and a CPU included in the computer reads the program code stored in the storage medium.
  • the program code itself read from the storage medium realizes the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention.
  • Examples of storage media for supplying such program codes include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A non-volatile memory card, ROM, or the like is used.
  • program code for realizing the functions described in this embodiment can be implemented by a wide range of programs or script languages such as assembler, C / C ++, Perl, Shell, PHP, Java, and the like.
  • the program code is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or CD-R.
  • the CPU included in the computer may read and execute the program code stored in the storage unit or the storage medium.
  • control lines and information lines indicate those that are considered necessary for the explanation, and do not necessarily indicate all the control lines and information lines on the product. All the components may be connected to each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Computer And Data Communications (AREA)

Abstract

L'invention concerne un ordinateur de gestion connecté à un système informatique dans lequel une pluralité d'environnements de test pour implémenter des groupes de cas de test sont construits, chaque groupe de cas de test comprenant un ou plusieurs cas de test, l'ordinateur de gestion stockant des informations de groupe qui comprennent des données saisies comprenant à la fois des informations d'identification concernant les groupes de cas de test, et des informations d'identification concernant des environnements de test candidats déterminés sur la base de caractéristiques de cas de test inclus dans chaque groupe de cas de test, et stocke également des informations de conditions qui comprennent des conditions dynamiques relatives à l'état de chaque environnement de test, et si l'ordinateur de gestion détecte le moment où un premier groupe de cas d'essai doit être implémenté, l'ordinateur de gestion se réfère aux informations de groupe pour identifier les environnements de test candidats pour le premier groupe de cas de test, acquiert des informations d'état indiquant les états des environnements de test candidats, et détermine, parmi les environnements de test candidats, un environnement de test pour implémenter le premier groupe de cas de test, sur la base des informations de condition et des informations d'état.
PCT/JP2016/079330 2016-10-03 2016-10-03 Ordinateur de gestion et procédé de détermination d'environnement de test WO2018066040A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2016/079330 WO2018066040A1 (fr) 2016-10-03 2016-10-03 Ordinateur de gestion et procédé de détermination d'environnement de test
JP2018543496A JP6695437B2 (ja) 2016-10-03 2016-10-03 管理計算機及びテスト環境決定方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2016/079330 WO2018066040A1 (fr) 2016-10-03 2016-10-03 Ordinateur de gestion et procédé de détermination d'environnement de test

Publications (1)

Publication Number Publication Date
WO2018066040A1 true WO2018066040A1 (fr) 2018-04-12

Family

ID=61832054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2016/079330 WO2018066040A1 (fr) 2016-10-03 2016-10-03 Ordinateur de gestion et procédé de détermination d'environnement de test

Country Status (2)

Country Link
JP (1) JP6695437B2 (fr)
WO (1) WO2018066040A1 (fr)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110347584A (zh) * 2019-05-27 2019-10-18 平安银行股份有限公司 信用卡策略包的测试调整方法、装置、电子设备及介质
CN110413528A (zh) * 2019-07-31 2019-11-05 中国工商银行股份有限公司 测试环境智能配置方法及系统
CN110569188A (zh) * 2019-08-14 2019-12-13 平安普惠企业管理有限公司 自动切换测试环境的方法、装置、计算机设备及存储介质
WO2020137566A1 (fr) * 2018-12-27 2020-07-02 日立オートモティブシステムズ株式会社 Dispositif de détermination d'environnement de test et procédé de détermination d'environnement de test
JP2020101994A (ja) * 2018-12-21 2020-07-02 富士通株式会社 決定方法、決定装置及び決定プログラム
CN112711542A (zh) * 2019-05-06 2021-04-27 盛威时代科技集团有限公司 一种用于手机客户端进行测试环境切换的方法
CN113596871A (zh) * 2021-07-05 2021-11-02 哲库科技(上海)有限公司 一种测试方法、服务器及计算机存储介质
CN114637691A (zh) * 2022-05-17 2022-06-17 云账户技术(天津)有限公司 一种测试用例的管理方法及装置
CN116225944A (zh) * 2023-03-09 2023-06-06 矩阵时光数字科技有限公司 一种预置组网环境的软件测试系统和方法
WO2023162272A1 (fr) * 2022-02-28 2023-08-31 日本電気株式会社 Dispositif, système et procédé d'aide au test et support lisible par ordinateur

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070168970A1 (en) * 2005-11-07 2007-07-19 Red Hat, Inc. Method and system for automated distributed software testing
US20120144370A1 (en) * 2010-12-01 2012-06-07 Sap Ag System and method for reversibility categories and characteristics
WO2013073504A1 (fr) * 2011-11-15 2013-05-23 独立行政法人科学技術振興機構 Système de fourniture de service d'analyse/vérification de programmes, procédé de commande associé, programme de commande, programme de commande d'exploitation d'un ordinateur en vue d'actionner un dispositif d'analyse/vérification de programmes, un dispositif de gestion d'outils d'analyse/vérification de programmes

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1069402A (ja) * 1996-08-29 1998-03-10 Nippon Telegr & Teleph Corp <Ntt> ソフトウェアの自動試験制御方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070168970A1 (en) * 2005-11-07 2007-07-19 Red Hat, Inc. Method and system for automated distributed software testing
US20120144370A1 (en) * 2010-12-01 2012-06-07 Sap Ag System and method for reversibility categories and characteristics
WO2013073504A1 (fr) * 2011-11-15 2013-05-23 独立行政法人科学技術振興機構 Système de fourniture de service d'analyse/vérification de programmes, procédé de commande associé, programme de commande, programme de commande d'exploitation d'un ordinateur en vue d'actionner un dispositif d'analyse/vérification de programmes, un dispositif de gestion d'outils d'analyse/vérification de programmes

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020101994A (ja) * 2018-12-21 2020-07-02 富士通株式会社 決定方法、決定装置及び決定プログラム
JP7200659B2 (ja) 2018-12-21 2023-01-10 富士通株式会社 決定方法、決定装置及び決定プログラム
JP7161936B2 (ja) 2018-12-27 2022-10-27 日立Astemo株式会社 テスト環境決定装置及びテスト環境決定方法
WO2020137566A1 (fr) * 2018-12-27 2020-07-02 日立オートモティブシステムズ株式会社 Dispositif de détermination d'environnement de test et procédé de détermination d'environnement de test
JP2020107133A (ja) * 2018-12-27 2020-07-09 日立オートモティブシステムズ株式会社 テスト環境決定装置及びテスト環境決定方法
US11907103B2 (en) 2018-12-27 2024-02-20 Hitachi Astemo, Ltd. Test environment determination device and test environment determination method
CN112711542A (zh) * 2019-05-06 2021-04-27 盛威时代科技集团有限公司 一种用于手机客户端进行测试环境切换的方法
CN112711542B (zh) * 2019-05-06 2023-12-01 盛威时代科技集团有限公司 一种用于手机客户端进行测试环境切换的方法
CN110347584A (zh) * 2019-05-27 2019-10-18 平安银行股份有限公司 信用卡策略包的测试调整方法、装置、电子设备及介质
CN110347584B (zh) * 2019-05-27 2023-11-07 平安银行股份有限公司 信用卡策略包的测试调整方法、装置、电子设备及介质
CN110413528A (zh) * 2019-07-31 2019-11-05 中国工商银行股份有限公司 测试环境智能配置方法及系统
CN110413528B (zh) * 2019-07-31 2023-12-22 中国工商银行股份有限公司 测试环境智能配置方法及系统
CN110569188A (zh) * 2019-08-14 2019-12-13 平安普惠企业管理有限公司 自动切换测试环境的方法、装置、计算机设备及存储介质
CN113596871A (zh) * 2021-07-05 2021-11-02 哲库科技(上海)有限公司 一种测试方法、服务器及计算机存储介质
WO2023162272A1 (fr) * 2022-02-28 2023-08-31 日本電気株式会社 Dispositif, système et procédé d'aide au test et support lisible par ordinateur
CN114637691A (zh) * 2022-05-17 2022-06-17 云账户技术(天津)有限公司 一种测试用例的管理方法及装置
CN116225944A (zh) * 2023-03-09 2023-06-06 矩阵时光数字科技有限公司 一种预置组网环境的软件测试系统和方法
CN116225944B (zh) * 2023-03-09 2024-05-07 矩阵时光数字科技有限公司 一种预置组网环境的软件测试系统和方法

Also Published As

Publication number Publication date
JP6695437B2 (ja) 2020-05-20
JPWO2018066040A1 (ja) 2019-07-11

Similar Documents

Publication Publication Date Title
JP6695437B2 (ja) 管理計算機及びテスト環境決定方法
US10922654B2 (en) Software assurance and trust in a distributed delivery environment
US8386636B2 (en) Business process system management method
US10048955B2 (en) Accelerating software builds
US9584442B2 (en) Managing a set of assets of a shared pool of configurable computing resources
US20160154673A1 (en) Methods, systems, and computer program products for providing a minimally complete operating environment
CN102236578A (zh) 分布式工作流执行
US9898258B2 (en) Versioning of build environment information
JP2022036800A (ja) Ａｐｉ選定システム及びａｐｉ選定方法
US9785464B2 (en) Intellective switching between tasks
US10248554B2 (en) Embedding profile tests into profile driven feedback generated binaries
CN114174983B (zh) 用于高级构造的优化的自动验证的方法和系统
Danciu et al. Performance awareness in Java EE development environments
Procaccianti Energy-efficient software
JP2018055249A (ja) システム構築支援装置、システム構築支援方法、および、システム構築支援プログラム
JP4997144B2 (ja) マルチタスク処理装置およびその方法
Cecowski et al. Cloud computing applications
Danciu et al. Towards Performance Awareness in Java EE Development Environments.
US11681934B2 (en) System and method for differential testing of evolving rules
US10970073B2 (en) Branch optimization during loading
US20150365302A1 (en) Dynamic collaboration service platform and method for providing an application service at the same platform
JP2024005179A (ja) インフラ要件テンプレート管理装置、インフラ要件テンプレート管理システム及びインフラ要件テンプレート管理方法
Manasa An Approach for Processing Data Clusters Using Cloning Scheme
JPWO2011114478A1 (ja) 生成方法、スケジューリング方法、生成プログラム、スケジューリングプログラム、生成装置、および情報処理装置
JP2020009271A (ja) 検証情報生成装置、検証情報生成方法、及び検証情報生成プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16918241

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018543496

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16918241

Country of ref document: EP

Kind code of ref document: A1