CN114036058A - Software automation test method and device - Google Patents
Software automation test method and device Download PDFInfo
- Publication number
- CN114036058A CN114036058A CN202111374812.9A CN202111374812A CN114036058A CN 114036058 A CN114036058 A CN 114036058A CN 202111374812 A CN202111374812 A CN 202111374812A CN 114036058 A CN114036058 A CN 114036058A
- Authority
- CN
- China
- Prior art keywords
- test
- test case
- page
- case
- file
- 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
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
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 provides a software automatic testing method and device, and relates to the field of software testing. The method comprises the following steps: creating a test case directory structure isomorphic with an operation page of the app to be tested; editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located; setting the name of a test case file corresponding to the sub-level page as a mark; setting a use case containing a specific mark in a child page for returning to a parent page; picking the selected test cases through the script to generate a final case library to be tested; and reading the to-be-tested use case library by the execution script and executing. The execution sequence can be set at will, and even the program can randomly arrange the use cases for execution. Redundant operation is greatly reduced, and repeated page jumping is automatically realized through a program. The execution of the repeated steps is greatly reduced, thereby reducing the execution time. Close to the user's usage scenario. The use case execution can be chosen at will.
Description
Technical Field
The invention relates to the field of software testing, in particular to a software automatic testing method and device.
Background
Automated testing is a process that translates human-driven test behavior into machine execution. Typically, after a test case is designed and passes review, the test is performed step by a tester according to the procedures described in the test case, resulting in a comparison of the actual results with the expected results.
The disadvantages of the prior art are as follows:
the execution order cannot be specified at will without manual intervention. For example: the method comprises three test cases A, B and C, wherein A needs to be logged in, B needs to be logged out, C needs to be logged in, and the cases A, B and C are sequentially executed without a method; only A, C can be executed in a group, and B can be executed in a group.
Many redundant, duplicate codes are written manually. For example: each use case needs to be written based on a home page, which requires that before each use case is actually executed, a code is written first and jumps to the current page all the way, and after the execution is finished, the code ensures that the page returns to the home page all the way.
The repeated steps are executed, and the running time is long; as in 2), redundant code steps, resulting in redundant operation steps at runtime, take more execution time.
The user use scene is not close to; or 2), the user returns to the first page after not doing some operations, and then jumps back to the corresponding page step by step.
And a specific use case cannot be selected for execution. The use cases are generally divided into a plurality of levels, for example, our company divides p0, p1, p2, p0 represents basic use cases, p1 represents common use cases, p2 represents remote functions, sometimes, in order to reduce the running time, it is desirable to only execute the p0 level use cases, and because of the problems stated in 1), the use cases cannot be automatically selected to be directly executed.
Disclosure of Invention
In order to overcome the above problems or at least partially solve the above problems, embodiments of the present invention provide a software automation testing method and apparatus.
The embodiment of the invention is realized by the following steps:
in a first aspect, the present invention provides a software automation testing method, including:
creating a test case directory structure isomorphic with an operation page of the app to be tested;
editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located;
in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark;
setting a use case containing a specific mark in a child page for returning to a parent page;
after each test case is tested, stopping on the corresponding page;
picking the selected test cases through the script to generate a final case library to be tested;
and reading the to-be-tested use case library by the execution script and executing.
Based on the first aspect, in some embodiments of the present invention, the step of creating a test case directory structure isomorphic with an operation page of the app to be tested includes:
in the test case directory structure, if the bottom tag has no relationship with the parent-child pages, a main page is virtualized to serve as the virtual parent page of the tag.
Based on the first aspect, in some embodiments of the present invention, the setting a use case containing a specific flag in the child-level page, and the step of returning to the parent-level page further includes:
each use case file has one and only one specific flag use case for returning to the parent page from the current page.
Based on the first aspect, in some embodiments of the present invention, after the specific flag use case of the virtual parent page and the corresponding child page is selected, the parent page of the virtual parent page is returned.
Based on the first aspect, in some embodiments of the present invention, after the test of each test case is completed, before the step of staying on the corresponding page, the method further includes:
and enabling the page of the App to be tested to correspond to the App page corresponding to the file of the test case.
Based on the first aspect, in some embodiments of the present invention, the step of picking the selected test case through the script and generating the final to-be-tested case library includes:
in the picking process, for the test cases of different pages, the test case corresponding to the page jump is automatically picked according to the path information.
Based on the first aspect, in some embodiments of the invention, the step of extracting comprises:
when the two use case files are executed A, B in sequence;
if A and B are in a parent-child relationship, firstly picking the test case in the A file and placing the test case in a test library, then picking the test case with the mark B from the A test file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
if A and B are grandchild relations and the execution sequence is A, C, D, B, firstly picking the test case in the A file and placing the test case in the test library, then picking the test case with the mark C from A and placing the test case in the test library, then picking the test case with the mark D from the C file and placing the test case in the test library, then picking the test case with the mark B from the D file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
if A and B are child-parent relations, firstly picking test cases in the A file and placing the test cases in a test library, then picking test cases with specific mark cases from the A test file and placing the test cases in the test library, and finally picking test cases in the B file and placing the test cases in the test library;
if A and B are in a grandchild relationship and the execution sequence is A, C, D, B, firstly picking the test case in the A file and placing the test case in the test library, then picking the test case with the specific mark case from the A test file and placing the test case in the test library, then picking the test case with the specific mark case from the C test file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
when A, B has no relationship among father, son, father, grand, according to the test case directory structure described in S1, A, B must have a common ancestor, and the processing procedure at this time is to find their common ancestor D, then walk the grand ancestor process in the order of A, D, put the picked test cases into the test library, then walk the grand process in the order of D, B, and put the picked test cases into the test library.
Based on the first aspect, in some embodiments of the present invention, the step of picking the selected test case through the script and generating the final to-be-tested case library includes:
in the process of picking, if all test cases contained in a certain test file are designated to be selected completely, the cases with specific marks are excluded.
Based on the first aspect, in some embodiments of the present invention, in the test case of the parent-level page jumping to the child-level page, the step of setting a name of a test case file corresponding to the child-level page as a flag includes:
the tagging of the jumplist page is in the steps of the use case, not the tagged use case itself.
In a second aspect, an embodiment of the present invention provides a software automation test apparatus, including:
the creation module is used for creating a test case directory structure isomorphic with the operation page of the app to be tested;
an editing module: editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located;
a flag setting module: in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark;
a specific flag setting module: setting a use case containing a specific mark in a child page for returning to a parent page;
a stay module: after each test case is tested, stopping on the corresponding page;
selecting a module: picking the selected test cases through the script to generate a final case library to be tested;
an execution module: and reading the to-be-tested use case library by the execution script and executing.
Compared with the prior art, the embodiment of the invention has at least the following advantages or beneficial effects:
the invention provides a software automation test method and a device, wherein a test case directory structure isomorphic with an operation page of app to be tested is created; editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located; in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark; setting a use case containing a specific mark in a child page for returning to a parent page; after each test case is tested, stopping on the corresponding page; picking the selected test cases through the script to generate a final case library to be tested; and reading the to-be-tested use case library by the execution script and executing. The execution sequence can be set at will, and even the program can randomly arrange the use cases for execution. Redundant operation is greatly reduced, and repeated page jumping is automatically realized through a program. The execution of the repeated steps is greatly reduced, thereby reducing the execution time. Close to the user's usage scenario. The use case execution can be chosen at will.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
FIG. 1 is a flow chart of an embodiment of a software automation test method of the present invention;
fig. 2 is a block diagram of an embodiment of an automated software testing apparatus according to the present invention.
Icon: 1. a creation module; 2. an editing module; 3. setting a mark module; 4. setting a specific mark module; 5. a stay module; 6. a picking module; 7. and executing the module.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some embodiments of the present invention, but not all embodiments. The components of embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present invention, presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
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.
In the embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other ways. The system embodiments are merely illustrative, and for example, the block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems and computer program products 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/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, 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. 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: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
Examples
Referring to fig. 1, in a first aspect, the present invention provides a software automation testing method, including:
s1: creating a test case directory structure isomorphic with an operation page of the app to be tested;
in the step, after the directory structure of the operation page of the app to be tested is obtained, a test case directory structure which is isomorphic with the operation page of the app to be tested is created, namely, the directory structure of the operation page of the app to be tested corresponds to the directory structure of the created test case one by one, the father page corresponds to the father page one by one, and the son page corresponds to the son page one by one, so that subsequent testing is facilitated.
S2: editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located;
in the step, the test case file is located in the folder, and after the name of the folder is obtained, the name of the test case file is edited, so that the name of the edited test case file is identical to the name of the folder where the test case file is located, and subsequent testing is facilitated.
S3: in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark;
in the step, in the test case of the parent-level page jumping to the child-level page, the name of the test case file corresponding to the child-level page is set as a mark for jumping to the child-level page.
S4: setting a use case containing a specific mark in a child page for returning to a parent page;
in this step, the specific flag use case may be "gosack". The purpose of this is to: redundant operation is greatly reduced, and repeated page jumping is automatically realized through a program. Greatly reducing the execution of repeated steps, thereby reducing the execution time
S5: after each test case is tested, stopping on the corresponding page;
s6: picking the selected test cases through the script to generate a final case library to be tested;
in the step, the test cases to be tested are picked, and the test cases which are not picked are not tested, so that the test time is saved, and the cases can be selected to be executed at will.
S7: and reading the to-be-tested use case library by the execution script and executing.
Based on the first aspect, in some embodiments of the present invention, the step of creating a test case directory structure isomorphic with an operation page of the app to be tested includes:
in the test case directory structure, if the bottom tag has no relationship with the parent-child pages, a main page is virtualized to serve as the virtual parent page of the tag.
In this step, in the test case directory structure, there may be special cases, for example, after similar to WeChat login, the bottom tabbar includes four tabs, which are respectively "WeChat", "Address", "found", "I", and these four tabs do not have the relationship of parent and child pages, and for the purpose of logic processing consistency, a main page is virtualized to serve as the parent page of these four tabs.
Based on the first aspect, in some embodiments of the present invention, the setting a use case containing a specific flag in the child-level page, and the step of returning to the parent-level page further includes:
each use case file has one and only one specific flag use case for returning to the parent page from the current page.
In this step, each use case file has only one specific flag use case for returning to the parent page from the current page. Redundant operation is greatly reduced, and repeated page jumping is automatically realized through a program.
Based on the first aspect, in some embodiments of the present invention, after the specific flag use case of the virtual parent page and the corresponding child page is selected, the parent page of the virtual parent page is returned.
In the step, the parent page of the virtual parent page can be returned by selecting the specific mark, and for the virtual parent page, the implementation of the goBack case of the virtual parent page and the child pages of the virtual parent page is required to be that the parent page of the virtual parent page is returned, that is, the login page is returned (the process of quitting login), so that the execution of repeated steps is greatly reduced, and the execution time is reduced.
Based on the first aspect, in some embodiments of the present invention, after the test of each test case is completed, before the step of staying on the corresponding page, the method further includes:
and enabling the page of the App to be tested to correspond to the App page corresponding to the file of the test case.
In the step, the page of the App to be tested corresponds to the App page corresponding to the file of the test case, so that the consistency of logic processing is ensured.
Based on the first aspect, in some embodiments of the present invention, the step of picking the selected test case through the script and generating the final to-be-tested case library includes:
in the picking process, for the test cases of different pages, the test case corresponding to the page jump is automatically picked according to the path information.
In the step, for the test cases of different pages, the test cases corresponding to the page jump are automatically picked according to the path information, so that the execution of repeated steps is reduced to a great extent, and the execution time is reduced.
Based on the first aspect, in some embodiments of the invention, the step of extracting comprises:
when the two use case files are executed A, B in sequence;
if A and B are in a parent-child relationship, firstly picking the test case in the A file and placing the test case in a test library, then picking the test case with the mark B from the A test file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
if A and B are grandchild relations and the execution sequence is A, C, D, B, firstly picking the test case in the A file and placing the test case in the test library, then picking the test case with the mark C from A and placing the test case in the test library, then picking the test case with the mark D from the C file and placing the test case in the test library, then picking the test case with the mark B from the D file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
if A and B are child-parent relations, firstly picking test cases in the A file and placing the test cases in a test library, then picking test cases with specific mark cases from the A test file and placing the test cases in the test library, and finally picking test cases in the B file and placing the test cases in the test library;
if A and B are in a grandchild relationship and the execution sequence is A, C, D, B, firstly picking the test case in the A file and placing the test case in the test library, then picking the test case with the specific mark case from the A test file and placing the test case in the test library, then picking the test case with the specific mark case from the C test file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
when A, B has no relationship among father, son, father, grand, according to the test case directory structure described in S1, A, B must have a common ancestor, and the processing procedure at this time is to find their common ancestor D, then walk the grand ancestor process in the order of A, D, put the picked test cases into the test library, then walk the grand process in the order of D, B, and put the picked test cases into the test library.
In the above embodiment, the execution sequence may be optionally determined, and even the program may randomly arrange the use cases for execution. Close to the user's usage scenario.
Based on the first aspect, in some embodiments of the present invention, the step of picking the selected test case through the script and generating the final to-be-tested case library includes:
in the process of picking, if all test cases contained in a certain test file are designated to be selected completely, the cases with specific marks are excluded.
Based on the first aspect, in some embodiments of the present invention, in the test case of the parent-level page jumping to the child-level page, the step of setting a name of a test case file corresponding to the child-level page as a flag includes:
the tagging of the jumplist page is in the steps of the use case, not the tagged use case itself.
Referring to fig. 2, in a second aspect, an embodiment of the present invention provides an apparatus for automatically testing software, including:
the creation module 1 is used for creating a test case directory structure isomorphic with an operation page of the app to be tested;
and an editing module 2: editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located;
setting a flag module 3: in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark;
set specific flag module 4: setting a use case containing a specific mark in a child page for returning to a parent page;
the stay module 5: after each test case is tested, stopping on the corresponding page;
the picking module 6: picking the selected test cases through the script to generate a final case library to be tested;
the execution module 7: and reading the to-be-tested use case library by the execution script and executing.
For the specific implementation of the apparatus, please refer to the above embodiments of the method, which are not described herein in detail.
In summary, the invention provides a method and a device for automatically testing software, which create a test case directory structure isomorphic with an operation page of app to be tested; editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located; in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark; setting a use case containing a specific mark in a child page for returning to a parent page; after each test case is tested, stopping on the corresponding page; picking the selected test cases through the script to generate a final case library to be tested; and reading the to-be-tested use case library by the execution script and executing. The execution sequence can be set at will, and even the program can randomly arrange the use cases for execution. Redundant operation is greatly reduced, and repeated page jumping is automatically realized through a program. The execution of the repeated steps is greatly reduced, thereby reducing the execution time. Close to the user's usage scenario. The use case execution can be chosen at will.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned.
Claims (10)
1. A software automation test method is characterized by comprising the following steps:
creating a test case directory structure isomorphic with an operation page of the app to be tested;
editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located;
in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark;
setting a use case containing a specific mark in a child page for returning to a parent page;
after each test case is tested, stopping on the corresponding page;
picking the selected test cases through the script to generate a final case library to be tested;
and reading the to-be-tested use case library by the execution script and executing.
2. The software automation test method according to claim 1, further comprising: the step of creating a test case directory structure isomorphic with the operation page of the app to be tested comprises the following steps:
in the test case directory structure, if the bottom tag has no relationship with the parent-child pages, a main page is virtualized to serve as the virtual parent page of the tag.
3. The software automation test method according to claim 1, further comprising: the step of setting a use case containing a specific flag in the child page and returning to the parent page further comprises:
each use case file has one and only one specific flag use case for returning to the parent page from the current page.
4. The software automation test method according to claim 2, further comprising: and returning the father page of the virtual father page after the special mark use cases responding to the virtual father page and the corresponding child page are selected.
5. The method according to claim 2, wherein after each test case is tested, the step of staying on the corresponding page further comprises:
and enabling the page of the App to be tested to correspond to the App page corresponding to the file of the test case.
6. The method for automatically testing software according to claim 2, wherein the step of picking the selected test case through the script to generate the final case library to be tested comprises:
in the picking process, for the test cases of different pages, the test case corresponding to the page jump is automatically picked according to the path information.
7. The method according to claim 6, wherein the step of extracting comprises:
when the two use case files are executed A, B in sequence;
if A and B are in a parent-child relationship, firstly picking the test case in the A file and placing the test case in a test library, then picking the test case with the mark B from the A test file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
if A and B are grandchild relations and the execution sequence is A, C, D, B, firstly picking the test case in the A file and placing the test case in the test library, then picking the test case with the mark C from A and placing the test case in the test library, then picking the test case with the mark D from the C file and placing the test case in the test library, then picking the test case with the mark B from the D file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
if A and B are child-parent relations, firstly picking test cases in the A file and placing the test cases in a test library, then picking test cases with specific mark cases from the A test file and placing the test cases in the test library, and finally picking test cases in the B file and placing the test cases in the test library;
if A and B are in a grandchild relationship and the execution sequence is A, C, D, B, firstly picking the test case in the A file and placing the test case in the test library, then picking the test case with the specific mark case from the A test file and placing the test case in the test library, then picking the test case with the specific mark case from the C test file and placing the test case in the test library, and finally picking the test case in the B file and placing the test case in the test library;
when A, B has no relationship among father, son, father, grand, according to the test case directory structure described in S1, A, B certainly has a common ancestor, and the processing procedure at this time is to find the common ancestor D, then walk the grand ancestor process in the order of A, D, put the picked test cases into the test library, then walk the grand process in the order of D, B, and put the picked test cases into the test library.
8. The method for automatically testing software according to claim 1, wherein the step of picking the selected test case through the script to generate the final case library to be tested comprises:
in the process of picking, if all test cases contained in a certain test file are designated to be selected completely, the cases with specific marks are excluded.
9. The method according to claim 1, wherein in the test case of the parent-level page jumping to the child-level page, the step of setting a name of a test case file corresponding to the child-level page as a flag comprises:
the tagging of the jumplist page is in the steps of the use case, not the tagged use case itself.
10. An automated software testing device, comprising:
the creation module is used for creating a test case directory structure isomorphic with the operation page of the app to be tested;
an editing module: editing the test case file in the test case directory structure to enable the name of the test case file to be the same as the name of the folder in which the test case file is located;
a flag setting module: in a test case of a parent-level page jumping to a child-level page, setting a name of a test case file corresponding to the child-level page as a mark;
a specific flag setting module: setting a use case containing a specific mark in a child page for returning to a parent page;
a stay module: after each test case is tested, stopping on the corresponding page;
selecting a module: picking the selected test cases through the script to generate a final case library to be tested;
an execution module: and reading the to-be-tested use case library by the execution script and executing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111374812.9A CN114036058A (en) | 2021-12-14 | 2021-12-14 | Software automation test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111374812.9A CN114036058A (en) | 2021-12-14 | 2021-12-14 | Software automation test method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114036058A true CN114036058A (en) | 2022-02-11 |
Family
ID=80144916
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111374812.9A Pending CN114036058A (en) | 2021-12-14 | 2021-12-14 | Software automation test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114036058A (en) |
-
2021
- 2021-12-14 CN CN202111374812.9A patent/CN114036058A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110489116B (en) | Page rendering method and device and computer storage medium | |
| CN105446865A (en) | Test method and device under multi-environment | |
| CN104794048A (en) | Automatic UI testing method and system | |
| CN111367890A (en) | Data migration method and device, computer equipment and readable storage medium | |
| CN110968505A (en) | Automatic test method and system for API (application program interface) | |
| CN111581076A (en) | System code testing method and device, computer equipment and storage medium | |
| CN104714957A (en) | List structure changing method and device | |
| US9501390B1 (en) | Enhancing automated mobile application testing | |
| CN110659393B (en) | Method and system for generating xml code | |
| CN117234520A (en) | Prefabrication generation method, equipment and medium based on Unity | |
| CN108062323B (en) | Log reading method and device | |
| CN104765775A (en) | Log saving method and device | |
| CN114036058A (en) | Software automation test method and device | |
| CN114416641A (en) | File data processing method and device, electronic equipment and storage medium | |
| CN115705297A (en) | Code call detection method, device, computer equipment and storage medium | |
| US9471569B1 (en) | Integrating information sources to create context-specific documents | |
| CN112559331A (en) | Test method and device | |
| CN106775629B (en) | Search file generation method and device | |
| CN111352824A (en) | Test method and device and computer equipment | |
| CN111104109A (en) | Method, system, medium and computer equipment for processing right-click menu on WEB page | |
| CN113495928B (en) | Data consistency checking method and device, electronic equipment and readable storage medium | |
| CN116663515B (en) | Method and device for generating dynamic reporting form | |
| CN116166617A (en) | Catalog generation method and device for combined open format document OFD | |
| CN111190898B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN113821437A (en) | Page testing method, device, equipment and medium |
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 |