Test resource dynamic management system, method and storage medium

Abstract

The present invention relates to a test resource dynamic management system, method and storage medium. The method comprises: obtaining a test task and parsing the test task; obtaining the closedness attribute of each test case; obtaining the dependency relationship of the test case relative to the test resource; executing the test environment required for the test case in the test tool; when applying for the test resources required for the test from the test system in the order of the test case execution, judging whether the required test resources exist in the resource pool, directly allocating them to the test case for use if yes, and requesting the system to allocate new test resources if no; executing the test case using the test tool; and judging whether the test resource is reused in the subsequent test case according to the dependency relationship between the test case and the test resource after the test case is executed, and if yes, reclaiming the test resource, and if not, putting the test resource back into the resource pool.

Description

Technical Field

[0001] The present invention generally relates to the field of testing, and more specifically to a system, method and storage medium for dynamically managing test resources. Background Art

[0002] In the process of automated testing, resources need to be frequently applied for and recovered, and improper resource management can easily lead to resource leakage. How to effectively manage resources to improve the efficiency and security of test automation is an important issue.

[0003] In the existing test process, the test case first applies for test resources, executes the test task, reclaims the test resources, and finally returns the test results. This test case is called a closed test case. A closed test case can be regarded as atomic execution. After the test task is completed, the test resources applied by this case are reclaimed, which will not cause leakage of test resources. However, there is a problem with this test case, which requires frequent application and destruction of resources. Frequent execution of resource application and destruction operations will significantly increase the pressure on the system under test and reduce test efficiency. Summary of the invention

[0004] The present invention is completed to solve such problems. In the present invention, a resource monitoring management module and a resource pool mechanism are proposed, which can realize dynamic management of test resources, improve test efficiency and the flexibility and security of resource management. In particular, in a test path composed of multiple test cases, resources are allowed to be reused between test cases, which can avoid frequent application of test resources. In addition, this mechanism enables test cases to have the capabilities of closed testing and non-closed testing at the same time, simplifying the development of test cases.

[0005] A brief overview of the invention is given below in order to provide a basic understanding of some aspects of the invention. However, it should be understood that this overview is not an exhaustive overview of the invention. It is not intended to identify the key or important parts of the invention, nor is it intended to limit the scope of the invention. Its purpose is merely to give some concepts of the invention in a simplified form as a prelude to a more detailed description that will be given later.

[0006] According to one aspect of the present invention, a method for dynamic management of test resources is provided, comprising the following steps: (A) obtaining a test task and parsing the test task, wherein the test task includes more than one test case; (B) obtaining the closedness attribute of each test case; (C) parsing the dependency relationship between all test cases of the test task and required test resources, and obtaining the dependency relationship between the test case and the test resource; (D) executing the test environment required for the test case in the test tool; (E) when applying for the test resources required for the test from the test system in the order of test case execution, determining whether the required test resources exist in the resource pool, directly allocating the required test resources to the test case if the required test resources already exist, and requesting the system to allocate new test resources if the required test resources do not exist; (F) executing the test case using the test tool; and (G) after the test case is executed, determining whether the test resource is reused in a subsequent test case based on the dependency relationship between the test case and the test resource, recycling the test resource if it is no longer reused, and returning the test resource to the resource pool if it is reused by a subsequent test case.

[0007] According to another aspect of the present invention, a test resource dynamic management system is provided, comprising: a test task conversion module, which obtains a test task and parses the test task to obtain one or more test cases, and obtains the closed properties of the one or more test cases; a test task execution module, which initializes the test environment when testing the test case, applies for the required test resources, and executes the test on the test case; a resource pool module, which stores the test resources occupied by the test task and the status of the test resources; a resource monitoring and management module, which parses the test task to obtain a static dependency relationship between the test case and the test resource, wherein the dependency relationship represents the dependency relationship between the test case and the test resource, and is generated by When the test task execution module applies for the required test resources, it determines whether the required test resources exist in the resource pool module. If the required test resources already exist, they are directly allocated to the test case for use. If the required test resources do not exist, the resource pool module is ordered to allocate new test resources. After the test case is executed, it is determined whether the current test resources will be reused in subsequent test cases based on the dependency relationship between the test case and the test resources. If the test resources are not reused, the test resources are recycled. If the test resources are reused by subsequent test cases, the test resources are returned to the resource pool module; and a resource recycling module is received by the resource monitoring and management module to execute the recycling of test resources.

[0008] According to one aspect of the present invention, a test resource dynamic management device is provided, comprising: a memory storing instructions; and a processor configured to execute the instructions stored in the memory to perform the method according to the above aspect of the present invention.

[0009] According to another aspect of the present invention, a computer-readable storage medium is provided, which includes computer-executable instructions. When the computer-executable instructions are executed by one or more processors, the one or more processors execute the method according to the above aspect of the present invention.

[0010] According to the present invention, dynamic management of test resources can be achieved, and the efficiency of testing and the flexibility and security of resource management can be improved. In particular, in a test path composed of multiple test cases, resources can be reused between test cases, which can avoid frequent application of test resources. In addition, this mechanism enables test cases to have the capabilities of closed testing and non-closed testing at the same time, simplifying the development of test cases. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which constitute a part of the specification, illustrate embodiments of the present invention and, together with the description, serve to explain the principles of the present invention.

[0012] The present invention may be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

[0013] Figure 1 It is a schematic flow chart showing a method for dynamic management of test resources according to an embodiment of the present invention.

[0014] Figure 2 is a schematic flow chart showing a method for dynamic management of test resources according to another embodiment of the present invention.

[0015] Figure 3 A schematic functional block diagram of a test resource dynamic management system according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0016] The following detailed description is made with reference to the accompanying drawings, and the following detailed description is provided to assist in a comprehensive understanding of various exemplary embodiments of the present invention. The following description includes various details to assist in understanding, but these details are considered to be examples only and are not intended to limit the present invention, which is defined by the appended claims and their equivalents. The words and phrases used in the following description are only used to enable a clear and consistent understanding of the present invention. In addition, for the sake of clarity and brevity, descriptions of well-known structures, functions, and configurations may be omitted. Those of ordinary skill in the art will recognize that various changes and modifications may be made to the examples described herein without departing from the spirit and scope of the present invention.

[0017] Figure 1 It is a schematic flow chart showing a method for dynamic management of test resources according to an embodiment of the present invention.

[0018] like Figure 1 As shown, in step S101, a test task is obtained and parsed, wherein the test task includes one or more test cases. The test case includes one or more of a test target, a test environment, input data, a test step, an expected result, a test script, and the like.

[0019] Next, in step S103, the closed attribute of each test case is obtained. Here, the closed attribute refers to the test resources that need to be applied for when each test case is executed separately and are recovered after the test is completed.

[0020] Next, in step S105 , the dependency relationship between all test cases in the test task and the required test resources is parsed to obtain the dependency relationship between the test cases and the test resources.

[0021] Next, in step S107, the test environment required for the test case execution initialization is executed in the test tool. Here, the test tool is not particularly limited and can be selected according to actual needs (eg, test object).

[0022] Next, in step S109, when applying for the required resources for the test from the test system in the order of test case execution, it is determined whether the required test resources exist in the resource pool. If the required test resources already exist (that is, step S109 determines as "yes"), in step S111, the existing required test resources are directly allocated to the test case for use. If the required test resources do not exist (that is, step S109 determines as "no"), the system is requested to allocate test resources in step S113.

[0023] Next, in step S115 , the test case is executed using the aforementioned test tool.

[0024] Then, in step S117, after the test case is executed, it is determined whether the test resource is reused in subsequent test cases based on the dependency relationship between the test case and the test resource. If the test resource is no longer reused (that is, step S117 is judged as "no"), the test resource is recycled in step S119; if the test resource is reused by subsequent test cases (that is, step S117 is judged as "yes"), the test resource is put back into the resource pool in step S121.

[0025] According to the present invention, the test case can not only be executed as a closed test case alone, but through the resource monitoring management and resource pool mechanism, each test case can also be used as a non-closed test case to pass the applied test resources to the subsequent test cases for reuse, without having to apply repeatedly in the subsequent test cases, and the subsequent test cases can also delete the resources passed by the predecessor node at an appropriate time. In this way, frequent application and deletion of resources can be avoided, and no longer needed resources can be returned to the tested system in a timely manner, avoiding waste of resources.

[0026] In addition, according to the resource dynamic monitoring and recovery mechanism of the method of the present invention, the resources required during the execution of the test case are monitored throughout the process, and the resources that are no longer needed can be recovered in time, and the resources that are still in use can be recovered with a delayed recovery, which can improve the utilization efficiency of resources and avoid resource leakage.

[0027] In one embodiment, after all test cases in the test task are executed, the resource pool module is cleared and all test resources are returned to the test system.

[0028] In one embodiment, it also includes the step of determining whether all test cases in the test task have been executed. If all test cases in the test task are completed, the test task ends and the test results are obtained. If all test cases in the test task are not completed, steps S109 to S121 are repeated.

[0029] In a preferred embodiment, the system under test is a cloud network system. After years of development, cloud computing technology and ecology have become increasingly mature, and have continued to penetrate into various key industries, including the telecommunications industry. In order to meet the rapidly growing needs of network services, the process of cloudification of network functions with the help of cloud technology is constantly advancing. At the same time, due to the complexity of cloud network systems, testing and verification technologies for cloud network systems are also constantly developing, and the demand for automation of cloud network system testing is becoming increasingly prominent. In the process of automated testing of cloud network systems, frequent resource application and recovery operations are required, and improper resource management can easily lead to resource leakage problems. According to the present invention, resources can be effectively managed to improve the efficiency and security of test automation.

[0030] In one embodiment, the step of obtaining a test task from an orchestration engine may also be included. The orchestration engine orchestrates one or more test cases selected from a predefined test case set into a test task according to a test process based on user needs.

[0031] The method according to the present invention has good compatibility and can be compatible with different orchestration engine frameworks and different testing tools.

[0032] Figure 2is a schematic flow chart showing a method for dynamic management of test resources according to another embodiment of the present invention.

[0033] exist Figure 2 In the embodiment, after the step of preparing the test environment, a step of determining whether the test task has a next test case is performed.

[0034] like Figure 2 As shown, in step S201, a test task is obtained from an orchestration engine, wherein the orchestration engine orchestrates one or more test cases selected from a predefined test case set into a test task according to a test process based on user needs.

[0035] Then, in step S202, the test cases are transformed and the closed attributes of the test cases are configured, wherein the closed attributes refer to the test resources that need to be applied for when each test case is executed separately and are recycled after the test is completed.

[0036] Following step S202, in step S203, the dependency relationship between the test case and the test resource is parsed to obtain a use case resource dependency graph representing the dependency relationship.

[0037] Next, in step S204, a test environment is prepared to execute the test case in the test tool to initialize the required test environment. Here, the test tool is not particularly limited and can be selected according to actual needs (eg, test object).

[0038] Next, in step S205, it is determined whether there is a next test case that has not been tested in the test task. If there is no next test case that has not been tested (i.e., the judgment of step S205 is "no"), it is considered that all test cases included in the test task have been tested. At this time, the resource pool is cleared in step S207, the test task is completed, and the process ends. If there is a next test case that has not been tested (i.e., the judgment of step S205 is "yes"), proceed to step S206.

[0039] In step S206, the test resources required for the test are applied for, and it is determined whether the required test resources exist in the resource pool. If the required test resources already exist (i.e., step S208 determines "yes"), the required test resources are directly allocated to the test case for use. If the required test resources do not exist (i.e., step S208 determines "no"), the system is requested to allocate new test resources. Regardless of whether existing test resources or new test resources are allocated, the test resources are used to execute the test case in step S209.

[0040] Then, after the test case is executed, in step S212, based on the dependency graph of the test case and the test resource, and based on whether the test resource will be reused in subsequent use cases, it is determined whether the test resource needs to be recycled. If the current test resource is no longer reused and needs to be recycled (that is, step S212 is judged as "yes"), the test resource is recycled; if the test resource will be reused by subsequent use cases and does not need to be recycled (that is, step S212 is judged as "no"), it is put back into the resource pool to wait for use by subsequent test cases.

[0041] Next, in step S215, the test result is obtained, and the process returns to step S205. After all the test cases in the test task are executed, the resource pool is cleared and all the test resources are returned to the system.

[0042] According to the present invention, the test case can not only be executed as a closed test case alone, but through the resource monitoring management and resource pool mechanism, each test case can also be used as a non-closed test case to pass the applied test resources to the subsequent test cases for reuse, without having to apply repeatedly in the subsequent test cases, and the subsequent test cases can also delete the resources passed by the predecessor node at an appropriate time. In this way, frequent application and deletion of resources can be avoided, and no longer needed resources can be returned to the tested system in a timely manner, avoiding waste of resources.

[0043] Figure 3 A schematic functional block diagram of a test resource dynamic management system according to an embodiment of the present invention is shown.

[0044] like Figure 3 As shown, the test resource dynamic management system 3 includes a test task conversion module 31 , a test task execution module 32 , a resource pool module 33 , a resource monitoring and management module 34 and a resource recovery module 35 .

[0045] The test task conversion module 31 obtains the test task and parses the test task to obtain one or more test cases, and obtains the closed attributes of the one or more test cases. The test case includes one or more of the test objectives, test environment, input data, test steps, expected results, test scripts, etc. The closed attribute refers to the test resources that need to be applied for when each test case is executed separately and recovered after the test is completed.

[0046] When testing a test case, the test task execution module 32 initializes the test environment, applies for required test resources from the system, and executes the test on the test case.

[0047] The resource pool module 33 stores the test resources occupied by the test tasks and the states of the test resources.

[0048] The resource monitoring and management module 34 parses the test task to obtain the static dependency relationship between the test case and the test resource. The dependency relationship represents the dependency relationship between the test case and the test resource. When the test task execution module 32 applies for the required resource, it determines whether the required resource exists in the resource pool module 33. If the required resource already exists, the existing required test is directly allocated to the test case for use. If the required resource does not exist, the resource pool module is commanded to allocate new test resources. After the test case is executed, it determines whether the current test resource is reused in subsequent test cases based on the dependency relationship between the test case and the test resource. If the test resource is not reused, the test resource is recycled. If the test resource is reused by subsequent test cases, the test resource is returned to the resource pool module.

[0049] The resource recovery module 35 receives the call from the resource monitoring and management module 34 and executes the recovery of test resources.

[0050] The predefined test case set module 1 stores a predefined test case set for testing. The predefined test case set is provided to the orchestration engine module 2. The orchestration engine module 2 orchestrates one or more test cases selected from the predefined test case set into a test task according to the test process according to user needs. In one embodiment, the predefined test case set module 1 and the orchestration engine module 2 can be connected to the test resource dynamic management system 3. In another embodiment, the predefined test case set module 1 and the orchestration engine module 2 can also be included as part of the test resource dynamic management system 3.

[0051] The test tool module 4 is used to test the system under test 5. There is no particular limitation on the test tool, and it can be selected according to actual needs (such as the test object). The test tool in the test tool module 4 can be one or more. In one embodiment, the test tool module 4 can be connected to the test resource dynamic management system 3. In another embodiment, the test tool module 4 can also be included as a part of the test resource dynamic management system 3.

[0052] According to the present invention, the test case can not only be executed as a closed test case alone, but through the resource monitoring management and resource pool mechanism, each test case can also be used as a non-closed test case to pass the applied test resources to the subsequent test cases for reuse, without having to apply repeatedly in the subsequent test cases, and the subsequent test cases can also delete the resources passed by the predecessor node at an appropriate time. In this way, frequent application and deletion of resources can be avoided, and no longer needed resources can be returned to the tested system in a timely manner, avoiding waste of resources.

[0053] In addition, according to the resource dynamic monitoring and recovery mechanism of the method of the present invention, the resources required during the execution of the test case are monitored throughout the process, and the resources that are no longer needed can be recovered in time, and the resources that are still in use can be recovered with a delayed recovery, which can improve the utilization efficiency of resources and avoid resource leakage.

[0054] The method according to the present invention has good compatibility and can be compatible with different orchestration engine frameworks and different testing tools.

[0055] In one embodiment, when a test task ends abnormally or normally, the resource recovery module will perform a resource check and recover all resources in the resource pool.

[0056] In one embodiment, the system under test 5 is a cloud network system.

[0057] The following is a typical application example according to the present invention. The test resource dynamic management system 3 needs to test whether the functions of (1) creating and deleting virtual machines, (2) creating and deleting disks, and (3) mounting and unmounting disks of the system under test 5 are normal enough. The tests of the above three functions (1) to (3) can be used as a closed test case respectively, but mounting and unmounting disks are often based on the creation of virtual machines and disks. According to the present invention, the resources applied for by the first two test cases are reserved for the test cases for mounting and unmounting disks, thereby avoiding the need to apply for resources again, and deleting the test resources after verifying the mounting and unmounting of the disk. Based on the above concept, the three test cases can be designed to have the functions of both closed test cases and non-closed test cases. Each test case is run as a closed test case when used alone. If the three test cases are used in combination, the resource monitoring management module 34 uses the test case resource dependency relationship to find that the next third test case depends on the test resources created by the first two test cases, thereby putting the test resources created by the first two test cases into the resource pool to realize the reuse of test resources. When the third test case is executed, the required virtual machine and disk resources are obtained directly from the resource pool. Then, it is only necessary to verify whether the mounting and unmounting functions are normal, without applying for virtual machine and disk resources from the system. Finally, after the test task is completed, the resource recycling module is used to clear the resource pool and recycle virtual machine and disk resources.

[0058] According to the present invention, the test case can not only be executed as a closed test case alone, but through the resource monitoring management and resource pool mechanism, each test case can also be used as a non-closed test case to pass the applied test resources to the subsequent test cases for reuse, without having to apply repeatedly in the subsequent test cases, and the subsequent test cases can also delete the resources passed by the predecessor node at an appropriate time. In this way, frequent application and deletion of resources can be avoided, and no longer needed resources can be returned to the tested system in a timely manner, avoiding waste of resources.

[0059] In addition, according to the resource dynamic monitoring and recovery mechanism of the method of the present invention, the resources required during the execution of the test case are monitored throughout the process, and the resources that are no longer needed can be recovered in time, and the resources that are still in use can be recovered with a delayed recovery, which can improve the utilization efficiency of resources and avoid resource leakage.

[0060] The present invention may be implemented as any combination of a device, a system, an integrated circuit, and a computer program on a non-transitory computer-readable medium. One or more processors may be implemented as an integrated circuit (IC), an application specific integrated circuit (ASIC), or a large scale integrated circuit (LSI), a system LSI, a super LSI, or a super LSI component that performs some or all of the functions described in the present invention.

[0061] The present invention includes the use of software, applications, computer programs or algorithms. The software, applications, computer programs or algorithms may be stored on a non-transitory computer-readable medium to enable a computer such as one or more processors to perform the above steps and the steps described in the accompanying drawings. For example, one or more memories store the software or algorithms in executable instructions, and one or more processors may associate a set of instructions to execute the software or algorithm to provide various functions according to the embodiments described in the present invention.

[0062] Software and computer programs (which may also be referred to as programs, software applications, applications, components or code) include machine instructions for a programmable processor and may be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logic programming language, or an assembly language or a machine language. The term "computer-readable medium" refers to any computer program product, apparatus or device for providing machine instructions or data to a programmable data processor, such as magnetic disks, optical disks, solid-state storage devices, memories and programmable logic devices (PLDs), including computer-readable media that receive machine instructions as computer-readable signals.

[0063] For example, computer readable media may include dynamic random access memory (DRAM), random access memory (RAM), read-only memory (ROM), electrically erasable read-only memory (EEPROM), compact disk read-only memory (CD-ROM) or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to carry or store the desired computer readable program code in the form of instructions or data structures and can be accessed by a general or special purpose computer or a general or special purpose processor. As used herein, disk or disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically by laser. Combinations of the above are also included in the scope of computer readable media.

[0064] The subject matter of the present invention is provided as an example of an apparatus, system, method and program for performing the features described in the present invention. However, in addition to the above-mentioned features, other features or variations may also be expected. It is expected that the implementation of the components and functions of the present invention may be accomplished with any emerging technology that may replace any of the above-mentioned implementation technologies.

[0065] In addition, the above description provides examples without limiting the scope, applicability or configuration set forth in the claims. Without departing from the spirit and scope of the present invention, the functions and arrangements of the elements discussed may be changed. Various embodiments may appropriately omit, replace or add various processes or components. For example, features described with respect to certain embodiments may be combined in other embodiments.

[0066] In addition, in the description of the present invention, the terms “first”, “second”, “third”, etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance and order.

[0067] Similarly, while operations are depicted in a particular order in the drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve desired results. In certain circumstances, multitasking and parallel processing can be advantageous.

Claims

1. A method for dynamic management of test resources, comprising the following steps: (A) obtaining a test task and parsing the test task, wherein the test task includes more than one test case; (B) obtaining the closedness attribute of each test case, wherein the closedness attribute is the test resources that need to be applied for when each test case is executed separately and are recovered after the test is completed; (C) parsing the dependency relationship between all test cases of the test task and the required test resources, and obtaining the dependency relationship between the test cases and the test resources; (D) Initializing the test environment required for test case execution in the test tool; (E) When applying for the test resources required by the test from the test system in the order in which the test cases are executed, determine whether the required test resources exist in the resource pool. If the required test resources already exist, directly allocate the required test resources to the test case for use. If the required test resources do not exist, request the system to allocate new test resources. (F) executing the test case using the test tool; as well as (G) After the test case is executed, determine whether the test resource will be reused in subsequent test cases based on the dependency relationship between the test case and the test resource. If the test resource is no longer reused, recycle the test resource. If the test resource is reused by subsequent test cases, put the test resource back into the resource pool.

2. The method for dynamic management of test resources according to claim 1, wherein: After all the test cases in the test task are executed, the resource pool is cleared and all the test resources are returned to the test system.

3. The test resource dynamic management method according to claim 1, further comprising: (H) Repeat steps (E) to (G) until all test cases are executed.

4. The method for dynamic management of test resources according to claim 1, wherein: The system under test is a cloud network system.

5. A test resource dynamic management system, comprising: A test task conversion module, which obtains a test task and parses the test task to obtain one or more test cases, and obtains the closed attributes of the one or more test cases, wherein the closed attributes are test resources that need to be applied for when each test case is executed separately and are recovered after the test is completed; The test task execution module initializes the test environment, applies for the required test resources, and executes the test case when testing the test case; Resource pool module, which stores the test resources occupied by the test tasks and the status of the test resources; A resource monitoring and management module, which parses the test task to obtain a static dependency relationship between the test case and the test resource, wherein the dependency relationship represents the dependency relationship between the test case and the test resource, and determines whether the required test resource exists in the resource pool module when the required test resource is applied for by the test task execution module, and directly allocates the required test resource to the test case for use if the required test resource already exists, and commands the resource pool module to allocate new test resources if the required test resource does not exist, and determines whether the current test resource is reused in subsequent test cases based on the dependency relationship between the test case and the test resource after the test case is executed, and recycles the test resource if it is not reused, and puts the test resource back into the resource pool module if it is reused by subsequent test cases; as well as The resource recovery module accepts the call of the resource monitoring and management module and executes the recovery of test resources.

6. The test resource dynamic management system according to claim 5, wherein: When the test task ends abnormally or normally, the resource recovery module will perform resource checks and recycle all resources in the resource pool.

7. The test resource dynamic management system according to claim 5 further comprises an orchestration engine module, which orchestrates one or more test cases selected from a predefined test case set into a test task according to a test process based on user needs.

8. The test resource dynamic management system according to claim 5, wherein: The system under test is a cloud network system.

9. A test resource dynamic management system, comprising: a memory having instructions stored therein; as well as A processor configured to execute instructions stored on the memory to perform the method according to any one of claims 1 to 4.

10. A computer-readable storage medium comprising computer-executable instructions, which, when executed by one or more processors, cause the one or more processors to perform the method according to any one of claims 1 to 4.

Images