CN113342698A

CN113342698A - Test environment scheduling method, computing device and storage medium

Info

Publication number: CN113342698A
Application number: CN202110825016.6A
Authority: CN
Inventors: 李艳峰; 张喜丹; 王潇柔
Original assignee: Uniontech Software Technology Co Ltd
Current assignee: Uniontech Software Technology Co Ltd
Priority date: 2021-07-21
Filing date: 2021-07-21
Publication date: 2021-09-03

Abstract

The invention discloses a test environment scheduling method, a computing device and a storage medium, wherein the test environment scheduling method is executed in the computing device, the computing device is configured with a plurality of processors, any processor is used for constructing a test node, and the method comprises the following steps: constructing a corresponding test set according to the test case data, wherein the test set comprises a plurality of test nodes; determining the test environment type of a case to be tested; judging whether the test nodes in the test set meet preset conditions or not based on the test environment type; and if so, applying for at least one test node from the test set to execute the case to be tested.

Description

Test environment scheduling method, computing device and storage medium

Technical Field

The invention relates to the field of internet, in particular to a test environment scheduling method, computing equipment and a storage medium.

Background

In the process of automated test execution, it is common practice to directly create a corresponding test environment group according to an environment type specified in a test case. However, in complex and various testing environment type tasks, the method has poor fault tolerance and is easy to cause the problem of case execution blocking. The type of each test node is cured in advance, so the environment reuse rate is low.

Disclosure of Invention

In view of the above, the present invention has been made to provide a test environment scheduling method, a computing device and a storage medium that overcome or at least partially solve the above-mentioned problems.

According to an aspect of the present invention, there is provided a test environment scheduling method, executed in a computing device configured with a plurality of processors, wherein any processor is configured to construct a test node, the method comprising: constructing a corresponding test set according to the test case data, wherein the test set comprises a plurality of test nodes; determining the test environment type of a case to be tested; judging whether the test nodes in the test set meet preset conditions or not based on the test environment type; and if so, applying for at least one test node from the test set to execute the case to be tested.

Optionally, in the method according to the present invention, the step of determining the test environment type of the use case to be tested includes: determining the testing environment type of the to-be-tested case by identifying the keywords of the to-be-tested case, wherein the testing environment type comprises a single-node environment type and a multi-node environment type; and determining the number of test nodes which need to be applied to the test set by the case to be tested according to the determined test environment type.

Optionally, in the method according to the present invention, the step of determining whether each test node in the test set satisfies a preset condition based on the test environment type includes: and acquiring the states of all the test nodes in the test set, wherein the states of the test nodes comprise idle states, occupied states and abnormal states.

Optionally, in the method according to the present invention, the preset condition includes determining whether the number of test nodes in the test set that are idle meets the number of test nodes required by the case to be tested.

Optionally, in the method according to the present invention, after the step of determining whether each test node in the test set satisfies a preset condition based on the environment type, the method further includes: if not, the step of determining the type of the test environment is executed again, and whether each test node in the test set meets the preset condition is judged again.

Optionally, in the method according to the present invention, if the test case is satisfied, the step of calling the corresponding test node to execute the test case to be tested further includes: calling the test nodes to execute the cases to be tested, and adjusting the states of the corresponding test nodes to be occupied; and after the execution of the case to be tested is finished, adjusting the state of the corresponding test node to be idle.

Optionally, in the method according to the present invention, constructing a corresponding test set according to each test case data, where the test set includes a plurality of test nodes includes: and constructing the test set based on the number of the test cases and the number of the required test nodes.

Optionally, in the method according to the present invention, constructing a corresponding test set according to each test case data, where the step of the test set including a plurality of test nodes further includes: and creating test nodes according to a multi-process mode, and creating a corresponding record table to record the state information of each test node.

According to yet another aspect of the invention, there is provided a computing device comprising: at least one processor; and a memory storing program instructions, wherein the program instructions are configured to be executed by the at least one processor, the program instructions comprising instructions for performing the above-described method.

According to yet another aspect of the present invention, there is provided a readable storage medium storing program instructions which, when read and executed by a computing device, cause the computing device to perform the above-described method.

According to the scheme of the invention, the test set is constructed in advance, and then the test nodes are applied from the constructed test set according to the requirements of the test cases, so that on one hand, the problem that batch cases cannot be continuously executed due to abnormal test environments of specific types is solved. On the other hand, the problem of low test environment reuse rate is solved.

The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.

Drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:

FIG. 1 shows a schematic diagram of a computing device 100, according to one embodiment of the invention;

FIG. 2 illustrates a flow diagram of a test environment scheduling method 200 according to one embodiment of the invention;

FIG. 3 shows a flow diagram of a testing method 300 according to one embodiment of the invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The following explains the terms involved in the present invention:

the test case is used for describing a test task of a specific software product and embodying a test scheme, a method, a technology and a strategy. Briefly, a test case is a set of test inputs, execution conditions, and expected results tailored for a particular purpose to verify that a particular software requirement is met.

Test environment refers to the description of the software and hardware environment on which the test runs, as well as any other software that interacts with the software under test, including drivers and stubs. The stable and controllable test environment can ensure that the test personnel can finish the execution of the test case with less time, and extra time does not need to be spent for the maintenance of the test case and the test process, and each submitted defect can be accurately reproduced at any time.

The test node refers to an execution environment of a test case.

The test set refers to a plurality of test node sets.

The state of the test node refers to the real-time state of the test node. There are a total of 4 states, idle, available, abnormal and occupied respectively.

The test environment type refers to a test environment type required for executing the test case. As single node environment types: the running of the test case needs a test node environment; dual node test environment type: the test case operation needs two test node environments, one of which is a local end environment and the other is an opposite end environment.

In the existing test environment scheduling method, generally, the test environment is classified to run according to the environment types (single node or multiple nodes) required by the test cases, for example, in multiple test cases, a single-node test case, a double-node test case and a three-node test case exist respectively, three sets of corresponding test environments are created to execute test tasks, after the execution of one type of test case is completed, the corresponding test node is in an idle state until all test cases run, which results in low test node reuse rate, and in addition, the single-node/two-node/three-node test cases relate to the problem that the scene cannot run in a cross mode and cannot be found more.

In addition, in the above test environment scheduling method, as long as there is a test node creation failure or abnormality, the test case execution will be blocked, and the test case operation reliability is low. Moreover, after the execution of the current test case is completed, all test nodes created for executing the test case are destroyed, and the test nodes cannot be reused.

In order to solve the problems in the prior art, the invention provides a scheme. One embodiment of the present invention provides a test environment scheduling method that may be performed in a computing device. FIG. 1 shows a block diagram of a computing device 100, according to one embodiment of the invention. As shown in FIG. 1, in a basic configuration 102, a computing device 100 typically includes a system memory 106 and one or more processors 104. A memory bus 108 may be used for communication between the processor 104 and the system memory 106.

Depending on the desired configuration, the processor 104 may be any type of processing, including but not limited to: a microprocessor (μ P), a microcontroller (μ C), a Digital Signal Processor (DSP), or any combination thereof. The processor 104 may include one or more levels of cache, such as a level one cache 110 and a level two cache 112, a processor core 114, and registers 116. The example processor core 114 may include an Arithmetic Logic Unit (ALU), a Floating Point Unit (FPU), a digital signal processing core (DSP core), or any combination thereof. The example memory controller 118 may be used with the processor 104, or in some implementations the memory controller 118 may be an internal part of the processor 104.

Depending on the desired configuration, system memory 106 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The physical memory in the computing device is usually referred to as a volatile memory RAM, and data in the disk needs to be loaded into the physical memory to be read by the processor 104. System memory 106 may include an operating system 120, one or more applications 122, and program data 124. The application 122 is actually a plurality of program instructions that direct the processor 104 to perform corresponding operations. In some embodiments, the application 122 may be arranged to execute instructions on an operating system with the program data 124 by the one or more processors 104 in some embodiments. Operating system 120 may be, for example, Linux, Windows, etc., which includes program instructions for handling basic system services and performing hardware dependent tasks. The application 122 includes program instructions for implementing various user-desired functions, and the application 122 may be, for example, but not limited to, a browser, instant messenger, a software development tool (e.g., an integrated development environment IDE, a compiler, etc.), and the like. When the application 122 is installed into the computing device 100, a driver module may be added to the operating system 120.

When the computing device 100 is started, the processor 104 reads program instructions of the operating system 120 from the memory 106 and executes them. The application 122 runs on top of the operating system 120, utilizing the operating system 120 and interfaces provided by the underlying hardware to implement various user-desired functions. When the user starts the application 122, the application 122 is loaded into the memory 106, and the processor 104 reads the program instructions of the application 122 from the memory 106 and executes the program instructions.

The computing device 100 also includes a storage device 132, the storage device 132 including removable storage 136 and non-removable storage 138, the removable storage 136 and the non-removable storage 138 each connected to the storage interface bus 134.

Computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (e.g., output devices 142, peripheral interfaces 144, and communication devices 146) to the basic configuration 102 via the bus/interface controller 130. The example output device 142 includes a graphics processing unit 148 and an audio processing unit 150. They may be configured to facilitate communication with various external devices, such as a display or speakers, via one or more a/V ports 152. Example peripheral interfaces 144 may include a serial interface controller 154 and a parallel interface controller 156, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 158. An example communication device 146 may include a network controller 160, which may be arranged to facilitate communications with one or more other computing devices 162 over a network communication link via one or more communication ports 164.

A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media, such as carrier waves or other transport mechanisms, in a modulated data signal. A "modulated data signal" may be a signal that has one or more of its data set or its changes made in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or private-wired network, and various wireless media such as acoustic, Radio Frequency (RF), microwave, Infrared (IR), or other wireless media. The term computer readable media as used herein may include both storage media and communication media.

The computing device 100 also includes a storage interface bus 134 coupled to the bus/interface controller 130. The storage interface bus 134 is coupled to the storage device 132, and the storage device 132 is adapted to store data. An example storage device 132 may include removable storage 136 (e.g., CD, DVD, usb disk, removable hard disk, etc.) and non-removable storage 138 (e.g., hard disk drive HDD, etc.).

In the computing device 100 according to the invention, the application 122 comprises a plurality of program instructions that perform the method 200.

FIG. 2 shows a flow diagram of a test environment scheduling method 200 according to one embodiment of the invention. Method 200 is suitable for execution in a computing device (e.g., computing device 100 described above) having a plurality of processors configured therein, wherein any of the processors is used to construct a test node.

As shown in fig. 2, the method 200 is to implement a method for scheduling a test environment, starting at step S202, and in step S202, a corresponding test set is constructed according to each test case data, where the test set includes a plurality of test nodes. It should be noted that the test environment scheduling method provided by this embodiment is applicable to a single test case scenario and a multiple test case scenario.

The test case data mainly comprises the number of the test cases and the environment type of each test case. The number of the test cases can be directly obtained, and the environment type of each test case can determine the test environment type of each test case to be tested by identifying the keywords of each test case. The test environment type includes a single node environment type and a multi-node environment type. The test case can mark the test environment type needed by executing the test case when being generated, namely, any test case contains the keywords of the test environment type needed by executing the test case, and the keywords are embedded in the test case in a binary mode (a language which can be recognized by computing equipment). The testing environment type required by the testing case can be obtained by identifying the keyword.

As described above, the environment type of a test case refers to the number of test nodes required to execute the test case, and thus, in some embodiments, a test set may be constructed based on the number of test cases and the number of required test nodes.

It should be noted that the multiple processors in the computing device are not all used for building the test node, and a part of the test node must be reserved for the computing device to execute the basic process or other processes. As mentioned above, the test environment type of the test case indicates the number of test nodes required by the test case, and the total number of test nodes required for executing each test case can be clearly obtained by combining the number of test cases, however, the total number of test nodes required by each test case is generally much larger than the total number of processors in one computing device, so that when a test set is constructed, an appropriate number of processors should be selected to construct the test nodes according to the total number of test nodes required by each test case, for example, when the total number of test nodes required by each test case is larger, more processors should be selected to construct the test nodes, and when the total number of test nodes required by each test case is smaller, fewer processors should be selected to construct the test nodes.

In addition, the total number of the test nodes in the constructed test set should be not less than the maximum value of the number of the test nodes indicated by the test environment types of the test cases in each test case, for example, one multi-test case includes 4 test cases, where the test environment type of the first test case is a single node, the second test environment type is a three-node, the third test environment type is a four-node, and the fourth test environment type is a double-node. Then the number of test nodes in the constructed test set should be equal to or greater than 4.

In addition, in some embodiments, the test nodes may be created according to a multi-process manner, and a corresponding record table may be created to record the state information of each test node. Specifically, the created state information of the test node may be recorded in a data table, and a state (e.g., an idle state) of each test node is indicated, it should be noted that the initial state of each test node in the test set is idle.

In step S204, the test environment type of the use case to be tested is determined. After the test set is constructed, the test tasks are executed, and the execution tasks of the test cases may be executed sequentially or simultaneously in a multi-process manner, which is not limited in this embodiment.

In some embodiments, determining the test environment type of the use case to be tested may be accomplished by:

and S224, determining the testing environment type of the to-be-tested case by identifying the keywords of the to-be-tested case. For a specific identification process, reference may be made to the identification of the environment type of each test case in step S202, which is not described herein again.

And step S244, determining the number of the test nodes which need to be applied to the test set by the case to be tested according to the determined test environment type. Exemplarily, if the test environment type of the case to be tested is a single-node environment type, determining that the number of test nodes of the case to be tested, which need to apply for the test set, is 1; and if the test environment type of the to-be-tested case is the three-node environment type, determining that the number of the test nodes which need to be applied to the test set by the to-be-tested case is 3 and the like.

In step S206, it is determined whether the test nodes in the test set satisfy a preset condition based on the test environment type. Specifically, the preset condition includes that whether the number of each test node in the test set in an idle state meets the number of test nodes required by the case to be tested is judged.

In a specific example, the number of the test cases is 2, the test environment type of the first test case is a three-node environment type, and the test environment type of the second test case is a four-node environment type. A total of 5 test nodes are included in the test set. The two test cases are executed in the order of executing the first test case first and then the second test case.

It can be known that the number of test nodes required by the first test case is 3, the number of test nodes in the idle state in the test set is 5, and for the first test case, it is determined that 5 test nodes in the test set satisfy the preset condition, and when the first test case is normally executed, the state of 3 test nodes in the test set is in the occupied state. At this time, the number of test nodes required by the second test case is 4, the number of test nodes in an idle state in the test set is 2, and for the second test case, it is determined by judgment that the test nodes in the test set do not meet the preset condition.

As described above, when determining whether each test node in the test set satisfies the preset condition, the state of each test node needs to be known first, and therefore, in some embodiments, the step S206 further includes the following sub-steps: and acquiring the states of all the test nodes in the test set, wherein the states of the test nodes comprise idle, available, occupied and abnormal states.

It is easily understood that the idle state refers to the test node being in the non-operating state, and the occupied state refers to the test node being in the operating state. The abnormal state means that the test node in the idle state is abnormal and cannot execute the test case, and the available state means that the test node in the idle state has no abnormality. Specifically, whether the test node is in an abnormal state or not can be determined according to user rules (such as a disk, a cpu, a network state and the like).

It should be noted that it is necessary to first determine whether the test node is in an idle state, and then determine whether the test node in the idle state is in an available state.

In step S208, if the number of test nodes in the test set that are idle satisfies the number of test nodes required by the to-be-tested case, the test set is applied for a corresponding number of test nodes to execute the to-be-tested case. And when the number of the test nodes in the idle state in the test set is not less than the test environment type of the case to be tested, applying the corresponding number of test nodes in the test set to execute the case to be tested.

Specifically, first, a test node is called to execute a case to be tested, and the state of the corresponding test node is adjusted to be occupied. And then, after the execution of the case to be tested is finished, adjusting the state of the corresponding test node to be idle.

In a specific example, the test environment type of the case to be tested is a three-node environment type, a total of 5 test nodes are included in the test set, and the states of the 5 test nodes are all available. Then 3 test nodes are called from the test set for executing the case to be tested, and the state of the called 3 test nodes is adjusted from idle to occupied. After the test case is executed, the states of the 3 called test nodes are adjusted from occupied to idle so as to execute other test cases.

In addition, when the test nodes in the test set do not meet the preset conditions, in some embodiments, when the number of the test nodes in the test set in the idle state does not meet the number of the test nodes required by the case to be tested, the step of determining the type of the test environment is executed again, and whether the test nodes in the test set meet the preset conditions is judged again. In other words, if the number of test nodes in the test set does not satisfy the number of test nodes required by the case to be tested, step S204 and step S206 are executed again until the test nodes in the test set satisfy the preset condition.

In some embodiments, the number of test cases is 2, the test environment type of the first test case is a three-node environment type, and the test environment type of the second test case is a four-node environment type. A total of 5 test nodes are included in the test set. The first test case is executed first, and then the second test case is executed.

According to the foregoing embodiment, the first test case executed first meets the preset condition, and when the first test case is normally executed, 3 test nodes in the testable set are called, at this time, the states of 3 test nodes in the test set are occupied, and the states of 2 test nodes are idle.

The second test case needs 4 test nodes, and the test nodes in the test set do not meet the preset condition, at this time, the second test case needs to wait.

After the first test case is executed, the states of the 3 test nodes are adjusted to be idle by occupation, namely, the states of the 5 test nodes in the test set are idle.

And if the second test case judges that the test nodes in the test set meet the preset conditions again, 4 test nodes in the test set are called to execute the second test case.

It should be noted that, if the number of test cases in the test set is large enough, for example, there are more than 7 test nodes in the test set, the second test case may be executed at the same time while the first test case occupies 3 test nodes.

According to the test environment scheduling method provided by the embodiment, the size of a test set (the number of required test nodes) is determined according to test case data, a test environment is created, and the states of the test nodes are marked. And then according to the test environment type of each test case, acquiring nodes which accord with the state in the test set, establishing a corresponding test type environment, and releasing the test nodes for the execution of the subsequent test cases after the execution of the test cases is finished. The problem of test case execution blocking caused by abnormal specific test environment types is solved, the reuse rate of the test environment is increased, and the test duration is shortened.

In a specific example, the test environment scheduling method 200 provided in connection with the present embodiment is described as follows:

The test method 300 is described in detail in connection with FIG. 3:

and 3.1, determining the number of the test nodes, wherein the number can be determined according to the number of the test cases and the test environment types of the test cases.

And 3.2, creating a test set according to the determined number of the test nodes, and marking the states of the test nodes (the initial states are idle).

3.3, for a certain test case, before executing the test case, firstly determining the test environment type (single node/multi-node) of the test case.

And 3.4, starting a task for checking the states of all the test nodes in the test set, wherein the states of the test nodes are divided into four types, namely idle, occupied, available and abnormal.

3.5, firstly, judging whether the test node is in an idle state or an occupied state, wherein the idle state indicates that the test node is in a non-working state at the moment, and the occupied state indicates that the test node is in a working state (namely other test cases are being executed) at the moment.

And 3.6, judging whether the test node in the idle state is an available test node or not, if so, updating the state of the test node to be available, and otherwise, updating the state to be abnormal.

And 3.7, finally judging whether the number of the test nodes in the available state meets the condition of executing the test case, for example, if the test environment type of a certain test case is three nodes, which indicates that the number of the test nodes required for executing the test case is 3, judging whether the number of the test nodes in the available state in the test set is not less than 3, and if so, executing a normal test flow to execute the test case. Otherwise, the state of each test node in the test set needs to be re-checked (this is because the state of each test node in the test set changes, for example, when another previously executed test case completes execution and releases the corresponding test node, the number of test nodes in the test set in the idle state changes).

And 3.8, applying for a corresponding test node.

3.9, the computing equipment calls a corresponding number of test nodes in the test set to execute the test cases, and updates the states of the called test nodes to be occupied.

And 3.10, after the execution of the case to be tested is finished, updating the state of the test node from occupied to idle.

When a test task starts, the number of test nodes in the computing equipment is firstly determined to complete the construction of a test set, then the test environment type (namely the required number of the test nodes) of a test case is determined, the test nodes are applied to the test set, the computing equipment firstly judges whether the state of each test node in the test set is idle or not and records the idle state, then judges whether each test node in the idle state is an available test node or not, the state of the available test node is updated to be available, and the state of the unavailable test node is updated to be unavailable

The various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present invention, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U.S. disks, floppy disks, CD-ROMs, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.

In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Wherein the memory is configured to store program code; the processor is configured to perform the method of the invention according to instructions in said program code stored in the memory.

By way of example, and not limitation, readable media may comprise readable storage media and communication media. Readable storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.

In the description provided herein, algorithms and displays are not inherently related to any particular computer, virtual system, or other apparatus. Various general purpose systems may also be used with examples of this invention. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose preferred embodiments of the invention.

In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into multiple sub-modules.

Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Furthermore, some of the described embodiments are described herein as a method or combination of method elements that can be performed by a processor of a computer system or by other means of performing the described functions. A processor having the necessary instructions for carrying out the method or method elements thus forms a means for carrying out the method or method elements. Further, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is used to implement the functions performed by the elements for the purpose of carrying out the invention.

As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.

While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this description, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The present invention has been disclosed in an illustrative rather than a restrictive sense with respect to the scope of the invention, as defined in the appended claims.

Claims

1. A test environment scheduling method for execution in a computing device configured with a plurality of processors, wherein any of the processors is configured to construct a test node, the method comprising:

constructing a corresponding test set according to the data of each test case, wherein the test set comprises a plurality of test nodes;

determining the test environment type of a case to be tested;

judging whether the test nodes in the test set meet preset conditions or not based on the test environment type;

and if so, applying for at least one test node from the test set to execute the case to be tested.

2. The method of claim 1, wherein the determining a test environment type for a use case to be tested comprises:

determining the testing environment type of the to-be-tested case by identifying the keywords of the to-be-tested case, wherein the testing environment type comprises a single-node environment type and a multi-node environment type;

and determining the number of test nodes which need to be applied to the test set by the case to be tested according to the determined test environment type.

3. The method of claim 1, wherein the determining whether each test node in the test set satisfies a preset condition based on the test environment type comprises:

and acquiring the states of all the test nodes in the test set, wherein the states of the test nodes comprise idle states, occupied states and abnormal states.

4. The method of claim 3, wherein the preset condition includes determining whether the number of test nodes in the test set that are idle meets the number of test nodes required by the case to be tested.

5. The method of claim 2, wherein after the step of determining whether each test node in the test set satisfies a preset condition based on the environment type, the method further comprises:

if not, re-executing the step of determining the test environment type, and re-judging whether each test node in the test set meets the preset condition.

6. The method of claim 1, wherein if yes, invoking the corresponding test node to execute the case to be tested, further comprising:

calling the test node to execute the case to be tested, and adjusting the state of the corresponding test node to be occupied;

and after the execution of the case to be tested is finished, adjusting the state of the corresponding test node to be idle.

7. The method of claim 1, wherein the step of constructing a corresponding test set according to each test case data, the test set comprising a plurality of test nodes comprises:

and constructing the test set based on the number of the test cases and the number of the required test nodes.

8. The method of claim 7, wherein the step of constructing a corresponding test set according to each test case data, the test set including a plurality of test nodes further comprises:

and creating the test nodes according to a multi-process mode, and creating a corresponding record table to record the state information of each test node.

9. A computing device, comprising:

at least one processor; and

a memory storing program instructions configured for execution by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-8.

10. A readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the method of any of claims 1-8.