CN114706753A

CN114706753A - Display interface testing method and device, electronic equipment and storage medium

Info

Publication number: CN114706753A
Application number: CN202210249372.2A
Authority: CN
Inventors: 周俊; 蒋宁; 罗仕杰; 赵飞; 吴海英
Original assignee: Mashang Xiaofei Finance Co Ltd
Current assignee: Mashang Xiaofei Finance Co Ltd
Priority date: 2022-03-14
Filing date: 2022-03-14
Publication date: 2022-07-05

Abstract

The application discloses a display interface testing method, a display interface testing device, electronic equipment and a storage medium, and relates to the technical field of display interface testing, wherein under the condition that a display interface is loaded by the electronic equipment, a target element loaded on the display interface is detected; under the condition that the target element is detected, acquiring the currently loaded target element on the display interface; determining the display interface as a target display interface under the condition that the currently loaded target elements meet a preset display scene; and loading a test case, and testing the target display interface according to the test case to ensure that the test case can successfully test the target display interface.

Description

Display interface testing method and device, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of display interface testing technologies, and in particular, to a display interface testing method and apparatus, an electronic device, and a storage medium.

Background

Due to the rapid development of the internet, the business process of products (mobile terminals and web terminals) is more and more complex and the iteration speed is faster and faster, the pressure of testers on the regression test of interface functions is higher and higher, and the automatic test of the interface is more and more important. Writing or single case execution is often successful in daily interface automation test, but once a test script file is formally tested, verification failure occurs, and finally, the display interface test fails.

Disclosure of Invention

In view of the above problems, the present application provides a display interface testing method, device, electronic device and storage medium, which can solve the above problems.

In a first aspect, an embodiment of the present application provides a display interface testing method, which is applied to an electronic device, and the method includes: under the condition that the electronic equipment loads a display interface, detecting a target element loaded on the display interface; under the condition that the target element is detected, acquiring the currently loaded target element on the display interface; determining the display interface as a target display interface under the condition that the currently loaded target elements meet a preset display scene; and loading a test case, and testing the target display interface according to the test case.

In a second aspect, an embodiment of the present application provides a display interface testing apparatus, which is applied to an electronic device, and the apparatus includes: the loading module is used for detecting the target elements loaded on the display interface under the condition that the electronic equipment loads the display interface; the acquisition module is used for acquiring the currently loaded target element on the display interface under the condition that the target element is detected; the determining module is used for determining the display interface as a target display interface under the condition that the currently loaded target elements meet a preset display scene; and the test module is used for loading a test case and testing the target display interface according to the test case.

In a third aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a memory; one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the above-described method.

In a fourth aspect, the present application provides a computer-readable storage medium, in which a program code is stored, and the program code can be called by a processor to execute the above method.

In a fifth aspect, the present application provides a computer program product, wherein the computer program/instructions are executed by a processor to perform the above method.

According to the display interface testing method, the display interface testing device, the electronic equipment and the storage medium, the test case is loaded after the target display interface is loaded by the electronic equipment, the target display interface is tested according to the test case, namely the target display interface is tested after the target display interface is obtained, and the test case is ensured to be capable of testing the target display interface, so that the test failure condition can be avoided to a certain extent.

These and other aspects of the present application will be more readily apparent from the following description of the embodiments.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram illustrating an application environment of a display interface testing method according to an embodiment of the present disclosure;

FIG. 2 is a schematic flow chart illustrating a display interface testing method according to an embodiment of the present disclosure;

FIG. 3 is a schematic flow chart illustrating a display interface testing method according to another embodiment of the present application;

FIG. 4 is a flow chart illustrating step S250 of the display interface testing method of FIG. 3 of the present application;

FIG. 5 is a flow chart illustrating a method for testing a display interface according to another embodiment of the present application;

FIG. 6 is a block diagram illustrating a display interface testing apparatus according to an embodiment of the present application;

FIG. 7 is a block diagram of an electronic device for executing a display interface testing method according to an embodiment of the present application;

fig. 8 illustrates a storage unit for storing or carrying program codes for implementing a display interface testing method according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

First, the terms and expressions referred to in the embodiments of the present application are explained, and the terms and expressions referred to in the embodiments of the present application are explained as follows:

(1) test Case (Test Case): refers to a set of test inputs, execution conditions, and expected results tailored to a particular target for testing a certain program path or verifying whether a program (or script, code) meets a certain specified requirement.

(2) UI automation test: is a process of converting an artificially driven test behavior into machine execution. Typically, after the test cases are designed and reviewed, the test is performed step by a tester according to the procedures described in the test cases, resulting in a comparison of the actual results with the expected results. In the process, in order to save manpower, time or hardware resources and improve the testing efficiency, the concept of automatic testing is introduced.

(3) Forced wait (sleep): and setting a waiting time according to the code, and executing the next operation when the set time is reached.

(4) Explicit wait (visibility _ of _ element _ located): setting a waiting maximum time according to the code, waiting for the specified elements in the page to appear in the specified time, immediately executing the next operation after the elements appear, and throwing out the overtime exception if the overtime does not appear.

(5) Implicit wait (implicit _ wait): if the WebDriver does not find an element in a Document Object Model (DOM), continuing to wait, throwing an exception that the element cannot be found after the set time is exceeded, when the element or the element is not found immediately, implicitly waiting for a period of time and then finding the DOM, wherein the default time is 0, once the implicit waiting is set, the element or the element exists in the declaration period of the whole WebDriver object instance, and the element or the element is waited when each element is found.

In the related technology, the writing or the execution of a single test case is often successful in the automatic testing of the page, and once the test case formally runs in the actual testing process, the verification failure occurs and the script of the test case is very unstable; in the actual running process, various conditions, such as unstable network and inconsistent high and low configuration of running machines, are encountered, so that the page loading and element loading rendering time is inconsistent during testing, and thus various problems occur when the script runs.

At present, a selenium interface automation framework encapsulates a hidden waiting method and an explicit waiting method aiming at the condition that the page loading rendering time and the element loading rendering time are different, the explicit waiting method can only solve whether elements appear or not, and the hidden waiting method can only solve the scene that whether all the interface elements are completely loaded or not. And when the mandatory waiting is encapsulated in the selenium interface automation framework, if the loading of the interface element is completed, the interface element still needs to be continuously waited until the preset time in the mandatory waiting is finished, the verification is not executed, the test time is prolonged due to the continuous waiting after the loading (appearance) of the interface element is completed, the test efficiency is reduced, if the preset waiting time is short, the situation that the waiting time is finished but the loading of the interface element is not completed may occur, and the test is performed at this moment, and the direct test fails.

In some embodiments, the test case and the test page are loaded simultaneously, and the currently loaded test page is directly tested after the test case is loaded, but at this time, it cannot be determined that a page element to be tested has appeared, and therefore, the situation of test invalidation is easily caused. Illustratively, in a scene that a test case test searches names from a list, a script edited by a tester inputs a preset name element 'Zhang III' for searching, the preset name element is positioned to a name bar through an element positioning method, and the elements in the name bar are tested. Because the test case loading speed is high, for example, the loading can be completed in 0.1 second, and at 0.1 second, only the name element located before the preset name element in the list can be loaded, for example, the name element loaded on the display page is "Liqu" at 0.1 second, but the preset name element "Zhang three" is not loaded successfully for a while, that is, when the test case is loaded at 0.1 second, the display page loaded with the name element "Liqu" at the same time is tested, and thus, the implementation scheme does not achieve the purpose of testing the preset name element "Zhang three" by the tester at all.

In view of the above technical problems, the inventor has found and proposed a display interface testing method, device, electronic device and storage medium through long-term research, and after the electronic device loads a target display interface, the electronic device loads a test case and tests the target display interface according to the test case, that is, the test case is ensured to be able to test the target display interface, so that a test failure situation can be avoided to a certain extent. The specific display interface test method is specifically described in the following embodiments.

In combination with the above example, in the method provided by the embodiment of the present application, the preset name element "zhang san" is loaded in advance, and the test case is loaded after the preset name element "zhang san" is successfully loaded, so that it is ensured that the preset name element is successfully loaded when the test case is loaded, and thus the success rate of testing the preset name element is ensured.

In order to better understand the method, the apparatus, the electronic device, and the storage medium for testing the display interface provided in the embodiments of the present application, an application environment suitable for the embodiments of the present application is described below.

Fig. 1 is a schematic diagram illustrating an application environment of a display interface testing method according to an embodiment of the present application, and referring to fig. 1, the display interface testing method according to the embodiment of the present application can be applied to a display interface testing system 100. The display interface testing system 100 includes an electronic device 110, a server 120, and a communication network 130, wherein the electronic device 110 and the server 120 are connected via the communication network 130.

In fig. 1, the electronic device 110 is a test terminal, and is used to display a user interface during interface test and also used to display a test result. For example, the test result may include a test pass and a test fail, and the text result of "test pass" or "test fail" may be displayed on the test result display page of the electronic device 110, so that the tester can know the test result.

In this embodiment of the application, a tester may input a test operation based on the electronic device 110, the electronic device 110 may load a display interface from the server 120 through the communication network 130, and load a test case from the server 120 through the communication network 130, and the electronic device 110 tests the display interface through the test case to obtain a test result.

The electronic device 110 may be, among other things, various types of computer devices, such as portable handheld devices, general purpose computers (such as personal computers and laptop computers), and wearable devices, among others. Among other things, portable handheld devices may include cellular phones, smart phones, tablets, Personal Digital Assistants (PDAs), and the like; wearable devices may include head mounted displays and other devices. The electronic device 110 is capable of executing a variety of different applications, such as various Internet-related applications, communication applications (e.g., email applications), Short Message Service (SMS) applications, and may use a variety of communication protocols.

The server 120 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a Network acceleration service (CDN), a big data and artificial intelligence platform, and the like.

Communication network 130 may be any type of network that may support data communications using any of a variety of available protocols, including but not limited to TCP/IP, SNA, IPX, etc. By way of example only, the one or more communication networks 130 may be a Local Area Network (LAN), an ethernet-based network, a token ring, a Wide Area Network (WAN), the internet, a virtual network, a Virtual Private Network (VPN), an intranet, an extranet, a Public Switched Telephone Network (PSTN), an infrared network, a wireless network (e.g., bluetooth, WIFI), and/or any combination of these and/or other networks.

It should be noted that the application environment diagram shown in fig. 1 is only an example, and the display interface test scenario described in the embodiment of the present application is for more clearly illustrating the technical solution of the present application, and does not constitute a limitation on the technical solution provided by the present application. As can be known to those skilled in the art, with the evolution of display pages and test cases and the appearance of new service scenarios, the technical solution provided in the present application is also applicable to similar technical problems. The following describes in detail a display interface testing method, a display interface testing apparatus, an electronic device, and a storage medium, which are provided in the embodiments of the present application, with specific embodiments.

Fig. 2 is a schematic flow chart illustrating a display interface testing method according to an embodiment of the present application, and referring to fig. 2, the embodiment of the present application provides a display interface testing method, which can be applied to the display interface testing system 100 shown in fig. 1. The following will describe in detail the flow shown in fig. 2 by taking an example of applying the display interface testing method to the electronic device 110, where the display interface testing method specifically includes the following steps:

step S110: and under the condition that the electronic equipment loads a display interface, detecting the target elements loaded on the display interface.

The electronic device can load a display interface from the local or the server, wherein the display interface can be a display interface of a webpage, a display interface of an application program, a desktop, or the like.

Under the condition that the electronic equipment loads the display interface, detecting the loaded display interface to detect a target element appearing on the display interface, wherein the target element can be an element at a preset position or a preset element, and the target element is used for judging whether the display interface displaying the target element is the target display interface.

It should be noted that an element, that is, a data element, is a term of computer science and is a basic unit of data.

In some embodiments, the electronic device receives an input operation of a user, where the input operation may be performed based on a touch screen, a keyboard, a mouse, a remote controller, and the like of the electronic device, for example, the input operation may be to touch a loading control on the touch screen, or to click a link displayed on the touch screen; the electronic equipment responds to the input operation of the user to load the display interface.

In other embodiments, a loading event is preset, and the electronic device automatically loads the display interface from the server in response to the loading event. As one mode, a timer (setTimeout) function is preset, and when a predetermined time is reached, a display page is automatically loaded.

When the target element of the display interface is detected, the target element appearing on the display interface is waited through a pre-packaging waiting method. The target elements may include elements such as pictures, titles, interface keywords, authors, and the like.

In some embodiments, the waiting method (expected _ conditions _ availability _ of _ element _ location) may be pre-packaged and stored in the common configuration file, and when the target element on the display interface needs to be detected, the execution script of the pre-packaged waiting method is run from the common configuration file, and the display interface is detected to wait for the target element to appear.

In other embodiments, the loop method (webdriverwait. unit) may be prepackaged and saved in the common configuration file, and in conjunction with the prepackaged wait method, an execution script of the prepackaged wait method is run from the common configuration file, an element appearing on the display interface is detected by the wait method, when the element is detected not to be a target element, the execution script of the prepackaged loop method is obtained from the common configuration file, and the loop is waited for the target element by the prepackaged loop method.

In other embodiments, in conjunction with explicit wait, the wait duration is preset and stored in a common configuration file to facilitate candidate invocation and management. When the target element on the display interface needs to be detected, the preset waiting time length is called from the public configuration file, the target element is loaded on the display interface within the preset waiting time length, and when the target element is waited within the preset waiting time length, waiting is finished, or when the target element is not waited within the preset waiting time length, waiting is also finished.

It should be noted that the pre-packaged waiting method, the pre-packaged circulation method, and the pre-set waiting duration are all stored in a common configuration file, which is convenient for direct calling when detecting the display target element, and is also convenient for unified management and modification. Besides the target element is detected, the method can be used for detecting the target element subsequently, and the code reuse rate is improved.

Step S120: and under the condition that the target element is detected, acquiring the currently loaded target element on the display interface.

And after the target elements are detected to exist on the display interface, acquiring the currently loaded target elements on the display interface.

In some embodiments, after the target element is detected, the currently loaded target element on the display interface is acquired through a pre-packaged public method. For example, when the target element is a title, a title on the display interface is selected by running an execution script of a pre-packaged title detection method (element. title ()), for example, the obtained title is "method for making fish ball"; for another example, when the target element is an element value, obtaining a value of an element loaded on the display interface by running an execution script of an element detection method (element. text ()) pre-packaged by an assertion expression, where the value of the element is standard to a specific meaning represented by the element, for example, if the target element is an element in a preset position (for example, in a lower right corner of the display interface), the element value is "ok"; for another example, when the target element is a picture, the picture of the target position on the display interface is captured by a capture tool (e.g., caserjs).

Step S130: and under the condition that the currently loaded target elements meet a preset display scene, determining the display interface as a target display interface.

The preset display scene is a scene displayed on a display interface expected by a tester.

And judging whether the currently loaded target element meets a preset display scene, when the loaded target element meets the preset display scene, indicating that the display interface loaded with the target element meets the preset display scene, and determining the display interface as the target display interface. The target display interface is a test interface expected by a tester, and the target display interface is also an interface for testing.

In some embodiments, preset elements are preset, wherein the preset elements are elements expected by a tester, the preset elements are obtained, whether a currently loaded target element is consistent with the preset elements is judged, when the currently loaded target element is consistent with the preset elements, it is indicated that an element meeting the test expectation has been loaded on a display interface, that is, the target element meets a preset display scene, and the display interface loaded with the target element is determined to be the target display interface.

For example, a preset control exists in a preset display scene, a preset element on the preset control is "ok", when the preset control is loaded on the display interface, the element displayed on the preset control is a target element, when the target element is "ok", the target element is consistent with the preset element, the display interface meets the preset scene, and the display interface is determined to be the target display interface.

Alternatively, the preset element of the present embodiment may be obtained by obtaining a display position of the currently loaded target element on the display interface as follows. According to a first preset mapping relation, preset elements corresponding to the display positions are obtained, wherein the first preset mapping relation comprises a plurality of display positions and a plurality of corresponding relations between the preset elements, the plurality of display positions correspond to the preset elements one by one, and one display position corresponds to one preset element. For example, the first preset relationship includes that the display position a corresponds to the preset element "ok", the display position B corresponds to the preset element "cancel", and the display position C corresponds to the preset element "back". If the display position of the target element is C in this embodiment, based on the first preset relationship, the display position C of the target element corresponds to the preset element "return". And if the target element is matched with the preset element, determining that the currently loaded target element meets the preset display scene, and continuing to explain by combining the above example, if the target element is 'return', the preset element 'return' is matched with the target element 'return', and the target element loaded on the display interface is consistent with the expected preset element, wherein the test result is that the currently loaded target element meets the preset display scene. If the target elements are not matched, the currently loaded target elements do not meet the preset display scene, and by continuing combining the above example, if the target elements are confirmed, the preset elements return to be not matched with the target elements confirmed, which indicates that the target elements appearing on the display interface are not the preset elements expected to appear, and the test result is that the currently loaded target elements do not meet the preset display scene, and the backstage personnel modify the software program for displaying the interface according to the test result, so that the actually loaded elements are consistent with the expected elements.

Step S140: and loading a test case, and testing the target display interface according to the test case.

After the target display interface is determined to be loaded, the electronic equipment loads a test case corresponding to the target display interface, wherein the test case comprises a test rule written by a program or a code, and the target display interface is tested according to the test rule contained in the test case.

Optionally, after the target display interface is loaded, a smaller time interval is preset, for example, 0.2 second, and after the electronic device loads the target display interface for 0.2 second, the time interval is set to load the test case corresponding to the target display interface, so that the test case is loaded after the target display interface is successfully loaded, and the test success rate is improved.

The electronic device loads the test case from the storage location. In some embodiments, the test cases may be pre-stored locally on the electronic device, and when the electronic device needs to use the test cases, the test cases may be quickly loaded locally from the electronic device. Moreover, because the test case is stored in the local electronic equipment, the loading speed of the test case can be effectively prevented from being reduced due to the influence of network factors, and the test of the display interface is ensured to be rapidly carried out.

In other embodiments, the test case may be pre-stored in a server in communication connection with the electronic device, when the electronic device needs to load the test case, the test requirement may be sent to the server, the server responds to the test requirement and feeds back the test case, and the electronic device loads the test case from the server.

And testing the target display interface according to the test rule included in the test case to obtain a test result, wherein the test result can include that the test passes TURE or test failure FALSE and a corresponding reason. The obtained test result can be fed back to the background or directly displayed on the electronic equipment to inform the tester of the test result.

In the display interface testing method provided by this embodiment, a target element loaded on a display interface is detected when a display interface is loaded by an electronic device, the target element currently loaded on the display interface is acquired when the target element is detected, the display interface loaded with the target element is determined as the target display interface when the currently loaded target element meets a preset display scene, a test case is loaded after the target display interface is successfully loaded, the target display interface is tested according to the test case, and the test case is loaded after the display interface is loaded, so that the target display interface can be successfully tested by the test case to a certain extent, and the success rate of test of the test case and the stability of the test are improved.

Optionally, in the above embodiment, when determining whether the currently loaded target element meets the preset display scene, the obtained determination result may further include, in addition to the case that the currently loaded target element meets the preset display scene in the foregoing embodiment, determining the display interface as the target display interface, in this embodiment: if the target element does not meet the preset display scene, which indicates that an abnormal pop-up window may appear on the display window loaded with the target element, the step of step S110 is continuously executed, that is, the step of detecting the target element loaded on the display interface is continuously executed.

In some embodiments, preset elements are preset, where the preset elements are elements expected by a tester, and when a currently loaded target element is inconsistent with the preset elements, it is described that an element expected by a full test is not loaded on a display interface temporarily, and the target element does not meet a preset display scene and needs to continue waiting.

For example, a preset element is preset as a "name" in a preset display scene, and when a target element loaded on a display interface is the "identity card number", and the target element "identity card number" is inconsistent with the preset element "name", the display interface is not loaded completely, or a display page expected by a tester is not loaded, and the display interface needs to continue waiting.

And when the step of detecting the target element loaded on the display interface is executed again, the actual acquisition times are increased progressively once, until the target element acquired again within the preset acquisition times is matched with the preset element, the target element acquired again meets the preset display scene, and the display interface is determined as the target display interface for subsequent tests. That is to say, the actual acquisition times are at most preset acquisition times, and as one mode, preset acquisition times are pre-configured in the public configuration file, where the preset acquisition times are times of returning to the step of performing detection on the target element loaded on the display interface, and the preset acquisition times are used to limit the times of repeatedly acquiring the target element, and for example, the preset acquisition times may be 3 times, 6 times, and the like.

Optionally, the preset obtaining times preconfigured in the public configuration file may be a fixed value, for example, may be 5 times, after the preset obtaining times are configured, the step of detecting the target element loaded on the display interface is executed again is mostly a fixed preset obtaining times, and in order to adapt to different test scenarios, the tester may adjust the fixed preset obtaining times, for example, may adjust the fixed preset obtaining times to 6 times.

Optionally, the preset obtaining times preconfigured in the common configuration file may be variable, and the variable preset obtaining times may be more adapted to different preset display scenarios, for example, the preset obtaining times may vary along with the display interface testing system 100, the electronic device 110, the server 120, and the communication network 130 in fig. 1. As an implementation manner, a current state of the electronic device is obtained, where the current state at least includes a current network state, and the current network state includes a network speed at the electronic device, for example, the network speed is 8kb/s and 0.6kb/s, and then a preset obtaining number is determined based on the current network state.

As one of the modes, a preset network state is preset, for example, the preset network state is 7kb/s, and the preset network state is compared with the preset network state; under the condition that the current network state is superior to the preset network state, for example, the preset network state is 7kb/s, and the current network state is 8kb/s, the current network state is 8kb/s superior to the preset network state 7kb/s, which represents that the current network state of the electronic equipment is better, and the first acquisition times can be configured; or, when the preset network state is better than the current network state, for example, the preset network state is 7kb/s, and the current network state is 0.6kb/s, the preset network state is 7kb/s better than the current network state 0.6kb/s, which indicates that the current network status of the electronic device is poor, and the second acquisition times may be configured, where the first acquisition times are more than the second acquisition times. That is, the preset acquiring times determined when the current network state is better than the preset network state is greater than the preset acquiring times determined when the preset network state is better than the current network state.

As another mode, a correspondence between a plurality of network states and the number of acquisition times is established in advance, and when the network state of the electronic device is detected, the number of acquisition times corresponding to the network state is acquired based on the correspondence.

As another embodiment, the network status may further include processor remaining resources, such as remaining space of the random access memory, acquiring the processor remaining resources of the electronic device, determining the acquisition times based on the processor remaining resources, and regarding the acquisition times as the preset acquisition times. And when the processor residual resource is larger than the preset residual resource, acquiring a third acquisition frequency, and when the processor residual resource is smaller than or equal to the preset residual resource, acquiring a fourth acquisition frequency, wherein the third acquisition frequency is more than the fourth acquisition frequency.

The embodiment provides a method for testing a display page, which includes detecting and acquiring a target element loaded on a display interface when the display interface is loaded by an electronic device; judging whether the currently loaded target elements meet a preset display scene or not; when the currently loaded target element is judged to meet the preset display scene, the display page loaded with the target element can be tested; when the currently loaded target elements do not meet the preset display scene, the display interface loaded with the reacquired target elements is tested, and when the target elements meeting the preset display scene are loaded, the display page is tested.

Optionally, on the basis of the foregoing embodiment, this embodiment provides a display interface testing method, fig. 3 shows a schematic flow chart of the display interface testing method provided in another embodiment of the present application, and please refer to fig. 3, where the display interface testing method specifically includes the following steps:

step S210: and under the condition that the electronic equipment loads the display interface, detecting the target elements loaded on the display interface within a preset waiting time.

In the case of loading a display interface on electronic equipment, an explicit waiting method is used, a preset waiting time length is preset and stored in a public configuration file, when a target element needs to be detected, the preset waiting time length is obtained from the public configuration file, the target element loaded on the display interface is detected within the preset waiting time length, if the target element is not loaded on the display interface after the waiting time length exceeds the preset waiting time length, the loading failure of a target display page is explained, the detection of the target element is finished, because the target element is not detected, the loading failure of the target display interface and the test of the target display interface are also failed, prompts such as 'loading failure of the target display interface' or 'loading failure' and the like can be displayed on the electronic equipment to prompt a tester to investigate the reason of the loading failure, such as poor network instruction.

Step S220: and acquiring the currently loaded target elements on the display interface.

Step S230: and under the condition that the currently loaded target elements meet a preset display scene, determining the display interface as a target display interface.

In this embodiment, for specific description of steps S220 to S230, reference may be made to steps S120 to S130 in the above embodiment, which is not described herein again.

Step S240: and determining a plurality of function points on the target display interface.

The function points can be understood as positions on the target display interface where functions of the target display interface need to be tested, and a plurality of function points are distributed on the display interface. Optionally, the tester may select a plurality of function points in advance, or select a plurality of function points in a place where problems easily occur according to historical verification data.

Step S250: and loading the test case, and testing the plurality of functional points according to the test case.

And loading the test case, and testing the plurality of functional points according to the test rule carried in the test case so as to realize the test of the target display interface.

In some embodiments, a test case is loaded, and the plurality of function points are tested one by one according to a test sequence of the plurality of function points set by a test rule in the test case until the last function point in the plurality of function points is tested, and the test of the whole target display interface is determined to be finished. Or loading the test cases, acquiring the position sequence of the plurality of test cases, testing the plurality of function points one by the test cases according to the position sequence until each function point is tested, and determining that the test of the whole target display interface is finished.

In other embodiments, a part of function points may be selected from a plurality of function points as target function points, the target function points are tested, and a display interface test rate is increased, where fig. 4 shows a flowchart of step S250 of the display interface test method shown in fig. 3 of the present application, please refer to fig. 4, and step S250 includes the following sub-steps:

substep S251: and acquiring a first duration, wherein the first duration is the duration of the target element currently loaded in the display interface.

The method comprises the steps of obtaining the duration of loading a target element on a display interface as a first duration, wherein the first duration refers to the duration from the beginning of loading to the successful loading of the target element. For example, the first period of time is 2 s.

It should be noted that, if the currently loaded target element does not satisfy the preset display scene, step S210 needs to be repeatedly executed, that is, when the electronic device loads the display interface, the target element loaded on the display interface is detected within the preset waiting time, the target element is obtained in a circulating manner until the target element satisfying the preset display scene is obtained within the preset waiting time, and in the case of obtaining the target element in a circulating manner, the first time duration is a time duration from starting to load to successfully loading the target element satisfying the preset display scene.

Substep S252: and obtaining a second time length according to the difference between a preset waiting time length and the first time length, wherein the preset waiting time length is the testing time length of the target display interface.

For a scenario of testing an automatically switched display interface (e.g., a slide display interface, a video playing page, etc.), the time for testing each target display interface is limited, the test duration for each target display interface may be a preset wait duration, and a second duration is obtained according to a difference between the preset wait duration and the first duration, where the second duration may represent a duration of testing a target function point and may also represent a duration of testing the target display interface. It can be understood that, when the speed of loading the target display interface is faster, the first duration is correspondingly shorter, the second duration left for the display interface test is longer, and conversely, when the speed of loading the target display interface is slower, the first duration is correspondingly longer, and the second duration left for the display interface test is correspondingly shorter.

Sub-step S253: and determining a target function point from the plurality of function points according to the second time length.

The second duration is a duration for testing the function points, and the longer the second duration is, the more time the electronic device has to test the function points, so that more function points can be selected as the target function points, whereas the shorter the second duration is, the less time the electronic device has to test the function points, so that less function points can be selected as the target function points.

As a mode, a second preset mapping relationship is pre-established, where the second preset mapping relationship includes a correspondence between a plurality of second durations and a plurality of numbers, the plurality of second durations correspond to the plurality of numbers one to one, and one second duration corresponds to one number. It can be understood that each of the plurality of second durations corresponds to one quantity, for example, the second preset mapping relationship includes 5 function points corresponding to 0.2 second and 9 function points corresponding to 0.8 second, and it can be understood that, when the value of the second duration is inconsistent with the second duration in the second preset mapping relationship, the value can be rounded to perform the value taking, and then the corresponding quantity of the function points is found. And acquiring a target number corresponding to the second duration based on a second preset mapping relation, wherein the target number is less than or equal to the total number of the plurality of function points, that is, the selected target number does not exceed the total number of the function points on the display interface. The target function point needs to be verified through the test cases, and the number of the test cases is at least one.

Substep S254: and loading the test case, and testing the target function point according to the test case.

And loading a test case, wherein the test case carries a test rule, and testing the target function point according to the test rule so as to realize the test of the target display page loaded with the target function point.

In this embodiment, when the electronic device loads the display interface, the target element loaded on the display interface is detected, the currently loaded target element is obtained, when the currently loaded target element meets the preset display scene, the display interface loaded with the target element is determined as the target display interface, a plurality of function points are determined on the target display interface, part of the function points are selected from the plurality of function points as the target function points, then the test case is loaded, and the target function points are tested according to the test case, so that the target display interface is tested, only part of the target function points are tested, and the test rate is improved.

On the basis of the foregoing embodiment, the present embodiment provides a display interface testing method, fig. 5 shows a schematic flow chart of the display interface testing method provided in another embodiment of the present application, and please refer to fig. 5, the display interface testing method may specifically include the following steps:

step S301: and detecting the target element.

When the electronic device loads the display page, the target element is detected by a pre-packaged public method, such as (expected _ conditions. visibility _ of _ element _ location), (WebDriveWait. unit), and the like

Step S302: and judging whether the target element appears.

When the target element is not present, i.e. the target element is not loaded on the display page, step S303 is performed, otherwise, when the target element is present, i.e. the target element is loaded on the display page, step S304 is performed.

Step S303: and judging whether the time is within the preset waiting time.

When the time is within the waiting time period, the flow returns to step S301 to continue detecting the target element, and when the time is not within the waiting time period, the flow proceeds to step S310.

Step S304: and acquiring interface element values.

The interface element value refers to a specific meaning represented by the target element, for example, the target element is an element in a preset position (for example, in the lower right corner of the display interface), and the element value is "confirmation".

Step S305: it is determined whether the element value meets expectations.

When the element value does not meet the expectation, the flow proceeds to step S306, whereas when the element value meets the expectation, the flow proceeds to step S307.

Step S306: and judging whether the circulation times are more than the set times.

When the number of cycles is less than the set number, the process returns to step S304, whereas when the number of cycles is greater than the set number, the process proceeds to step S310.

Step S307: and checking the target display page. I.e. it is checked whether the target page is tune.

When the verification result is tune, the flow proceeds to step S308, whereas when the verification result is FALSE, the flow proceeds to step S309.

Step S308: and obtaining a first checking result, and then the test is passed.

And displaying the first verification result on a display screen of the electronic equipment, and displaying the verification result in a text form of 'verification pass' or broadcasting the verification pass in a voice playing form. The first verification result can also be fed back to the back-end server.

Step S309: and obtaining a second check result, and failing the test.

And displaying the second check result on the electronic equipment, for example, displaying the second check result in a form of 'check fail' text, and displaying a corresponding fail reason, so that modification is facilitated. The second check result can also be fed back to the back-end server.

Step S310: and finishing the verification.

In this embodiment, for the specific description of steps S301 to S310, reference may be made to the steps in the above embodiments, and details are not repeated here.

To implement the foregoing method embodiments, this embodiment provides a display interface testing apparatus, fig. 6 shows a block diagram of the display interface testing apparatus provided in an embodiment of the present application, and referring to fig. 6, the display interface testing apparatus 200 includes: a loading module 210, an acquisition module 220, a determination module 230, and a testing module 240.

The loading module 210 is configured to, when the electronic device loads a display interface, detect a target element loaded on the display interface;

an obtaining module 220, configured to obtain, when the target element is detected, a currently loaded target element on the display interface;

a determining module 230, configured to determine the display interface as a target display interface when the currently loaded target element meets a preset display scene;

and the test module 240 is configured to load a test case and test the target display interface according to the test case.

Optionally, the display interface testing apparatus 200 further includes: and a circulation module.

And the circulation module is used for continuously executing the step of detecting the target elements loaded on the display interface under the condition that the currently loaded target elements do not meet a preset display scene until the reacquired target elements within the preset acquisition times are matched with the preset elements, determining that the reacquired target elements meet the preset display scene, and determining the display interface as the target display interface, wherein the preset acquisition times are the times of returning to execute the step of detecting the target elements loaded on the display interface.

Optionally, the display interface testing apparatus 200 further includes: the device comprises a state acquisition module and a frequency determination module.

The state acquisition module is used for acquiring the current network state of the electronic equipment;

and the frequency determining module is used for determining the preset acquiring frequency based on the current network state, wherein the preset acquiring frequency determined when the current network state is better than the preset network state is greater than the preset acquiring frequency determined when the preset network state is better than the current network state.

Optionally, the determining module 230 comprises: the display device comprises a display position determining submodule, a mapping submodule and a preset element determining submodule.

The display position determining submodule is used for acquiring the display position of the currently loaded target element on the display interface;

the mapping sub-module is used for acquiring preset elements corresponding to the display positions according to a first preset mapping relation, wherein the first preset mapping relation comprises corresponding relations between a plurality of display positions and a plurality of preset elements, and the plurality of display positions correspond to the plurality of preset elements one to one;

and the preset element determining submodule is used for determining that the currently loaded target element meets a preset display scene under the condition that the target element is matched with a preset element.

Optionally, the loading module 210 includes: waiting for the submodule.

And the waiting submodule is used for detecting the target elements loaded on the display interface within a preset waiting time when the electronic equipment loads the display interface.

Optionally, the test module 240 comprises: a function point driving submodule and a testing submodule.

The function point driving submodule is used for determining a plurality of function points on the target display interface;

and the test submodule is used for loading the test case and testing the plurality of functional points according to the test case.

Optionally, the test sub-module comprises: the device comprises a first time length obtaining submodule, a second time length obtaining submodule, a target function point determining submodule and a target function point testing submodule.

The first time length obtaining submodule is used for obtaining a first time length, wherein the first time length is the time length of the target element currently loaded on the display interface;

the second duration obtaining submodule is used for obtaining second duration according to the difference between preset waiting duration and the first duration, and the preset waiting duration is testing duration of the target display interface;

the target function point determining submodule is used for determining a target function point from the plurality of function points according to the second time length;

and the target function point testing submodule is used for loading the test case and testing the target function point according to the test case.

Optionally, the target function point determining sub-module includes: a target number determination submodule and a target function point.

The target number determining submodule is used for acquiring the number corresponding to the second duration as the target number based on a second preset mapping relation, wherein the second preset mapping relation comprises the corresponding relation between a plurality of second durations and a plurality of numbers, and the plurality of second durations correspond to the plurality of numbers one to one;

and the target function point determining submodule is used for selecting the function points with the target number from the plurality of function points as the target function points.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, the coupling between the modules may be electrical, mechanical or other type of coupling.

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

Fig. 7 is a block diagram of an electronic device for executing a display interface testing method according to an embodiment of the present application, please refer to fig. 7, which shows a block diagram of an electronic device 110 according to an embodiment of the present application. The electronic device 110 may be a smart phone, a tablet computer, an electronic book, or other electronic devices capable of running an application. The electronic device 110 in the present application may include one or more of the following components: a processor 111, a memory 112, and one or more applications, wherein the one or more applications may be stored in the memory 112 and configured to be executed by the one or more processors 111, the one or more programs configured to perform a method as described in the aforementioned method embodiments.

Processor 111 may include one or more processing cores, among others. The processor 111, which is connected to various parts throughout the electronic device 110 using various interfaces and lines, performs various functions of the electronic device 110 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 112 and calling data stored in the memory 112. Alternatively, the processor 111 may be implemented in hardware using at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 111 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the components to be displayed; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 111, but may be implemented by a communication chip.

The Memory 112 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). The memory 112 may be used to store instructions, programs, code sets, or instruction sets. The memory 112 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like. The stored data area may also store data created by electronic device 110 in use (such as historical configuration files), and the like.

Fig. 8 shows a storage unit for storing or carrying program codes for implementing a display interface testing method according to an embodiment of the present application, and please refer to fig. 8, which shows a block diagram of a computer-readable storage medium according to an embodiment of the present application. The computer-readable medium 300 has stored therein a program code that can be called by a processor to execute the method described in the above-described method embodiments.

The computer-readable storage medium 300 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer-readable storage medium 300 includes a non-volatile computer-readable storage medium. The computer readable storage medium 300 has storage space for program code 310 for performing any of the method steps of the method described above. The program code can be read from or written to one or more computer program products. The program code 310 may be compressed, for example, in a suitable form.

Optionally, an embodiment of the present application further provides a computer program product, where the computer program product includes a computer program/instruction, and the computer program/instruction, when executed by a processor, implements the above method.

To sum up, the application provides a display interface testing method, a display interface testing device, an electronic device, and a storage medium, when the electronic device loads a display interface, the target element loaded on the display interface is detected, the target element currently loaded on the display interface is obtained, when the currently loaded target element meets a preset display scene, the display interface loaded with the target element is determined as the target display interface, after the target display interface is ensured to be loaded successfully, a test case is loaded, the target display interface is tested according to the test case, and the test case is ensured to be capable of testing the target display interface successfully.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A display interface testing method is applied to electronic equipment, and the method comprises the following steps:

under the condition that the electronic equipment loads a display interface, detecting a target element loaded on the display interface;

under the condition that the target element is detected, acquiring the currently loaded target element on the display interface;

determining the display interface as a target display interface under the condition that the currently loaded target elements meet a preset display scene;

and loading a test case, and testing the target display interface according to the test case.

2. The method of claim 1, further comprising:

and under the condition that the currently loaded target element does not meet a preset display scene, returning to execute the step of detecting the loaded target element on the display interface, and determining that the reacquired target element meets the preset display scene and the display interface is determined as the target display interface under the condition that the reacquired target element within preset acquisition times is matched with a preset element, wherein the preset acquisition times are the times of returning to execute the step of detecting the loaded target element on the display interface.

3. The method of claim 2, further comprising:

acquiring the current network state of the electronic equipment;

and determining the preset acquisition times based on the current network state, wherein the preset acquisition times determined when the current network state is superior to the preset network state are greater than the preset acquisition times determined when the preset network state is superior to the current network state.

4. The method according to claim 2, wherein the determining the display interface as the target display interface in the case that the currently loaded target element meets a preset display scene comprises:

acquiring the display position of the currently loaded target element on the display interface;

acquiring preset elements corresponding to the display positions according to a first preset mapping relation, wherein the first preset mapping relation comprises corresponding relations between a plurality of display positions and a plurality of preset elements, and one display position corresponds to one preset element;

and under the condition that the target element is matched with a preset element, determining that the currently loaded target element meets a preset display scene.

5. The method of claim 1, wherein the loading a test case and testing the target display interface according to the test case comprises:

determining a plurality of function points on the target display interface;

and loading the test case, and testing the plurality of functional points according to the test case.

6. The method of claim 5, wherein the loading the test case and testing the plurality of function points according to the test case comprises:

acquiring a first duration, wherein the first duration is the duration of a target element currently loaded in the display interface;

obtaining a second time length according to the difference between a preset waiting time length and the first time length, wherein the preset waiting time length is the testing time length of the target display interface;

determining a target function point from the plurality of function points according to the second duration;

and loading the test case, and testing the target function point according to the test case.

7. The method of claim 6, wherein determining a target function point from the plurality of function points according to the second duration comprises:

acquiring a target number corresponding to the second time length based on a second preset mapping relation, wherein the second preset mapping relation comprises corresponding relations between various second time lengths and various numbers, and one second time length corresponds to one number;

and selecting the target number of function points from the plurality of function points to determine the function points as target function points.

8. A display interface testing device is applied to electronic equipment, and the device comprises:

the loading module is used for detecting the target elements loaded on the display interface under the condition that the electronic equipment loads the display interface;

the acquisition module is used for acquiring the currently loaded target element on the display interface under the condition that the target element is detected;

the determining module is used for determining the display interface as a target display interface under the condition that the currently loaded target elements meet a preset display scene;

and the test module is used for loading a test case and testing the target display interface according to the test case.

9. An electronic device, comprising:

one or more processors;

a memory;

one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more applications configured to perform the method of any of claims 1-7.

10. A computer-readable storage medium, characterized in that a program code is stored in the computer-readable storage medium, which program code can be called by a processor to execute the method according to any of claims 1-7.

11. A computer program product comprising computer programs/instructions, characterized in that the computer programs/instructions, when executed by a processor, implement the method of any of claims 1-7.