CN113326183A - UI test method, electronic device and storage medium - Google Patents

UI test method, electronic device and storage medium Download PDF

Info

Publication number
CN113326183A
CN113326183A CN202110485718.4A CN202110485718A CN113326183A CN 113326183 A CN113326183 A CN 113326183A CN 202110485718 A CN202110485718 A CN 202110485718A CN 113326183 A CN113326183 A CN 113326183A
Authority
CN
China
Prior art keywords
test
connection
instruction server
client
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110485718.4A
Other languages
Chinese (zh)
Inventor
邢晓菲
郑雷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hefei Yirui Communication Technology Co Ltd
Original Assignee
Hefei Yirui Communication Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hefei Yirui Communication Technology Co Ltd filed Critical Hefei Yirui Communication Technology Co Ltd
Priority to CN202110485718.4A priority Critical patent/CN113326183A/en
Publication of CN113326183A publication Critical patent/CN113326183A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The embodiment of the invention relates to the field of testing, and discloses a UI testing method, electronic equipment and a storage medium. In the invention, the UI test method is applied to the client of the UI automation test tool and comprises the following steps: sending a test request of a UI element to a connected instruction server according to a test script, and receiving a test result message which indicates a UI test result and is returned by the instruction server, wherein the test result message comprises any one of a test success message and a test failure message; after receiving the test failure message, checking whether the connection with the instruction server is normal; if the connection is normal, judging that the UI element test fails, and testing the next UI element; if the connection is abnormal, the UI element is reconnected with the instruction server and retested. The UI testing method can reduce the workload of UI testing and improve the efficiency of UI testing.

Description

UI test method, electronic device and storage medium
Technical Field
The embodiment of the invention relates to the field of testing, in particular to a UI testing method, electronic equipment and a storage medium.
Background
A User Interface (UI) is a medium for interaction and information exchange between a system and a User, and it implements conversion between an internal form of information and a human-acceptable form. The user interface test, namely the UI test, is used for testing whether the layout of the functional modules of the user interface is reasonable, whether the overall style is consistent and whether the placement positions of the controls accord with the use habits of customers, and more importantly, the UI test is characterized by conforming to the convenience in operation, simplicity and comprehensiveness in navigation, whether characters in the interface are correct, whether names are unified, whether pages are beautiful, whether combinations of the characters and pictures are perfect, and the like.
In the related UI test, an automatic test tool is used to realize the UI automatic test. The automatic testing tool is provided with an instruction server and a client, the client is connected with the instruction server, a testing script imported by the client is transmitted to the instruction server through a connecting interface, the instruction server carries out positioning and testing on various UI elements, and positioning and testing result messages are returned to the client.
However, the related UI test method has the following problems: in order to explore the reason of the UI element test failure, a tester can only manually repeat the UI test and search the reason of the test failure, so that the workload of the UI test is large, and the efficiency is low.
Disclosure of Invention
The embodiment of the invention aims to provide a UI testing method, electronic equipment and a storage medium, so that the UI testing workload is reduced, and the UI testing efficiency is improved.
In order to solve the above technical problem, an embodiment of the present invention provides a UI test method, which is applied to a client of an UI automation test tool, where the automation test tool is provided with an instruction server and the client, the instruction server is connected to the client through a first port, the instruction server is connected to a mobile UI test tool through a second port, the client sends a test request to the instruction server, the instruction server sends a test instruction to the mobile UI test tool according to the test request, the mobile UI test tool receives the test instruction, performs a UI test according to the test instruction, and returns a UI test result to a server, and the instruction server returns the received UI test result to the client, and the method includes: sending a test request of a UI element to a connected instruction server according to a test script, and receiving a test result message which indicates a UI test result and is returned by the instruction server, wherein the test result message comprises any one of a test success message and a test failure message; after receiving the test failure message, checking whether the connection with the instruction server is normal; if the connection is normal, judging that the UI element test fails, and testing the next UI element; if the connection is abnormal, the UI element is reconnected with the instruction server and retested.
An embodiment of the present invention also provides an electronic device, including: at least one processor; a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the UI testing method described above.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program, and the computer program realizes the UI testing method when being executed by a processor.
Compared with the prior art, the implementation mode of the invention has the advantages that the client sends the test command of the UI element to the instruction server according to the test script, receives the test result message returned by the instruction server, checks whether the connection with the instruction server is normal or not after receiving the test failure message returned by the instruction server, judges that the test of the UI element fails if the connection is normal, tests the next UI element, reconnects with the instruction server and retests the UI element if the connection is abnormal, and the test failure of the UI element can be automatically checked if the test failure is caused by the connection problem of the client and the instruction server because the test code of the UI element in the test script is wrongly written and the connection of the client of the automatic test tool and the instruction server is abnormal, the test personnel do not need to repeat the test manually, the reason of the test failure is searched, the workload of the UI test is reduced, and the efficiency of the UI test is improved.
In addition, checking whether the connection with the command server is normal includes: connecting the detection process with a pre-established detection process through a socket, and indicating the detection process to return connection information of the instruction server; acquiring connection information; judging whether the connection is normal or not according to the connection information; the detection process is established in advance and used for starting the instruction server, acquiring the connection information and sending the connection information to the client. The client is connected with a pre-established detection process socket, the detection process acquires connection information and sends the connection information to the client, so that the client can know the connection abnormity when the client is abnormally connected with the instruction server, the socket is an interprocess communication mode of a surface phase network, and can cross any limitation as long as the network exists, interprocess communication under various conditions can be realized, and the reliability of connection can be ensured by utilizing the socket to carry out communication.
In addition, the connection information includes: whether the first port is in a monitoring state; judging whether the connection is normal or not according to the connection information, comprising the following steps: if the first port is in a monitoring state, judging that the connection is normal; if the first port is in an idle state, judging that the connection is abnormal; before reconnecting with the instruction server, the method further comprises the following steps: and indicating the detection process to send a restart instruction server. When the connection port is in abnormal connection, the detection process is instructed to restart the instruction server, the instruction server is reconnected with the instruction server, and the UI element is retested, so that the possibility that the client and the instruction server are normally connected after reconnection is improved, the retest frequency is reduced, the UI test workload is reduced, and the UI test efficiency is improved.
In addition, after receiving the test result message returned by the instruction server, the method further comprises the following steps: recording the number of times of the received test failure message; before checking whether the connection with the service end is normal, the method further comprises the following steps: confirming the UI element is the first test failure. The client checks whether the connection with the instruction server is normal only when the first test of the UI element fails, and the probability that the connection with the instruction server is unavailable is low because the client is continuously connected with the instruction server twice, so that the connection with the instruction server is checked whether the connection with the instruction server is normal when the first test of the UI element fails, the computing resource and the test time can be saved, and the UI test efficiency is improved.
Drawings
One or more embodiments are illustrated by way of example in the accompanying drawings, which correspond to the figures in which like reference numerals refer to similar elements and which are not to scale unless otherwise specified.
FIG. 1 is a flow diagram of a UI testing method provided in accordance with one embodiment of the invention;
FIG. 2 is a flow diagram providing for UI element positioning using a UI test method according to one embodiment of the invention;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that numerous technical details are set forth in order to provide a better understanding of the present application in various embodiments of the present invention. However, the technical solution claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present invention, and the embodiments may be mutually incorporated and referred to without contradiction.
The embodiment of the invention relates to a UI test method, which is applied to a client, and the specific flow is as shown in figure 1:
step 101, sending a test request of a UI element to a connected instruction server according to a test script, and receiving a test result message which indicates a UI test result and is returned by the instruction server, wherein the test result message comprises any one of a test success message and a test failure message;
step 102, after receiving a test failure message returned by the instruction server, checking whether the connection with the instruction server is normal;
step 103, if the connection is normal, determining that the UI element test fails, and testing the next UI element; if the connection is abnormal, the UI element is reconnected with the instruction server and retested.
The UI testing method of the embodiment is applied to a client of UI automation testing software. The automatic testing tool is provided with an instruction server and a client, the instruction server is connected with the client through a first port, the instruction server is connected with a mobile terminal UI testing tool through a second port, the client sends a testing request to the instruction server, the instruction server sends a testing instruction to the mobile terminal UI testing tool according to the testing request, the mobile terminal UI testing tool receives the testing instruction, carries out UI testing according to the testing instruction and returns a UI testing result to the server, and the instruction server returns the received UI testing result to the client and sequentially tests all UI elements. In this embodiment, for example, the application of the automation test software supporting multiple languages is taken as an example, the application is an automation test tool and supports native applications, web applications and hybrid applications on the iOS platform and the Android platform. The Appium uses a command Server-Client (C/S) architecture, including a command Server and a Client. According to different writing languages of the test scripts, the Appium client can be installed in different integrated development environments, such as IntelliJ IDEA, eclipse and the like, according to different used programming languages. If the Python language is used for writing a test script, i.e. a test code, the client may be installed in a development environment PyCharm of the Python language. The instruction server Apdium-server is connected with a Python-Apdium-client through a 4723 port, a tester introduces a test script into the client, the client sends a test command of the UI element to the instruction server according to the test script, receives a test result message returned by the instruction server, and tests each UI element in sequence.
In the UI test method of this embodiment, the client sends a test command of a UI element to the instruction server according to the test script, receives a test result message returned by the instruction server, checks whether the connection with the instruction server is normal after receiving a test failure message returned by the instruction server, determines that the UI element test fails if the connection is normal, tests the next UI element, reconnects with the instruction server and retests the UI element if the connection is abnormal, and the UI element test fails because of a test code of the UI element in the test script being wrongly written and the connection between the client of the automated test tool and the instruction server being abnormal (for example, the request sent by the client cannot be completely acquired due to the operation error of the instruction server), so that when the test fails, the client and the instruction server are reconnected and tested, whether the test fails due to the connection problem between the client and the instruction server can be automatically checked, the test personnel do not need to repeat the test manually, the reason of the test failure is searched, the workload of the UI test is reduced, and the efficiency of the UI test is improved.
The following describes implementation details of the UI testing method of the present embodiment in detail, and the following is only provided for easy understanding and is not necessary for implementing the present embodiment.
In step 101, the client needs to establish a connection with the command server in advance and log in the command server. Taking the app as an example, the app instruction server is an HTTP instruction server implemented based on node. Specifically, the Appium client requests to create a session from the Appium instruction server, and after the session is created, the Appium client sends a request to the Appium instruction server through HTTP in the session, and the Appium instruction server parses the request and returns a test result message to the Appium client through the session. After the connection with the appum client is established, the appum instruction server monitors a UI element test request sent from the appum client, sends the UI element test request to a bootstrap jar or bootstrap js on the mobile phone, and the bootstrap converts the request into a command that the mobile-end UI test tool can execute the UI element test and sends the command to the mobile-end UI test tool for execution. Jar is an application program running on an Android mobile phone, js is an application program running on an IOS mobile phone, and plays the role of a TCP instruction server on the mobile phone. In this embodiment, an Android mobile phone is taken as an example for explanation, when an app instruction server needs to run a command, the app instruction server establishes TCP communication with a bootstrap server through a 4724 port, and sends the command to the bootstrap server, the bootstrap server monitors the 4724 port to obtain the command sent by the app instruction server, and converts the command into a command that can be recognized by a mobile-end UI test tool, which is sent to the uo automation to be executed, the uo automation is a UI test tool of the Android mobile phone, and then the bootstrap server returns an execution result to the app instruction server, and then the app instruction server feeds back an execution result of the command, that is, a test result message of a test request sent by the app client, to the app client through an HTTP response, so that the app client can receive a test result message returned by the app instruction server. The test result message may be a test success or a test failure. The mobile terminal UI testing tool can be installed in a mobile terminal device such as a mobile phone or a virtual mobile terminal device such as an android virtual machine of a PC terminal.
In step 102, after the application client receives the test failure message returned by the application instruction server, it immediately checks whether the connection with the instruction server is normal. For example, the communication between the Appium client and the Appium command server may be performed by means of a shared memory or a named pipe.
In one example, after receiving the test failure message returned by the instruction server, the Appium client also records the number of times of the test failure message of the UI element, and may record the number of times of the test failure message of the UI element by using one test variable, and when the Appium client receives the current test failure message of the UI element once, the value of the test variable is increased by 1. And when the tested UI element is changed, the value of the test variable is also changed to be 0, and the test failure message frequency of the new UI element is calculated. Before checking whether the connection with the instruction server is normal, the Appium client also confirms that the UI element fails in the first test, that is, the value of the test variable is 1. If the UI element fails the first test, the UI element is judged to fail the test.
In this embodiment, the app client checks whether the connection with the app instruction server is normal only when the first test of the UI element fails, and since the probability that the connection with the app instruction server is unavailable for two consecutive times is low, when the first test of the UI element fails, the connection with the app instruction server is checked whether the connection with the app instruction server is normal, so that the calculation resources and the test time can be saved, and the UI test efficiency can be improved.
In one example, the app client may also send a command to the app instruction server to instruct the app instruction server to check whether the connection is normal in a manner of responding. If the Apium instruction server responds within the preset time, judging that the connection between the Apium client and the Apium instruction server is normal; and if the Apium instruction server does not respond within the preset time, judging that the connection between the Apium client and the Apium instruction server is abnormal.
In one example, the app client is further connected with a pre-created detection process through a socket and instructs the detection process to return instruction server connection information; acquiring connection information; judging whether the connection is normal or not according to the connection information; the detection process is established in advance and used for starting the instruction server, acquiring the connection information and sending the connection information to the client. For example, a User Datagram Protocol (UDP) connection may be established between the client and the detection process, and a UDP Datagram may be sent from the socket of the client to the socket of the detection process, so as to instruct the detection process to return connection information instructing the server. And after receiving the indication of the client socket, the detection process acquires the connection information of the instruction server and returns the connection information to the client socket in the form of UDP datagram. And judging whether the connection is normal or not according to the connection information, wherein a socket of the client is established in advance, the life cycle of the socket can be the same as that of the process of the Apium client, a socket of the detection process end is established in advance, the life cycle of the socket can be the same as that of the detection process, the socket is used for acquiring the connection information and sending the connection information to the socket of the client, and the detection process starts an instruction server after being established.
Specifically, the instruction server connection information may be whether a connection port (4723 port by default) of the instruction server and the client is in a listening state. If the connection port is in a monitoring state, the Apium client determines that the connection between the instruction server and the client is normal, and if the connection port is in an idle state, the Apium client determines that the connection between the instruction server and the client is abnormal.
In one example, when the app client is connected with a pre-created detection process through a socket, a client socket is to be created to be connected with a server socket pre-created in the detection process; and after judging that the UI element test fails or reconnecting with the instruction server and retesting the UI element, the Apium client disconnects the client socket from the server socket and closes the client socket.
In this embodiment, the app client creates a client socket immediately, and closes the client socket after determining that the UI element test fails or reconnects with the instruction server and retests the UI element, that is, creates the client socket to connect with the server socket when the app client needs to communicate with the app instruction server, so as to save communication resources.
In one example, the connection established between the client socket and the server socket is a Transmission Control Protocol (TCP) connection, and the TCP connection establishes a connection using a three-way handshake Protocol, which can prevent an erroneous connection, and is a connection-oriented and reliable connection method that can ensure Transmission accuracy.
In step 103, if the connection between the Appium client and the Appium instruction server is normal, the Appium client determines that the test of the UI element fails, and tests the next UI element, and if the connection between the Appium client and the Appium instruction server is abnormal, the Appium client and the Appium instruction server are reconnected and the UI element is retested.
Specifically, the app client may close the created session, send a session creation request to the app instruction server again, create a new session, send a test request through the new session, and retest the UI element with the app instruction server. If the application client judges that the UI element fails to test, the test code of the UI element can be marked in a test script display interface of the application, so that a tester can quickly locate an error code.
In one example, the app client is connected with a pre-established detection process through a socket, the detection process is pre-established and used for starting the app instruction server, acquiring connection information and sending the connection information to the app client, and the app client instructs the detection process to send a restart app instruction server after judging that the connection with the app instruction server is abnormal.
In this embodiment, when the connection port is not in the connection state, the client socket is called to send a restart message to the server socket, the server socket is instructed to notify the instruction server of restart, and the client socket is reconnected with the instruction server and retests the UI element, that is, before reconnection, the instruction server is restarted, so that the possibility that the client and the instruction server are normally connected after reconnection is improved, the retest frequency is reduced, the workload of UI test is reduced, and the efficiency of UI test is improved.
In one example, the test failure message may be an element positioning failure message, and determining that the UI element fails to test specifically determines that the positioning expression of the UI element is set incorrectly, and marks the positioning expression in the display interface of the test script. The test personnel can quickly locate the wrong location expression, and the UI test efficiency is improved.
One embodiment of the present invention uses the UI test method described above for UI element positioning, as shown in fig. 2, including:
step 201, a client is connected with an instruction server and logs in the instruction server;
step 202, the client sends a positioning request (i.e. a test request) of a UI element to be tested to a connected instruction server according to the test script, and receives a positioning result message (i.e. a test result message) returned by the instruction server;
step 203-1, the client determines whether the positioning is successful according to the positioning result message, if the positioning is successful, step 203-1 is executed, and if the positioning is failed, step 204 is executed;
step 203-2, after acquiring the next UI element to be tested, executing step 202 again;
step 204, the client determines whether the UI element fails to be positioned for the first time, and if not, step 207 is executed to position the next UI element; if the first positioning fails, go to step 205;
step 205-1, the client establishes a TCP client (i.e. client socket) to connect with a TCP server (i.e. server socket) created in a pre-created detection process;
step 205-2, detecting the state of the process detection port 4723, and sending the state to the TCP client through the TCP server, wherein if the state is a monitoring state, the connection between the client and the instruction server is normal, otherwise, the connection is abnormal;
and step 205-3, the client acquires the message sent to the TCP client by the TCP server, disconnects the TCP client and the TCP server, and closes the TCP client.
Step 206, the client determines whether the connection between the instruction server and the client is normal, if the connection between the instruction server and the client is normal, the client executes step 207, and if the connection between the instruction server and the client is abnormal, the client executes step 201 again;
in step 207, the client determines that the UI element has failed to be located.
The steps of the above methods are divided for clarity, and the implementation may be combined into one step or split some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included, which are all within the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.
An embodiment of the present invention further relates to an electronic device, as shown in fig. 3, including: at least one processor 301; a memory 302 communicatively coupled to the at least one processor; the memory 302 stores instructions executable by the at least one processor 301, and the instructions are executed by the at least one processor 301 to perform the UI testing method.
Where the memory 302 and the processor 301 are coupled in a bus, the bus may comprise any number of interconnected buses and bridges, the buses coupling one or more of the various circuits of the processor 301 and the memory 302. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. Information processed by processor 301 is transmitted over a wireless medium through an antenna, which further receives the information and passes the information to processor 301.
The processor 301 is responsible for managing the bus and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory 302 may be used to store information used by the processor in performing operations.
Embodiments of the present invention also relate to a computer-readable storage medium storing a computer program. The computer program realizes the above-described method embodiments when executed by a processor.
That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the invention, and that various changes in form and details may be made therein without departing from the spirit and scope of the invention in practice.

Claims (9)

1. A UI test method is applied to a client of a UI automation test tool, the automation test tool is provided with an instruction server and the client, the instruction server is connected with the client through a first port, the instruction server is connected with a mobile terminal UI test tool through a second port, the client sends a test request to the instruction server, the instruction server sends a test instruction to the mobile terminal UI test tool according to the test request, the mobile terminal UI test tool receives the test instruction, conducts UI test according to the test instruction and returns a UI test result to a server, and the instruction server returns the received UI test result to the client, and the method comprises the following steps:
sending a test request of a UI element to a connected instruction server according to a test script, and receiving a test result message which indicates the UI test result and is returned by the instruction server, wherein the test result message comprises any one of a test success message and a test failure message;
after receiving the test failure message, checking whether the connection with the instruction server is normal;
if the connection is normal, judging that the UI element test fails, and testing the next UI element;
if the connection is abnormal, reconnecting with the instruction server and retesting the UI element.
2. The UI test method according to claim 1, wherein the checking whether the connection with the instruction server is normal comprises:
connecting the detection process with a pre-established detection process through a socket, and indicating the detection process to return connection information of an instruction server;
acquiring the connection information;
judging whether the connection is normal or not according to the connection information;
the detection process is pre-established and used for starting the instruction server, acquiring the connection information and sending the connection information to the client.
3. The UI test method according to claim 2, wherein the connection information includes: whether the first port is in a monitoring state;
the judging whether the connection is normal according to the connection information comprises: if the first port is in a monitoring state, judging that the connection is normal; if the first port is in an idle state, judging that the connection is abnormal;
before the reconnection with the instruction server, the method further comprises:
and instructing the detection process to send and restart the instruction server.
4. The UI test method according to claim 2, wherein the connecting with the pre-created detection process through a socket comprises:
creating the connection between the client socket and a server socket created in advance in the detection process;
after the determining that the UI element test fails or after the reconnecting with the instruction server and retesting the UI element, the method further includes:
and disconnecting the client socket from the server socket and closing the client socket.
5. The UI test method according to any of claims 1 to 4, further comprising, after the receiving the test result message returned by the instruction server:
recording the number of times of the received test failure message;
before the checking whether the connection with the service end is normal, the method further comprises the following steps:
confirming that the UI element failed the first test.
6. The UI test method of any of claims 1 to 4, wherein the test failure message comprises: an element location failure message;
the determining that the UI element test fails comprises:
and judging that the positioning expression of the UI element is set wrongly, and marking the positioning expression in a display interface of the test script.
7. The UI test method according to claim 1, wherein checking whether the connection with the instruction server is normal comprises:
sending a connection test message to the instruction server, wherein the connection test message indicates the instruction server to reply;
if the reply message of the instruction server is received within the preset time, judging that the connection is normal;
and if the reply message of the instruction server is not received within the preset time, judging that the connection is abnormal.
8. An electronic device, comprising:
at least one processor;
a memory communicatively coupled to the at least one processor;
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a UI testing method as claimed in any one of claims 1 to 7.
9. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the UI testing method of any of claims 1 to 7.
CN202110485718.4A 2021-04-30 2021-04-30 UI test method, electronic device and storage medium Pending CN113326183A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110485718.4A CN113326183A (en) 2021-04-30 2021-04-30 UI test method, electronic device and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110485718.4A CN113326183A (en) 2021-04-30 2021-04-30 UI test method, electronic device and storage medium

Publications (1)

Publication Number Publication Date
CN113326183A true CN113326183A (en) 2021-08-31

Family

ID=77414200

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110485718.4A Pending CN113326183A (en) 2021-04-30 2021-04-30 UI test method, electronic device and storage medium

Country Status (1)

Country Link
CN (1) CN113326183A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117149638A (en) * 2023-09-01 2023-12-01 镁佳(北京)科技有限公司 UI (user interface) automatic testing method and device, computer equipment and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101916224A (en) * 2010-08-20 2010-12-15 迈普通信技术股份有限公司 Test progress abnormality detection method and automatic test control device
CN107894950A (en) * 2017-10-30 2018-04-10 北京奇虎科技有限公司 A kind of equipment detection method, device, server and storage medium
CN108287789A (en) * 2017-12-29 2018-07-17 五八有限公司 Batch-automated test method, device and electronic equipment
CN111538650A (en) * 2020-03-24 2020-08-14 中国平安人寿保险股份有限公司 User interface automatic testing method and related equipment
CN112241356A (en) * 2019-07-16 2021-01-19 腾讯科技(深圳)有限公司 Page testing method, device, equipment and storage medium
CN112269744A (en) * 2020-10-30 2021-01-26 深圳壹账通智能科技有限公司 System abnormity testing method and device, computer equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101916224A (en) * 2010-08-20 2010-12-15 迈普通信技术股份有限公司 Test progress abnormality detection method and automatic test control device
CN107894950A (en) * 2017-10-30 2018-04-10 北京奇虎科技有限公司 A kind of equipment detection method, device, server and storage medium
CN108287789A (en) * 2017-12-29 2018-07-17 五八有限公司 Batch-automated test method, device and electronic equipment
CN112241356A (en) * 2019-07-16 2021-01-19 腾讯科技(深圳)有限公司 Page testing method, device, equipment and storage medium
CN111538650A (en) * 2020-03-24 2020-08-14 中国平安人寿保险股份有限公司 User interface automatic testing method and related equipment
CN112269744A (en) * 2020-10-30 2021-01-26 深圳壹账通智能科技有限公司 System abnormity testing method and device, computer equipment and storage medium

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
BINZICHEN: "Pytest测试框架(一)", pages 1 - 21, Retrieved from the Internet <URL:https://www.cnblogs.com/zibinchen/p/12985828.html> *
望月成三人: "appium多设备,重连优化开源", pages 1 - 4, Retrieved from the Internet <URL:https://www.jianshu.com/p/35131a188c41> *
那夜床塌了: "自动化实现 Appium 服务启动", pages 1 - 3, Retrieved from the Internet <URL:https://www.cnblogs.com/chanper/p/10485411.html> *
那夜床塌了: "自动化实现Appium服务启动", pages 1 - 3, Retrieved from the Internet <URL:https://www.cnblogs.com/chanper/p/10485411.html> *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117149638A (en) * 2023-09-01 2023-12-01 镁佳(北京)科技有限公司 UI (user interface) automatic testing method and device, computer equipment and storage medium

Similar Documents

Publication Publication Date Title
CN110719199B (en) Network automatic testing and fault positioning method and device
CN112463511B (en) Automatic test system and test method for serial port equipment of Internet of things
CN110784879A (en) Network mode switching test method, system, equipment and medium of communication module
CN113259996A (en) IOT wireless debugging method and equipment
US11442831B2 (en) Method, apparatus, device and system for capturing trace of NVME hard disc
CN109582324B (en) IC burning method and board card
CN113326183A (en) UI test method, electronic device and storage medium
CN114218072A (en) Test script generation method and device, storage medium and computer equipment
CN113392028A (en) Distributed test system and control method
CN112817883A (en) Method, device and system for adapting interface platform and computer readable storage medium
CN112000579B (en) Software interface testing method, system, equipment and medium
CN111752782B (en) Stability testing method, system, device and storage medium
CN114844859B (en) Domain name configuration method, device, electronic equipment and storage medium
CN112506764B (en) Method, system, equipment and medium for automatically testing RDS function
CN114691427B (en) Method and device for restarting large-scale host
CN116382968B (en) Fault detection method and device for external equipment
CN112925700B (en) Program debugging method, device and system and embedded equipment
CN118444965A (en) Nonvolatile memory firmware management method, device, equipment and readable storage medium
CN114297009A (en) Server testing method and device and electronic equipment
CN115396288A (en) Fault analysis method, device and equipment and computer readable storage medium
CN117873519A (en) Firmware upgrading method and device, storage medium and electronic device
CN105607878A (en) Log printing method and device
CN117472756A (en) Application system testing method and device, storage medium and computer equipment
CN111611006A (en) Version switching method and device
CN113836040A (en) Application program testing method and device, computer storage medium and electronic equipment

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