CN112988558A - Test execution method and device, electronic equipment and storage medium - Google Patents
Test execution method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112988558A CN112988558A CN201911299189.8A CN201911299189A CN112988558A CN 112988558 A CN112988558 A CN 112988558A CN 201911299189 A CN201911299189 A CN 201911299189A CN 112988558 A CN112988558 A CN 112988558A
- Authority
- CN
- China
- Prior art keywords
- test
- data
- list
- test case
- execution
- 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.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 547
- 238000000034 method Methods 0.000 title claims abstract description 58
- 238000004590 computer program Methods 0.000 claims description 8
- 230000007717 exclusion Effects 0.000 abstract description 8
- 238000013522 software testing Methods 0.000 abstract description 4
- 238000012545 processing Methods 0.000 description 10
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 239000002699 waste material Substances 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000000275 quality assurance Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The application provides a test execution method, a test execution device, electronic equipment and a storage medium, and relates to the technical field of software testing. The method comprises the following steps: acquiring a test case to be executed currently from the test case set; reading a reference data identification list of the test case; when any data identifier in the reference data identifier list exists in the runtime data list, adjusting the execution sequence of the test case into the last bit of the test case set; and when all the data identifications in the quoted data identification list do not exist in the runtime data list, distributing the test case to an idle test actuator in a plurality of preset test actuators for testing, and storing the data identification of the test case into the runtime data list. The method performs parallel test on the test cases through the data identification of the test cases needing to quote data based on the mutual exclusion relation of the test data, and improves the test efficiency.
Description
Technical Field
The present application relates to the field of software testing technologies, and in particular, to a test execution method and apparatus, an electronic device, and a storage medium.
Background
With the increasing delivery speed of application software, in order to improve the rapid delivery capability of the software, it is an industry common practice to add software automation test for quality assurance in the software development process, and in order to reduce the analysis difficulty of the automation test, the execution of the automation test cases is generally performed in a serial manner, but with the expansion of the software scale, the number of the automation test cases is increased, and the efficiency of the serial automation test is increasingly unable to meet the requirements. In order to improve the efficiency of the automated testing, the automated testing cases need to be executed in parallel to complete the automated testing quickly.
A test case set is maintained in an existing automatic test framework, and a test executor in the automatic test framework sequentially takes cases in the test case set for execution. The whole process is serial, and only one use case can be executed and then the next use case is executed. When the number of the cases is small and the execution speed of a single case is high, the serial execution influence is small, and when the number of the test cases is large and the execution time of each case is long, the time consumed for completing the execution of the whole automatic test is long, and the quick verification of the version is influenced.
Disclosure of Invention
In view of the above, an object of the embodiments of the present application is to provide a test execution method, a test execution apparatus, an electronic device, and a storage medium, so as to solve the problems of long time consumption and low efficiency of serial testing in the prior art.
The embodiment of the application provides a test execution method, which comprises the following steps: acquiring a test case to be executed currently from the test case set; reading a reference data identification list of the test case, wherein the reference data identification list comprises data identifications of one or more pieces of test data to be referred by the test case; when any data identifier in the reference data identifier list exists in a runtime data list, adjusting the execution sequence of the test case to be the last bit of the test case set, wherein the test data corresponding to the data identifier in the runtime data list is in an executing state; and when all the data identifications in the reference data identification list do not exist in the runtime data list, distributing the test case to idle test executors in a plurality of preset test executors for testing, and storing all the data identifications in the reference data identification list into the runtime data list.
In the implementation mode, whether the test data which needs to be quoted by the test case is executed or not is judged based on the data identification and the runtime data list, so that the test case of which the test data which needs to be quoted is in an idle state is subjected to parallel test processing based on the quote mutual exclusion relation of the test data, the test efficiency is improved, and the test time consumption is reduced.
Optionally, after storing all the data identifiers in the reference data identifier list into the runtime data list, the method further includes: storing the test result of the test case into a test result list; deleting all data identifications in the list of referenced data identifications from the run-time data list.
In the implementation mode, the data identifier corresponding to the test case is deleted from the run-time data list after the test case completes the test, so that data occupation is avoided when other test cases need to refer to the same test data, and the execution efficiency of the test case is ensured.
Optionally, after the test case is allocated to an idle test executor to be tested, the method further includes: setting the execution state of a test executor executing the test case to be in operation; after the removing all data identifiers in the list of referenced data identifiers from the runtime data list, the method further comprises: and setting the execution state of a test executor executing the test case to be idle.
In the implementation mode, the multiple test executors can simultaneously perform parallel test processing on multiple test cases through the state setting of the test executors, and the test efficiency is improved in the aspect of test operation of the test cases.
Optionally, the method further comprises: creating the test case set, adding one or more test cases to be executed into the test case set, wherein the sequence in the test case set represents the sequence of the test cases in the test case set.
In the implementation mode, the test case set with the sequence is used for testing and calling the test cases, the test sequence of the test cases can be adjusted based on the priority and the running condition of the test cases, the situation that the test executor cannot test and waste test executor resources after calling a certain test case is avoided, and the test efficiency is improved.
Optionally, the method further comprises: and after all the test cases in the test case set are tested, generating a test report based on the test result list.
In the implementation mode, the test report is generated uniformly by taking the test case set as a unit, and the test result is not output for each test case one by one, so that the relevance and the overall operation condition of the tested program can be better reflected by the test report.
Optionally, the obtaining the test case includes: and when the idle test executors exist currently, acquiring the test cases from the test case set based on the arrangement sequence.
In the implementation mode, the state of the test executors and the sequence of the test cases are determined when the test cases are called and enter the test executors, so that the test cases can be smoothly tested after being called, and invalid operation is avoided.
Optionally, the method further comprises: and acquiring test data to be referred by all test cases in the test case set, and adding a globally unique data identifier to each piece of test data.
In the implementation mode, the test data to be referred by the test case is identified by setting the globally unique data identifier, so that the test of the test case can be arranged in parallel in the subsequent steps based on the mutual exclusion relation of the test data, and the test efficiency is ensured.
An embodiment of the present application further provides a test execution apparatus, including: the case acquisition module is used for acquiring the test case to be executed currently from the test case set; the identification list reading module is used for reading a reference data identification list of the test case, wherein the reference data identification list comprises data identifications of one or more pieces of test data which need to be referred by the test case; a bit-adjusting module, configured to adjust an execution sequence of the test case to a last bit of the test case set when any data identifier in the reference data identifier list already exists in a runtime data list, where test data corresponding to the data identifier in the runtime data list is in an executing state; and the test execution module is used for distributing the test case to a vacant test executor in a plurality of preset test executors for testing when all the data identifications in the reference data identification list do not exist in the runtime data list, and storing all the data identifications in the reference data identification list into the runtime data list.
In the implementation mode, whether the test data which needs to be quoted by the test case is executed or not is judged based on the data identification and the runtime data list, so that the test case of which the test data which needs to be quoted is in an idle state is subjected to parallel test processing based on the quote mutual exclusion relation of the test data, the test efficiency is improved, and the test time consumption is reduced.
Optionally, the apparatus further comprises: the identification processing module is used for storing the test result of the test case into a test result list; deleting all data identifications in the list of referenced data identifications from the run-time data list.
In the implementation mode, the data identifier corresponding to the test case is deleted from the run-time data list after the test case completes the test, so that data occupation is avoided when other test cases need to refer to the same test data, and the execution efficiency of the test case is ensured.
Optionally, the apparatus further comprises: the executor processing module is used for setting the execution state of the test executor executing the test case to be running after the test case is distributed to the idle test executor to be tested; and after all the data identifications in the reference data identification list are deleted from the runtime data list, setting the execution state of a test executor executing the test case to be idle.
In the implementation mode, the multiple test executors can simultaneously perform parallel test processing on multiple test cases through the state setting of the test executors, and the test efficiency is improved in the aspect of test operation of the test cases.
Optionally, the apparatus further comprises: and the report generation module is used for generating a test report based on the test result list after all the test cases in the test case set are tested.
In the implementation mode, the test report is generated uniformly by taking the test case set as a unit, and the test result is not output for each test case one by one, so that the relevance and the overall operation condition of the tested program can be better reflected by the test report.
Optionally, the apparatus further comprises: and the set creating module is used for creating the test case set and adding one or more test cases to be executed into the test case set, and the sequence in the test case set represents the sequence of the test cases in the test case set.
In the implementation mode, the test case set with the sequence is used for testing and calling the test cases, the test sequence of the test cases can be adjusted based on the priority and the running condition of the test cases, the situation that the test executor cannot test and waste test executor resources after calling a certain test case is avoided, and the test efficiency is improved.
Optionally, the use case obtaining module is specifically configured to: and when the idle test executors exist currently, acquiring the test cases from the test case set based on the arrangement sequence.
In the implementation mode, the state of the test executors and the sequence of the test cases are determined when the test cases are called and enter the test executors, so that the test cases can be smoothly tested after being called, and invalid operation is avoided.
Optionally, the apparatus further comprises: an identity addition module to: and acquiring test data to be referred by all test cases in the test case set, and adding a globally unique data identifier to each piece of test data.
In the implementation mode, the test data to be referred by the test case is identified by setting the globally unique data identifier, so that the test of the test case can be arranged in parallel in the subsequent steps based on the mutual exclusion relation of the test data, and the test efficiency is ensured.
The embodiment of the application also provides electronic equipment, which comprises a memory and a processor, wherein the memory is stored with program instructions, and the processor executes any one of the test execution methods when reading and running the program instructions.
The embodiment of the application also provides a storage medium, wherein computer program instructions are stored in the storage medium, and when the computer program instructions are read and run by a processor, any one of the test execution methods is executed.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic flowchart of a test execution method according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart of a data identifier deleting step according to an embodiment of the present application;
fig. 3 is a schematic overall flowchart of a test execution method according to an embodiment of the present disclosure;
fig. 4 is a block diagram of a test execution apparatus according to an embodiment of the present disclosure.
Icon: 20-a test execution device; 21-a use case obtaining module; 22-identification list reading module; 23-a positioning module; 24-test execution module.
Detailed Description
The technical solution in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
The applicant researches and discovers that an automatic testing framework in the existing automatic testing operates a tested system according to the content of an automatic testing case, judges according to the returned information of the tested system and an expected result in the testing case, and if the result is consistent with the expected result, the automatic testing case passes the execution, otherwise, the execution fails. The whole process is executed in series, and when the number of test cases is large or the execution time of each test case is long, the whole automatic test execution consumes long time and is low in efficiency.
In order to solve the above problems, an embodiment of the present application provides a test execution method, please refer to fig. 1, where fig. 1 is a schematic flow chart of the test execution method according to the embodiment of the present application. The specific steps of the test execution method may be as follows:
step S12: and obtaining the test case to be executed currently from the test case set.
Test cases are concepts in software testing, which is a process that is described to facilitate the identification of the correctness, integrity, security, and quality of software. In other words, software testing is a process of auditing or comparing actual outputs with expected outputs, i.e., a process of operating a program under prescribed conditions to find out bugs, to measure software quality, and to evaluate whether it can meet design requirements.
The test case is a description of a software test task performed on a specific software product, and embodies a test scheme, a method, a technology and a strategy. Generally, the contents of the test case include a test target, a test environment, input data, a test step, an expected result, a test script, and the like, and finally form a document. Simply considered, a test case is a set of test inputs, execution conditions, and expected results tailored for a particular purpose to verify whether a particular software requirement is met.
As an optional implementation manner, the test case may be obtained from a test case set, so before step S12, a test case set creating step may be further included, which may specifically include: creating a test case set, adding one or more test cases to be executed into the test case set, wherein the sequence in the test case set represents the sequence of the test cases in the test case set.
The test executor in this step is a code tool for executing commands on the test case to complete the related tests.
Further, for the call of the test executor to the test case, the test case can be obtained from the test case set based on the ranking sequence when the idle test executor exists currently. Therefore, the test cases can be successfully tested after being called, invalid operation is avoided, the test sequence of the test cases can be adjusted based on the priority and the running condition of the test cases, the condition that the test executors cannot test after calling a certain test case and waste the resources of the test executors is avoided, and the test efficiency is improved.
Step S14: reading a reference data identification list of the test case, wherein the reference data identification list comprises data identifications of one or more pieces of test data to be referenced by the test case.
Optionally, after the test case set is created, test data to be referred to by all test cases in the test case set needs to be acquired, and a globally unique data identifier is added to each piece of test data.
Each test case is correspondingly provided with a reference data identification list, and the reference data identification list contains data identifications corresponding to all test data to be referenced when the test case is tested. Therefore, reading the reference data identification list of the test case is to determine all the test data that the test case needs to reference.
The data identification can be Tag which is a flexible classification mode of files such as logs, the Tag can also be a keyword mark which is more beneficial to search and search, and one or more tags can be added to each file such as log.
Alternatively, where the data identification is Tag, the list of reference data identifications may be a form named "TagList".
In this embodiment, through the step S14 and the sub-steps thereof, the globally unique data identifier is set to identify the test data that needs to be referred to by the test case, so as to determine all the test data that needs to be referred to by each test case during the test, so that the subsequent steps can arrange the tests of the test cases in parallel based on the mutual exclusion relationship of the test data, thereby improving the utilization efficiency of the test data, and further ensuring the overall test efficiency.
Step S16: when any data identification in the reference data identification list exists in the runtime data list, the execution sequence of the test cases is adjusted to be the last bit of the test case set, and the test data corresponding to the data identification in the runtime data list is in the executing state.
It should be understood that, before step S16, an operation data list is also created, and the operation data list is used to store and display the data identifier corresponding to the test data under test. Therefore, taking the test case with the data identifiers 56 and 68 in the reference data identifier list as an example that needs to be tested, if the data identifier 56 and the data identifier 68 do not exist in the query runtime data list, it is indicated that the test data with the data identifier 56 is being tested, and no test data with the data identifier 68 is being tested.
Alternatively, where the data is identified as Tag, the running data list may be a set of deposit hours Tag named "RunTagSet".
When any data identifier in the quote data identifier list of the inquired test case exists in the runtime data list, the test data corresponding to the data identifier existing in the runtime data list is tested, and in order to wait for the test to be finished and simultaneously test other test cases which do not need to quote the test data as soon as possible, the execution sequence of the test cases is adjusted to be the last bit of the test case set, so that the overall test efficiency can be improved.
Specifically, when the sequence of the test cases in the test case set indicates the calling sequence of the test cases, the execution sequence of the test cases is adjusted to the execution mode of the last bit of the test case set, so that the test cases can be placed at the last bit of the test case set.
Step S18: and when all the data identifications in the reference data identification list do not exist in the runtime data list, distributing the test case to an idle test executor in a plurality of preset test executors for testing, and storing all the data identifications in the reference data identification list into the runtime data list.
When all the data identifications in the reference data identification list of the inquired test case do not exist in the runtime data list, the embodiment shows that the test data corresponding to the data identification existing in the runtime data list are not in the running test state, and the test case can be tested by directly referencing the test data.
Meanwhile, when the test case is tested by the idle test executor, all the data identifications in the reference data identification list of the test case need to be stored in the runtime data list, so that the situation that other test executors test other test cases which need to reference the same test data to generate conflicts when the test case is tested is avoided.
As an optional implementation manner, please refer to fig. 2, after the test of the test case is completed, the embodiment may further include the following steps:
step S191: and storing the test result of the test case into a test result list.
The test result list is a list used for storing test operation results of test cases. Alternatively, the test result list may be named "CaseRunResult".
Step S192: all data identifications in the list of referenced data identifications are deleted from the run-time data list.
Because the test executor tests the test case according to the mutual exclusion relationship of the test data, after the test case tests, all the data identifiers in the reference data identifier list are deleted from the runtime data list, the runtime data list does not contain the data identifiers in the reference data identifier list, so that the test task can be executed when any one of the same data identifiers exists in the reference data identifier lists of other test cases.
Optionally, after all the test cases in the test case set are tested, the test results of all the test cases are stored in the test result list, and then a test report is generated based on the test result list. Based on the test report, the evaluation and judgment of the test program can be carried out more systematically and comprehensively.
For the test executor, if the test efficiency is to be improved, the use efficiency of the test executor should be noticed, so the embodiment sets the execution state of the test executor executing the test case to be running after allocating the test case to an idle test executor for testing. On the other hand, after all the data identifications in the reference data identification list are deleted from the runtime data list, the execution state of the test executor executing the test case is set to be idle.
In the steps, the multiple test executors can simultaneously perform parallel test processing on multiple test cases through the state setting of the test executors, and the test efficiency is improved in the aspect of test operation of the test cases.
The following illustrates an overall flow of the test execution method of this embodiment:
creating a plurality of test executors for automatic testing according to the pre-configuration and requirements, creating a runtime data list for storing data identifications corresponding to the running test data, creating a test result list for storing test results, and creating a test case set for storing test cases;
adding all test cases to be tested into the test case set, extracting all test data to be quoted by each test case, and adding a globally unique data identifier to each test data;
creating a reference data identification list aiming at each test case, and adding the data identification of the test data to be referenced when each test case is tested into the reference data identification list of the test case;
determining whether an idle test executor exists at present based on a scheduling program, and if so, acquiring a first test case in a current execution test case set;
reading a reference data identification list from the test case, and inquiring whether a data identification in the reference data identification list exists in a runtime data list;
when any data identifier in the reference data identifier list exists in the runtime data list, placing the case to the last of the test case set;
when the data identification in the reference data identification list does not exist in the runtime data list, calling an idle test executor to test the test case, putting the test result of the test case into a test result list after the test is finished, setting the state of the test executor to be idle, and deleting the data identification in the reference data identification list from the runtime data list;
and after all the test cases in the test case set are tested, generating a test report based on the test result list.
Referring to fig. 3, fig. 3 is a schematic overall flow chart of a test execution method according to an embodiment of the present application, where executing a test program on each test case may be a main loop step, so as to complete testing on all test cases in a test case set.
In order to cooperate with the test execution method, the present embodiment further provides a test execution device 20, please refer to fig. 4, and fig. 4 is a schematic block diagram of the test execution device according to the present embodiment.
The test execution apparatus 20 includes:
the case obtaining module 21 is configured to obtain a test case to be currently executed from the test case set;
the identification list reading module 22 is configured to read a reference data identification list of the test case, where the reference data identification list includes data identifications of one or more pieces of test data that need to be referred to by the test case;
the positioning module 23 is configured to, when any data identifier in the reference data identifier list already exists in the runtime data list, adjust the execution sequence of the test case to be the last position of the test case set, where the test data corresponding to the data identifier in the runtime data list is in an executing state;
and the test execution module 24 is configured to, when all the data identifiers in the reference data identifier list do not exist in the runtime data list, allocate the test case to an idle test executor of the preset multiple test executors for testing, and store all the data identifiers in the reference data identifier list into the runtime data list.
Optionally, the test execution apparatus 20 further includes: the identification processing module is used for storing the test result of the test case into a test result list; all data identifications in the list of referenced data identifications are deleted from the run-time data list.
Optionally, the test execution apparatus 20 further includes: the executor processing module is used for setting the execution state of the test executor executing the test case to be running after the test case is distributed to the idle test executor to be tested; and after all the data identifications in the reference data identification list are deleted from the runtime data list, setting the execution state of a test executor executing the test case to be idle.
Optionally, the test execution apparatus 20 further includes: and the report generation module is used for generating a test report based on the test result list after all the test cases in the test case set are tested.
Optionally, the test execution apparatus 20 further includes: the set creating module is used for creating a test case set, adding one or more test cases to be executed into the test case set, and the sequence in the test case set represents the sequence of the test cases in the test case set.
Optionally, the use case obtaining module 21 is specifically configured to: and when the idle test executors exist currently, acquiring the test cases from the test case set based on the arrangement sequence.
Optionally, the test execution apparatus 20 further includes: an identity addition module to: the method comprises the steps of obtaining test data which need to be quoted by all test cases in a test case set, and adding a globally unique data identifier to each piece of test data.
The embodiment of the present application further provides an electronic device, where the electronic device includes a memory and a processor, where the memory stores program instructions, and the processor executes the steps in any test execution method provided in this embodiment when reading and executing the program instructions.
It should be understood that the electronic device may be a Personal Computer (PC), a tablet PC, a smart phone, a Personal Digital Assistant (PDA), or other electronic device having a logical computing function.
The embodiment of the application also provides a readable storage medium, wherein computer program instructions are stored in the readable storage medium, and the computer program instructions are read by a processor and run to execute the steps in any test execution method.
To sum up, the embodiment of the present application provides a test execution method, an apparatus, an electronic device, and a storage medium, where the method includes: acquiring a test case to be executed currently from the test case set; reading a reference data identification list of the test case, wherein the reference data identification list comprises data identifications of one or more pieces of test data to be referred by the test case; when any data identifier in the reference data identifier list exists in a runtime data list, adjusting the execution sequence of the test case to be the last bit of a test case set, wherein test data corresponding to the data identifier in the runtime data list is in an executing state; and when all the data identifications in the reference data identification list do not exist in the runtime data list, distributing the test case to idle test executors in a plurality of preset test executors for testing, and storing all the data identifications in the reference data identification list into the runtime data list.
In the implementation mode, whether the test data which needs to be quoted by the test case is executed or not is judged based on the data identification and the runtime data list, so that the test case of which the test data which needs to be quoted is in an idle state is subjected to parallel test processing based on the quote mutual exclusion relation of the test data, the test efficiency is improved, and the test time consumption is reduced.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. The apparatus embodiments described above are merely illustrative, and for example, the block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of devices according to various embodiments of the present application. In this regard, each block in the block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams, and combinations of blocks in the block diagrams, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Therefore, the present embodiment further provides a readable storage medium, in which computer program instructions are stored, and when the computer program instructions are read and executed by a processor, the computer program instructions perform the steps of any of the block data storage methods. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a RanDom Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. A method of test execution, the method comprising:
acquiring a test case to be executed currently from the test case set;
reading a reference data identification list of the test case, wherein the reference data identification list comprises data identifications of one or more pieces of test data to be referred by the test case;
when any data identifier in the reference data identifier list exists in a runtime data list, adjusting the execution sequence of the test case to be the last bit of the test case set, wherein the test data corresponding to the data identifier in the runtime data list is in an executing state;
and when all the data identifications in the reference data identification list do not exist in the runtime data list, distributing the test case to idle test executors in a plurality of preset test executors for testing, and storing all the data identifications in the reference data identification list into the runtime data list.
2. The method of claim 1, wherein after storing all data identifiers in the list of referenced data identifiers in the runtime data list, the method further comprises:
storing the test result of the test case into a test result list;
deleting all data identifications in the list of referenced data identifications from the run-time data list.
3. The method of claim 2, wherein after said assigning the test case to an idle test executor for testing, the method further comprises:
setting the execution state of a test executor executing the test case to be in operation;
after the removing all data identifiers in the list of referenced data identifiers from the runtime data list, the method further comprises:
and setting the execution state of a test executor executing the test case to be idle.
4. The method according to any one of claims 1 to 3, wherein before the obtaining of the test case to be executed currently from the test case set, the method further comprises:
creating the test case set, adding one or more test cases to be executed into the test case set, wherein the sequence in the test case set represents the sequence of the test cases in the test case set.
5. The method of claim 4, further comprising:
and after all the test cases in the test case set are tested, generating a test report based on the test result list.
6. The method according to claim 4, wherein the obtaining of the test case to be executed currently from the test case set comprises:
and when the idle test executors exist currently, acquiring the test cases from the test case set based on the arrangement sequence.
7. The method of claim 4, further comprising:
and acquiring test data to be referred by all test cases in the test case set, and adding a globally unique data identifier to each piece of test data.
8. A test execution apparatus, the apparatus comprising:
the case acquisition module is used for acquiring the test case to be executed currently from the test case set;
the identification list reading module is used for reading a reference data identification list of the test case, wherein the reference data identification list comprises data identifications of one or more pieces of test data which need to be referred by the test case;
a bit-adjusting module, configured to adjust an execution sequence of the test case to a last bit of the test case set when any data identifier in the reference data identifier list already exists in a runtime data list, where test data corresponding to the data identifier in the runtime data list is in an executing state;
and the test execution module is used for distributing the test case to a vacant test executor in a plurality of preset test executors for testing when all the data identifications in the reference data identification list do not exist in the runtime data list, and storing all the data identifications in the reference data identification list into the runtime data list.
9. An electronic device comprising a memory having stored therein program instructions and a processor that, when executed, performs the test execution method of any one of claims 1-7.
10. A storage medium having stored thereon computer program instructions which, when executed by a processor, perform a test execution method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911299189.8A CN112988558A (en) | 2019-12-16 | 2019-12-16 | Test execution method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911299189.8A CN112988558A (en) | 2019-12-16 | 2019-12-16 | Test execution method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112988558A true CN112988558A (en) | 2021-06-18 |
Family
ID=76341969
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911299189.8A Pending CN112988558A (en) | 2019-12-16 | 2019-12-16 | Test execution method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112988558A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1967500A (en) * | 2006-04-19 | 2007-05-23 | 华为技术有限公司 | Resource using method in automatic testing process |
| US20090276663A1 (en) * | 2007-05-02 | 2009-11-05 | Rauli Ensio Kaksonen | Method and arrangement for optimizing test case execution |
| CN103186561A (en) * | 2011-12-28 | 2013-07-03 | 深圳市金蝶友商电子商务服务有限公司 | Data test method, test library generating method and related device |
| CN103391225A (en) * | 2013-07-26 | 2013-11-13 | 大连飞创信息技术有限公司 | Parallel automated testing system for test case in futures and security industry |
| US10037263B1 (en) * | 2016-07-27 | 2018-07-31 | Intuit Inc. | Methods, systems, and articles of manufacture for implementing end-to-end automation of software services |
| CN108664381A (en) * | 2017-03-27 | 2018-10-16 | 腾讯科技（深圳）有限公司 | test method and device |
| CN108932196A (en) * | 2018-06-27 | 2018-12-04 | 郑州云海信息技术有限公司 | A kind of parallel automated testing method, system, equipment and readable storage medium storing program for executing |
| CN109960645A (en) * | 2017-12-22 | 2019-07-02 | 迈普通信技术股份有限公司 | Script testing method, device and script test macro |
| CN110471833A (en) * | 2019-06-27 | 2019-11-19 | 网宿科技股份有限公司 | A kind of acquisition methods of test data, electronic equipment and storage medium |
-
2019
- 2019-12-16 CN CN201911299189.8A patent/CN112988558A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1967500A (en) * | 2006-04-19 | 2007-05-23 | 华为技术有限公司 | Resource using method in automatic testing process |
| US20090276663A1 (en) * | 2007-05-02 | 2009-11-05 | Rauli Ensio Kaksonen | Method and arrangement for optimizing test case execution |
| CN103186561A (en) * | 2011-12-28 | 2013-07-03 | 深圳市金蝶友商电子商务服务有限公司 | Data test method, test library generating method and related device |
| CN103391225A (en) * | 2013-07-26 | 2013-11-13 | 大连飞创信息技术有限公司 | Parallel automated testing system for test case in futures and security industry |
| US10037263B1 (en) * | 2016-07-27 | 2018-07-31 | Intuit Inc. | Methods, systems, and articles of manufacture for implementing end-to-end automation of software services |
| CN108664381A (en) * | 2017-03-27 | 2018-10-16 | 腾讯科技（深圳）有限公司 | test method and device |
| CN109960645A (en) * | 2017-12-22 | 2019-07-02 | 迈普通信技术股份有限公司 | Script testing method, device and script test macro |
| CN108932196A (en) * | 2018-06-27 | 2018-12-04 | 郑州云海信息技术有限公司 | A kind of parallel automated testing method, system, equipment and readable storage medium storing program for executing |
| CN110471833A (en) * | 2019-06-27 | 2019-11-19 | 网宿科技股份有限公司 | A kind of acquisition methods of test data, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10860312B1 (en) | Defect ownership assignment system and predictive analysis for codebases | |
| CN107908540B (en) | Test case creating method and device, computer equipment and medium | |
| US8966460B2 (en) | Transmission point pattern extraction from executable code in message passing environments | |
| US20160378647A1 (en) | Development supporting system | |
| US20070214391A1 (en) | Method and apparatus for testing software | |
| CN110231994B (en) | Memory analysis method, memory analysis device and computer readable storage medium | |
| CN111078481B (en) | Method, device, electronic equipment and storage medium for acquiring configuration checklist | |
| US11366713B2 (en) | System and method for automatically identifying and resolving computing errors | |
| CN105095077B (en) | User interface automated testing method and device | |
| CN114780138B (en) | Flow field simulation software code version management method and device and storage medium | |
| CN114237754A (en) | Data loading method and device, electronic equipment and storage medium | |
| CN113568836A (en) | Multi-time-series sample feature extraction method and software detection method applying same | |
| CN117009230A (en) | Accurate test method and system based on code coverage rate evaluation | |
| CN111783094A (en) | Data analysis method and device, server and readable storage medium | |
| CN116841885A (en) | Test case library-based test method and device and electronic equipment | |
| CN112988558A (en) | Test execution method and device, electronic equipment and storage medium | |
| CN114896164A (en) | Interface optimization method and device, electronic equipment and storage medium | |
| CN115705297A (en) | Code call detection method, device, computer equipment and storage medium | |
| CN110119351B (en) | Test case execution method and device | |
| CN110177006B (en) | Node testing method and device based on interface prediction model | |
| CN111143229A (en) | Software testing method and device, computer equipment and computer readable storage medium | |
| CN117573564B (en) | Method for automatically identifying differences based on gitlab code submitted log | |
| CN113254328B (en) | White box testing method, system, mobile terminal and storage medium | |
| CN117971643A (en) | Automatic source code testing method and device, storage medium and computer equipment | |
| CN117215917A (en) | Method and device for determining detection mode |
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 |