CN113342698B - Test environment scheduling method, computing device and storage medium - Google Patents
Test environment scheduling method, computing device and storage medium Download PDFInfo
- Publication number
- CN113342698B CN113342698B CN202110825016.6A CN202110825016A CN113342698B CN 113342698 B CN113342698 B CN 113342698B CN 202110825016 A CN202110825016 A CN 202110825016A CN 113342698 B CN113342698 B CN 113342698B
- Authority
- CN
- China
- Prior art keywords
- test
- node
- nodes
- case
- tested
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 515
- 238000000034 method Methods 0.000 title claims abstract description 73
- 230000002159 abnormal effect Effects 0.000 claims description 10
- 238000004891 communication Methods 0.000 description 16
- 230000008569 process Effects 0.000 description 7
- 230000008901 benefit Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 230000005856 abnormality Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 238000010998 test method Methods 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 230000009977 dual effect Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000007723 transport mechanism Effects 0.000 description 2
- 230000000903 blocking effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000007667 floating Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
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
- G06F11/3664—Environments for testing or debugging software
-
- 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
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
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)
- Test And Diagnosis Of Digital Computers (AREA)
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 one 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 type of the test environment of the test case to be tested; judging whether the test nodes in the test set meet preset conditions or not based on the test environment types; if yes, applying at least one test node to the test set to execute the test case to be tested.
Description
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 at present to directly create a corresponding test environment group according to the environment type specified in the test case. However, in the method, in complex and various test environment type tasks, the fault tolerance is poor, and the problem of blockage of use case execution is easy to occur. The type of each test node is cured in advance so the environmental reuse rate is low.
Disclosure of Invention
The present invention has been made in view of the above problems, and provides a test environment scheduling method, a computing device, and a storage medium that overcome or at least partially solve the above problems.
According to one aspect of the present invention, there is provided a test environment scheduling method, for execution in a computing device configured with a plurality of processors, wherein any one processor is used 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 type of the test environment of the test case to be tested; judging whether the test nodes in the test set meet preset conditions or not based on the test environment types; if yes, applying at least one test node to the test set to execute the test case to be tested.
Optionally, in the method according to the present invention, the step of determining a test environment type of the test case to be tested includes: determining the test environment type of the test case to be tested by identifying the keywords of the test case to be tested, wherein the test environment type comprises a single-node environment type and a multi-node environment type; and determining the number of test nodes required to be applied to the test set by the test case to be tested according to the determined test environment type.
Optionally, in the method according to the present invention, the step of determining, based on the test environment type, whether each test node in the test set meets a preset condition includes: the method comprises the steps of obtaining states of all test nodes in a test set, wherein the states of the test nodes comprise idle, occupied 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 with idle states meets the number of test nodes required by the test 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 meets the preset condition based on the environment type, the method further includes: if not, the step of determining the test environment type is re-executed, and whether each test node in the test set meets the preset condition is re-judged.
Optionally, in the method according to the present invention, if the test result is met, the step of calling the corresponding test node to execute the test case to be tested further includes: calling a test node to execute a test case to be tested, and adjusting the state of the corresponding test node to be occupied; and after the test case to be tested is executed, the state of the corresponding test node is adjusted to be idle.
Optionally, in the method according to the present invention, the step of constructing a corresponding test set according to each test case data, the test set including a plurality of test nodes includes: and constructing the test set based on the number of each test case and the number of required test nodes.
Optionally, in the method according to the present invention, 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 includes: and creating test nodes according to the 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 present 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 adapted 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 that, 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 the abnormality of the specific type of test environment is solved. On the other hand, the problem of low multiplexing rate of the test environment is solved.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
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 designate like parts throughout the figures. 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 chart of a test 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 is an explanation of terms involved in the present invention:
The test case refers to the description of a specific software product for testing tasks, and the test scheme, method, technology and strategy are embodied. Briefly, a test case is a set of test inputs, execution conditions, and expected results tailored for a particular goal to verify that a particular software requirement is met.
Test environment refers to a description of the software and hardware environment on which the test is run, as well as any other software that interacts with the software under test, including drivers and stub. The test environment is stable and controllable, so that a tester can spend less time to complete the execution of the test case, additional time is not required to be spent for the maintenance of the test case and the test process, and each submitted defect can be ensured to be accurately reproduced at any time.
The test node refers to the execution environment of the 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. A total of 4 states are divided into idle, available, abnormal and occupied.
The test environment type refers to the test environment type required by the execution of the test case. Such as single-node environment types: indicating that a test node environment is needed for test case operation; dual node test environment type: two test node environments are needed for test case operation, one is a local environment, and the other is an opposite environment.
In the existing test environment scheduling method, the test environment scheduling method is generally classified and operated according to the environment types (single node or multiple nodes) required by the test cases, for example, in the 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, when one type of test case is executed, the corresponding test node is in an idle state until all the test cases are operated, and the test node multiplexing rate is low.
In addition, in the test environment scheduling method, if only one test node fails to be created or is abnormal, the test case execution is 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.
The proposal of the invention is provided for solving the problems in the prior art. One embodiment of the present invention provides a test environment scheduling method that may be executed in a computing device. FIG. 1 illustrates 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. The 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: microprocessor (μp), microcontroller (μc), digital information processor (DSP), or any combination thereof. The processor 104 may include one or more levels of caches, such as a first level cache 110 and a second level 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. Physical memory in a computing device is often referred to as volatile memory, RAM, and data in disk needs to be loaded into physical memory in order to be read by processor 104. The 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 for instructing the processor 104 to perform a corresponding operation. In some implementations, the application 122 may be arranged to execute instructions on an operating system by the one or more processors 104 using the program data 124 in some implementations. Operating system 120 may be, for example, linux, windows or the like, which includes program instructions for handling basic system services and performing hardware-dependent tasks. The application 122 includes program instructions for implementing various functions desired by the user, and the application 122 may be, for example, a browser, instant messaging software, a software development tool (e.g., integrated development environment IDE, compiler, etc.), or the like, but is not limited thereto. When an application 122 is installed into computing device 100, a driver module may be added to operating system 120.
When the computing device 100 starts up running, the processor 104 reads the program instructions of the operating system 120 from the memory 106 and executes them. Applications 122 run on top of operating system 120, utilizing interfaces provided by operating system 120 and underlying hardware to implement various user-desired functions. When a user launches the application 122, the application 122 is loaded into the memory 106, and the processor 104 reads and executes the program instructions of the application 122 from the memory 106.
Computing device 100 also includes storage device 132, storage device 132 including removable storage 136 and non-removable storage 138, both removable storage 136 and non-removable storage 138 being connected to 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 basic configuration 102 via 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 communication with one or more other computing devices 162 via one or more communication ports 164 over a network communication link.
The 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 in a modulated data signal, such as a carrier wave or other transport mechanism. A "modulated data signal" may be a signal that has one or more of its data set or changed 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 special purpose network, and 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.
Computing device 100 also includes a storage interface bus 134 that is coupled to 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, U disk, removable hard disk, etc.) and non-removable storage 138 (e.g., hard disk drive HDD, etc.).
In computing device 100 according to the present invention, application 122 includes a plurality of program instructions to perform method 200.
FIG. 2 illustrates a flow diagram of a test environment scheduling method 200 according to one embodiment of the invention. The method 200 is suitable for execution in a computing device (e.g., the computing device 100 described above) having a plurality of processors configured therein, wherein any one processor is used to construct a test node.
As shown in fig. 2, the method 200 is for implementing a method for scheduling a test environment, and starts 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 in 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 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 be determined by identifying the keywords of each test case. The test environment type comprises a single-node environment type and a multi-node environment type. The test cases can indicate the types of the test environments required by executing the test cases when the test cases are generated, namely, any test case contains keywords of the types of the test environments required by executing the test cases, and the keywords are embedded in the test cases in a binary mode (language which can be identified by the computing equipment). By identifying the keywords, the type of the test environment required by the test case can be obtained.
As described above, the environmental type of a test case refers to the number of test nodes needed 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 test nodes needed.
It should be noted that the multiple processors in the computing device cannot all be used to build the test node, and a portion must be reserved for the computing device to execute the underlying process or other processes. The above-mentioned test environment types of the test cases indicate the number of test nodes needed by the test cases, and the total number of test nodes needed by executing each test case can be definitely obtained by combining the number of test cases, but the total number of test nodes needed by each test case is generally far greater than the total number of processors in one computing device, so when the test set is constructed, a proper number of processors should be selected according to the total number of test nodes needed by each test case to construct the test nodes, for example, when the total number of test nodes needed by each test case is greater, more processors are selected to construct the test nodes, and when the total number of test nodes needed by each test case is smaller, fewer processors are selected to construct the test nodes.
In addition, the total number of test nodes in the constructed test set should be not less than the maximum value of the number of test nodes indicated by the test environment types of the test cases in each test case, for example, one multiple 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 three nodes, the third test environment type is four nodes, and the fourth test environment type is a dual 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 status information of each test node. Specifically, the state information of the created test nodes may be recorded in a data table to indicate the states (e.g., idle states) of the test nodes, where it is to be noted that the initial states of the test nodes in the test set are all idle.
In step S204, the test environment type of the test case to be tested is determined. After the test set is built, the test tasks will be started to be executed, and the execution tasks of the test cases can 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 test case under test may be accomplished by the following sub-steps:
Step S224, determining the type of the test environment of the test case by identifying the keywords of the test case. The specific identification process may refer to step S202 for identifying the environment type of each test case, which is not described herein.
Step S244, according to the determined test environment type, determining the number of test nodes required to be applied to the test set by the test case to be tested. The method includes the steps that an example is that the type of a test environment of a test case to be tested is a single-node environment type, and the number of test nodes, which the test case to be tested needs to apply to a test set, is determined to be 1; the test environment type of the test case to be tested is a three-node environment type, and the number of test nodes which the test case to be tested needs to apply to the test set is determined to be 3.
In step S206, based on the test environment type, it is determined whether the test nodes in the test set satisfy the preset condition. Specifically, the preset condition includes judging whether the number of the test nodes with idle states in the test set meets the number of the test nodes required by the test case to be tested.
In a specific example, 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 two test cases are executed in the order in which the first test case is executed first and then the second test case is executed.
The number of the test nodes required by the first test case is 3, the number of the test nodes in the idle state in the test set is 5, and for the first test case, the 5 test nodes in the test set are judged to meet the preset condition, and when the first test case is in normal execution, the states of the 3 test nodes in the test set are in an occupied state. At this time, the number of the test nodes required by the second test case is 4, and the number of the test nodes in the idle state in the test set is 2, and for the second test case, the test nodes in the test set do not meet the preset condition after being determined.
As described above, when determining whether each test node in the test set meets the preset condition, the state of each test node needs to be known first, so in some embodiments, step S206 further includes the sub-steps of: the method comprises the steps of obtaining states of all test nodes in a test set, wherein the states of the test nodes comprise idle, available, occupied and abnormal states.
It is easy to understand that the idle state refers to the test node being in a non-operating state, and the occupied state refers to the test node being in an operating state. The abnormal state means that the test node in the idle state is abnormal, the test case cannot be executed, and the available test node in the idle state is free of abnormality. Specifically, whether the test node is in an abnormal state may be determined according to a user rule (such as a disk, cpu, network state, etc.).
It should be noted that, it is necessary to determine whether the test node is in an idle state, and then determine whether the test node 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 test case to be tested, a corresponding number of test nodes is applied to the test set to execute the test case to be tested. 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 test case to be tested, applying for the corresponding number of the test nodes in the test set to execute the test case to be tested.
Specifically, first, a test node is called to execute a test case to be tested, and the state of the corresponding test node is adjusted to be occupied. And then, after the test case to be tested is executed, the state of the corresponding test node is adjusted to be idle.
In a specific example, the test environment type of the test case to be tested is a three-node environment type, the test set includes 5 test nodes in total, and states of the 5 test nodes are all available. Then, 3 test nodes are called from the test set for executing the test case under test, and the states of the 3 called test nodes are adjusted from idle to occupied. And 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, which are idle, does not meet the number of the test nodes required by the test case to be tested, the step of determining the test environment type is re-executed, and whether the test nodes in the test set meet the preset conditions is re-determined. In other words, if the number of test nodes in the test set does not meet the number of test nodes required by the test case to be tested, step S204 and step S206 are re-executed until the test nodes in the test set meet 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, it can be known that the first test case executed first satisfies the preset condition, and when the first test case is executed normally, 3 test nodes in the testable set are called, and 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 conditions, and 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 from occupied to idle, namely the states of the 5 test nodes in the test set are all idle.
And the second test case judges that the test nodes in the test set meet the preset conditions again, and 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 sufficiently large, for example, more than 7 test nodes in the test set, the second test case may be executed simultaneously while the first test case occupies 3 test nodes.
According to the test environment scheduling method, the size of the test set (the number of the needed test nodes) is determined according to the test case data, a test environment is created, and the states of the test nodes are marked. And acquiring nodes conforming to the state in the test set according to the test environment type of each test case, constructing a corresponding test type environment, and releasing the test nodes after the execution of the test cases is completed for the execution of the subsequent test cases. The problem of test case execution blocking caused by the abnormality of the specific test environment type is solved, the multiplexing 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 describes the entire test work as follows:
FIG. 3 shows a flow chart of a test method 300 according to one embodiment of the invention.
The test method 300 is described in detail in connection with fig. 3:
and 3.1, determining the number of the test nodes, and particularly determining 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 all idle).
3.3 For a test case, before executing the test case, determining the test environment type (single node/multi-node) of the test case.
And 3.4, starting tasks 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 of idle states, occupied states, usable states and abnormal states.
And 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 at the moment (namely, other test cases are being executed).
And 3.6, judging whether the test node in the idle state is an available test node or not, if the test node is the available test node, updating the state of the test node into the available test node, and otherwise updating the test node into the abnormal test node.
And 3.7, finally judging whether the number of the test nodes in the available state meets the condition for executing the test case, for example, if the test environment type of a certain test case is three nodes, indicating 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 checked again (this is because the state of each test node in the test set changes, for example, when another previously executed test case is executed, and the corresponding test node is released, then the number of test nodes in the test set in an idle state changes).
And 3.8, applying for a corresponding test node.
And 3.9, the computing equipment calls a corresponding number of test nodes in the test set for executing the test cases, and updates the states of the called test nodes to be occupied.
And 3.10, updating the state of the test node from occupied to idle after the test case to be tested is executed.
When a test task starts, firstly determining the number of test nodes in the computing equipment to complete the construction of a test set, then determining the test environment type (namely the number of required test nodes) of the test case, applying for the test nodes in the test set, firstly judging whether the states of all the test nodes in the test set are idle or not by the computing equipment, recording, judging whether all the test nodes in the idle state are available test nodes or not, updating the states of the available test nodes to be available and updating the states of the unavailable test nodes 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 of the methods and apparatus of the present invention, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U-drives, floppy diskettes, 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 in accordance with instructions in said program code stored in the memory.
By way of example, and not limitation, readable media comprise readable storage media and communication media. The readable storage medium stores 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 the invention. The required structure for a construction of such a system is apparent from the description above. In addition, the present invention is not directed to any particular programming language. It should be appreciated that the teachings of the present invention as described herein may be implemented in a variety of programming languages and that the foregoing description of specific languages is provided for disclosure of preferred embodiments of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood 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 construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim.
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 a plurality of sub-modules.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. 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. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units 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 but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments.
Furthermore, some of the embodiments are described herein as methods or combinations of method elements that may be implemented by a processor of a computer system or by other means of performing the functions. Thus, a processor with the necessary instructions for implementing the described method or method element forms a means for implementing the method or method element. Furthermore, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is for carrying out the functions performed by the elements for carrying out the objects of the invention.
As used herein, unless otherwise specified the use of the ordinal terms "first," "second," "third," etc., to describe a general object merely denote different instances of like objects, and are not intended to imply that the objects so described must have a given order, 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 the above description, will appreciate that other embodiments are contemplated within 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 disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the invention, which is defined by the appended claims.
Claims (9)
1. A test environment scheduling method executed 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 test case data, wherein the test set comprises a plurality of test nodes;
Determining the test environment type of a test case to be tested, which comprises determining the test environment type of the test case to be tested by identifying keywords of the test case to be tested, wherein the test environment type comprises a single-node environment type and a multi-node environment type, and determining the number of test nodes required to be applied to the test set by the test case to be tested according to the determined test environment type;
judging whether a test node in the test set meets a preset condition or not based on the test environment type;
If yes, applying at least one test node to the test set to execute the test cases to be tested, wherein the test cases to be tested are executed simultaneously in a multi-process mode.
2. The method of claim 1, wherein the step of determining whether each test node in the test set meets a preset condition based on the test environment type comprises:
the states of all the test nodes in the test set are obtained, wherein the states of the test nodes comprise idle states, occupied states and abnormal states.
3. The method of claim 2, wherein the preset condition includes determining whether a number of test nodes in the test set that are idle meets a number of test nodes required by the test case under test.
4. The method of claim 1, wherein the step of determining whether each test node in the test set meets a preset condition based on the test environment type further comprises:
If not, the step of determining the test environment type is re-executed, and whether each test node in the test set meets the preset condition is re-judged.
5. The method of claim 2, wherein the step of calling the corresponding test node to execute the test case if satisfied further comprises:
calling the test node to execute the test case to be tested, and adjusting the state of the corresponding test node to be occupied;
and after the test case to be tested is executed, the state of the corresponding test node is adjusted to be idle.
6. The method of claim 1, wherein the step of constructing a corresponding test set from each test case data, the test set including a plurality of test nodes comprises:
and constructing the test set based on the number of each test case and the number of required test nodes.
7. The method of claim 6, wherein the step of constructing a corresponding test set from 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.
8. A computing device, comprising:
At least one processor; and
A memory storing program instructions, wherein the program instructions are configured to be adapted to be executed by the at least one processor, the program instructions comprising instructions for performing the method of any of claims 1-7.
9. A readable storage medium storing program instructions which, when read and executed by a computing device, cause the computing device to perform the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110825016.6A CN113342698B (en) | 2021-07-21 | 2021-07-21 | Test environment scheduling method, computing device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110825016.6A CN113342698B (en) | 2021-07-21 | 2021-07-21 | Test environment scheduling method, computing device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113342698A CN113342698A (en) | 2021-09-03 |
| CN113342698B true CN113342698B (en) | 2024-07-09 |
Family
ID=77480145
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110825016.6A Active CN113342698B (en) | 2021-07-21 | 2021-07-21 | Test environment scheduling method, computing device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113342698B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116225944B (en) * | 2023-03-09 | 2024-05-07 | 矩阵时光数字科技有限公司 | Software testing system and method for presetting networking environment |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111008116A (en) * | 2019-10-31 | 2020-04-14 | 苏州浪潮智能科技有限公司 | Timing snapshot characteristic testing method and system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0552288A1 (en) * | 1990-10-03 | 1993-07-28 | Thinking Machines Corporation | Parallel computer system |
| US9071631B2 (en) * | 2012-08-09 | 2015-06-30 | International Business Machines Corporation | Service management roles of processor nodes in distributed node service management |
| CN106776309A (en) * | 2016-12-06 | 2017-05-31 | 郑州云海信息技术有限公司 | A kind of testing time optimization method and system |
| CN109815154A (en) * | 2019-02-22 | 2019-05-28 | 深圳市网心科技有限公司 | A kind of test method, device, system and medium |
| CN111881018A (en) * | 2020-06-29 | 2020-11-03 | 苏州浪潮智能科技有限公司 | Automatic test dynamic scheduling system |
-
2021
- 2021-07-21 CN CN202110825016.6A patent/CN113342698B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111008116A (en) * | 2019-10-31 | 2020-04-14 | 苏州浪潮智能科技有限公司 | Timing snapshot characteristic testing method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113342698A (en) | 2021-09-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8918783B2 (en) | Managing virtual computers simultaneously with static and dynamic dependencies | |
| CN108153849B (en) | Database table segmentation method, device, system and medium | |
| US7665005B2 (en) | In situ processor margin testing | |
| TW201537461A (en) | Framework for user-mode crash reporting | |
| CN103415840A (en) | Error management across hardware and software layers | |
| US20100293513A1 (en) | Method and System for Design Simplification Through Implication-Based Analysis | |
| US8145944B2 (en) | Business process error handling through process instance backup and recovery | |
| KR100633827B1 (en) | Method and apparatus for enumeration of a multi-node computer system | |
| CN113342698B (en) | Test environment scheduling method, computing device and storage medium | |
| US20100186003A1 (en) | Per Group Verification | |
| CN109034668B (en) | ETL task scheduling method, ETL task scheduling device, computer equipment and storage medium | |
| US11380356B2 (en) | Flexible on-cylinder limit for drive performance management | |
| JP2017045217A (en) | Log management device, log management method, and log management program | |
| CN111880803B (en) | Software construction method and device applied to multiple platforms | |
| US10635444B2 (en) | Shared compare lanes for dependency wake up in a pair-based issue queue | |
| US20070079109A1 (en) | Simulation apparatus and simulation method | |
| US20230275931A1 (en) | Dynamic management of role-based access control systems | |
| CN111404715B (en) | Network service instantiation method and device, electronic equipment and storage medium | |
| US20060184729A1 (en) | Device, method, and computer product for disk management | |
| US20100077383A1 (en) | Simulation method and storage medium for storing program | |
| JP2828590B2 (en) | Microprogram verification method | |
| JP2009238176A (en) | Information processing apparatus and program verifying method | |
| US6564178B1 (en) | Method and apparatus for evaluating processors for architectural compliance | |
| US20120123761A1 (en) | Testing Software On A Computer System | |
| CN117112311B (en) | I/O driven data recovery method, system and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |