CN113778898B - User interface automatic test method and device, electronic equipment and storage medium - Google Patents
User interface automatic test method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113778898B CN113778898B CN202111130065.4A CN202111130065A CN113778898B CN 113778898 B CN113778898 B CN 113778898B CN 202111130065 A CN202111130065 A CN 202111130065A CN 113778898 B CN113778898 B CN 113778898B
- Authority
- CN
- China
- Prior art keywords
- test
- page
- tested
- automatic
- automation
- 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
- 238000010998 test method Methods 0.000 title claims description 13
- 238000012360 testing method Methods 0.000 claims abstract description 459
- 238000000034 method Methods 0.000 claims abstract description 113
- 238000013515 script Methods 0.000 claims abstract description 52
- 238000000926 separation method Methods 0.000 claims abstract description 13
- 238000012795 verification Methods 0.000 claims abstract description 8
- 230000006870 function Effects 0.000 claims description 53
- 230000008569 process Effects 0.000 claims description 40
- 238000004806 packaging method and process Methods 0.000 claims description 26
- 230000006399 behavior Effects 0.000 claims description 21
- 238000004590 computer program Methods 0.000 claims description 10
- 238000012544 monitoring process Methods 0.000 claims description 8
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 230000005856 abnormality Effects 0.000 claims description 5
- 238000013142 basic testing Methods 0.000 claims description 5
- 238000010276 construction Methods 0.000 claims description 4
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 238000013461 design Methods 0.000 description 15
- 230000008859 change Effects 0.000 description 10
- 238000012423 maintenance Methods 0.000 description 10
- 238000012545 processing Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- XSQUKJJJFZCRTK-NJFSPNSNSA-N UREA C 14 Chemical compound N[14C](N)=O XSQUKJJJFZCRTK-NJFSPNSNSA-N 0.000 description 3
- 230000007547 defect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000006872 improvement Effects 0.000 description 3
- 230000000007 visual effect Effects 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000013524 data verification Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000011990 functional testing Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 206010036618 Premenstrual syndrome Diseases 0.000 description 1
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000002349 favourable effect Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 229910052711 selenium Inorganic materials 0.000 description 1
- 239000011669 selenium Substances 0.000 description 1
- 230000000391 smoking effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/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
-
- 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
Abstract
The application discloses a user interface automatic testing method, a device, electronic equipment and a readable storage medium. The method comprises the steps of pre-building an automatic test frame and deploying the automatic test frame in an automatic test environment; the automated test framework encapsulates the page element locations in the page object based on the page object model and adopts a separation mode of UI layer operation, business layer regression and data layer verification. When a UI test instruction is received, acquiring a test case and a corresponding UI automation script, wherein the UI automation scripts are independent from each other; and calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case. The method and the device realize the definition of the test service flow, not only can precisely count the passing rate of the test case, but also can reduce the test cost of the whole user interface, have less code redundancy and are beneficial to improving the quality of software products.
Description
Technical Field
The present disclosure relates to the field of automated testing technologies, and in particular, to a method and apparatus for automatically testing a user interface, an electronic device, and a readable storage medium.
Background
With the rapid development and the general application of the internet technology, various software products are not separated from daily work and life, the software products need to rely on a User Interface (UI) to complete man-machine interaction, user pages are directly related to the use experience of users on the software products, and the advantages and disadvantages of the User interfaces concern the use value of the whole software products. Therefore, in the process of developing software, a user interface test is an indispensable stage, and in order to improve the software test efficiency, an automatic test application is generated.
It can be understood that, although the software automation test is realized, the UI test is still the link that consumes the most manpower of the test team currently, and most of the full-time testers perform the UI test in daily life, so that the manpower cost is high. For some complicated user interface tests, the test business flow of the related technology is unclear, the maintenance cost of the test frame is higher, and the statistics result of the passing rate of the test cases is inaccurate. Regardless of how complex and important the technical architecture is, the end point the user contacts is the front-end user interface. The existing software products have a plurality of front-end business logics and specification patterns besides background logics, and the availability of the products at the user side cannot be effectively proved by simply relying on a background interface and simple unit test. In addition, when the related technology performs automatic test, the related technology needs to rely on the current test environment, and cannot independently run the test, so that a large amount of invalid service data can be generated, and the system memory is occupied; and the automatic test framework code is redundant, so that the quality of the software product is low.
Disclosure of Invention
The application provides a user interface automatic test method, a device, electronic equipment and a readable storage medium, which realize the definition of a test service flow and can precisely count the passing rate of test cases. The investment of labor cost of a test team is reduced, the maintenance cost of the test framework is reduced, and the test cost of the whole user interface is effectively reduced. And the redundancy of the automatic test framework codes is reduced, and the quality of the software product is improved.
In order to solve the technical problems, the embodiment of the invention provides the following technical scheme:
in one aspect, an embodiment of the present invention provides a method for automatically testing a user interface, including:
pre-building an automatic test frame, and deploying the automatic test frame in an automatic test environment; the automatic test framework positions and encapsulates page elements in a page object based on a page object model, and adopts a separation mode of UI layer operation, business layer regression and data layer verification;
when a UI test instruction is received, acquiring a test case and a corresponding UI automation script, wherein the UI automation scripts are independent from each other;
and calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case.
Optionally, the building an automated test framework includes:
packaging a browser driver and a target tool into the automated test framework;
uniformly packaging a public operation method into basic test classes to form test public classes for operating the page elements to be tested, inheriting the test public classes by the test classes corresponding to the pages to be tested, and managing the page elements of the test classes through the browser driver;
and packaging the preset behavior operation method into a webpage test tool.
Optionally, the packaging the browser driver and the target tool into the automated test framework includes:
packaging the browser driver into the automated test framework;
any one or any combination of an Excel driven read-write data tool, an Email mail tool, a logging tool, a configuration tool and a common path storage tool is packaged into the automated test framework.
Optionally, the building an automated test framework includes:
and packaging the automatic login method for the software system to the automatic test framework.
Optionally, the step of calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case includes:
Dividing the page to be tested into a presentation layer, an operation layer and a service layer based on the automatic test framework; the performance layer is used for visualizing interface elements of the page to be tested, the operation layer is used for executing operation behaviors on the interface elements, and the service layer is a function realized in the operation process of the interface elements;
acquiring an element operation method and elements to be operated in the test case, and positioning the elements to be operated on the presentation layer of the page to be tested;
calling corresponding page object classes based on each element operation method, and driving corresponding elements to be operated by utilizing the browser driver so as to simulate corresponding user operation behaviors;
and triggering an automatic screenshot function if an abnormality or loophole occurs in the process of executing the test case.
Optionally, the positioning each element to be operated at the presentation layer of the page to be tested includes:
for each element to be operated, if detecting that the current element to be operated exists in the page to be tested or the current element to be operated is successfully loaded on the page to be tested in a preset waiting time period at intervals of preset monitoring time, positioning the current element to be operated in the page to be tested;
If the current element to be operated is not detected in the page to be tested at intervals of preset monitoring time or the current element to be operated is not successfully loaded on the page to be tested within the preset waiting time, the page loading is abnormal.
Optionally, the step of calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case includes:
recording and calling the UI automation script to execute the execution process of the automation test on the page to be tested so as to form a log file;
generating an automatic test report according to the execution result of each test case;
and outputting the log file, the automatic test report and the screenshot file to a preset target path.
Another aspect of the embodiments of the present invention provides a user interface automation test device, including:
the test frame construction and deployment module is used for constructing an automatic test frame and deploying the automatic test frame in an automatic test environment; the automatic test framework positions and encapsulates page elements in a page object based on a page object model, and adopts a separation mode of UI layer operation, business layer regression and data layer verification;
The UI test module is used for acquiring test cases and corresponding UI automation scripts when receiving the UI test instruction, and the UI automation scripts are independent; and calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case.
The embodiment of the invention also provides electronic equipment, which comprises a processor, wherein the processor is used for realizing the steps of the user interface automatic test method when executing the computer program stored in the memory.
Finally, an embodiment of the present invention provides a readable storage medium, where a computer program is stored, where the computer program, when executed by a processor, implements the steps of the user interface automation test method according to any one of the preceding claims.
The technical scheme provided by the application has the advantages that the UI behavior operation, the service flow and the data verification are separated in an automatic test design mode, so that the clear and concise test service flow is realized, and the passing rate of the test cases is accurately counted. Human intervention is not needed in the whole automatic test process, the regression test period is saved, and the investment of the labor cost of a test team can be reduced. The method has the advantages that the page elements and the business operation flow are separated, namely, the separation of the test objects, the test scripts, the object library and the test cases is realized, the test objects can be reused, when the page elements are changed due to the change of requirements, business logic in the test scripts is not required to be changed, only element codes in the page objects are required to be changed, and the maintenance efficiency of the automatic test framework is enhanced. Each test script is independent of each other, does not generate other dependence and call, keeps the independence of the use cases of the functional module not influenced by other use cases and service scenes, cannot depend on the existing data in the current test environment, can be deployed independently, and the test frames can be operated independently, so that the redundancy of the automatic test frame codes is reduced, and the quality of software products is improved. The repetition of test codes is reduced, and the readability and reusability of test cases can be improved; the maintainability of the test case is improved, and particularly, the maintenance cost of the test frame is reduced aiming at the items of frequent change requirements of UI page elements and interface style modification, so that the test cost of the whole user interface is effectively reduced.
In addition, the embodiment of the invention also provides a corresponding implementation device, electronic equipment and a readable storage medium for the user interface automatic test method, so that the method has more practicability, and the device, the electronic equipment and the readable storage medium have corresponding advantages.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions of the related art, the drawings that are required to be used in the embodiments or the description of the related art will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort to those of ordinary skill in the art.
FIG. 1 is a flow chart of an automated testing method for a user interface according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a PMT mode working principle provided in an embodiment of the present invention;
FIG. 3 is a schematic diagram of a PMT mode webpage operation flow according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of an automated test flow provided by an embodiment of the present invention;
Fig. 5 is a schematic diagram of a PMT mode for UI automation test according to an embodiment of the present invention;
FIG. 6 is a block diagram of a specific implementation of an automated user interface testing apparatus according to an embodiment of the present invention;
fig. 7 is a block diagram of an embodiment of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to better understand the aspects of the present invention, the present invention will be described in further detail with reference to the accompanying drawings and detailed description. It will be apparent that the described embodiments are only some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of this application and in the above-described figures, are used for distinguishing between different objects and not necessarily for describing a sequential or chronological order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may include other steps or elements not expressly listed.
Having described the technical solutions of embodiments of the present invention, various non-limiting implementations of the present application are described in detail below.
Referring first to fig. 1, fig. 1 is a flow chart of an automatic testing method for a user interface according to an embodiment of the present invention, where the embodiment of the present invention may include the following:
s101: and pre-building an automatic test framework, and deploying the automatic test framework in an automatic test environment.
The automatic test framework of the embodiment is used for executing UI automatic test, namely simulating the automatic operation mode of the user's behavior on the browser, the use of the automatic test can reduce the labor cost of a test team, is favorable for counting the accurate test case passing rate, completes repeated work of various functional tests, effectively improves the UI test efficiency,
considering PMT (Page Model Test), repetition of Test code can be reduced; the readability and reusability of the test cases are improved; the maintainability of the test case is improved, and particularly, the items of the UI page element frequent change requirement and the interface style modification are aimed at. In addition, the PMT can be maintained and developed together with multiple members of a team, so that team cooperation is facilitated, project testing period is saved, testing work efficiency is improved, and product quality is improved. The framework mode can cover full scene full function full service in regression test, and coverage rate is improved. The PMT can also save the cost and equipment resources of the project, the framework can be tested across the main stream browser, the equipment and the server and the computer operating system, and the compatibility is improved. Furthermore, the PMT can continuously monitor the stability of the test function, the UI automatic test can monitor the test process in an unattended humanized way, the distributed and threads are operated in a designated sequence, different browser drivers share the same test case in different devices, and the failed case can be rerun after the execution failure is caused by external factors. However, building an automated test framework using PMTs requires a foundation for developing languages, i.e., code capability to develop a test PMT pattern framework. In addition, the PMT mode framework is suitable for scenes with less complex test services, namely, PMT mode framework is not easy to be suitable for when the software product test service is complex. Based on the method, the automatic test framework can be designed based on the PMT, and the PMT is mainly embodied in the method packaging of the system interface interaction details, so that the browser operating system page is driven by the method. The design mode is a page operation method packaging idea, and aims to create a page object for each page to be tested, position and package complicated page elements in the page object, and solve the problem of layering and separating design of the page elements and the element operation method. The automatic test framework of the embodiment positions and encapsulates the page elements in the page objects based on the page object model, adopts a separation mode of UI layer operation, business layer regression and data layer verification, realizes regression test full-scene full-function coverage, and realizes a method of digital separation based on a PMT frame mode. The data layer verification refers to a process of verifying data on which a function operation depends in advance. By separating the page elements from the business operation flow, the test objects and the test scripts are separated, and the object library and the use cases are separated, so that the test objects are reused. When the page elements are changed due to the change of the requirements, the business logic in the test script is not required to be changed, and only the element codes in the page objects are required to be changed, so that the maintenance efficiency is enhanced.
It will be appreciated that the automated test frameworks are built based on a computer language, and that the corresponding computer language may be installed in the system in advance based on the language used by the automated test framework. For example, in this embodiment, an automated test framework is built based on Python and PMT, python3 language can be installed, the language version needs to be between 3.X (e.g. 3.4 to 3.9), and the environment variable "C; python34; c, performing operation; python34\scripts; "add to System variable path". After the automated test framework is built, the automated test framework needs to be verified, for example, the same test cases which can run on multiple platforms daily for pages with less stable requirement point variation are combined with traversal tests, a large number of repeated test tasks are performed, frequent regression tests are performed, the coverage rate of the test cases of the automated cases in the whole project is covered with common cases by 60++, and the coverage rate of the important process cases is covered with 85++. After the automatic test framework is built and verified, the automatic test framework is deployed in an environment required to execute UI automatic tests according to UI automatic test scenes, and optionally, jenkins continuous integrated server (CI, continuous Integration Server) environment can be built, continuous delivery and automatic smoking tests are carried out in the environment, independent test environment is built, windows desktop operating system is installed, browser is installed, distributed execution is carried out, host creation node-release node-single-camera registration is connected to a host, when a plurality of single cameras exist, the host can specify the single cameras through names or tag names of the single cameras, the single cameras need to have corresponding execution environments, and codes need to be loaded on the host to execute test processes. Based on the fact that the data operation and the page object of the automatic test framework are separated, in order to achieve separation of the data and the page object, the method of independently managing the test data can be adopted, the test data are independently separated into Excel files to be stored, and the test data are assigned to the test case through reading and writing.
S102: and when receiving the UI test instruction, acquiring the test case and the corresponding UI automation script.
The UI test instruction in this embodiment may be issued by a user, or may be issued by an automated test script when triggered to execute a certain test task, which does not affect the implementation of the present application. The test cases are pre-stored in the test environment after being written by a user, the test cases are matched with the UI test instructions, and the UI automation script is used for executing corresponding test tasks according to the test cases based on the UI test instructions. The UI automation scripts of the present application are independent of each other. The embodiment keeps the independence of the use cases of the functional module unaffected by other use cases and service scenes, does not depend on existing data in the current test environment, can be deployed independently, and the test frames should operate independently. Therefore, the generation probability of invalid service data can be reduced, the cleaning operation flow of the invalid service data is saved, and the test flow is further simplified.
S103: and calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case.
In this embodiment, through inheritance and dependency to implement the corresponding test steps, the automation test frame constructed in S101 is an idea of an automation test frame and a tool design, and the linear test thinking makes each test script relatively opposite, no other dependency and call are generated, so that a modularized driving idea is reflected, a part of repeated operation is used as an independent common module for calling and quoting other functions, repetition is eliminated, maintainability of the automation test frame is improved, and the automation test frame in this embodiment executes an automation test by using a data driving service and an element driving page, and finally causes a change of a test result and automatically generates a test report.
In addition, in order to improve the efficiency and accuracy of the whole UI automatic test, when the UI test task is executed, all functional test cases are not required to be converted into automatic tests, the service is not complex, the scene is simple, the service flow is clear, the functions can be converted into automatic tests, the functional scene is not too complex, the single case test single scene is increased, and the efficiency is improved by splitting the test steps.
In the technical scheme provided by the embodiment of the invention, the automatic test design mode of UI behavior operation, service flow and data verification separation realizes clear and concise test service flow and is beneficial to precisely counting the pass rate of test cases. Human intervention is not needed in the whole automatic test process, the regression test period is saved, and the investment of the labor cost of a test team can be reduced. The method has the advantages that the page elements and the business operation flow are separated, namely, the separation of the test objects, the test scripts, the object library and the test cases is realized, the test objects can be reused, when the page elements are changed due to the change of requirements, business logic in the test scripts is not required to be changed, only element codes in the page objects are required to be changed, and the maintenance efficiency of the automatic test framework is enhanced. Each test script is independent of each other, does not generate other dependence and call, keeps the independence of the use cases of the functional module not influenced by other use cases and service scenes, cannot depend on the existing data in the current test environment, can be deployed independently, and the test frames can be operated independently, so that the redundancy of the automatic test frame codes is reduced, and the quality of software products is improved. The repetition of test codes is reduced, and the readability and reusability of test cases can be improved; the maintainability of the test case is improved, and particularly, the maintenance cost of the test frame is reduced aiming at the items of frequent change requirements of UI page elements and interface style modification, so that the test cost of the whole user interface is effectively reduced.
In the above embodiment, how to perform step S101 is not limited, and an optional implementation of building an automated test framework based on PMT as a design mode in this embodiment may include the following:
firstly, the aim of the PMT design mode in setting up an automatic test frame and the problem to be solved are required to be clarified: 1. reasonable modularization, reasonable layered encapsulation, data and service separation and improvement of the multiplexing rate of the frame codes; the coupling degree between each module and the class is not too high, so that the subsequent maintenance is convenient; the method can be expanded, and an entrance is reserved in the frame design, so that the function is conveniently updated in the later period; the language used in the design is transplantable, and the cross-platform language is convenient to deploy; the system is easy to maintain, reasonable in scheme design, complete and perfect in log system and clear in code annotation; 2. the project period is long, the history function is stable, and the automatic test is carried out according to the PMT design mode. 3. Challenges faced by automated testing: the biggest challenges faced are interface element changes, which can cause test case failures, requiring continuous Debug of automation scripts, cost control, and resource reduction are challenges to automation test tools and test practitioner capabilities. The demand is stable and the change is not frequent; the greatest challenge of the automatic test is the change of the demand, and the automatic script itself needs to be modified, expanded and debug to adapt to the new function, if the input-output ratio is too low, the automatic test also loses the value and meaning; the trade-off method is that a relatively stable module and function are selected for automatic test, and the parts with larger variation and more frequent requirement change are manually tested; 4. the multi-platform operation, combination traversal type, repeated tasks, test data, test cases and automation scripts have strong reusability and portability, the cost is reduced, and the efficiency and the value are improved; the software maintenance period is long and the life is powerful; the requirement for automatic test stability, the design of an automatic framework and script development and debugging all require time, which is a software development process, and if the project period is short, enough time is not needed to support the process, and the automatic test is not needed. 5. The development of the tested system is more standard, and the testability is strong; mainly considered for this point: the architecture difference of the tested system, the adaptability of the testing technology and tools, and whether the capability of the tester can design and develop an automatic testing framework adapting to the difference. The process of building an automated test framework of this embodiment may include:
Packaging the browser driver, namely a module for packaging the browser driver program and the target tool into an automatic test framework; uniformly packaging the public operation method into basic test classes to form test public classes for operating the page elements to be tested, inheriting the test public classes by the test classes corresponding to the pages to be tested, and managing the page elements of the test classes through a browser driver; and packaging the preset behavior operation method into a webpage test tool.
The target tool is a third party tool, and for the third party library tool package, as shown in fig. 5, an Excel driving data reading and writing function and an Email mail sending function can be used to send test results to team members and Log functions to record test execution processes, a Config configuration file constant data reading and writing function, a contents relative path OS function and an element operation method Basestest element operation keyword function. The relative path function is to provide a public path, namely the storage position of the storage file relative to the current project, the storage drive and the file folder are not required to be indicated, namely the personal configuration of all cooperators is not influenced, and the OS is the interpretation of the storage target of the file. Accordingly, packaging the browser driver and target tools into an automated test framework may include: packaging the browser driver into an automated test framework; any one or any combination of an Excel driven read-write data tool, an Email mail tool, a logging tool, a configuration tool, and a common path storage tool is packaged into an automated test framework.
In PMT mode of this embodiment, common operation methods are uniformly packaged into a base Test (basic Test class), and tool common behavior operation methods for Web application program testing such as Selenium are secondarily packaged. Each independent page corresponds to a respective Test class, the Test class needs to inherit the BasesTest public class, page elements in the Test class are managed through driving, and behavior operations in the Test class are packaged into independent methods to serve as a service presentation layer (such as a deletion flow) and a behavior operation layer (such as a click deletion function). After the common operation method is uniformly packaged into the basetest, the common operation method may be called a basetest method, and the basetest method comprises the following steps: the method for operating the screen_screen_shot screen, the wait_element_visible waiting element is visible, the get_element acquires all elements in the page, the get_element_click waiting element can be clicked, the get_element_input_txt inputs text content to an input box, the clear_text clears text box content, the wait_page_container_element waiting element exists, the get_element_select waiting element can be selected, the get_upload_file upload file, the scroll_test page slide scroll bar and the like.
It can be understood that when UI test is performed on a certain browser, the browser needs to be logged in first, so that in order to further improve the automation test efficiency, when the automation test frame is built, the method for implementing automatic login of the software system can be packaged into the automation test frame.
As an alternative embodiment, the process of performing UI automation test based on the PMT mode automation test framework described in connection with fig. 2-5 may include the following processes:
first, as shown in fig. 2, the principle of the PMT mode-based automation test framework performing the UI automation test is: the UI automation script sends an operation request to the browser, and simultaneously triggers a browser driver, and the browser executes corresponding operation under the drive of the browser driver so as to respond to the operation request. Specifically, as shown in fig. 3, the test case is parsed to obtain each element operation method, the corresponding page object class is called based on each element operation method, and then the page operation of the browser execution operation driven by the browser driver is unified. As shown in fig. 4, the automated test flow of the present application is: and (3) making a test plan according to the project version and the demand specification, making a corresponding test scheme according to the test demand and the test plan, building an automatic test environment based on the test scheme, and designing an automatic test case. In designing Test cases, the naming rule of the Test case class (TestCase) may be test_py or a file of ×test_py, a function name beginning with test_py, a function beginning with test_st among the Test classes (without __ init __ functions), an auto-discovery Test module and a Test method default to search under the pytest command execution path, search level: directory-file-functions and classes. And (3) setting up an automatic test environment, and storing the automatic test cases into the automatic test environment. When an automatic test task is received, a test case is acquired, and an automatic test script is called to execute the automatic test task in an automatic test environment. Judging whether the current test case passes or not, if the current test case passes the execution of the next test case, if the current test case does not pass the execution of the next test case, then, providing defects, tracking the defects, verifying the problem, carrying out regression test, and executing automatic test based on the test case again. If all the test cases are executed, analyzing and summarizing the execution result of each test case to generate an automatic test result, and completing the automatic test task. In the whole automatic test process, the documents to be output comprise software version test packages, test plans, test scheme books, test cases, test scripts, test data, defect record sheets, automatic test reports and test summary books. The process for executing the debug automation test script and executing the automation test may be based on the illustration of FIG. 5. In this embodiment, the concept of the PMT mode-based automated test flow is: and packaging the browser driver, wherein when the PMT program framework executes the test case, the PMT program framework triggers an error reason screenshot function after the execution failure of the abnormal reason case, so that the follow-up browsing and checking and the quick positioning of the error position of the function are facilitated. And packaging page element basic class operation and page elements of the front-end page function module, and enabling the system login method to be packaged to facilitate the front-end call of the subsequent function module. Meanwhile, after the use case execution is finished, a use case execution result statistics device of a PMT design mode is called, failure, success and abnormal quantity of each module and service function test cases are counted, so that a test report is generated, and the test report is sent to a corresponding receiver through a mail function.
Based on the thought of the automatic testing flow of the PMT mode, the process of executing the automatic test on the page to be tested by calling the UI automation script based on the automatic testing framework and the test case may include:
based on an automatic test framework, dividing a page to be tested into a presentation layer, an operation layer and a service layer; the presentation layer is used for visualizing interface elements of the page to be tested, the operation layer is used for executing operation behaviors on the interface elements, and the service layer is a function realized in the operation process of the interface elements.
And acquiring an operation method of each element and the element to be operated in the test case, and positioning each element to be operated on the presentation layer of the page to be tested.
Calling corresponding page object classes based on each element operation method, and driving corresponding elements to be operated by utilizing a browser driver so as to simulate corresponding user operation behaviors;
and triggering an automatic screenshot function if an abnormality or loophole occurs in the process of executing the test case.
In this embodiment, PMT mode divides the page into three layers: expression layer: interface elements in the visual page belong to the expression layer and the element locator is written. Operation layer: operational behavior on page visible elements, such as tab drop-down, element click, parameter input, target drag, file upload, page slide, file download, etc. Service layer: functional targets, namely test cases, realized in the operation process of a plurality of elements in the page. The PageLoctors can be utilized to locate the Web element, and page elements can be precisely located based on parameters such as id, xpath, name, class _name, tag_name, link_text, partial_link_text and css of the element, so that the operation page elements are realized. After an abnormal condition occurs in the process of automatically testing the case, automatically starting a screenshot function, and storing the intercepted image into a finally generated test report so as to trace back or locate faults. When the automatic test task is completed, the comparison of the actual result and the expected result can be further asserted, and whether the element exists or not is judged to be consistent with the expected result or not. The management and execution of the test suite may be performed, for example, by a main use case execution command, or may be run with a pytest.main () function in a main.py file under the project root directory path.
It can be appreciated that in the UI automation test process, the problem that the element program to be searched is already executed but the page is not loaded successfully, which causes the element to be positioned is encountered because the loading time of the page is too slow. In order to solve the technical disadvantage that elements cannot be found caused by page loading time, loading time can be set for pages. Specifically, for each element to be operated, if the existence of the current element to be operated is detected in the page to be tested at intervals of preset monitoring time or the current element to be operated is successfully loaded on the page to be tested within the preset waiting time, the current element to be operated is positioned in the page to be tested; or if the current element to be operated is not detected in the page to be tested at intervals of preset monitoring time or the current element to be operated is not successfully loaded on the page to be tested within the preset waiting time, the page loading is abnormal. In this embodiment, the two modes described above may be referred to as a display wait element and an implicit wait. An explicit wait element is a wait time set for a particular element, and if no element is found within a specified time frame, an exception is thrown, and if an element is found within a specified time frame, the execution is directly performed, i.e., the element is found, and the related subsequent operation is performed. Implicit wait sets global wait, such as page load timeout wait, page element load timeout, asynchronous script timeout. If the page element is overtime, setting waiting time and setting loading time for all elements in the page. Implicit waiting is to improve the robustness of the page element and the efficiency of the test efficiency when the browser continuously refreshes the page within a specified time range until the relevant element is found or the time is over.
In order to further improve the high availability of the automated test, the embodiment also records the execution process of calling the UI automated script to execute the automated test on the page to be tested so as to form a log file; generating an automatic test report according to the execution result of each test case; and outputting the log file, the automatic test report and the screenshot file to a preset target path.
Wherein the test report, such as the ytest-alarm report, may include statistics such as success/failure/retry, execution results for each test case, and time-consuming data for each test case. After operation, the command generation report needs to be additionally executed and stored in the test result file directory. Visual test result reports can be generated, success rate and failure rate of the functional module are reflected, specific error positions of the test function can be clearly described through screenshot of the failed use case, regression test efficiency of the function is improved more conveniently and intelligently, and personnel cost is saved. The operation process can be clearly recorded through log output (such as log file output and mail notification), when the execution fails, the error position line number can be positioned fastest through the log file, and the execution result and the execution process are synchronously sent to the mailbox of the relevant responsible person, so that timely notification and problem tracking are facilitated. In addition, through automatically generating detailed test processes and test results, the accurate test case passing rate is counted.
In order to further improve the automated test effect, an intermediate common module, for example a conftest.py common module, may also be provided when the automated test framework is built. The fixture in the pytestUI automation test framework is an inheritance mechanism for separating code that performs preparation and cleanup tasks before and after testing out of core test logic. Similar to the setup\teardown mechanism in the framework. The front and rear mechanism functions are more advanced, elegant and more practical than the front and rear mechanism functions of the same setup/setdown in the pytest framework; a Fixture decorator is used in test cases, test classes, and test sessions, and is a functional method decorated by the decorator for other functions to add additional functions or methods to without any modification. The implementation principle is a closure mode, a plurality of functions are accepted as parameters, the functions are internally packaged and modified, and a plurality of new function methods with perfect functions are returned. Creating a conftest.py file in the root directory of the tested system, wherein the application range of the fixture in the file is all the test modules; a conftest.py file is created in a separate test folder, and the scope of the Fixture in the file is limited to only the test modules in the test folder. The test module outside the test folder or the test folder outside the test folder cannot call the Fixture function in the conftest.py file.
It should be noted that, in the present application, the steps may be executed simultaneously or in a certain preset order as long as the steps conform to the logic order, and fig. 1-5 are only schematic, and do not represent only such an execution order.
The embodiment of the invention also provides a corresponding device for the automatic testing method of the user interface, so that the method has more practicability. Wherein the device may be described separately from the functional module and the hardware. The user interface automatic testing device provided by the embodiment of the invention is introduced below, and the user interface automatic testing device described below and the user interface automatic testing method described above can be correspondingly referred to each other.
Based on the angles of the functional modules, referring to fig. 6, fig. 6 is a block diagram of a user interface automation testing device provided by an embodiment of the present invention, where the device may include:
the test frame constructing and deploying module 601 is configured to construct an automated test frame and deploy the automated test frame in an automated test environment; the automated test framework encapsulates the page element locations in the page object based on the page object model and adopts a separation mode of UI layer operation, business layer regression and data layer verification.
The UI test module 602 is configured to obtain a test case and a corresponding UI automation script when a UI test instruction is received, where each UI automation script is independent of the other UI automation script; and calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case.
Optionally, in some implementations of the present embodiment, the test frame building and deploying module 601 includes a frame building unit, where the frame building unit may be used to package the browser driver and the target tool into an automated test frame; uniformly packaging the public operation method into basic test classes to form test public classes for operating the page elements to be tested, inheriting the test public classes by the test classes corresponding to the pages to be tested, and managing the page elements of the test classes through a browser driver; and packaging the preset behavior operation method into a webpage test tool.
As an alternative implementation of the present embodiment, the above-mentioned frame construction unit may further be adapted to: packaging the browser driver into an automated test framework; any one or any combination of an Excel driven read-write data tool, an Email mail tool, a logging tool, a configuration tool, and a common path storage tool is packaged into an automated test framework.
As an alternative implementation of the present embodiment, the above-mentioned frame construction unit may further be adapted to:
and packaging the automatic login method for the software system into an automatic test framework.
Optionally, in some implementations of this embodiment, the UI test module 602 may be configured to: based on an automatic test framework, dividing a page to be tested into a presentation layer, an operation layer and a service layer; the display layer is used for visualizing interface elements of the page to be tested, the operation layer is used for executing operation behaviors on the interface elements, and the service layer is a function realized in the operation process of the interface elements; acquiring an element operation method and elements to be operated in a test case, and positioning the elements to be operated on a presentation layer of a page to be tested; calling corresponding page object classes based on each element operation method, and driving corresponding elements to be operated by utilizing a browser driver so as to simulate corresponding user operation behaviors; and triggering an automatic screenshot function if an abnormality or loophole occurs in the process of executing the test case.
As an alternative implementation of this embodiment, the UI test module 602 may be further configured to: for each element to be operated, if detecting that the current element to be operated exists in the page to be tested or the current element to be operated is successfully loaded on the page to be tested within the preset waiting time period at intervals of preset monitoring time, positioning the current element to be operated in the page to be tested; if the current element to be operated is not detected in the page to be tested at intervals of preset monitoring time or the current element to be operated is not successfully loaded on the page to be tested within the preset waiting time, the page loading is abnormal.
As an alternative implementation of this embodiment, the UI test module 602 may be further configured to: recording and calling an UI automation script to execute an execution process of an automation test on a page to be tested so as to form a log file; generating an automatic test report according to the execution result of each test case; and outputting the log file, the automatic test report and the screenshot file to a preset target path.
The functions of each functional module of the user interface automatic test device according to the embodiment of the present invention may be specifically implemented according to the method in the embodiment of the method, and the specific implementation process may refer to the related description of the embodiment of the method, which is not repeated herein.
From the above, the embodiment of the invention realizes the definition of the test service flow, and can precisely count the passing rate of the test case. The investment of labor cost of a test team is reduced, the maintenance cost of the test framework is reduced, and the test cost of the whole user interface is effectively reduced. And the redundancy of the automatic test framework codes is reduced, and the quality of the software product is improved.
The user interface automatic test equipment mentioned above is described from the perspective of functional modules, and further, the application also provides an electronic device, which is described from the perspective of hardware. Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application in an implementation manner. As shown in fig. 7, the electronic device comprises a memory 70 for storing a computer program; a processor 71 for implementing the steps of the user interface automation test method as mentioned in any of the embodiments above when executing a computer program.
Processor 71 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and processor 71 may also be a controller, microcontroller, microprocessor, or other data processing chip, among others. The processor 71 may be implemented in at least one hardware form of DSP (Digital Signal Processing ), FPGA (Field-Programmable Gate Array, field programmable gate array), PLA (Programmable Logic Array ). The processor 71 may also include a main processor, which is a processor for processing data in an awake state, also called a CPU (Central Processing Unit ), and a coprocessor; a coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 71 may be integrated with a GPU (Graphics Processing Unit, image processor) for taking care of rendering and drawing of content that the display screen is required to display. In some embodiments, the processor 71 may also include an AI (Artificial Intelligence ) processor for processing computing operations related to machine learning.
Memory 70 may include one or more computer-readable storage media, which may be non-transitory. Memory 70 may also include high-speed random access memory as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. Memory 70 may be an internal storage unit of the electronic device, such as a hard disk of a server, in some embodiments. The memory 70 may also be an external storage device of the electronic device, such as a plug-in hard disk provided on a server, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash Card (Flash Card), etc. in other embodiments. Further, the memory 70 may also include both internal storage units and external storage devices of the electronic device. The memory 70 may be used to store not only application software installed on the electronic device, but also various types of data, such as: code of a program that executes the vulnerability processing method, or the like, may also be used to temporarily store data that has been output or is to be output. In this embodiment, the memory 70 is at least used to store a computer program 701 that, when loaded and executed by the processor 71, is capable of implementing the relevant steps of the user interface automated test method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 70 may further include an operating system 702, data 703, and the like, where the storage manner may be transient storage or permanent storage. The operating system 702 may include Windows, unix, linux, among other things. The data 703 may include, but is not limited to, data corresponding to user interface automated test results, and the like.
In some embodiments, the electronic device may further include a display screen 72, an input/output interface 73, a communication interface 74, alternatively referred to as a network interface, a power supply 75, and a communication bus 76. Among other things, the display screen 72, an input output interface 73 such as a Keyboard (Keyboard) belong to a user interface, which may alternatively include a standard wired interface, a wireless interface, etc. Alternatively, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch, or the like. The display may also be referred to as a display screen or display unit, as appropriate, for displaying information processed in the electronic device and for displaying a visual user interface. The communication interface 74 may optionally include a wired interface and/or a wireless interface, such as a WI-FI interface, a bluetooth interface, etc., typically used to establish a communication connection between an electronic device and other electronic devices. The communication bus 76 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 7, but not only one bus or one type of bus.
Those skilled in the art will appreciate that the configuration shown in fig. 7 is not limiting of the electronic device and may include more or fewer components than shown, for example, may also include sensors 77 to perform various functions.
The functions of each functional module of the electronic device according to the embodiment of the present invention may be specifically implemented according to the method in the embodiment of the method, and the specific implementation process may refer to the related description of the embodiment of the method, which is not repeated herein.
From the above, the embodiment of the invention realizes the definition of the test service flow, and can precisely count the passing rate of the test case. The investment of labor cost of a test team is reduced, the maintenance cost of the test framework is reduced, and the test cost of the whole user interface is effectively reduced. And the redundancy of the automatic test framework codes is reduced, and the quality of the software product is improved.
It will be appreciated that the user interface automated test methods of the embodiments described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored on a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in part or all of the technical solution contributing to the prior art, or in a software product stored in a storage medium, performing all or part of the steps of the methods of the various 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 (Random Access Memory, RAM), an electrically erasable programmable ROM, registers, a hard disk, a multimedia card, a card-type Memory (e.g., SD or DX Memory, etc.), a magnetic Memory, a removable disk, a CD-ROM, a magnetic disk, or an optical disk, etc., that can store program code.
Based on this, an embodiment of the present invention further provides a readable storage medium storing a computer program, where the computer program when executed by a processor performs the steps of the user interface automation test method according to any one of the embodiments above.
The functions of each functional module of the readable storage medium according to the embodiments of the present invention may be specifically implemented according to the method in the embodiments of the method, and the specific implementation process may refer to the related description of the embodiments of the method, which is not repeated herein.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other. For the hardware including the device and the electronic equipment disclosed in the embodiments, the description is relatively simple because the hardware includes the device and the electronic equipment corresponding to the method disclosed in the embodiments, and relevant places refer to the description of the method.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative elements and steps are described above generally in terms of functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The above describes in detail a method, an apparatus, an electronic device, and a readable storage medium for automatically testing a user interface provided in the present application. The principles and embodiments of the present invention have been described herein with reference to specific examples, the description of which is intended only to facilitate an understanding of the method of the present invention and its core ideas. It should be noted that it would be obvious to those skilled in the art that various improvements and modifications can be made to the present application without departing from the principles of the present invention, and such improvements and modifications fall within the scope of the claims of the present application.
Claims (9)
1. A method for automated testing of a user interface, comprising:
pre-building an automatic test frame, and deploying the automatic test frame in an automatic test environment; the automatic test framework positions and encapsulates page elements in a page object based on a page object model, and adopts a separation mode of UI layer operation, business layer regression and data layer verification;
when a UI test instruction is received, acquiring a test case and a corresponding UI automation script, wherein the UI automation scripts are independent from each other;
based on the automatic test framework and the test case, calling the UI automation script to execute an automatic test on the page to be tested;
The step of calling the UI automation script to execute the automation test on the page to be tested based on the automation test framework and the test case comprises the following steps:
dividing the page to be tested into a presentation layer, an operation layer and a service layer based on the automatic test framework; the performance layer is used for visualizing interface elements of the page to be tested, the operation layer is used for executing operation behaviors on the interface elements, and the service layer is a function realized in the operation process of the interface elements;
acquiring an element operation method and elements to be operated in the test case, and positioning the elements to be operated on the presentation layer of the page to be tested;
calling corresponding page object classes based on each element operation method, and driving corresponding elements to be operated by utilizing a browser driver so as to simulate corresponding user operation behaviors;
and triggering an automatic screenshot function if an abnormality or loophole occurs in the process of executing the test case.
2. The automated user interface testing method of claim 1, wherein the building an automated test framework comprises:
packaging a browser driver and a target tool into the automated test framework;
Uniformly packaging a public operation method into basic test classes to form test public classes for operating page elements to be tested, inheriting the test public classes by the test classes corresponding to the pages to be tested, and managing the page elements of the test classes through the browser driver;
and packaging the preset behavior operation method into a webpage test tool.
3. The method of claim 2, wherein packaging the browser driver and the target tool into the automated test framework comprises:
packaging the browser driver into the automated test framework;
any one or any combination of an Excel driven read-write data tool, an Email mail tool, a logging tool, a configuration tool and a common path storage tool is packaged into the automated test framework.
4. The automated user interface testing method of claim 2, wherein the building an automated test framework comprises:
and packaging the automatic login method for the software system to the automatic test framework.
5. The method for automatically testing a user interface according to claim 1, wherein positioning each element to be operated at the presentation layer of the page to be tested comprises:
For each element to be operated, if detecting that the current element to be operated exists in the page to be tested or the current element to be operated is successfully loaded on the page to be tested in a preset waiting time period at intervals of preset monitoring time, positioning the current element to be operated in the page to be tested;
if the current element to be operated is not detected in the page to be tested at intervals of preset monitoring time or the current element to be operated is not successfully loaded on the page to be tested within the preset waiting time, the page loading is abnormal.
6. The method of claim 1, wherein the calling the UI automation script to perform an automated test on a page to be tested based on the automated test framework and the test case comprises:
recording and calling the UI automation script to execute the execution process of the automation test on the page to be tested so as to form a log file;
generating an automatic test report according to the execution result of each test case;
and outputting the log file, the automatic test report and the screenshot file to a preset target path.
7. A user interface automated test apparatus comprising:
The test frame construction and deployment module is used for constructing an automatic test frame and deploying the automatic test frame in an automatic test environment; the automatic test framework positions and encapsulates page elements in a page object based on a page object model, and adopts a separation mode of UI layer operation, business layer regression and data layer verification;
the UI test module is used for acquiring test cases and corresponding UI automation scripts when receiving the UI test instruction, and the UI automation scripts are independent; based on the automatic test framework and the test case, calling the UI automation script to execute an automatic test on the page to be tested;
wherein the UI test module is further to:
dividing the page to be tested into a presentation layer, an operation layer and a service layer based on the automatic test framework; the performance layer is used for visualizing interface elements of the page to be tested, the operation layer is used for executing operation behaviors on the interface elements, and the service layer is a function realized in the operation process of the interface elements;
acquiring an element operation method and elements to be operated in the test case, and positioning the elements to be operated on the presentation layer of the page to be tested;
Calling corresponding page object classes based on each element operation method, and driving corresponding elements to be operated by utilizing a browser driver so as to simulate corresponding user operation behaviors;
and triggering an automatic screenshot function if an abnormality or loophole occurs in the process of executing the test case.
8. An electronic device comprising a processor and a memory, the processor being configured to implement the steps of the user interface automation test method of any one of claims 1 to 6 when executing a computer program stored in the memory.
9. A readable storage medium, characterized in that it has stored thereon a computer program which, when executed by a processor, implements the steps of the user interface automation test method according to any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111130065.4A CN113778898B (en) | 2021-09-26 | 2021-09-26 | User interface automatic test method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111130065.4A CN113778898B (en) | 2021-09-26 | 2021-09-26 | User interface automatic test method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113778898A CN113778898A (en) | 2021-12-10 |
| CN113778898B true CN113778898B (en) | 2024-02-20 |
Family
ID=78853558
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111130065.4A Active CN113778898B (en) | 2021-09-26 | 2021-09-26 | User interface automatic test method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113778898B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115700465B (en) * | 2022-11-09 | 2023-05-09 | 安超云软件有限公司 | Mobile electronic equipment and application method thereof |
| CN115858402A (en) * | 2023-02-27 | 2023-03-28 | 国网瑞嘉(天津)智能机器人有限公司 | Automatic regression testing method and device based on cloud platform |
| CN116126739A (en) * | 2023-04-18 | 2023-05-16 | 北京安锐卓越信息技术股份有限公司 | Module updating method and device of APP product and electronic equipment |
| CN116594917B (en) * | 2023-07-18 | 2023-09-22 | 建信金融科技有限责任公司 | UI testing method and device, electronic equipment and machine-readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107957948A (en) * | 2017-12-07 | 2018-04-24 | 郑州云海信息技术有限公司 | A kind of user interface automatic test device and method |
| CN110297758A (en) * | 2019-05-20 | 2019-10-01 | 深圳壹账通智能科技有限公司 | User interface automated testing method, device and computer readable storage medium |
| CN112416788A (en) * | 2020-11-27 | 2021-02-26 | 中国科学院电子学研究所苏州研究院 | Hierarchical standard Web application UI automatic test method |
-
2021
- 2021-09-26 CN CN202111130065.4A patent/CN113778898B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107957948A (en) * | 2017-12-07 | 2018-04-24 | 郑州云海信息技术有限公司 | A kind of user interface automatic test device and method |
| CN110297758A (en) * | 2019-05-20 | 2019-10-01 | 深圳壹账通智能科技有限公司 | User interface automated testing method, device and computer readable storage medium |
| CN112416788A (en) * | 2020-11-27 | 2021-02-26 | 中国科学院电子学研究所苏州研究院 | Hierarchical standard Web application UI automatic test method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113778898A (en) | 2021-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113778898B (en) | User interface automatic test method and device, electronic equipment and storage medium | |
| CN110764753B (en) | Business logic code generation method, device, equipment and storage medium | |
| US9703694B2 (en) | Techniques for testing software | |
| US20130263090A1 (en) | System and method for automated testing | |
| CN109710508A (en) | Test method, test device, test equipment and computer readable storage medium | |
| CN107526676B (en) | Cross-system test method and device | |
| CN110457211B (en) | Script performance test method, device and equipment and computer storage medium | |
| CN111858371A (en) | Software testing method, system, storage medium and computer equipment | |
| US20060020931A1 (en) | Method and apparatus for managing complex processes | |
| CN103914315A (en) | Configuration method of drivers | |
| WO2021097824A1 (en) | Code quality and defect analysis method, server and storage medium | |
| US20200050534A1 (en) | System error detection | |
| CN114818565A (en) | Simulation environment management platform, method, equipment and medium based on python | |
| CN107451058A (en) | A kind of software development methodology and device | |
| CN112241360A (en) | Test case generation method, device, equipment and storage medium | |
| CN116194894A (en) | Fault localization of native cloud applications | |
| US11734134B2 (en) | Automatically locating resources using alternative locator expressions during heterogeneous component-based testing in a portable automation framework | |
| CN112506772B (en) | Web automatic test method, device, electronic equipment and storage medium | |
| CN113778460A (en) | Production environment deployment method and device | |
| CN113051171A (en) | Interface test method, device, equipment and storage medium | |
| CN112035300A (en) | Server BMC automatic test system, method, storage medium and electronic device | |
| CN111813659A (en) | UI and interface based automatic test method, device, equipment and readable medium | |
| CN112765040B (en) | Page test method, system, computer equipment and storage medium | |
| Singh et al. | Exploring problems and solutions in estimating testing effort for non functional requirement | |
| CN112256554B (en) | Method and equipment for testing based on scene test cases |
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 |