CN112181809B - Graphic user interface automatic test method based on multiple positioning methods - Google Patents
Graphic user interface automatic test method based on multiple positioning methods Download PDFInfo
- Publication number
- CN112181809B CN112181809B CN202010959746.0A CN202010959746A CN112181809B CN 112181809 B CN112181809 B CN 112181809B CN 202010959746 A CN202010959746 A CN 202010959746A CN 112181809 B CN112181809 B CN 112181809B
- Authority
- CN
- China
- Prior art keywords
- positioning
- tested
- test
- positioning method
- name
- 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
- 238000000034 method Methods 0.000 title claims abstract description 180
- 238000010998 test method Methods 0.000 title claims abstract description 19
- 238000012360 testing method Methods 0.000 claims abstract description 132
- 238000013515 script Methods 0.000 claims abstract description 20
- 230000009286 beneficial effect Effects 0.000 abstract description 3
- 230000008569 process Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000000361 pesticidal effect Effects 0.000 description 2
- 235000013421 Kaempferia galanga Nutrition 0.000 description 1
- 244000062241 Kaempferia galanga Species 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006872 improvement Effects 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/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Human Computer Interaction (AREA)
- Debugging And Monitoring (AREA)
Abstract
A graphical user interface automated test method based on a plurality of positioning methods, the method comprising the steps of: identifying the system environment to be tested; judging whether the system environment to be tested meets the test requirement or not; if yes, executing an automatic test script; if not, exiting the system environment to be tested, and outputting a test report; calling a positioning library corresponding to the element to be tested; element positioning is carried out by using a plurality of positioning methods in the positioning library; and outputting the test report according to the positioning result. The graphic user interface automatic test method based on the multiple positioning methods has the following beneficial effects: (1) The method can be applied to domestic Galaxy kylin operation systems, and enriches the use objects of graphical user interface automatic test technology of the Linux operation systems; (2) The method adopts a graphical user interface positioning mode, enhances the portability of scripts, can also operate on the arm, x86 and other architectures, and expands the application range of the test method.
Description
Technical Field
The invention belongs to the technical field of automatic testing of graphical user interfaces, and particularly relates to an automatic testing method of a graphical user interface based on multiple positioning methods.
Background
The automatic test of the user interface is a process of converting the manual test into machine execution, the user operation such as clicking, right clicking, dragging and the like is realized by simulating a mouse through positioning each element of the user interface, and the automatic test of the application to be tested is realized through judging the expected result by the test program, wherein the positioning technology is a key technology for realizing the automatic test.
The known positioning method of the existing automatic test tool is relatively single, and the single positioning method is easily interfered by other factors. For example, the positioning is performed through the button attribute of the element, the requirement on the bottom layer writing of the application is high in the actual testing process, the attribute of part of the button cannot be captured, and even most of the applications cannot be automatically tested according to the method, especially in the system desktop environment with more diversified applications. The existing user interface automation test is mostly applied to windows application and web application, is not much effectively applied to a Linux operating system, and is also in need of automation test on the UI level of the Linux operating system today when the development of the domestic Linux operating system is increasingly strong.
The existing user interface automation test technology is mostly suitable for browser applications, namely BS architecture applications, and can effectively aim at automation test tools and method index numbers of client applications (namely CS architecture applications). The CS architecture application tends to be more complex than the BS architecture application, the browser application tends to be unified in underlying code, and all of its interface element properties can be exposed typically by the browser's own tools. However, CS architecture applications are relatively much more complex, different software may be implemented in different programming languages, requiring different tools to expose their element properties. Currently, in a domestic Linux operating system, available resources for automatic testing tools, testing methods and the like of a user interface are very limited. A single test tool does not meet the vast needs of automated testing.
The Chinese patent of the invention, "an improved method based on UI automation test positioning elements" (application number CN 201911026311.4) discloses an improved method of UI automation test positioning elements, which comprises the following steps: defining parameters in an excel table, finding a name capable of uniquely determining the element by searching an interface element, adding the name into the excel table, and determining a positioning element according to a type parameter and an index parameter. The invention only proposes an improved method of data driven testing in browser applications, but the invention does not address how to obtain element properties in client applications.
The Chinese patent 'UI-based CS architecture software automatic test method and system' (application number CN 201810282603.3) discloses a UI-based CS architecture software automatic test method and system, wherein the method comprises the following steps: identifying names and identification information of all components of the tested software to form a description file; acquiring running environment data of tested software; forming a test case execution list according to the names of the test case scripts, and executing the test case scripts according to the name sequence of the scripts in the list; and calling a verification result script to generate a test report of the tested software. The invention only provides a method for testing CS architecture application by data driving, but does not solve the problem of how to deal with automatic test positioning failure on a Linux system.
The Chinese patent of the invention (a GUI automatic test method and system) (application number CN 201710618522.1) discloses a GUI automatic test method and system, wherein the method comprises the following steps: analyzing the related information of the automatic test of each case through the generated test cases; creating/updating a picture library; and (3) carrying out automatic test to obtain a result picture, and comparing the picture with a standard picture to obtain a test result. The invention only introduces a method for asserting and comparing test results by using pictures, and focuses on data driving, but does not solve the problem of positioning failure in the process of executing automatic use cases.
The Chinese patent of the invention, "a GUI automatic test method and system" (application number CN 201610056854.0) discloses an automatic test method and system, which comprises the steps of searching a plurality of to-be-tested controls of a test object by using a control ID, carrying out a first mark on the to-be-tested controls which cannot be positioned normally by using the control ID, and searching the to-be-tested controls which cannot be positioned normally by using the control ID based on the first mark; and carrying out second identification on the control to be tested which still cannot be positioned normally after the first identification is carried out, searching the control to be tested which still cannot be positioned normally after the first identification is carried out based on the second identification, and finally carrying out automatic test on the test object based on the searched control to be tested. The method and the device solve the problems that the control ID does not exist in the browser application page, the control IDs are all the same or the control cannot be searched because the page is too complex, but the problem that the control cannot be positioned in the non-browser application is not solved.
Disclosure of Invention
In order to solve the above problems, the present invention provides a graphic user interface automatic test method based on a plurality of positioning methods, the method comprising the steps of:
Identifying the system environment to be tested;
judging whether the system environment to be tested meets the test requirement or not;
if yes, executing an automatic test script;
If not, exiting the system environment to be tested, and outputting a test report;
Calling a positioning library corresponding to the element to be tested;
element positioning is carried out by using a plurality of positioning methods in the positioning library;
and outputting the test report according to the positioning result.
Preferably, the identifying the system environment to be tested includes the steps of:
Identifying the platform type of the system to be tested;
Identifying a resolution of the system to be tested;
Identifying the version type of the system to be tested;
and identifying the resource record of the system to be tested.
Preferably, the step of determining whether the system environment to be tested meets the test requirement includes the steps of:
Acquiring a test requirement;
acquiring the platform type, resolution, version type and resource record of the system to be tested;
Judging whether the platform type, the resolution, the version model and the resource record simultaneously meet the test requirement;
if yes, judging that the system environment to be tested meets the test requirement;
If not, judging that the system environment to be tested does not meet the test requirement.
Preferably, before the identifying the system environment to be tested, the method further comprises the steps of:
Setting the test requirement;
Writing the automatic test script;
creating a positioning library corresponding to the element to be tested;
Adding a picture name positioning method, a button name positioning method and a window address positioning method into the positioning library;
acquiring element attribute values of the elements to be tested;
Storing the element attribute values sequentially according to the picture name positioning method, the button name positioning method and the window address positioning method, and sequentially obtaining a picture name label, a button name label and a window address label;
and sequentially placing the picture name label, the button name label and the window address label into a null set, and obtaining a global label corresponding to the element to be tested.
Preferably, the element positioning using the plurality of positioning methods in the positioning library includes the steps of:
acquiring a window address positioning method, a picture name positioning method and a button name positioning method in the positioning library;
positioning the element to be tested by using the window address positioning method;
Judging whether the window address positioning method is successfully positioned;
if yes, continuing to use the picture name positioning method to position the element to be tested;
If not, the log is saved, and the current use case test is terminated;
judging whether the picture name positioning method is successful in positioning or not;
if yes, ending the current positioning operation and continuing the current use case test;
If not, storing a log, and positioning the element to be tested by using the button name positioning method;
Judging whether the button name positioning method is successfully positioned;
if yes, ending the current positioning operation and continuing the current use case test;
If not, the log is saved, and the current use case test is terminated.
Preferably, the positioning the element to be tested by using the window address positioning method includes the steps of:
calling a window address tag in a global tag corresponding to the element to be tested;
judging whether the window address of the window to which the element to be tested belongs is successfully acquired or not;
if yes, judging that the window address positioning method is successful;
if not, judging that the window address positioning method fails.
Preferably, the positioning the element to be tested by using the picture name positioning method includes the steps of:
invoking a picture name tag in a global tag corresponding to the element to be tested;
judging whether the picture name of the picture to which the element to be tested belongs is successfully acquired or not;
If yes, judging that the picture name positioning method is successful;
if not, judging that the picture name positioning method fails.
Preferably, the positioning the element to be tested using the button name positioning method includes the steps of:
Invoking a button name label in the global label corresponding to the element to be tested;
judging whether the button name of the button to which the element to be tested belongs is successfully acquired or not;
If yes, judging that the button name positioning method is successful;
if not, judging that the button name positioning method fails.
The graphic user interface automatic test method based on the multiple positioning methods has the following beneficial effects:
(1) The method can be applied to domestic Galaxy kylin operation systems, and enriches the use objects of graphical user interface automatic test technology of the Linux operation systems;
(2) The method has the advantages that the graphical user interface positioning mode is adopted, the portability of scripts is enhanced, the scripts can also run on the arm, x86 and other architectures, and the application range of the testing method is widened;
(3) The method has the advantages that the method adopts a plurality of positioning methods to be matched, the pesticide effect of the test is effectively avoided, the positioning failure rate in the test process is reduced, and the test execution rate is improved;
(4) The test method has wide coverage and meets the diversity of the software to be tested.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions of the prior art, the drawings which are used in the description of the embodiments or the prior art will be briefly described, it being obvious that the drawings in the description below are only some embodiments of the invention, and that other drawings can be obtained according to these drawings without inventive faculty for a person skilled in the art.
Fig. 1 is a schematic flow chart of an automatic testing method of a graphical user interface based on a plurality of positioning methods.
Detailed Description
The objects, technical solutions and advantages of the present invention will become more apparent by the following detailed description of the present invention with reference to the accompanying drawings. It should be understood that the description is only illustrative and is not intended to limit the scope of the invention. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the present invention.
Referring to fig. 1, in an embodiment of the present application, the present application provides a method for automatically testing a graphical user interface based on a plurality of positioning methods, the method comprising the steps of:
S1: identifying the system environment to be tested;
S2: judging whether the system environment to be tested meets the test requirement or not;
S3: if yes, executing an automatic test script;
S4: if not, exiting the system environment to be tested, and outputting a test report;
s5: calling a positioning library corresponding to the element to be tested;
s6: element positioning is carried out by using a plurality of positioning methods in the positioning library;
S7: and outputting the test report according to the positioning result.
When the graphical user interface automatic test method based on the multiple positioning methods is used for carrying out automatic test operation on the graphical user interface in the system environment to be tested, firstly identifying the system environment to be tested, and judging whether the system environment to be tested meets the test requirement; when the test requirement is met, executing an automatic test script, and automatically testing the system to be tested; when the test requirement is not met, the system environment to be tested is withdrawn, and a test report is output; when executing the automatic test script, specifically, calling a positioning library corresponding to the element to be tested, then using a plurality of positioning methods in the positioning library to position the element, and finally outputting the test report according to the positioning result.
In the embodiment of the application, the graphical user interface automatic test method based on the multiple positioning methods can be applied to a Linux system, in particular to a domestic Galangal kylin operating system.
In the embodiment of the present application, the identifying the system environment to be tested in step S1 includes the steps of:
Identifying the platform type of the system to be tested;
Identifying a resolution of the system to be tested;
Identifying the version type of the system to be tested;
and identifying the resource record of the system to be tested.
In the embodiment of the application, identifying the system environment to be tested comprises identifying the platform type, resolution, version model and resource record of the system to be tested. Specifically, some platforms cannot support the running of the automated test smoothly, and the type of the platform of the system to be tested is identified to reduce the occurrence probability that the automated test operation cannot run smoothly due to the mismatching of the platforms, and the type of the platform can be arm, x86 and the like; the resolution recognition is used for preventing inaccurate positioning caused by lower resolution than the requirement when the picture and the coordinates are used for positioning the element to be tested; version type identification is to consider that the system interfaces of different version types have differences; the system resource record is used for recording the change of each resource of the system before and after the automatic test, so that the situation that the change is not objectively reflected on the test report due to the change of some resources before and after the test is avoided, and the overall consideration of the system to be tested can be improved.
In the embodiment of the present application, the step S2 of determining whether the system environment to be tested meets the test requirement includes the steps of:
Acquiring a test requirement;
acquiring the platform type, resolution, version type and resource record of the system to be tested;
Judging whether the platform type, the resolution, the version model and the resource record simultaneously meet the test requirement;
if yes, judging that the system environment to be tested meets the test requirement;
If not, judging that the system environment to be tested does not meet the test requirement.
In the embodiment of the application, the test requirements can be set according to personal preference of a tester or according to the requirements of smooth running of an automatic test script, when judging whether the system environment to be tested meets the test requirements, the platform type, resolution, version type and resource record of the system environment to be tested need to be acquired firstly and then are compared with the platform type, resolution, version type and resource record set in the test requirements in a one-to-one correspondence mode respectively, and when the four items meet the requirements at the same time, the system environment to be tested is considered to meet the test requirements; and if any one of the four items does not meet the requirements, the system environment to be tested is considered to not meet the test requirements.
In the embodiment of the present application, before the identifying the system environment to be tested in step S1, the method further includes the steps of:
Setting the test requirement;
Writing the automatic test script;
creating a positioning library corresponding to the element to be tested;
Adding a picture name positioning method, a button name positioning method and a window address positioning method into the positioning library;
acquiring element attribute values of the elements to be tested;
Storing the element attribute values sequentially according to the picture name positioning method, the button name positioning method and the window address positioning method, and sequentially obtaining a picture name label, a button name label and a window address label;
and sequentially placing the picture name label, the button name label and the window address label into a null set, and obtaining a global label corresponding to the element to be tested.
In the embodiment of the application, before the system environment to be tested is identified, test requirements are set, an automatic test script is written, a positioning library corresponding to the element to be tested is created, and a plurality of positioning methods are set in the positioning library. Specifically, the various positioning methods include: a picture name positioning method, a button name positioning method and a window address positioning method, then obtaining element attribute values of elements to be tested, storing the element attribute values according to the picture name positioning method, the button name positioning method and the window address positioning method in sequence, and obtaining a picture name label, a button name label and a window address label in sequence; and then sequentially placing the picture name label, the button name label and the window address label into a null set, and obtaining a global label corresponding to the element to be tested. For example, a picture name positioning method, a button name positioning method and a window address positioning method are configured in a positioning library corresponding to the existing element to be tested a, and a picture name label, a button name label and a window address label obtained according to the methods are respectively and sequentially:
"pic_name": "tests/imgs/a.png", "button_name": "File" and "Win_id": "123456", while the global label for element a under test is: tag_a= { "pic_name": "tests/imgs/a.png", "button_name": "File" and "Win_id": "123456"}.
In the embodiment of the present application, the element positioning in step S6 using the plurality of positioning methods in the positioning library includes the steps of:
acquiring a window address positioning method, a picture name positioning method and a button name positioning method in the positioning library;
positioning the element to be tested by using the window address positioning method;
Judging whether the window address positioning method is successfully positioned;
if yes, continuing to use the picture name positioning method to position the element to be tested;
If not, the log is saved, and the current use case test is terminated;
judging whether the picture name positioning method is successful in positioning or not;
if yes, ending the current positioning operation and continuing the current use case test;
If not, storing a log, and positioning the element to be tested by using the button name positioning method;
Judging whether the button name positioning method is successfully positioned;
if yes, ending the current positioning operation and continuing the current use case test;
If not, the log is saved, and the current use case test is terminated.
In the embodiment of the application, when a plurality of positioning methods are used for positioning the element to be tested, firstly, a window address positioning method, a picture name positioning method and a button name positioning method in a positioning library corresponding to the element are obtained; then using the window address positioning method to position the element to be tested; after the window address positioning method is finished, judging whether the window address positioning method is successfully positioned; if the window address positioning method is successfully positioned, continuing to position the element to be tested by using the picture name positioning method; if the window address positioning method is not successfully positioned, a log is saved, and the current use case test is terminated; after the picture name positioning method is finished, judging whether the picture name positioning method is successfully positioned; if the picture name positioning method is successfully positioned, ending the current positioning operation and continuing the current use case test; if the picture name positioning method is not successful in positioning, a log is saved, and the button name positioning method is used for positioning the element to be tested; after the button name positioning method is finished, judging whether the button name positioning method is successfully positioned; if the button name positioning method is successfully positioned, ending the current positioning operation and continuing the current use case test; if the button name positioning method is not successfully positioned, a log is saved, and the current use case test is terminated.
In the embodiment of the present application, the positioning the element to be tested by using the window address positioning method includes the steps of:
calling a window address tag in a global tag corresponding to the element to be tested;
judging whether the window address of the window to which the element to be tested belongs is successfully acquired or not;
if yes, judging that the window address positioning method is successful;
if not, judging that the window address positioning method fails.
In the embodiment of the application, when the window address positioning method is carried out on the element to be tested, firstly, the window address label in the global label corresponding to the element to be tested is called, namely, win_id is called: "123456", then judging whether the window address of the window to which the element to be tested belongs is successfully acquired, namely "123456" is successfully acquired, if so, judging that the window address positioning method is successful; if "123456" is not successfully acquired, it is determined that the window address location method failed.
In the embodiment of the present application, the positioning the element to be tested by using the picture name positioning method includes the steps of:
invoking a picture name tag in a global tag corresponding to the element to be tested;
judging whether the picture name of the picture to which the element to be tested belongs is successfully acquired or not;
If yes, judging that the picture name positioning method is successful;
if not, judging that the picture name positioning method fails.
In the embodiment of the application, when the picture name positioning method is carried out on the element to be tested, firstly, a picture name label in a global label corresponding to the element to be tested is called, namely, pic_name is called: "tests/imgs/a.png", then judging whether the picture name of the picture to which the element to be tested belongs is successfully acquired, namely "tests/imgs/a.png" is successfully acquired, if so, judging that the picture name positioning method is successful; if 'tests/imgs/a.png' is not successfully acquired, judging that the picture name positioning method fails.
In the embodiment of the present application, the positioning the element to be tested by using the button name positioning method includes the steps of:
Invoking a button name label in the global label corresponding to the element to be tested;
judging whether the button name of the button to which the element to be tested belongs is successfully acquired or not;
If yes, judging that the button name positioning method is successful;
if not, judging that the button name positioning method fails.
In the embodiment of the application, when the Button name positioning method is carried out on the element to be tested, firstly, the Button name label in the global label corresponding to the element to be tested is called, namely, the button_name is called: judging whether the button name of the button to which the element to be tested belongs is successfully acquired, namely whether the file is successfully acquired, and if so, judging that the button name positioning method is successful; if the file is not successfully acquired, judging that the button name positioning method fails.
The graphic user interface automatic test method based on the multiple positioning methods has the following beneficial effects:
(1) The method can be applied to domestic Galaxy kylin operation systems, and enriches the use objects of graphical user interface automatic test technology of the Linux operation systems;
(2) The method has the advantages that the graphical user interface positioning mode is adopted, the portability of scripts is enhanced, the scripts can also run on the arm, x86 and other architectures, and the application range of the testing method is widened;
(3) The method has the advantages that the method adopts a plurality of positioning methods to be matched, the pesticide effect of the test is effectively avoided, the positioning failure rate in the test process is reduced, and the test execution rate is improved;
(4) The test method has wide coverage and meets the diversity of the software to be tested.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explanation of the principles of the present invention and are in no way limiting of the invention. Accordingly, any modification, equivalent replacement, improvement, etc. made without departing from the spirit and scope of the present invention should be included in the scope of the present invention. Furthermore, the appended claims are intended to cover all such changes and modifications that fall within the scope and boundary of the appended claims, or equivalents of such scope and boundary.
Claims (6)
1. A graphical user interface automated test method based on a plurality of positioning methods, the method comprising the steps of:
Identifying the system environment to be tested;
judging whether the system environment to be tested meets the test requirement or not;
if yes, executing an automatic test script;
If not, exiting the system environment to be tested, and outputting a test report;
Calling a positioning library corresponding to the element to be tested;
element positioning is carried out by using a plurality of positioning methods in the positioning library, wherein a window address positioning method, a picture name positioning method and a button name positioning method in the positioning library are acquired;
positioning the element to be tested by using the window address positioning method;
Judging whether the window address positioning method is successfully positioned;
if yes, continuing to use the picture name positioning method to position the element to be tested;
If not, the log is saved, and the current use case test is terminated;
judging whether the picture name positioning method is successful in positioning or not;
if yes, ending the current positioning operation and continuing the current use case test;
If not, storing a log, and positioning the element to be tested by using the button name positioning method;
Judging whether the button name positioning method is successfully positioned;
if yes, ending the current positioning operation and continuing the current use case test;
If not, the log is saved, and the current use case test is terminated;
the method further comprises the steps of:
Setting the test requirement;
Writing the automatic test script;
creating a positioning library corresponding to the element to be tested;
Adding a picture name positioning method, a button name positioning method and a window address positioning method into the positioning library;
acquiring element attribute values of the elements to be tested;
Storing the element attribute values sequentially according to the picture name positioning method, the button name positioning method and the window address positioning method, and sequentially obtaining a picture name label, a button name label and a window address label;
sequentially placing the picture name label, the button name label and the window address label into a null set, and obtaining a global label corresponding to the element to be tested;
and outputting the test report according to the positioning result.
2. The method for automatically testing a graphical user interface based on a plurality of positioning methods according to claim 1, wherein the step of identifying a system environment to be tested comprises the steps of:
Identifying the platform type of the system to be tested;
Identifying a resolution of the system to be tested;
Identifying the version type of the system to be tested;
and identifying the resource record of the system to be tested.
3. The method for automatically testing a graphical user interface based on a plurality of positioning methods according to claim 1, wherein the step of determining whether the system environment to be tested meets the test requirement comprises the steps of:
Acquiring a test requirement;
acquiring the platform type, resolution, version type and resource record of the system to be tested;
Judging whether the platform type, the resolution, the version model and the resource record simultaneously meet the test requirement;
if yes, judging that the system environment to be tested meets the test requirement;
If not, judging that the system environment to be tested does not meet the test requirement.
4. The method for automatically testing a graphical user interface based on a plurality of positioning methods according to claim 1, wherein the positioning the element to be tested using the window address positioning method comprises the steps of:
calling a window address tag in a global tag corresponding to the element to be tested;
judging whether the window address of the window to which the element to be tested belongs is successfully acquired or not;
if yes, judging that the window address positioning method is successful;
if not, judging that the window address positioning method fails.
5. The method for automatically testing a graphical user interface based on a plurality of positioning methods according to claim 1, wherein the positioning the element to be tested using the picture name positioning method comprises the steps of:
invoking a picture name tag in a global tag corresponding to the element to be tested;
judging whether the picture name of the picture to which the element to be tested belongs is successfully acquired or not;
If yes, judging that the picture name positioning method is successful;
if not, judging that the picture name positioning method fails.
6. The method for automatically testing a graphical user interface based on a plurality of positioning methods according to claim 1, wherein the positioning the element to be tested using the button name positioning method comprises the steps of:
Invoking a button name label in the global label corresponding to the element to be tested;
judging whether the button name of the button to which the element to be tested belongs is successfully acquired or not;
If yes, judging that the button name positioning method is successful;
if not, judging that the button name positioning method fails.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010959746.0A CN112181809B (en) | 2020-09-14 | 2020-09-14 | Graphic user interface automatic test method based on multiple positioning methods |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010959746.0A CN112181809B (en) | 2020-09-14 | 2020-09-14 | Graphic user interface automatic test method based on multiple positioning methods |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112181809A CN112181809A (en) | 2021-01-05 |
| CN112181809B true CN112181809B (en) | 2024-06-11 |
Family
ID=73921903
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010959746.0A Active CN112181809B (en) | 2020-09-14 | 2020-09-14 | Graphic user interface automatic test method based on multiple positioning methods |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181809B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933735A (en) * | 2015-12-30 | 2017-07-07 | 优信拍（北京）信息科技有限公司 | Test case update method and device |
| CN107832230A (en) * | 2017-12-04 | 2018-03-23 | 中国工商银行股份有限公司 | Method of testing, equipment and system based on data tuning |
| CN108536584A (en) * | 2018-03-12 | 2018-09-14 | 广东睿江云计算股份有限公司 | A kind of automated testing method based on Sikuli |
| CN109032936A (en) * | 2018-07-13 | 2018-12-18 | 陈希 | A kind of desktop automatic test development approach and system |
| CN110727603A (en) * | 2019-10-25 | 2020-01-24 | 重庆誉存大数据科技有限公司 | Improved method for automatically testing positioning elements based on UI (user interface) |
| CN111538650A (en) * | 2020-03-24 | 2020-08-14 | 中国平安人寿保险股份有限公司 | User interface automatic testing method and related equipment |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110214107A1 (en) * | 2010-03-01 | 2011-09-01 | Experitest, Ltd. | Method and system for testing graphical user interfaces |
| US10846206B2 (en) * | 2017-06-14 | 2020-11-24 | T-Mobile Usa, Inc. | Adaptive software testing |
-
2020
- 2020-09-14 CN CN202010959746.0A patent/CN112181809B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106933735A (en) * | 2015-12-30 | 2017-07-07 | 优信拍（北京）信息科技有限公司 | Test case update method and device |
| CN107832230A (en) * | 2017-12-04 | 2018-03-23 | 中国工商银行股份有限公司 | Method of testing, equipment and system based on data tuning |
| CN108536584A (en) * | 2018-03-12 | 2018-09-14 | 广东睿江云计算股份有限公司 | A kind of automated testing method based on Sikuli |
| CN109032936A (en) * | 2018-07-13 | 2018-12-18 | 陈希 | A kind of desktop automatic test development approach and system |
| CN110727603A (en) * | 2019-10-25 | 2020-01-24 | 重庆誉存大数据科技有限公司 | Improved method for automatically testing positioning elements based on UI (user interface) |
| CN111538650A (en) * | 2020-03-24 | 2020-08-14 | 中国平安人寿保险股份有限公司 | User interface automatic testing method and related equipment |
Non-Patent Citations (1)
| Title |
|---|
| DCS软件界面自动化测试技术研究与应用;刘红刚;黄太新;宋立新;孟广国;;自动化博览;20170415(第04期);80-84 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112181809A (en) | 2021-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10698702B1 (en) | Automating interactions with software user interface | |
| US11755919B2 (en) | Analytics for an automated application testing platform | |
| US9846634B2 (en) | Visual graphical user interface verification | |
| US9720799B1 (en) | Validating applications using object level hierarchy analysis | |
| Leotta et al. | Visual vs. DOM-based web locators: An empirical study | |
| CN105468779B (en) | A kind of client Web application capture and playback system and method towards browser compatibility detection | |
| US11042472B2 (en) | Authoring automated test suites using artificial intelligence | |
| US8904358B1 (en) | Methods, systems, and articles of manufacture for synchronizing software verification flows | |
| US20050204343A1 (en) | Automated test system for testing an application running in a windows-based environment and related methods | |
| US20090217250A1 (en) | Graphical user interface metadata evolution tool | |
| CN104391797A (en) | GUI (graphical user interface) widget identification method and device | |
| CN110515848B (en) | Automatic test system and automatic test method | |
| CN108536593A (en) | CS Framework Softwares automated testing method based on UI and system | |
| CN110058998B (en) | Software testing method and device | |
| KR20090084905A (en) | Method and system for graphical user interface testing | |
| US11436133B2 (en) | Comparable user interface object identifications | |
| US20200327043A1 (en) | System and a method for automated script generation for application testing | |
| CN112732587A (en) | Method and device for acquiring automatic test log, electronic equipment and storage medium | |
| CN112506778A (en) | WEB user interface automatic test method, device, equipment and storage medium | |
| Ran et al. | Automated visual testing for mobile apps in an industrial seting | |
| US11422917B2 (en) | Deriving software application dependency trees for white-box testing | |
| CN112231206A (en) | Script editing method for application program test, computer readable storage medium and test platform | |
| US11403209B2 (en) | Rendering GUI test object of application under test to reflect test information | |
| CN116719736A (en) | Test case generation method and device for testing software interface | |
| CN112181809B (en) | Graphic user interface automatic test method based on multiple positioning methods |
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 |