CN110297767B - Automatic execution method, device, equipment and storage medium for test cases - Google Patents
Automatic execution method, device, equipment and storage medium for test cases Download PDFInfo
- Publication number
- CN110297767B CN110297767B CN201910476847.XA CN201910476847A CN110297767B CN 110297767 B CN110297767 B CN 110297767B CN 201910476847 A CN201910476847 A CN 201910476847A CN 110297767 B CN110297767 B CN 110297767B
- Authority
- CN
- China
- Prior art keywords
- test
- target
- test case
- expected effect
- expected
- 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 902
- 238000000034 method Methods 0.000 title claims abstract description 62
- 230000003631 expected effect Effects 0.000 claims abstract description 186
- 230000008569 process Effects 0.000 claims abstract description 28
- 238000001514 detection method Methods 0.000 claims description 27
- 230000004044 response Effects 0.000 claims description 15
- 238000012545 processing Methods 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 4
- 238000012827 research and development Methods 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000006243 chemical reaction Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 239000000969 carrier Substances 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012795 verification Methods 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the field of research and development management, and discloses an automatic execution method, device, equipment and storage medium for test cases, which are used for skipping the associated cases with execution errors or failure to achieve expected effects and checking test pages which do not respond for a long time, so that the execution efficiency of the cases is improved. The method comprises the following steps: reading a target configuration file; loading a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases; when an execution instruction of a target test case set is received, executing the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in the execution test process; judging whether a test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value; if the test result of the target test case does not reach the expected effect, stopping executing the target test case set; and generating a test report of the target test case set.
Description
Technical Field
The present invention relates to the field of test flow improvement, and in particular, to a method, an apparatus, a device, and a storage medium for automatically executing test cases.
Background
In the software development process or after the development, related tests are usually required to be carried out on the software, and problems are found in time, so that the software can be ensured to normally run after being released. The industry improves the testing efficiency and shortens the testing time and the labor cost by continuously researching and developing a series of automatic testing means.
At present, the mainstream page automation test tools in the industry are not full of abnormal scene processing mechanisms, and the execution errors of the test cases can cause the associated test cases to be unable to be executed, and in some processing scenes, the response speed of the test pages is slower, so that the automatic test of the pages is more required.
Disclosure of Invention
The invention provides a method, a device, equipment and a storage medium for automatically executing test cases, which are used for skipping the associated cases with execution errors or failure to achieve expected effects and checking test pages which do not respond for a long time, so that the execution efficiency of the cases is improved.
A first aspect of an embodiment of the present invention provides a method for automatically executing a test case, including: reading a target configuration file; loading a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases; when an execution instruction of the target test case set is received, executing the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in an execution test process; judging whether the test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value; if the test result of the target test case does not reach the expected effect, stopping executing the target test case set; and generating a test report of the target test case set.
Optionally, in a first implementation manner of the first aspect of the embodiment of the present invention, the determining whether the test result of the target test case reaches an expected effect includes an expected text value and an expected field value includes: detecting whether a test result of a page element on a test page reaches an expected effect or not within a preset waiting time period, and detecting whether a rear-end test result of the target test case reaches the expected effect or not; if the test result of the page element on the test page reaches the expected effect within the preset waiting time period and the back-end test result returned by the target test object reaches the expected effect, determining that the test result of the target test case reaches the expected effect; if the test result of the page element on the test page is not detected within the preset waiting time period and the back-end test result returned by the target test object reaches the expected result, determining that the test result of the target test case reaches the expected effect; if the test result of the page element on the test page is detected to not reach the expected effect within the preset waiting time, or the back-end test result returned by the target test object does not reach the expected result, determining that the test result of the target test case does not reach the expected effect.
Optionally, in a second implementation manner of the first aspect of the embodiment of the present invention, the detecting, in a preset waiting period, whether a test result of a page element on a test page reaches an expected effect includes: entering the test page and submitting a request for testing operation; after submitting the request for testing operation, starting to detect the text value of the page element by taking the preset duration as a detection period; stopping detecting whether the text value of the page element on the test page is changed when detecting that the text value of the page element is changed; counting the number of detection periods at the current moment; multiplying the preset time length by the detection period number of the current moment to obtain page response time length; when the page response time does not exceed the preset waiting time, comparing the target text value after the page element on the test page is changed with the expected text value in the expected effect; if the target text value of the changed page element is consistent with the expected text value, determining that the test result of the page element on the test page achieves the expected effect; and if the target text value of the changed page element is inconsistent with the expected text value, determining that the test result of the page element on the test page does not reach the expected effect.
Optionally, in a third implementation manner of the first aspect of the embodiment of the present invention, the detecting whether the back end test result of the target test case reaches the expected effect includes: submitting a test request to a target test object of the target test case in the back end; acquiring a test field value returned by the target test object after the target test object finishes processing the test request; comparing the test field value with an expected field value in an expected effect; if the test field value is consistent with the expected field value, determining that the rear-end test result of the target test case achieves an expected effect; if the test field value is inconsistent with the expected field value in the expected effect, determining that the back-end test result of the target test case does not reach the expected effect. Optionally, in a fourth implementation manner of the first aspect of the embodiment of the present invention, the generating a test report of the target test case set includes: recording the test result of the executed test case into the test report; and marking the test cases, the test cases and the unexecuted test cases, of which the test results reach the expected effect, in the test report, wherein the test cases, the test cases and the unexecuted test cases of which the test results do not reach the expected effect, in the target test case set.
Optionally, in a fifth implementation manner of the first aspect of the embodiment of the present invention, after the determining whether the test result of the target test case reaches the expected effect, where the expected effect includes an expected text value and an expected field value, before the generating the test report of the target test case set, the method further includes: and if the test result of the target test case reaches the expected effect, continuing to execute the rest test cases in the target test case set according to the preset execution sequence.
Optionally, in a sixth implementation manner of the first aspect of the embodiment of the present invention, after the generating the test report of the target test case set, the method further includes: prompting the failure of the execution of the target test case set; and calling a configuration file of the test case set to be tested in the waiting process, and testing the next test case set.
A second aspect of an embodiment of the present invention provides an automatic test case execution device, including: a reading unit for reading the target configuration file; the loading unit is used for loading a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases; the first execution unit is used for executing the target test cases in the target test case set according to a preset execution sequence when receiving an execution instruction of the target test case set, wherein the execution instruction is used for indicating the test case set in the execution test process; the judging unit is used for judging whether the test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value; the second execution unit is used for stopping executing the target test case set if the test result of the target test case does not reach the expected effect; and the generating unit is used for generating a test report of the target test case set.
Optionally, in a first implementation manner of the second aspect of the embodiment of the present invention, the determining unit specifically includes: the detection module is used for detecting whether the test result of the page element on the test page reaches the expected effect or not within the preset waiting time length, and detecting whether the rear-end test result of the target test case reaches the expected effect or not; the first determining module is used for determining that the test result of the target test case reaches the expected effect if the test result of the page element on the test page reaches the expected effect within the preset waiting time period and the back-end test result returned by the target test object reaches the expected effect; the second determining module is used for determining that the test result of the target test case reaches the expected effect if the test result of the page element on the test page is not detected within the preset waiting time period and the back-end test result returned by the target test object reaches the expected result; and the third determining module is used for determining that the test result of the target test case does not reach the expected effect if the test result of the page element on the test page does not reach the expected effect or the back-end test result returned by the target test object does not reach the expected result within the preset waiting time.
Optionally, in a second implementation manner of the second aspect of the embodiment of the present invention, the detection module is specifically configured to: entering the test page and submitting a request for testing operation; after submitting the request for testing operation, starting to detect the text value of the page element by taking the preset duration as a detection period; stopping detecting whether the text value of the page element on the test page is changed when detecting that the text value of the page element is changed; counting the number of detection periods at the current moment; multiplying the preset time length by the detection period number of the current moment to obtain page response time length; when the page response time does not exceed the preset waiting time, comparing the target text value after the page element on the test page is changed with the expected text value in the expected effect; if the target text value of the changed page element is consistent with the expected text value, determining that the test result of the page element on the test page achieves the expected effect; and if the target text value of the changed page element is inconsistent with the expected text value, determining that the test result of the page element on the test page does not reach the expected effect.
Optionally, in a third implementation manner of the second aspect of the embodiment of the present invention, the detection module is specifically further configured to: submitting a test request to a target test object of the target test case in the back end; acquiring a test field value returned by the target test object after the target test object finishes processing the test request; comparing the test field value with an expected field value in an expected effect; if the test field value is consistent with the expected field value, determining that the rear-end test result of the target test case achieves an expected effect; if the test field value is inconsistent with the expected field value in the expected effect, determining that the back-end test result of the target test case does not reach the expected effect.
Optionally, in a fourth implementation manner of the second aspect of the embodiment of the present invention, the generating unit is specifically configured to: recording the test result of the executed test case into the test report; and marking the test cases, the test cases and the unexecuted test cases, of which the test results reach the expected effect, in the test report, wherein the test cases, the test cases and the unexecuted test cases of which the test results do not reach the expected effect, in the target test case set.
Optionally, in a fifth implementation manner of the second aspect of the embodiment of the present invention, the second execution unit is further configured to continue to execute the remaining test cases in the target test case set according to the preset execution sequence if the test result of the target test case reaches the expected effect.
Optionally, in a sixth implementation manner of the second aspect of the embodiment of the present invention, the test case automatic execution device further includes: the prompting unit is used for prompting the failure of the execution of the target test case set; the prompting unit is also used for calling a configuration file of the test case set to be tested in the waiting process and testing the next test case set.
A third aspect of the embodiment of the present invention provides an automatic test case execution device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements the automatic test case execution method according to any one of the foregoing embodiments when executing the computer program.
A fourth aspect of the embodiments of the present invention provides a computer-readable storage medium, including instructions that, when executed on a computer, cause the computer to perform the steps of the test case automatic execution method according to any one of the embodiments described above.
In the technical scheme provided by the embodiment of the invention, the target configuration file is read; loading a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases; when an execution instruction of the target test case set is received, executing the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in an execution test process; judging whether the test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value; if the test result of the target test case does not reach the expected effect, stopping executing the target test case set; and generating a test report of the target test case set. According to the embodiment of the invention, the related use cases with wrong execution or unexpected effect are skipped, and the test pages which do not respond for a long time are checked, so that the execution efficiency of the use cases is improved.
Drawings
FIG. 1 is a schematic diagram of an embodiment of a test case automatic execution method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of another embodiment of a test case automatic execution method according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an embodiment of a test case automatic execution device according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of another embodiment of a test case automatic execution device according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an embodiment of a test case automatic execution device according to an embodiment of the present invention.
Detailed Description
The embodiment of the invention provides a method, a device, equipment and a storage medium for automatically executing test cases, which are used for skipping the associated cases with execution errors or failure to achieve expected effects and checking test pages which do not respond for a long time, so that the execution efficiency of the cases is improved.
In order to enable those skilled in the art to better understand the present invention, embodiments of the present invention will be described below with reference to the accompanying drawings.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
Referring to fig. 1, a flowchart of a method for automatically executing a test case according to an embodiment of the present invention specifically includes:
101. and reading the target configuration file.
The server reads the target configuration file. The target profile includes one or more of the following information: parameters of the target test case set, environmental parameters, browser engine identification, user name and password, and specified uniform resource location address (uniform resource locator, URL).
It should be noted that, the target configuration file is used for determining the page or frame where the target test case operation step is located, and storing parameters such as a preset execution sequence and a preset waiting duration. The tester can change the execution sequence of the target test cases in the target test case set and the waiting time of the server by adjusting the parameters in the target test file.
102. And loading a target test case set which is a plurality of associated test cases according to the target configuration file.
The server loads a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases, and in the target test case set, the associated test case sets are arranged according to a preset execution sequence.
The associated test cases are those that affect the execution result. One test case may be associated with another test case, for example, the execution conditions of one test case a include: the test case B associated with the test case A is successfully executed, and when the test case B associated with the test case A fails to execute, the test case A cannot execute. One test case may also be associated with a plurality of other test cases, for example, the execution conditions of one test case C include: the test case C is associated with the test case E and the test case F, and can be executed only after the test case E and the test case F are successfully executed.
103. When an execution instruction of the target test case set is received, executing the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in the execution test process.
When the server receives an execution instruction of the target test case set, the server executes the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in the execution test process. The target test case is a test input, execution conditions, execution steps and expected results compiled for the target test object.
When the device for testing is in an idle state, the device sends a test request to the server, wherein the test request comprises an execution instruction, and when the server receives the execution instruction, a test case set is called from a test process to test, and in the test process, the test case set is ordered according to the time of writing into the test process.
The server executes the target test case, specifically, the server initializes the test environment according to the target configuration file; the server enters a target test page according to the browser engine identification and the URL in the target configuration file; the server executes the operation steps in the target test case, including page operations such as inputting, clicking, submitting and the like.
The preset execution sequence is determined according to the association relation between target test cases in a target test case set, for example, a test case A, a test case B and a test case C are in a certain target test case set, the test case A is associated with the test case B, the test case A is successfully executed as a precondition that the test case B can be executed, the test case B is associated with the test case C, the test case B is successfully executed as a precondition that the test case C can be executed, and then the preset execution sequence is that the test case A is executed first, the test case B is executed, and the test case C is executed finally.
104. And judging whether the test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value.
The server judges whether the test result of the target test case reaches an expected effect, wherein the expected effect comprises an expected text value and an expected field value. The test result is a result displayed on a test page or a test result returned by a related target test object in the back end after the server executes the target test case, and the expected effect is an expected value preset according to the requirement.
Specifically, the server determines whether the test result of the page element on the test page reaches the expected effect within the preset waiting time, and determines whether the rear-end test result of the target test case reaches the expected effect, and the two verification modes verify whether the test result of the target test case reaches the expected result. It should be noted that, the text values displayed on the front page are represented in different manners at the back end, and are converted at the front end and the back end through a preset conversion interface, for example, in an application, the back end adopts a data exchange format of a JS object numbered musical notation (java script object notation, JSON), the text value "hello" of a certain element on the test page, and the field value of the JSON format corresponding to the back end is "a".
105. And if the test result of the target test case does not reach the expected effect, stopping executing the target test case set.
If the test result of the target test case does not reach the expected effect, the server stops executing the test cases related to the target test case in the target test case set, for example, in a certain test case set, the test case A is related to the test case B and the test case C, and the preset execution sequence is that the test case A is executed first, then the test case B is executed, and finally the test case C is executed; when the test result of the test case B does not reach the expected effect, the server does not execute the test case C any more. If the test result of the target test case reaches the expected effect, the server executes the test cases related to the target test case in the target test case set according to the preset execution sequence.
It should be noted that, if the test result of the target test case does not reach the expected effect, the server prompts the execution failure of the target test case set and reads the configuration file of the test case set to be tested in the waiting process, and the server performs the test of the next test case set. The server may prompt in text and popup window, or may prompt in voice, or may prompt in other modes, which is not limited herein.
106. And generating a test report of the target test case set.
The method comprises the steps that a server generates a test report of a target test case set, and specifically, the server records test results of executed test cases into the test report; the server marks the test cases with the expected effect of the test results in the target test case set, the test cases with the expected effect of the test results not, and the unexecuted test cases in the test report, so that a tester can distinguish the test cases with errors and analyze the reasons of the errors.
It should be noted that, the test report records the test result of the target test case in the form of a chart, text, or other forms, which are not limited herein.
The embodiment of the invention is used for skipping the associated use case with the execution error or the failure to achieve the expected effect and checking the test page which does not respond for a long time, thereby improving the execution efficiency of the use case.
Referring to fig. 2, another embodiment of the test case automatic execution method in the embodiment of the present invention includes:
201. and reading the target configuration file.
The server reads the target configuration file. The target profile includes one or more of the following information: parameters of the target test case set, environmental parameters, browser engine identification, user name and password, and URL.
It should be noted that, the target configuration file is used for determining the page or frame where the target test case operation step is located, and storing parameters such as a preset execution sequence and a preset waiting duration. The tester can change the execution sequence of the target test cases in the target test case set and the waiting time of the server by adjusting the parameters in the target test file.
202. And loading a target test case set which is a plurality of associated test cases according to the target configuration file.
The server loads a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases, and in the target test case set, the associated test case sets are arranged according to a preset execution sequence.
The associated test cases are those that affect the execution result. One test case may be associated with another test case, for example, the execution conditions for one test case a include: the test case B associated with the test case A is successfully executed, and when the test case B associated with the test case A fails to execute, the test case A cannot execute. One test case may also be associated with a plurality of other test cases, for example, the execution conditions of one test case C include: the test case C is associated with the test case E and the test case F, and can be executed only after the test case E and the test case F are successfully executed.
203. When an execution instruction of the target test case set is received, executing the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in the execution test process.
When the server receives an execution instruction of the target test case set, the server executes the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in the execution test process. The target test case is a test input, execution conditions, execution steps and expected results compiled for the target test object.
When the device for testing is in an idle state, the device sends a test request to the server, wherein the test request comprises an execution instruction, and when the server receives the execution instruction, a test case set is called from a test process to test, and in the test process, the test case set is ordered according to the time of writing into the test process.
The server executes the target test case, specifically, the server initializes the test environment according to the target configuration file; the server enters a target test page according to the browser engine identification and the URL in the target configuration file; the server executes the operation steps in the target test case, including page operations such as inputting, clicking, submitting and the like.
The preset execution sequence is determined according to the association relation between target test cases in a target test case set, for example, a test case A, a test case B and a test case C are in a certain target test case set, the test case A is associated with the test case B, the test case A is successfully executed as a precondition that the test case B can be executed, the test case B is associated with the test case C, the test case B is successfully executed as a precondition that the test case C can be executed, and then the preset execution sequence is that the test case A is executed first, the test case B is executed, and the test case C is executed finally.
204. And detecting whether the test result of the page element on the test page reaches the expected effect or not within the preset waiting time, and detecting whether the rear-end test result of the target test case reaches the expected effect or not.
The server detects whether the test result of the page element on the test page reaches the expected effect or not within the preset waiting time, and detects whether the back-end test result of the target test case reaches the expected effect or not. The server detects whether the test result of the page element on the test page reaches the expected effect within the preset waiting time length specifically comprises the following steps: when executing the target test case, the server enters a test page and submits a request for testing operation; after the server submits a request for testing operation, the server starts to detect the text value of the page element by taking the preset duration as a detection period; when the server detects that the text value of the page element is changed, the server stops detecting whether the text value of the page element on the test page is changed or not; the server counts the number of detection periods at the current moment; the server multiplies the preset time length by the detection period number at the current moment to obtain page response time length; when the page response time does not exceed the preset waiting time, the server compares the target text value after the page element on the test page is changed with the expected text value in the expected effect; if the target text value after the page element is changed is consistent with the expected text value, the server determines that the test result of the page element on the test page achieves the expected effect; if the target text value after the page element is changed is inconsistent with the expected text value, the server determines that the test result of the page element on the test page does not reach the expected effect.
For example, page response refers to a change in the relevant values of the original elements on the page or the presence of non-original elements on the page after the server submits the request for page operation. For example, the month report on the page is originally in an uncommitted state, and when the month report is filled in and the submitting operation is executed, the uncommitted state of the month report on the page becomes a state to be confirmed, and the response of the page means that the uncommitted state of the month report on the page becomes the state to be confirmed. The server detects whether the back-end test result of the target test case reaches the expected effect or not, and specifically, the server submits a test request to a target test object of the target test case in the back-end; the server acquires a test field value returned after the target test object finishes processing the test request; the server compares the test field value with an expected field value in the expected effect; if the test field value is consistent with the expected field value, the server determines that the back-end test result of the target test case achieves the expected effect; if the test field value is inconsistent with the expected field value in the expected effect, the server determines that the back-end test result of the target test case does not reach the expected effect.
It should be noted that, the text displayed on the front page has different representation modes at the back end, and is converted at the front end and the back end through a preset conversion interface, for example, in a certain application, the back end adopts a JSON data exchange format, the text "hello" displayed on the test page, and the JSON format corresponding to the back end is "a".
It can be understood that the server detects whether the test result of the page element on the test page reaches the expected effect within the preset waiting time period, and the server detects whether the back-end test result of the target test case reaches the expected effect, but the time period when the server obtains the test result of the page element is longer than the time period when the server obtains the back-end test result.
205. If the test result of the page element on the test page reaches the expected effect within the preset waiting time, and the back-end test result returned by the target test object reaches the expected effect, determining that the test result of the target test case reaches the expected effect.
If the server detects that the test result of the page element on the test page reaches the expected effect within the preset waiting time, and the back-end test result returned by the target test object reaches the expected effect, the server determines that the test result of the target test case reaches the expected effect. For example, the server detects that the text value of the page element becomes the expected text value within a preset waiting period of 5 seconds: "to be validated", and the test field value returned by the target test object in the backend is the expected field value: and c, the server confirms that the test result of the target test case achieves the expected effect.
After determining that the test result of the target test case reaches the expected effect, the server continues to execute the remaining test cases in the target test case set according to the preset execution sequence until the target test case set is normally tested or any of the remaining test cases does not reach the expected effect, and generates a test report of the target test case.
206. If the test result of the page element on the test page is not detected within the preset waiting time, and the back-end test result returned by the target test object reaches the expected result, determining that the test result of the target test case reaches the expected effect.
If the server does not detect the test result of the page element on the test page within the preset waiting time, and the back-end test result returned by the target test object reaches the expected result, the server determines that the test result of the target test case reaches the expected effect. For example, the server does not detect a text value change of the page element within a preset waiting period of 5 seconds, and the test field value returned by the target test object in the backend is the expected field value: and c, the server confirms that the test result of the target test case achieves the expected effect.
After determining that the test result of the target test case reaches the expected effect, the server continues to execute the remaining test cases in the target test case set according to the preset execution sequence until the target test case set is normally tested or the test result of any remaining test case does not reach the expected effect, and generates a test report of the target test case.
207. If the test result of the page element on the test page is detected to not reach the expected effect within the preset waiting time, or the back-end test result returned by the target test object does not reach the expected result, determining that the test result of the target test case does not reach the expected effect.
If the server detects that the test result of the page element on the test page does not reach the expected effect within the preset waiting time, or the back-end test result returned by the target test object does not reach the expected result, the server determines that the test result of the target test case does not reach the expected effect. For example, the server detects that the text value of the page element is changed to "to be changed" within a preset waiting period of 5 seconds, and does not change to the expected text value: the test field value returned by the target test object in the back end is: "b", not the expected field value: and c, the server confirms that the test result of the target test case does not reach the expected effect.
208. And if the test result of the target test case does not reach the expected effect, stopping executing the target test case set.
If the test result of the target test case does not reach the expected effect, the server stops executing the test case related to the target test case in the target test case set, for example, in a certain test case set, the test case A is related to the test case B and the test case C, and the preset execution sequence is that the test case A is executed first, then the test case B is executed, and finally the test case C is executed; when the test result of the test case B does not reach the expected effect, the server does not execute the test case C any more; if the test result of the target test case reaches the expected effect, the server executes the test cases related to the target test case in the target test case set according to the preset execution sequence.
It should be noted that, if the test result of the target test case does not reach the expected effect, the server will prompt that the execution of the target test case fails and call the configuration file of the test case set to be tested in the waiting process, and the server will test the next test case set. The server may prompt in text and popup window, or may prompt in voice, or may prompt in other modes, which is not limited herein.
209. And generating a test report of the target test case set.
The server generates a test report of the target test case set, and specifically, the server records the test result of the executed test case into the test report; the server marks the test cases with the expected effect of the test results in the target test case set, the test cases with the expected effect of the test results not, and the unexecuted test cases in the test report, so that a tester can distinguish the test cases with errors and analyze the reasons of the errors.
It should be noted that, the test report records the test result of the target test case in the form of a chart, text, or other forms, which are not limited herein.
The embodiment of the invention is used for skipping the associated use case with the execution error or the failure to achieve the expected effect and checking the test page which does not respond for a long time, thereby improving the execution efficiency of the use case.
The method for automatically executing the test case in the embodiment of the present invention is described above, and the device for automatically executing the test case in the embodiment of the present invention is described below, referring to fig. 3, and one embodiment of the device for automatically executing the test case in the embodiment of the present invention includes:
A reading unit 301, configured to read a target configuration file;
the loading unit 302 is configured to load a target test case set according to the target configuration file, where the target test case set is a plurality of associated test cases;
the first execution unit 303 is configured to execute, when receiving an execution instruction of the target test case set, a target test case in the target test case set according to a preset execution sequence, where the execution instruction is used to instruct to execute the test case set in a test process;
a judging unit 304, configured to judge whether the test result of the target test case reaches an expected effect, where the expected effect includes an expected text value and an expected field value;
the second execution unit 305 is configured to stop executing the target test case set if the test result of the target test case does not reach the expected effect;
and the generating unit 306 is configured to generate a test report of the target test case set.
The embodiment of the invention is used for skipping the associated use case with the execution error or the failure to achieve the expected effect and checking the test page which does not respond for a long time, thereby improving the execution efficiency of the use case.
Referring to fig. 4, an embodiment of a test case automatic execution device according to an embodiment of the present invention includes:
A reading unit 301, configured to read a target configuration file;
the loading unit 302 is configured to load a target test case set according to the target configuration file, where the target test case set is a plurality of associated test cases;
the first execution unit 303 is configured to execute, when receiving an execution instruction of the target test case set, a target test case in the target test case set according to a preset execution sequence, where the execution instruction is used to instruct to execute the test case set in a test process;
a judging unit 304, configured to judge whether the test result of the target test case reaches an expected effect, where the expected effect includes an expected text value and an expected field value;
the second execution unit 305 is configured to stop executing the target test case set if the test result of the target test case does not reach the expected effect;
and the generating unit 306 is configured to generate a test report of the target test case set.
Optionally, the judging unit 304 specifically includes:
the detection module 3041 is configured to detect, within a preset waiting period, whether a test result of a page element on a test page reaches an expected effect, and detect whether a back-end test result of the target test case reaches the expected effect;
A first determining module 3042, configured to determine that, if a test result of a page element on the test page reaches an expected effect within the preset waiting duration and a back end test result returned by the target test object reaches an expected effect, the test result of the target test case reaches the expected effect;
a second determining module 3043, configured to determine that, if the test result of the page element on the test page is not detected within the preset waiting duration and the back end test result returned by the target test object reaches the expected result, the test result of the target test case reaches the expected effect;
and a third determining module 3044, configured to determine that the test result of the target test case does not reach the expected effect if it is detected that the test result of the page element on the test page does not reach the expected effect within the preset waiting duration, or the back end test result returned by the target test object does not reach the expected result.
Optionally, the detection module 3041 is specifically configured to:
entering the test page and submitting a request for testing operation; after submitting the request for testing operation, starting to detect the text value of the page element by taking the preset duration as a detection period; stopping detecting whether the text value of the page element on the test page is changed when detecting that the text value of the page element is changed; counting the number of detection periods at the current moment; multiplying the preset time length by the detection period number of the current moment to obtain page response time length; when the page response time does not exceed the preset waiting time, comparing the target text value after the page element on the test page is changed with the expected text value in the expected effect; if the target text value of the changed page element is consistent with the expected text value, determining that the test result of the page element on the test page achieves the expected effect; and if the target text value of the changed page element is inconsistent with the expected text value, determining that the test result of the page element on the test page does not reach the expected effect.
Optionally, the detection module 3041 is specifically further configured to:
submitting a test request to a target test object of the target test case in the back end; acquiring a test field value returned by the target test object after the target test object finishes processing the test request; comparing the test field value with an expected field value in an expected effect; if the test field value is consistent with the expected field value, determining that the rear-end test result of the target test case achieves an expected effect; if the test field value is inconsistent with the expected field value in the expected effect, determining that the back-end test result of the target test case does not reach the expected effect.
Optionally, the generating unit 306 is specifically configured to: recording the test result of the executed test case into the test report; and marking the test cases, the test cases and the unexecuted test cases, of which the test results reach the expected effect, in the test report, wherein the test cases, the test cases and the unexecuted test cases of which the test results do not reach the expected effect, in the target test case set.
Optionally, the second execution unit 305 is further configured to:
and if the test result of the target test case reaches the expected effect, continuing to execute the rest test cases in the target test case set according to the preset execution sequence.
Optionally, the test case automatic execution device further includes:
a prompting unit 307, configured to prompt that the target test case set fails to execute;
the prompting unit 307 is further configured to call a configuration file of the test case set to be tested in the waiting process, and perform a test of the next test case set.
The embodiment of the invention is used for skipping the associated use case with the execution error or the failure to achieve the expected effect and checking the test page which does not respond for a long time, thereby improving the execution efficiency of the use case.
The test case automatic execution device in the embodiment of the present invention is described in detail from the point of view of the modularized functional entity in fig. 3 to 4 above, and the test case automatic execution device in the embodiment of the present invention is described in detail from the point of view of hardware processing below.
Fig. 5 is a schematic structural diagram of an automatic test case execution device according to an embodiment of the present invention, where the automatic test case execution device 500 may have a relatively large difference due to different configurations or performances, and may include one or more processors (central processing units, CPU) 501 (e.g., one or more processors) and a memory 509, and one or more storage media 508 (e.g., one or more mass storage devices) storing application programs 507 or data 506. Wherein the memory 509 and storage medium 508 may be transitory or persistent storage. The program stored on the storage medium 508 may include one or more modules (not shown), each of which may include a series of instruction operations in the automatic execution device for the test case. Still further, the processor 501 may be configured to communicate with a storage medium 508 and execute a series of instruction operations in the storage medium 508 on the test case automatic execution device 500.
The test case automatic execution device 500 may also include one or more power supplies 502, one or more wired or wireless network interfaces 503, one or more input/output interfaces 504, and/or one or more operating systems 505, such as Windows Serve, mac OS X, unix, linux, freeBSD, and the like. Those skilled in the art will appreciate that the test case automatic execution device structure shown in FIG. 5 does not constitute a limitation of the test case automatic execution device, and may include more or fewer components than shown, or may combine certain components, or may have a different arrangement of components. The processor 501 may perform the functions of the reading unit 301, the loading unit 302, the first executing unit 303, the judging unit 304, the second executing unit 305, the generating unit 306, and the prompting unit 307 in the above-described embodiments.
The following describes each component of the test case automatic execution device specifically with reference to fig. 5:
the processor 501 is a control center of the test case automatic execution device, and can perform processing according to a set information processing method. The processor 501 connects the various parts of the overall test case automatic execution device using various interfaces and lines, and performs various functions and processes data of the test case automatic execution device by running or executing software programs and/or modules stored in the memory 509 and calling data stored in the memory 509, thereby realizing the automatic execution of the test case. Both the storage medium 508 and the memory 509 are carriers for storing data, in embodiments the storage medium 508 may be referred to as an inner memory with a small storage capacity but a fast speed, and the memory 509 may be an outer memory with a large storage capacity but a slow storage speed.
The memory 509 may be used to store software programs and modules, and the processor 501 executes various functional applications and data processing of the test case automatic execution device 500 by running the software programs and modules stored in the memory 509. The memory 509 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as executing a target test case, etc.), and the like; the storage data area may store data created according to the use of the test case automatic execution device (such as test reports, etc.), and the like. In addition, the memory 509 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. The test case automatic execution method program and the received data stream provided in the embodiment of the present invention are stored in the memory, and when necessary, the processor 501 is called from the memory 509.
When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, twisted pair), or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., an optical disk), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present invention, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiment of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied essentially or in part or all of the technical solution or in part in the form of a software product stored in a storage medium, including instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims (10)
1. An automatic test case execution method is characterized by comprising the following steps:
reading a target configuration file;
loading a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases;
when an execution instruction of the target test case set is received, executing the target test case in the target test case set according to a preset execution sequence, wherein the execution instruction is used for indicating the test case set in an execution test process;
judging whether the test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value;
If the test result of the target test case does not reach the expected effect, stopping executing the target test case set;
generating a test report of the target test case set;
judging whether the test result of the target test case reaches an expected effect, wherein the expected effect comprises an expected text value and an expected field value and comprises the following steps:
detecting whether a test result of a page element on a test page reaches an expected effect or not within a preset waiting time period, and detecting whether a rear-end test result of the target test case reaches the expected effect or not;
if the test result of the page element on the test page reaches the expected effect within the preset waiting time period and the back-end test result returned by the target test object reaches the expected effect, determining that the test result of the target test case reaches the expected effect;
if the test result of the page element on the test page is not detected within the preset waiting time period and the back-end test result returned by the target test object reaches the expected result, determining that the test result of the target test case reaches the expected effect;
if the test result of the page element on the test page is detected to not reach the expected effect within the preset waiting time, or the back-end test result returned by the target test object does not reach the expected result, determining that the test result of the target test case does not reach the expected effect;
The detecting whether the test result of the page element on the test page reaches the expected effect within the preset waiting time length comprises the following steps:
entering the test page and submitting a request for testing operation;
after submitting the request for testing operation, starting to detect the text value of the page element by taking the preset duration as a detection period;
stopping detecting the text value of the page element on the test page when detecting the text value of the page element is changed;
counting the number of detection periods at the current moment;
multiplying the preset time length by the detection period number of the current moment to obtain page response time length;
when the page response time does not exceed the preset waiting time, comparing the target text value after the page element on the test page is changed with the expected text value in the expected effect;
if the target text value of the changed page element is consistent with the expected text value, determining that the test result of the page element on the test page achieves the expected effect;
and if the target text value of the changed page element is inconsistent with the expected text value, determining that the test result of the page element on the test page does not reach the expected effect.
2. The method for automatically executing test cases according to claim 1, wherein the detecting whether the back-end test result of the target test case reaches the expected effect comprises:
submitting a test request to a target test object of the target test case in the back end;
acquiring a test field value returned by the target test object after the target test object finishes processing the test request;
comparing the test field value with an expected field value in an expected effect;
if the test field value is consistent with the expected field value, determining that the rear-end test result of the target test case achieves an expected effect;
if the test field value is inconsistent with the expected field value in the expected effect, determining that the back-end test result of the target test case does not reach the expected effect.
3. The method for automatically executing test cases according to claim 1 or claim 2, wherein the generating the test report of the target test case set includes:
recording the test result of the executed test case into the test report;
and marking the test cases, the test cases and the unexecuted test cases, of which the test results reach the expected effect, in the test report, wherein the test cases, the test cases and the unexecuted test cases of which the test results do not reach the expected effect, in the target test case set.
4. The method according to claim 1 or claim 2, wherein after the determining whether the test result of the target test case reaches the expected effect, the expected effect including an expected text value and an expected field value, before the generating the test report of the target test case set, the method further comprises:
and if the test result of the target test case reaches the expected effect, continuing to execute the rest test cases in the target test case set according to the preset execution sequence.
5. The test case automatic execution method according to claim 1 or claim 2, wherein after the generating the test report of the target test case set, the method further comprises:
prompting the failure of the execution of the target test case set;
and calling a configuration file of the test case set to be tested in the waiting process, and testing the next test case set.
6. An automatic test case execution device, comprising:
a reading unit for reading the target configuration file;
the loading unit is used for loading a target test case set according to the target configuration file, wherein the target test case set is a plurality of associated test cases;
The first execution unit is used for executing the target test cases in the target test case set according to a preset execution sequence when receiving an execution instruction of the target test case set, wherein the execution instruction is used for indicating the test case set in the execution test process;
the judging unit is used for judging whether the test result of the target test case reaches an expected effect or not, wherein the expected effect comprises an expected text value and an expected field value;
the second execution unit is used for stopping executing the target test case set if the test result of the target test case does not reach the expected effect;
the generating unit is used for generating a test report of the target test case set;
the judging unit specifically includes:
the detection module is used for detecting whether the test result of the page element on the test page reaches the expected effect or not within the preset waiting time length, and detecting whether the rear-end test result of the target test case reaches the expected effect or not;
the first determining module is used for determining that the test result of the target test case reaches the expected effect if the test result of the page element on the test page reaches the expected effect within the preset waiting time period and the back-end test result returned by the target test object reaches the expected effect;
The second determining module is used for determining that the test result of the target test case reaches the expected effect if the test result of the page element on the test page is not detected within the preset waiting time period and the back-end test result returned by the target test object reaches the expected result;
a third determining module, configured to determine that, if the test result of the page element on the test page does not reach the expected effect or the test result of the back end returned by the target test object does not reach the expected result within the preset waiting duration, the test result of the target test case does not reach the expected effect;
the detection module is specifically used for:
entering the test page and submitting a request for testing operation;
after submitting the request for testing operation, starting to detect the text value of the page element by taking the preset duration as a detection period;
stopping detecting the text value of the page element on the test page when detecting the text value of the page element is changed;
counting the number of detection periods at the current moment;
multiplying the preset time length by the detection period number of the current moment to obtain page response time length;
When the page response time does not exceed the preset waiting time, comparing the target text value after the page element on the test page is changed with the expected text value in the expected effect;
if the target text value of the changed page element is consistent with the expected text value, determining that the test result of the page element on the test page achieves the expected effect;
and if the target text value of the changed page element is inconsistent with the expected text value, determining that the test result of the page element on the test page does not reach the expected effect.
7. The test case automatic execution device of claim 6, wherein the detection module is further specifically configured to:
submitting a test request to a target test object of the target test case in the back end;
acquiring a test field value returned by the target test object after the target test object finishes processing the test request;
comparing the test field value with an expected field value in an expected effect;
if the test field value is consistent with the expected field value, determining that the rear-end test result of the target test case achieves an expected effect;
if the test field value is inconsistent with the expected field value in the expected effect, determining that the back-end test result of the target test case does not reach the expected effect.
8. The test case automatic execution device according to claim 6 or claim 7, wherein the generating unit is specifically configured to:
recording the test result of the executed test case into the test report;
and marking the test cases, the test cases and the unexecuted test cases, of which the test results reach the expected effect, in the test report, wherein the test cases, the test cases and the unexecuted test cases of which the test results do not reach the expected effect, in the target test case set.
9. An automatic test case execution device, comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the automatic test case execution method according to any one of claims 1 to 5 when executing the computer program.
10. A computer readable storage medium comprising instructions which, when executed on a computer, cause the computer to perform the test case automatic execution method of any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910476847.XA CN110297767B (en) | 2019-06-03 | 2019-06-03 | Automatic execution method, device, equipment and storage medium for test cases |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910476847.XA CN110297767B (en) | 2019-06-03 | 2019-06-03 | Automatic execution method, device, equipment and storage medium for test cases |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110297767A CN110297767A (en) | 2019-10-01 |
| CN110297767B true CN110297767B (en) | 2024-02-23 |
Family
ID=68027483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910476847.XA Active CN110297767B (en) | 2019-06-03 | 2019-06-03 | Automatic execution method, device, equipment and storage medium for test cases |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110297767B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111177014B (en) * | 2020-02-24 | 2023-02-24 | 重庆长安新能源汽车科技有限公司 | Software automatic test method, system and storage medium |
| CN111767217B (en) * | 2020-06-24 | 2024-02-02 | 中国工商银行股份有限公司 | JS unit test case generation method and device |
| CN112231219A (en) * | 2020-10-22 | 2021-01-15 | 中国平安人寿保险股份有限公司 | Automatic test monitoring method, device, equipment and storage medium |
| CN112699040B (en) * | 2020-12-30 | 2024-02-23 | 深圳前海微众银行股份有限公司 | Pressure testing method, device, equipment and computer readable storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102523052A (en) * | 2011-12-01 | 2012-06-27 | 无锡中星微电子有限公司 | Testing method and testing device |
| CN103377101A (en) * | 2012-04-18 | 2013-10-30 | 百度在线网络技术（北京）有限公司 | Testing system and testing method |
| CN105955880A (en) * | 2016-04-22 | 2016-09-21 | 乐视控股（北京）有限公司 | Method and system for distributing automated test case, and distribution server |
| US9514037B1 (en) * | 2015-12-16 | 2016-12-06 | International Business Machines Corporation | Test program scheduling based on analysis of test data sets |
| CN107729234A (en) * | 2017-09-29 | 2018-02-23 | 郑州云海信息技术有限公司 | The scheduling of test case performs method, apparatus, equipment and computer-readable storage medium |
| CN108255738A (en) * | 2018-04-09 | 2018-07-06 | 平安普惠企业管理有限公司 | Automated testing method, device, computer equipment and storage medium |
| CN109032870A (en) * | 2018-08-03 | 2018-12-18 | 百度在线网络技术（北京）有限公司 | Method and apparatus for test equipment |
| CN109324969A (en) * | 2018-09-27 | 2019-02-12 | 平安普惠企业管理有限公司 | Generation method, device, computer equipment and the storage medium of test report |
| CN109597753A (en) * | 2018-10-22 | 2019-04-09 | 平安科技（深圳）有限公司 | Method, apparatus, computer equipment and the storage medium of interface testing |
| CN109726093A (en) * | 2017-10-27 | 2019-05-07 | 伊姆西Ip控股有限责任公司 | Method, equipment and computer program product for implementation of test cases |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10365994B2 (en) * | 2017-04-24 | 2019-07-30 | Facebook, Inc. | Dynamic scheduling of test cases |
-
2019
- 2019-06-03 CN CN201910476847.XA patent/CN110297767B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102523052A (en) * | 2011-12-01 | 2012-06-27 | 无锡中星微电子有限公司 | Testing method and testing device |
| CN103377101A (en) * | 2012-04-18 | 2013-10-30 | 百度在线网络技术（北京）有限公司 | Testing system and testing method |
| US9514037B1 (en) * | 2015-12-16 | 2016-12-06 | International Business Machines Corporation | Test program scheduling based on analysis of test data sets |
| CN105955880A (en) * | 2016-04-22 | 2016-09-21 | 乐视控股（北京）有限公司 | Method and system for distributing automated test case, and distribution server |
| CN107729234A (en) * | 2017-09-29 | 2018-02-23 | 郑州云海信息技术有限公司 | The scheduling of test case performs method, apparatus, equipment and computer-readable storage medium |
| CN109726093A (en) * | 2017-10-27 | 2019-05-07 | 伊姆西Ip控股有限责任公司 | Method, equipment and computer program product for implementation of test cases |
| CN108255738A (en) * | 2018-04-09 | 2018-07-06 | 平安普惠企业管理有限公司 | Automated testing method, device, computer equipment and storage medium |
| CN109032870A (en) * | 2018-08-03 | 2018-12-18 | 百度在线网络技术（北京）有限公司 | Method and apparatus for test equipment |
| CN109324969A (en) * | 2018-09-27 | 2019-02-12 | 平安普惠企业管理有限公司 | Generation method, device, computer equipment and the storage medium of test report |
| CN109597753A (en) * | 2018-10-22 | 2019-04-09 | 平安科技（深圳）有限公司 | Method, apparatus, computer equipment and the storage medium of interface testing |
Non-Patent Citations (1)
| Title |
|---|
| 软件回归测试中的自动测试生成方法;曾强 等;计算机应用研究(第06期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110297767A (en) | 2019-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110297767B (en) | Automatic execution method, device, equipment and storage medium for test cases | |
| CN109474488B (en) | Interface testing method and device and computer equipment | |
| CN108595329B (en) | Application testing method and device and computer storage medium | |
| CN110502366B (en) | Case execution method, device, equipment and computer readable storage medium | |
| CN112231219A (en) | Automatic test monitoring method, device, equipment and storage medium | |
| CN109522181B (en) | Performance test method, device and equipment of distributed storage system | |
| CN110908920A (en) | Interface function testing method and device and related components | |
| CN110569194A (en) | interface testing method and device, electronic equipment and storage medium | |
| CN110688063A (en) | Method, device, equipment and medium for screening Raid slow disc | |
| CN110740071A (en) | network interface monitoring method, device and system | |
| US9842044B2 (en) | Commit sensitive tests | |
| CN111309602A (en) | Software testing method, device and system | |
| CN103810086A (en) | Method, device and system for processing website causing browser breakdown | |
| CN112506751B (en) | Method, device, equipment and medium for contrast test of overall performance of server | |
| CN111026947B (en) | Crawler method and embedded crawler implementation method based on browser | |
| CN110309057B (en) | Automatic script-based flow project testing method and related equipment | |
| CN112416735A (en) | Application program detection method and device, terminal equipment and storage medium | |
| CN111666200A (en) | Testing method and terminal for time consumption of cold start of PC software | |
| CN115757138A (en) | Method and device for determining script abnormal reason, storage medium and electronic equipment | |
| CN111400245B (en) | Art resource migration method and device | |
| CN111198798B (en) | Service stability measuring method and device | |
| CN111209197B (en) | Application continuous integration test method, system, equipment and storage medium | |
| CN112558982A (en) | Code detection method and device and computer equipment | |
| CN113485919A (en) | Test method, test device and computer readable storage medium | |
| CN108845932B (en) | Unit testing method and device of network library, storage medium and terminal |
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 |