Interface design automation test method, device, terminal equipment and storage medium

Abstract

The embodiment of the present invention discloses an interface design automated testing method, device, terminal device and storage medium. The method comprises: receiving a test instruction, confirming the operation to be tested according to the test instruction; obtaining the associated icon of the operation to be tested from an icon library according to the operation to be tested, the icons in the icon library are the same as the design icons of the software to be tested, and the icons respectively record icon information, and the icon information includes operation information, operation sequence and display position; confirming the final icon of the operation to be tested from the associated icons, confirming the preceding icons of the final icon in sequence according to the operation sequence, and displaying the associated icons in sequence at the display positions corresponding to the associated icons. This scheme can complete the rapid generation of reference interfaces related to software interface design testing during the software development process, improve the efficiency of software testing, and shorten the time between the basic completion of software development and the release of software.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of software testing technology, and in particular to an interface design automation testing method, apparatus, terminal equipment and storage medium. Background Art

[0002] Software testing is the process of running or measuring a software system using manual or automatic means, with the purpose of verifying whether it meets the specified requirements or clarifying the difference between the expected results and the actual results. In order to improve the efficiency of testing, the use of automated testing is increasing. One of the important test contents is to use control recognition or graphic recognition methods to determine whether the interface is normal after the software is running during the test.

[0003] When the inventors performed software testing based on the existing automated testing methods, they found that the reference interface used to determine whether the interface is normal or not requires that the software to be tested be basically developed and its functions be relatively stable before the reference interface can be generated. This processing method of generating the reference interface after the software development is basically completed results in a longer time between the basic completion of the software development and the release of the software. Summary of the invention

[0004] The present invention provides an interface design automation testing method, device, terminal equipment and storage medium to solve the technical problem that the processing mode of the prior art reference interface starts to be generated after the software development is basically completed, resulting in a long time between the basic completion of software development and the release of software.

[0005] In a first aspect, an embodiment of the present invention provides an interface design automation testing method, comprising:

[0006] receiving a test instruction, and confirming the operation to be tested according to the test instruction;

[0007] According to the operation to be tested, an associated icon of the operation to be tested is obtained from an icon library, wherein the icons in the icon library are the same as the design icons of the software to be tested, and the icons respectively record icon information, wherein the icon information includes operation information, operation sequence and display position;

[0008] A final icon of the operation to be tested is confirmed from the associated icons, preceding icons of the final icon are confirmed in sequence according to the operation sequence, and the associated icons are displayed in sequence at display positions corresponding to the associated icons.

[0009] In a second aspect, an embodiment of the present invention further provides an interface design automation testing device, comprising:

[0010] An instruction receiving unit, used for receiving a test instruction and confirming the operation to be tested according to the test instruction;

[0011] An icon acquisition unit, used for acquiring an associated icon of the operation to be tested from an icon library according to the operation to be tested, wherein the icons in the icon library are the same as the design icons of the software to be tested, and the icons are respectively recorded with icon information, wherein the icon information includes operation information, operation sequence and display position;

[0012] The icon display unit is used to confirm the final icon of the operation to be tested from the associated icons, confirm the preceding icons of the final icon in sequence according to the operation sequence, and display the associated icons in sequence at the display positions corresponding to the associated icons.

[0013] In a third aspect, an embodiment of the present invention further provides a terminal device, including:

[0014] one or more processors;

[0015] A memory for storing one or more programs;

[0016] When the one or more programs are executed by the one or more processors, the one or more processors implement the interface design automation testing method as described in any one of the first aspects.

[0017] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the interface design automation testing method as described in any one of the first aspects.

[0018] The above-mentioned interface design automation test method, device, terminal device and storage medium receive test instructions, confirm the operation to be tested according to the test instructions; obtain the associated icon of the operation to be tested from the icon library according to the operation to be tested, the icons in the icon library are the same as the design icons of the software to be tested, and the icons are respectively recorded with icon information, and the icon information includes operation information, operation sequence and display position; confirm the final icon of the operation to be tested from the associated icons, confirm the preceding icons of the final icon in sequence according to the operation sequence, and display the associated icons in sequence at the display positions corresponding to the associated icons. By uniformly recording the icon information of the icons related to the software to be tested, the icon display response related to the operation to be tested is quickly completed based on the icon information, and the rapid generation of the reference interface related to the software interface design test can be completed during the software development process, thereby improving the efficiency of software testing and shortening the time between the basic completion of software development and the release of software. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 A flowchart of an interface design automation testing method provided by an embodiment of the present invention;

[0020] Figure 2 A schematic diagram of an interactive tablet provided by an embodiment of the present invention;

[0021] Figure 3 A schematic diagram of icon information of an icon provided by an embodiment of the present invention;

[0022] Figure 4-Figure 6 A schematic diagram of interface changes of an operation to be tested provided by an embodiment of the present invention;

[0023] Figure 7 A schematic diagram of the structure of an interface design automation test device provided by an embodiment of the present invention;

[0024] Figure 8 A schematic diagram of the structure of a terminal device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0025] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only the parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0026] It should be noted that due to space limitations, this application description does not list all optional implementation methods. After reading this application description, those skilled in the art should be able to understand that as long as the technical features do not contradict each other, any combination of technical features can constitute an optional implementation method.

[0027] For example, in one implementation of the embodiment, a technical feature is recorded: the reference interface and the comparison interface are compared by optical character recognition or image recognition, and in another implementation of the embodiment, another technical feature is recorded: in response to an icon replacement instruction, the old icon is replaced by a new icon in the icon library, and the icon information of the old icon is recorded correspondingly to the new icon. Since the above two technical features do not contradict each other, those skilled in the art should be able to think of it after reading the specification of this application that when testing based on the replaced icon, it is also possible to take a screenshot based on the display of the replaced icon, and then compare it by optical character recognition or image recognition.

[0028] Each embodiment is described in detail below.

[0029] Figure 1 A flowchart of an interface design automation test method provided in an embodiment of the present invention. The interface design automation test method provided in the embodiment can be executed by an operating device for testing, which can be implemented by software and / or hardware, and can be composed of two or more physical entities or one physical entity. For example, the operating device of the interactive tablet can be a microprocessor, an embedded processor, or a CPU.

[0030] The interface design test targeted in this solution can be the test of software with different operating systems, different development languages, and different terminal forms, as long as the software has the need for interface design testing.

[0031] In the description of the embodiment, for ease of understanding, the detailed process of each test link when implementing the interface design automation test method is described by way of example using an interactive tablet as the actual carrier and whiteboard software as the object to be tested. Among them, the interactive tablet can be an integrated device that controls the content displayed on the display screen and realizes human-computer interaction through touch technology, and it integrates one or more functions such as a projector, an electronic whiteboard, a screen, a sound system, a television, and a video conferencing terminal.

[0032] Generally speaking, if Figure 2 As shown, the interactive tablet 1 includes at least one display screen. For example, the interactive tablet 1 is configured with a display screen with a touch function, and the display screen can be a capacitive screen, a resistive screen or an electromagnetic screen. In this embodiment, an interactive tablet is provided, and further, the user can implement touch operation by touching the display screen with a finger or a stylus, and accordingly, the interactive tablet detects the touch position and responds according to the touch position to implement the touch function. Typically, the interactive tablet is installed with at least one operating system, wherein the operating system includes but is not limited to an Android system, a Linux system and a Windows system. Further, the interactive tablet can install at least one application with a writing function. Among them, the application can be an application that comes with the operating system, and at the same time, an application downloaded from a third-party device or server is also installed. Optionally, in addition to the writing function, the application also has other editing functions, such as inserting a table, inserting a picture, inserting a figure, drawing a table, drawing a figure and the like. Among them, the drawn table or figure is a computer-drawn standard element. The computer-drawn standard element can be understood as a printed standard element drawn by the interactive tablet, which is different from the element written by the user.

[0033] On the touch screen configured with the interactive tablet, there is a writing area for responding to the user's writing operation to display the input content. When writing in the writing area, such as touching the touch screen with a stylus or a finger, the touch screen can sense the change in current, voltage or magnetic flux (corresponding to the specific setting type of the capacitive touch screen, resistive touch screen or electromagnetic touch screen), and obtain a touch signal containing the coordinates of the touch position and the trigger time of the touch signal. According to the coordinates of the touch position and the trigger time of the touch signal, the trajectory data of the writing trajectory input by the stylus or the user's finger each time from pressing down to lifting up to stop writing can be obtained, and the writing trajectory input by the user is displayed in real time in the writing area of ​​the touch screen according to the trajectory data. Of course, the writing process is not limited to writing. Any input process for displaying the operation trajectory implemented on the touch screen of the interactive tablet can be regarded as a writing process. In addition, according to the different display elements at the location where the touch operation occurs, the touch operation can be responded to as a user's click, drag and other operations. These different response methods are the same in the underlying coordinate processing method. In this embodiment, an exemplary description based on the whiteboard software test in the interactive tablet is given, for example Figure 2 The interactive interface of the whiteboard software shown has a toolbar 21. The tools in the toolbar 21 will each generate a corresponding interactive response after detecting a trigger. This solution is used to judge the presentation of the interactive response and confirm that the final form of the whiteboard software conforms to the set interactive logic. In this embodiment, the test process of each interactive operation in the whiteboard software is not described in detail, but the overall test principle is the same, and the test process of the interactive operation described in the reference example can be used.

[0034] Specifically, refer to Figure 1 , the interface design automation test method specifically includes:

[0035] Step S101: receiving a test instruction, and confirming the operation to be tested according to the test instruction.

[0036] In the existing automated testing process, the generation of automated test scripts requires sequential confirmation of the associated preceding operations of each operation to be tested, and this process is usually carried out after the software development is basically completed, which is equivalent to the time required to generate automated test scripts after the main work of software development is completed and before the formal test begins, and this generation process requires input of the process actions of the operation to be tested. In the prior art, the response to the test instruction is actually to run the already written automated test script, and the relevant actions of the operation to be tested are executed one by one in accordance with the automated test script.

[0037] In this solution, there is no process of writing the associated preceding operations of the operation to be tested one by one, and the test of the operation to be tested can be quickly completed based on the pre-edited icon information. Compared with the test process of the prior art, the test instructions in this solution may come from two testing links. The first is the link of actual testing of the software to be tested, and the second is the link of testing the display process of the associated icons. The first test goal is the ultimate goal of software testing, which is used to determine whether the interface design of the software to be tested is normally implemented according to the established goals; the second test goal is to observe whether the automated test script implemented based on this solution can obtain the interface design effect of the established goals.

[0038] Step S102: acquiring an associated icon of the operation to be tested from an icon library according to the operation to be tested, wherein the icons in the icon library are the same as the design icons of the software to be tested, and the icons respectively record icon information, wherein the icon information includes operation information, operation sequence and display position.

[0039] In this solution, automated test scripts are generated quickly based on icons. During the software development process, all relevant design icons of the same software are saved in the same icon library. Only icons saved in the icon library are used during the software development process, and automated test scripts are also generated based on the icon library. In this process, software development and automated test script generation do not interfere with each other and are implemented independently.

[0040] In order to realize the generation of automated test scripts based on the icons themselves, this solution has standardized the recording of all icon and test-related icon information. The first way to record icon information is to establish a database, with the icon as a column in the database and various icon information saved as columns respectively. When generating automated test scripts, the database is accessed to obtain the corresponding data. The second way to record icon information is to record the icon information separately through a table or other document-type files. The icon information recorded in the table or other document-type files is associated with the icon through the file name. The third way to record icon information is to use the attribute detailed information of the image file to record the corresponding icon information. This attribute detailed information is referred to as EXIF ​​(Exchangeable image file format) information, such as Figure 3 The above three are just exemplary descriptions of icon information. In the specific implementation process, any scheme that can realize the recording of icons and their corresponding icon information is within the scope of the association recording framework based on icon-icon information in this scheme.

[0041] In the icon information, the operation information is mainly used to record what operation to be tested the icon is applied to (for example Figure 3The icon in the test is used to start the operation sequence, and the operation sequence is used to record the operation sequence of the icon in the operation to be tested (for example Figure 3 The icon in corresponds to step 3 for display), the display position is used to record the display position of the icon when it is displayed (for example Figure 3 The icon in the image is displayed in the middle, and the corresponding coordinates are (630,500).

[0042] Based on the icon information, the file name of the image can be ignored when generating an automated test script, and the corresponding icon can be called only according to the icon information. In the actual processing process, there are multiple operations to be tested for a software to be tested, and the same icon may be the preceding icon of more than two operations to be tested. In order to accurately generate the automated test script corresponding to each operation to be tested, the same icon can be copied multiple times and saved in the icon library with different file names, and the corresponding icon information can be edited for each relevant operation to be tested; or the same icon only needs to be saved once, but the operation information, operation sequence and display position are recorded in the icon information according to the operation to be tested. For the former method, each icon only needs to edit a set of icon information, and the icon information of an icon can be obtained as a whole, which can simplify the editing process and the information processing process when reading the icon information; for the latter method, it can reduce the repeated saving of icons, and correspondingly reduce the complex file naming that may be caused by the same saving.

[0043] For the icons in the icon library, the icons corresponding to the same operation to be tested are confirmed as associated icons, and this association relationship is confirmed through the operation information in the icon information. For example, if the operation to be tested confirmed by the current test instruction is operation A, the operation information of the icons in the icon library is traversed, and the icons corresponding to the operation information and operation A are confirmed as associated icons. A simple correspondence method is that the name of the operation to be tested is the same as the content recorded in the operation information. Of course, it can also be that the name of the operation to be tested and the content recorded in the operation information exist in some form or information correspondence. After confirming that it is an associated icon, the operation order and position information in the icon information of the associated icon are directly read, and the subsequent icon display can be performed based on the operation order and position information. It should be noted that the operation order in this scheme is not the order in which the user operates it, but the order in which it is displayed.

[0044] Step S103: confirming the final icon of the operation to be tested from the associated icons, confirming the preceding icons of the final icon in sequence according to the operation sequence, and displaying the associated icons in sequence at the display positions corresponding to the associated icons.

[0045] When icons are displayed during automated testing, relevant icons are directly obtained according to the name of the operation to be tested. For example, for the "View 'About' page" operation, the response icon of "About" can be directly confirmed as the final icon, and based on the final icon, the preceding icons can be confirmed in sequence according to the order of operations until the first icon is confirmed, completing the entire icon chain of "About" related operations, and displaying and responding accordingly according to the actual test objectives.

[0046] The icon information further includes title information, and the title information is displayed corresponding to the associated icon.

[0047] In the specific implementation process, considering that some icons cannot confirm the corresponding operations from the icons themselves, a title can be added to the icon. The title information corresponding to the title is also a kind of icon information. When displayed, it should be displayed in the display area of ​​the associated icon, such as immediately below the icon. In the subsequent specific testing process, the icon can also provide an efficient judgment reference for whether the test interface is abnormal or not through optical character recognition.

[0048] Corresponding to the testing process at different stages, the interface design automation testing method may also have more specific test response steps. For the test instructions for testing the software to be tested, it also includes steps S140 to S160 to judge the actual operation results of the interface design.

[0049] Step S140: taking screenshots in sequence during the display of the associated icons to obtain a reference interface.

[0050] Step S150: taking screenshots in sequence during the running of the software to be tested to obtain a comparison interface.

[0051] Step S160: Compare the reference interface and the comparison interface accordingly, and confirm the interface design operation test result of the software to be tested according to the comparison result.

[0052] In the specific test judgment process, step S140-step S160 is an optional comparison method, that is, the execution process and execution result of the operation to be tested of the software to be tested are compared with the pre-confirmed reference interface. If the two interfaces are the same, the test result is confirmed to be normal, otherwise the test result is confirmed to be abnormal and the program needs to be further debugged. The specific comparison of the two interfaces can be achieved by optical character recognition or image recognition.

[0053] In addition, automated testing can be performed directly. According to the page to be executed, during the execution process, the area corresponding to each icon is intercepted to determine whether the area corresponds to the display position recorded in the icon information of the icon. Specifically, it can be confirmed by optical character recognition of the title information corresponding to the area, or it can be confirmed by image comparison.

[0054] The test instruction for testing the display process of the associated icon also includes step S170 of observing the test script running result.

[0055] Step S170: When the confirmation of the preceding icon is interrupted, a test abnormality is displayed.

[0056] In the normal processing process, a test operation confirmed by a test instruction can obtain multiple consecutive icons from the final icon to the starting icon in sequence. When this acquisition process cannot be completed in sequence, it indicates that the icon information of one of the icons, especially the operation information and operation sequence, is incorrect. At this time, the test exception is displayed to remind the user to confirm and adjust the icon information of the relevant icons. In addition, it is also possible that the operation information and operation sequence of the icon are normal, but the icon content or the display position of the icon is incorrect when generating the reference interface. This exception itself cannot be detected by the machine. It is necessary to manually judge this type of exception and manually test the terminal. After adjusting the relevant icons or display positions, test again until the reference interface is consistent with the designed interface. The rapid generation of the reference interface based on icon information can complete the debugging of the automated test synchronously with the software development. According to the test function, the page to be executed is obtained. According to the associated operation sequence, the relevant icons are displayed in the corresponding positions one by one to simulate the real operation, which is convenient for the debugging of the automated test process. The reference interface confirmed by debugging is the predetermined designed page, which effectively improves the efficiency of the automated test preparation period.

[0057] During the entire software development and corresponding testing process, the icons may be adjusted in the middle. Based on the corresponding icon changes, the interface design automation testing method also includes:

[0058] Step S180: In response to the icon replacement instruction, the old icon is replaced by the new icon in the icon library, and the icon information of the old icon is recorded in the new icon accordingly.

[0059] When there is an icon adjustment, the new icon directly replaces the old icon, and the icon information of the old icon is directly read and recorded in the new icon. When performing automated testing after the icon replacement, the new icon can be directly used to generate a reference interface.

[0060] Please refer to Figure 4-Figure 6, which is a schematic diagram of the interface changes of an automated test of an operation to be tested based on the present solution with the whiteboard software as the software to be tested. The operation to be tested is to realize "viewing the 'About' page". Based on the prior art, the automated test script needs to explain all the actions of "viewing the 'About' page" step by step, that is, it is necessary to explain "clicking 'Settings'" and "clicking 'About'" in the automated test script. In the present solution, the automated test script only needs to explain "clicking the 'About' page". The background will automatically obtain the predecessor icon of the "About" icon according to the icon information, and complete the relevant operations accordingly, and then identify and compare the page obtained after clicking "About" with the predetermined picture to confirm whether the operation to be tested is running normally.

[0061]

[0062]

[0063] The above is a schematic diagram of the interface changes of the automated test of viewing the "About" operation based on this solution using the whiteboard software as the software to be tested. Figure 6 This is the interface for the whiteboard software to check whether "About" is running normally. When editing the icon information of the associated icons, it includes at least the "Settings" icon, "Writing Settings" icon, "Writing Background" icon, "Scan Code Network" icon, "About" icon and "Whiteboard Writing" icon. The operation order of the "Settings" icon is 1; the operation order of the "Writing Settings" icon, "Writing Background" icon, "Scan Code Network" icon and "About" icon is 2; the operation order of the "Whiteboard Writing" icon is 3. The display positions of each icon correspond to Figure 6 As shown, the coordinate representation of the specific display position is not described in detail here. The coordinate representation of different software and different devices may be different, and this embodiment does not make any specific limitation. In the process of generating the reference interface, the response icon of viewing "About" and the corresponding preceding operations are automatically obtained, and the initial page can be confirmed in turn. Figure 4 As shown, after clicking to view "Settings", 4 icons with operation order 2 are further displayed in the corresponding positions as follows Figure 5 As shown, after clicking to view "About", the icons with the operation sequence of 3 are further displayed in the corresponding position as follows Figure 6 As shown. When writing automated test scripts based on this solution, the test and display information are edited based on the corresponding icons in advance. You only need to write the target operation to automatically associate the previous actions, avoiding writing actions one by one, and improving the efficiency of generating automated test scripts. Moreover, since the icons are directly generated according to the design icons in the software development process, what you see is basically what you get, which can effectively reduce the error rate in the process of writing automated test scripts.

[0064] In the above, a test instruction is received, and the operation to be tested is confirmed according to the test instruction; the associated icon of the operation to be tested is obtained from the icon library according to the operation to be tested, the icons in the icon library are the same as the design icons of the software to be tested, and the icons respectively record icon information, and the icon information includes operation information, operation sequence and display position; the final icon of the operation to be tested is confirmed from the associated icons, and the preceding icons of the final icon are confirmed in sequence according to the operation sequence, and the associated icons are displayed in sequence at the display positions corresponding to the associated icons. By uniformly recording the icon information of the icons related to the software to be tested, the icon display response related to the operation to be tested is quickly completed based on the icon information, and the rapid generation of the reference interface related to the software interface design test can be completed during the software development process, thereby improving the efficiency of software testing and shortening the time between the basic completion of software development and the release of software.

[0065] Figure 7 This is a schematic diagram of the structure of an interface design automation test device provided by an embodiment of the present invention. Figure 7 The interface design automation test device includes: an instruction receiving unit 210, an icon acquiring unit 220 and an icon display unit 230.

[0066] Among them, the instruction receiving unit 210 is used to receive the test instruction and confirm the operation to be tested according to the test instruction; the icon acquisition unit 220 is used to obtain the associated icon of the operation to be tested from the icon library according to the operation to be tested, the icons in the icon library are the same as the design icons of the software to be tested, and the icons respectively record icon information, and the icon information includes operation information, operation sequence and display position; the icon display unit 230 is used to confirm the final icon of the operation to be tested from the associated icons, confirm the preceding icons of the final icon in sequence according to the operation sequence, and display the associated icons in sequence at the display positions corresponding to the associated icons.

[0067] Based on the above embodiment, the test instruction is used to test the software to be tested;

[0068] The interface design automation test device also includes:

[0069] A first screenshot unit, used for sequentially taking screenshots to obtain a reference interface during the display of the associated icons;

[0070] A second screenshot unit, used for sequentially taking screenshots to obtain a comparison interface during the running of the software to be tested;

[0071] The interface comparison unit is used to compare the reference interface with the comparison interface, and confirm the interface design operation test result of the software to be tested according to the comparison result.

[0072] Based on the above embodiment, the reference interface and the comparison interface are compared through optical character recognition or image recognition.

[0073] Based on the above embodiment, the test instruction is used to test the display process of the associated icon;

[0074] The interface design automation test device also includes:

[0075] The abnormality display unit is used to display the test abnormality when the confirmation of the preceding icon is interrupted.

[0076] Based on the above embodiment, the interface design automation test device further includes:

[0077] The icon replacement unit is used to replace the old icon with a new icon in the icon library in response to the icon replacement instruction, and record the icon information of the old icon in the new icon accordingly.

[0078] Based on the above embodiment, the icon information is recorded in the exchangeable image file format information of the icon.

[0079] Based on the above embodiment, the icon information further includes title information, and the title information is displayed corresponding to the associated icon.

[0080] The interface design automation testing device provided in the embodiment of the present invention is included in a terminal device and can be used to execute any interface design automation testing method provided in the above embodiments, and has corresponding functions and beneficial effects.

[0081] It is worth noting that in the embodiment of the above-mentioned interface design automatic testing device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0082] Figure 8 A schematic diagram of the structure of a terminal device provided in an embodiment of the present invention is shown in FIG. Figure 8 As shown, the terminal device includes a processor 310, a memory 320, an input device 330, an output device 340 and a communication device 350; the number of processors 310 in the terminal device can be one or more. Figure 8 A processor 310 is taken as an example; the processor 310, the memory 320, the input device 330, the output device 340 and the communication device 350 in the terminal device can be connected via a bus or other means. Figure 8 The example of connecting through bus is taken in the following.

[0083] The memory 320, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the interface design automation test method in the embodiment of the present invention (for example, the instruction receiving unit 210, the icon acquisition unit 220 and the icon display unit 230 in the interface design automation test device). The processor 310 executes various functional applications and data processing of the terminal device by running the software programs, instructions and modules stored in the memory 320, that is, realizes the above-mentioned interface design automation test method.

[0084] The memory 320 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory 320 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 320 may further include a memory remotely arranged relative to the processor 310, and these remote memories may be connected to the terminal device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0085] The input device 330 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the terminal device. The output device 340 may include a display device such as a display screen.

[0086] The above-mentioned terminal device includes an interface design automation testing device, which can be used to execute any interface design automation testing method and has corresponding functions and beneficial effects.

[0087] An embodiment of the present invention also provides a storage medium containing computer executable instructions, which, when executed by a computer processor, are used to perform relevant operations in the interface design automation testing method provided in any embodiment of the present application, and have corresponding functions and beneficial effects.

[0088] Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products.

[0089] Therefore, the present application may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code. The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the functions in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory produce a product including an instruction device, which implements the functions specified in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide for implementing the process in the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0090] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory. The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0091] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0092] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0093] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An interface design automation testing method, characterized in that: include: Receiving a test instruction and confirming the operation to be tested according to the test instruction, wherein the test instruction is used to test the software to be tested; According to the operation to be tested, an associated icon of the operation to be tested is obtained from an icon library, wherein the icons in the icon library are the same as the design icons of the software to be tested, and the icons are respectively recorded with icon information, wherein the icon information includes operation information, operation sequence and display position, and the operation sequence is used to record the sequence of corresponding icons in the operation to be tested; Confirming the final icon of the operation to be tested from the associated icons, confirming the preceding icons of the final icon in sequence according to the operation sequence, and displaying the associated icons in sequence at the display positions corresponding to the associated icons; During the display process of the associated icons, screenshots are taken in sequence to obtain a reference interface; During the operation of the software to be tested, screenshots are taken in sequence to obtain a comparison interface; The reference interface and the comparison interface are compared correspondingly, and the interface design operation test result of the software to be tested is confirmed according to the comparison result.

2. The interface design automation testing method according to claim 1, characterized in that: The reference interface and the comparison interface are compared by optical character recognition or image recognition.

3. The interface design automation testing method according to claim 1, characterized in that: The test instruction is used to test the display process of the associated icon; The interface design automation testing method further includes: When the confirmation of the preceding icon is interrupted, a test abnormality is displayed.

4. The interface design automation testing method according to claim 1, characterized in that: Also includes: In response to the icon replacement instruction, the old icon is replaced by the new icon in the icon library, and the icon information of the old icon is recorded correspondingly to the new icon.

5. The interface design automation testing method according to claim 1, characterized in that: The icon information is recorded in the exchangeable image file format information of the icon.

6. The interface design automation testing method according to claim 1, characterized in that: The icon information further includes title information, and the title information is displayed corresponding to the associated icon.

7. An interface design automation test device, characterized in that: include: An instruction receiving unit, used for receiving a test instruction and confirming the operation to be tested according to the test instruction, wherein the test instruction is used for testing the software to be tested; An icon acquisition unit, used for acquiring an associated icon of the operation to be tested from an icon library according to the operation to be tested, wherein the icons in the icon library are the same as the design icons of the software to be tested, and the icons are respectively recorded with icon information, wherein the icon information includes operation information, operation sequence and display position, and the operation sequence is used for recording the sequence of corresponding icons in the operation to be tested; An icon display unit, used to confirm the final icon of the operation to be tested from the associated icons, confirm the preceding icons of the final icon in sequence according to the operation sequence, and display the associated icons in sequence at the display positions corresponding to the associated icons; During the display process of the associated icons, screenshots are taken in sequence to obtain a reference interface; During the operation of the software to be tested, screenshots are taken in sequence to obtain a comparison interface; The reference interface and the comparison interface are compared correspondingly, and the interface design operation test result of the software to be tested is confirmed according to the comparison result.

8. A terminal device, characterized in that: include: one or more processors; A memory for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the interface design automation testing method as described in any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the interface design automation testing method as described in any one of claims 1 to 6 is implemented.

Images