Method and apparatus for checking interface of application, and device and medium

Abstract

Provided are a method and apparatus for checking an interface of an application, and a device and a medium. One method comprises: on the basis of an interface description of an interface of an application, determining at least one visual element in the interface of the application; acquiring a constraint associated with the interface of the application; on the basis of the constraint, checking the at least one visual element; and in response to determining that a visual element among the at least one visual element does not comply with the constraint, providing alert information to indicate that the visual element fails to pass interface check. By using the implementations of the present disclosure, whether each visual element in an interface of an application complies with a constraint can be automatically checked. In this way, interface check can be executed in a more effective manner, thereby improving the development efficiency of an application.

Description

Methods, apparatus, devices, and media for inspecting application interfaces. Technical Field

[0001] The implementation of this disclosure generally relates to application management, and in particular to methods, apparatus, devices, and computer-readable storage media for inspecting the interface of an application. Background Technology

[0002] With the development of computer and internet technologies, applications can offer a wide variety of functionalities. An application's interface can include numerous visual elements (e.g., menu items, buttons, text, images, etc.) to achieve these functionalities. During application development, to ensure the application provides the expected functionality, it's necessary to check whether various visual elements conform to predetermined constraints. However, manual checking incurs significant manpower and time costs, leading to low development efficiency. Therefore, it is desirable to automate the checking of application interfaces to improve application development efficiency. Summary of the Invention

[0003] In a first aspect of this disclosure, a method for inspecting the interface of an application is provided. In this method, at least one visual element in the application's interface is determined based on an interface description of the application's interface. Constraints associated with the application's interface are obtained. The at least one visual element is inspected based on the constraints. In response to determining that a visual element among the at least one visual element does not conform to the constraints, an alarm message is provided to indicate that the visual element has failed the interface inspection.

[0004] In a second aspect of this disclosure, an apparatus for inspecting the interface of an application is provided. The apparatus includes: a determining module configured to determine at least one visual element in the interface of the application based on an interface description of the application's interface; an acquiring module configured to acquire constraints associated with the interface of the application; an inspecting module configured to inspect the at least one visual element based on the constraints; and a providing module configured to provide an alarm message indicating that the visual element failed the interface inspection in response to determining that the visual element among the at least one visual element does not conform to the constraints.

[0005] In a third aspect of this disclosure, an electronic device is provided. The electronic device includes: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to a first aspect of this disclosure when executed by the at least one processing unit.

[0006] In a fourth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, causes the processor to implement the method according to a first aspect of this disclosure.

[0007] In a fifth aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method according to a first aspect of this disclosure.

[0008] It should be understood that the content described in this content section is not intended to limit the key or essential features of the implementation of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0009] In the following detailed description, the above and other features, advantages, and aspects of the various implementations of this disclosure will become more apparent, taken in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0010] Figure 1 shows a block diagram of an application environment according to one implementation of the present disclosure;

[0011] Figure 2 shows a block diagram of an interface for inspecting an application according to some implementations of this disclosure;

[0012] Figure 3 shows a block diagram of the inspection interface of an inspection tool according to some implementations of this disclosure;

[0013] Figure 4 shows a block diagram of another inspection interface of the inspection tool according to some implementations of this disclosure;

[0014] Figure 5 shows a block diagram of the interactive interface of an inspection tool according to some implementations of this disclosure;

[0015] Figure 6 shows a block diagram of the process of performing interface inspection using an interface inspection tool according to some implementations of this disclosure;

[0016] Figure 7 shows a flowchart of a method for inspecting the interface of an application according to some implementations of this disclosure;

[0017] Figure 8 shows a block diagram of an apparatus for inspecting an application interface according to some implementations of this disclosure; and

[0018] Figure 9 shows a block diagram of a device capable of implementing various implementations of the present disclosure. Detailed Implementation

[0019] Implementations of this disclosure will now be described in more detail with reference to the accompanying drawings. While some implementations of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the implementations set forth herein. Rather, these implementations are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and implementations of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0020] In the description of the implementation methods disclosed herein, the term "comprising" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one implementation" or "the implementation" should be understood as "at least one implementation". The term "some implementations" should be understood as "at least some implementations". Other explicit and implicit definitions may also be included below. As used herein, the term "model" can represent the relationships between various data. For example, the aforementioned relationships can be obtained based on various currently known and / or future-developed technical solutions.

[0021] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition or use of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0022] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure through appropriate means in accordance with relevant laws and regulations, and user authorization should be obtained.

[0023] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose whether to provide personal information to the software or hardware, such as the electronic device, application, server, or storage medium performing the operations of this disclosed technical solution, based on the prompt message.

[0024] As an optional but non-restrictive implementation, in response to a user's active request, a prompt message can be sent to the user, for example, via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose whether to "agree" or "disagree" to provide personal information to the electronic device.

[0025] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0026] The term "in response to" as used herein refers to a state in which a corresponding event occurs or a condition is satisfied. It will be understood that the timing of subsequent actions performed in response to such event or condition is not necessarily strongly correlated with the time when the event occurs or the condition is met. For example, in some cases, subsequent actions may be performed immediately upon the occurrence of the event or the fulfillment of the condition; while in others, they may be performed some time after the occurrence of the event or the fulfillment of the condition.

[0027] Example Environment

[0028] With the development of computer and internet technologies, applications can provide a wide variety of functions. The application interface can include numerous visual elements (e.g., menu items, buttons, text, images, tabs, lists, selection boxes, etc.). Referring to Figure 1, which describes an application environment according to some implementations of this disclosure, Figure 1 shows a block diagram 100 of an application environment according to one implementation of this disclosure. As shown in Figure 1, the application interface 110 can include multiple visual elements, which may include, for example, controls within the application. For example, visual elements 121 and 122 may represent tabs in interface 110, visual elements 123, 124, and 125 may represent buttons in the application, and visual elements may include text within the application, etc.

[0029] During application development, to ensure the application provides the expected functionality, it's necessary to check whether various visual elements conform to predetermined constraints. For example, this involves checking whether the various attributes of each visual element (e.g., shape, size, position, corresponding text, etc.) meet the requirements. Manual checking incurs significant manpower and time costs, leading to low development efficiency. While checking tools exist to assist in interface inspection, these tools lack flexibility, preventing developers from customizing constraints for visual elements. Furthermore, developers need to switch back and forth between checking tools and the application's interface, resulting in low efficiency. Therefore, there is a desire for automated methods to check the application's interface, thereby improving application development efficiency.

[0030] Overview of Interface Inspection

[0031] To at least partially address the shortcomings of the prior art, a method for inspecting the interface of an application is proposed according to one implementation of this disclosure. Referring to FIG2, which describes an overview of one implementation of this disclosure, FIG2 shows a block diagram 200 for inspecting the interface of an application according to some implementations of this disclosure. As shown in FIG2, a method for inspecting the interface of an application is provided. An interface description 210 of the application's interface can be obtained, whereby the interface description 210 can define at least one visual element that will be presented in the application's interface.

[0032] According to some implementations of this disclosure, the interface description can be defined in various formats. For example, one or more attributes of each visual element can be defined in text format, including but not limited to identifiers, names, positions, sizes, shapes, etc. Another example is that each visual element can be defined as a multi-layered image, with each image located in a separate image layer. One or more attributes of the visual element can be stored as text records, and a relationship can be established between the image layers and the text records. Yet another example is that the interface description can be stored in other formats, such as formats supported by the interface design tool, etc. In this case, the interface description 210 can be directly exported from the interface design tool.

[0033] At least one visual element (e.g., visual element 120, etc.) in the application's interface can be identified based on the interface description 210. Constraints 230 associated with the application's interface can be obtained. Specifically, constraints 230 can be entered by the developer (also referred to as the user). Alternatively and / or additionally, constraints 230 can be imported from a predefined configuration file, and constraints can be manually updated after import, etc. At least one visual element can be checked based on constraints 230, and a check result 240 can be provided. Specifically, in response to determining that a visual element among at least one visual element does not conform to the constraints, an alert 250 can be provided in the check result 240 to indicate that the visual element failed the interface check. Using the implementation of this disclosure, it is possible to automatically check whether individual visual elements in the application's interface conform to constraints. In this way, interface checks can be performed in a more efficient manner, thereby improving application development efficiency.

[0034] Detailed process of interface inspection

[0035] Having described an overview of some implementations according to this disclosure, further details regarding methods for inspecting the interface of an application will be described below. Figure 3 shows a block diagram 300 of an interface of an inspection tool according to some implementations of this disclosure. As shown in Figure 3, an inspection tool 310 may be provided, which can read relevant information about various visual elements defined in interface description 210 and then perform an interface inspection process. The inspection tool 310 may include multiple tabs; for example, tab 312 may correspond to a home page interface, and the user can click control 316 to specify the interface to be inspected. In response to detecting a user access request for control 316, a dialog box for specifying the access address of interface description 210 may be presented. The user can specify the address of interface description 210 in this dialog box, at which point the inspection tool 310 will read relevant information about various visual elements in interface description 210.

[0036] According to some implementations of this disclosure, the interface description 210 can be stored in various formats. For example, the interface description can store at least one visual element in a tree structure. In this case, relevant information about the visual element can be stored in the nodes of the tree structure, and the visual element among the at least one visual element can be determined based on the root node of the tree structure and the relationships between multiple nodes in the tree structure. Specifically, the visual element can have its own hierarchy, and the nodes can be traversed starting from the root node of the tree structure, for example, in a depth-first manner, to obtain information associated with each visual element. Using some implementations of this disclosure, the various visual elements in the application's interface can be traversed in a more efficient way.

[0037] It should be understood that multiple alternatives may be provided during the user interface setup process. For example, different text can be set for buttons in the interface among different alternative technologies to select the alternative technology that is more helpful for end-user operation of the application. In this case, a button in one alternative technology can be set to "visible," and buttons in other alternative technologies can be set to "invisible." In determining at least one visual element in the application's interface, multiple visual elements in the interface can be obtained based on the interface description, including visible and / or invisible visual elements. Then, at least one visual element can be selected from the multiple visual elements based on their display attributes (e.g., visible or invisible). Using some implementations of this disclosure, numerous invisible elements in the interface can be ignored, reducing the workload of the inspection process.

[0038] According to some implementations of this disclosure, in the process of obtaining constraints associated with the application's interface, a specified control for specifying constraints can be provided; and in response to receiving an access request for the specified control, the constraint is determined based on the access request. Using some implementations of this disclosure, auxiliary tools for setting constraints can be provided, thereby facilitating users to set corresponding constraints according to their own needs. Referring to Figure 3 for further details, the inspection tool 310 can provide a tab 314, which users can click to switch to the interface for specifying constraints. In response to detecting an access request for tab 314, the interface shown in Figure 4 can be presented, which shows a block diagram 400 of another interface of the inspection tool according to some implementations of this disclosure.

[0039] According to some implementations of this disclosure, constraints may include at least one of the following: the appearance, text, color, position of at least one visual element, and the positional relationship between the visual element and another visual element. Here, appearance may include, for example, the shape of the visual element, the width of its border, the corner radius, patterns, shadows, etc. Text may include, for example, the font, size, italics, bold, underline, etc., of the text presented in the visual element. Position may include, for example, the coordinates of the visual element in the application's interface, the distance between it and the four borders of the interface, etc. Positional relationship may include, for example, the horizontal and vertical distances between the visual element and other visual elements, etc. Using some implementations of this disclosure, constraints that each visual element should follow can be specified from multiple perspectives, thereby supporting application development in a more accurate manner.

[0040] According to some implementations of this disclosure, during the process of determining constraints based on access requests, a setting control for setting parameters of the constraints can be provided; and in response to receiving an access request for the setting control, the constraints can be set based on the access request. As shown in Figure 4, an add control 410 can be presented in the constraint setting interface. The user can click the add control 410 to import predefined constraints into the inspection tool. Alternatively and / or additionally, a constraint file can be selected and dragged into area 420 to add constraints to the inspection tool 310.

[0041] According to some implementations of this disclosure, different types of constraints can be added one by one. For example, a user can click control 430 to add and / or edit constraints for checking the appearance of a visual element (e.g., the radius of its outline). It should be understood that the radius here is merely an example of appearance; alternatively and / or additionally, other constraints related to the line width, pattern, shadow, etc., of the visual element's outline can be added. As another example, a user can click control 432 to add and / or edit constraints for checking text within a visual element. This constraint can specify information such as the text's font, size, underline, italic, bold, etc. As yet another example, a user can click control 434 to add and / or edit constraints for checking the color of a visual element. This constraint can specify information such as the visual element's color, saturation, contrast, etc.

[0042] It should be understood that although the above only illustratively shows an example of constraints applying to all visual elements in the interface, alternatively and / or additionally, constraints can be set for some visual elements in the interface. For example, the type of visual element can be determined first, and constraints can be set based on that type. Suppose the interface includes button-type visual elements and menu-type visual elements, constraints can be set for each type of visual element separately. Taking font size as an example, the constraint for button-type visual elements can be specified that the font size of the text presented in the button is 18 points; and the constraint for menu-type visual elements can be specified that the font size of the text presented in the menu is 16 points, and so on.

[0043] Returning to Figure 3, after specifying constraints in tab 314, the user can click control 320 to execute the inspection process. According to some implementations of this disclosure, in the process of inspecting at least one visual element based on constraints, the visual element within the at least one visual element can be determined based on the root node of the tree structure and the relationships between multiple nodes in the tree structure; and at least one attribute of the visual element can be inspected based on constraints. Specifically, each visual element in the tree structure can be traversed, and it can be determined whether each visual element conforms to the specified constraints. Taking font size as an example, the font size in the constraints can be compared one by one with the font size of the text in each visual element to identify visual elements that violate the constraints. Assuming the constraint specifies a font size of 18, and a visual element is found to have a font size of 20, an alert can be provided. When multiple constraints exist, subsequent constraints can be handled in a similar manner.

[0044] Assuming a color constraint specifies the text color as black, the black color in the constraint can be compared one by one with the text color of each visual element to identify those violating the constraint. If a visual element is found to have blue text, an alert can be provided. Using some implementation methods disclosed herein, for each visual element in the interface, it can be determined whether each visual element conforms to one or more specified constraints. In this way, all visual elements in the application can be automatically checked, thereby improving interface inspection efficiency and thus application development efficiency.

[0045] According to some implementations of this disclosure, alert information can be provided in various ways when a visual element that does not conform to the constraints is found. For example, the alert information can be provided within the inspection tool, or alternatively and / or additionally, it can be presented at a location in the application's interface associated with the visual element. See Figure 5 for further details, which shows a block diagram of the interface 500 of an inspection tool according to some implementations of this disclosure. As shown in Figure 5, the interface 500 of the inspection tool may include two parts: the left side shows the interface 110 of the application being inspected, and the right side shows the inspection interface 310.

[0046] According to some implementations of this disclosure, the alarm information may include at least one of the following: the reason why a visual element failed the interface check; or the position of the visual element in the application's interface. Specifically, assuming that the font size of visual element 120 in interface 110 does not conform to the constraints, alarm information 512 can be presented in the check interface 310 to indicate that the font size does not conform to the constraints. Alternatively and / or additionally, alarm information 510 can be presented at the location associated with visual element 120 in interface 110 to indicate that the font size of visual element 120 does not conform to the specified size 18 in the constraints. Alternatively and / or additionally, the erroneous visual element 120 can be presented with different visual attributes; for example, it can be indicated by yellow or other conspicuous colors to indicate that the visual element does not conform to the constraints. Using some implementations of this disclosure, detailed information about whether each visual element conforms to the constraints can be provided to the user, thereby facilitating the user to update the various visual elements in the interface.

[0047] Furthermore, the inspection results in the inspection interface 310 can include more information. For example, the number of visual elements that have been inspected can be displayed, and control 514 can be pressed to display details related to each visual element. Alternatively and / or additionally, adjustment controls for adjusting visual elements can be provided. In response to receiving an access request for alarm information, adjustment controls for adjusting visual elements are provided; and in response to receiving an access request for adjustment controls, the visual elements are updated based on the access request. For example, a user can press control 516 to adjust one or more attributes of a visual element, such as font, font size, etc. Alternatively and / or additionally, a user can interact with alarm information 510 and / or visual element 120 to update the visual elements. Using some implementations of this disclosure, users can directly adjust visual elements in the inspection tool, and users do not need to switch back and forth between the interface definition tool and the interface inspection tool. In this way, the complexity of application development can be reduced and the efficiency of application development can be improved.

[0048] According to some implementations of this disclosure, the attributes of visual elements that violate constraints can be automatically corrected. For example, the user can be prompted in interface 110 (or inspection interface 310) whether automatic correction is needed. In response to receiving user confirmation that automatic correction is needed, the corrected visual element can be provided; for example, the font size of the visual element can be set to 18. Alternatively and / or additionally, the user can be prompted whether the corrected interface needs to be saved. In response to receiving user confirmation that saving is needed, an interface description representing the corrected interface can be stored. In this way, the application's interface can be updated directly in the inspection tool.

[0049] According to some implementations of this disclosure, in response to determining that at least one visual element conforms to constraints, confirmation information is provided to indicate that at least one visual element passes the interface check. As shown in the check interface 310, confirmation information 520 can be provided, indicating that the radius, color, and screen size of each visual element in the application conform to the constraints. Using some implementations of this disclosure, the check results can provide richer information about each visual element in the interface. In this way, users can be supported in developing applications in a more efficient manner.

[0050] According to some implementations of this disclosure, the inspection interface 310 can provide more controls: control 530 can re-execute the inspection process, and control 534 can clear each alarm marker in the inspection results. Alternatively and / or additionally, according to some implementations of this disclosure, the inspection interface 310 can further provide a storage control for storing the inspection results of the interface inspection; and in response to receiving an access request for the storage control, store the inspection results at the target location specified by the access request. Specifically, the user can press control 532 to store the inspection results at the specified target location. The inspection results can be stored in various formats; for example, the relevant inspection results of all visual elements in the interface can be recorded in text format. Alternatively, only the inspection results of visual elements that violate constraints can be recorded, etc. Alternatively and / or additionally, the inspection results can be recorded in both text and image formats; specifically, image information of the original visual elements and / or corrected visual elements can be recorded, etc. Using some implementations of this disclosure, it is convenient for users to review the update history of the application's interface, thereby recording the application's development process.

[0051] The various steps of some implementations of this disclosure have been described. Hereinafter, the complete flow of the interface inspection process is described with reference to FIG6. FIG6 shows a block diagram 600 of the process of performing interface inspection using an interface inspection tool according to some implementations of this disclosure. As shown in FIG6, at box 610, the inspection tool can be started. At box 611, an interface description of the interface to be inspected can be entered. At box 612, if an alarm occurred during the last inspection, the alarm marker can be cleared. At box 613, one or more visible visual elements can be filtered from the interface description. At box 614, the filtered one or more visual elements can be inspected.

[0052] Specifically, the steps at box 614 can be refined. At box 620, the operation begins. At box 621, if the visual element passes the check, the process can proceed to box 625 and end. If the visual element fails the check, the process proceeds to box 622 to automatically correct the error in that visual element. If the correction is successful, the process proceeds to box 624 to provide a correction success message. If the correction fails, the process proceeds to box 623 to provide an alert message indicating the correction failure. Each visual element in the interface can be processed one by one in a similar manner, and the check results can be presented at box 615.

[0053] It should be understood that although the above description uses only a single interface as an example to illustrate the inspection of one interface of an application, alternatively and / or additionally, an application may include multiple interfaces. Each interface can be processed using the methods described above to determine whether each interface in the application conforms to predetermined constraints. Using the implementation of this disclosure, the conformity of each visual element in the application's interface to constraints can be automatically checked. In this way, interface inspection can be performed more efficiently, thereby improving application development efficiency.

[0054] Example process

[0055] Figure 7 illustrates a flowchart of a method 700 for inspecting an application's interface according to some implementations of this disclosure. At block 710, at least one visual element in the application's interface is determined based on the interface description of the application's interface. At block 720, constraints associated with the application's interface are obtained. At block 730, at least one visual element is inspected based on the constraints. At block 740, in response to determining that a visual element among at least one visual element does not conform to the constraints, an alarm message is provided to indicate that the visual element has failed the interface inspection.

[0056] According to some implementations of this disclosure, obtaining constraints associated with the application's interface includes: providing a specified control for specifying the constraints; and determining the constraints based on the access request in response to receiving an access request for the specified control.

[0057] According to some implementations of this disclosure, determining constraints based on access requests includes: providing a setting control for setting parameters of the constraints; and setting constraints based on access requests received for the setting control.

[0058] According to some implementations of this disclosure, the interface description stores at least one visual element in a tree structure, and checking at least one visual element based on constraints includes: determining the visual element in at least one visual element based on the root node of the tree structure and the association relationship between multiple nodes in the tree structure; and checking at least one attribute of the visual element based on constraints.

[0059] According to some implementations of this disclosure, providing alert information includes presenting the alert information at a location associated with a visual element in the application's interface.

[0060] According to some implementations of this disclosure, the alert information includes at least one of the following: the reason why the visual element failed the interface check; or the location of the visual element in the application's interface.

[0061] According to some implementations of this disclosure, the method further includes: in response to receiving an access request for alarm information, providing an adjustment control for adjusting visual elements; and in response to receiving an access request for the adjustment control, updating the visual elements based on the access request.

[0062] According to some implementations of this disclosure, the constraints associated with the application's interface include at least one of the following: the appearance, text, color, position of at least one visual element, and the positional relationship between the visual element and another visual element among at least one visual element.

[0063] According to some implementations of this disclosure, determining at least one visual element in the application's interface includes: obtaining multiple visual elements in the interface based on the interface description; and selecting at least one visual element from the multiple visual elements based on the display attributes of the multiple visual elements.

[0064] According to some implementations of this disclosure, the method further includes: in response to determining that at least one visual element conforms to the constraints, providing confirmation information to indicate that at least one visual element passes the interface check.

[0065] According to some implementations of this disclosure, the method further includes: providing a storage control for storing the inspection results of the interface inspection; and in response to receiving an access request for the storage control, storing the inspection results at a target location specified by the access request.

[0066] Example devices and equipment

[0067] Figure 8 shows a block diagram of an apparatus 800 for inspecting an application's interface according to some implementations of the present disclosure. The apparatus includes: a determining module 810 configured to determine at least one visual element in the application's interface based on an interface description of the application's interface; an acquiring module 820 configured to acquire constraints associated with the application's interface; an inspecting module 830 configured to inspect the at least one visual element based on the constraints; and a providing module 840 configured to provide an alarm message indicating that the visual element failed the interface inspection in response to determining that the visual element among the at least one visual element does not conform to the constraints.

[0068] According to some implementations of this disclosure, the acquisition module is further configured to include: providing a specified control for specifying constraints; and determining constraints based on the access request in response to receiving an access request for the specified control.

[0069] According to some implementations of this disclosure, the acquisition module is further configured to: provide a setting control for setting parameters of the constraint; and, in response to receiving an access request for the setting control, set the constraint based on the access request.

[0070] According to some implementations of this disclosure, the interface description stores at least one visual element in a tree structure, and the inspection module is further configured to: determine the visual element in the at least one visual element based on the root node of the tree structure and the association relationship between multiple nodes in the tree structure; and inspect at least one attribute of the visual element based on constraints.

[0071] According to some implementations of this disclosure, the module is further configured to: present alarm information at a location associated with a visual element in the application's interface.

[0072] According to some implementations of this disclosure, the alert information includes at least one of the following: the reason why the visual element failed the interface check; or the location of the visual element in the application's interface.

[0073] According to some implementations of this disclosure, the device further includes a processing module configured to: provide adjustment controls for adjusting visual elements in response to receiving an access request for alarm information; and update the visual elements based on the access request in response to receiving an access request for the adjustment controls.

[0074] According to some implementations of this disclosure, the constraints associated with the application's interface include at least one of the following: the appearance, text, color, position of at least one visual element, and the positional relationship between the visual element and another visual element among at least one visual element.

[0075] According to some implementations of this disclosure, the determining module is further configured to: obtain multiple visual elements in the interface based on the interface description; and select at least one visual element from the multiple visual elements based on the display attributes of the multiple visual elements.

[0076] According to some implementations of this disclosure, the providing module is further configured to: in response to determining that at least one visual element conforms to the constraints, provide confirmation information to indicate that at least one visual element passes the interface check.

[0077] According to some implementations of this disclosure, a module is provided, configured to: provide a storage control for storing the inspection results of the interface inspection; and, in response to receiving an access request for the storage control, store the inspection results at a target location specified by the access request.

[0078] Figure 9 shows a block diagram of a device 900 capable of implementing various implementations of the present disclosure. It should be understood that the computing device 900 shown in Figure 9 is merely exemplary and should not constitute any limitation on the functionality and scope of the implementations described herein. The computing device 900 shown in Figure 9 can be used to implement the methods described above.

[0079] As shown in Figure 9, the computing device 900 is in the form of a general-purpose computing device. Components of the computing device 900 may include, but are not limited to, one or more processors or processing units 910, memory 920, storage devices 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. The processing unit 910 may be a physical or virtual processor and is capable of performing various processes according to programs stored in the memory 920. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of the computing device 900.

[0080] Computing device 900 typically includes multiple computer storage media. Such media can be any available media accessible to computing device 900, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 920 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 930 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media capable of storing information and / or data (e.g., training data for training) and accessible within computing device 900.

[0081] The computing device 900 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 9, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks may be provided. In these cases, each drive may be connected to a bus (not shown) via one or more data media interfaces. The memory 920 may include a computer program product 925 having one or more program modules configured to perform various methods or actions of various implementations of the present disclosure.

[0082] The communication unit 940 enables communication with other computing devices via a communication medium. Additionally, the components of the computing device 900 can function as a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the computing device 900 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0083] Input device 950 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 960 can be one or more output devices, such as a monitor, speaker, printer, etc. Computing device 900 can also communicate as needed with one or more external devices (not shown) via communication unit 940. These external devices, such as storage devices, display devices, etc., can communicate with one or more devices that enable user interaction with computing device 900, or with any device (e.g., network card, modem, etc.) that enables computing device 900 to communicate with one or more other computing devices. Such communication can be performed via input / output (I / O) interfaces (not shown).

[0084] According to an implementation of this disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, which are executed by a processor to implement the method described above. According to an implementation of this disclosure, a computer program product is provided, on which a computer program is stored, which, when executed by a processor, implements the method described above.

[0085] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0086] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0087] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0088] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0089] Various implementations of this disclosure have been described above. The foregoing description is exemplary and not exhaustive, nor is it limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the various implementations disclosed herein.

Claims

1. A method for inspecting the interface of an application, comprising: Based on the interface description of the application's interface, at least one visual element in the application's interface is determined. Obtain the constraints associated with the interface of the application; The at least one visual element is examined based on the constraints; as well as In response to determining that a visual element among the at least one visual element does not conform to the constraint, an alarm message is provided to indicate that the visual element has failed the interface check.

2. The method of claim 1, wherein obtaining the constraints associated with the interface of the application comprises: Provide a specified control for specifying the constraints; as well as In response to receiving an access request for the specified control, the constraint is determined based on the access request.

3. The method of claim 2, wherein determining the constraint based on the access request comprises: Provides setting controls for setting parameters of the constraints; as well as In response to receiving an access request for the settings control, the constraint is set based on the access request.

4. The method of claim 1, wherein the interface description stores the at least one visual element in a tree structure, and checking the at least one visual element based on the constraints comprises: Based on the root node of the tree structure and the relationships between multiple nodes in the tree structure, the visual element in the at least one visual element is determined; as well as At least one attribute of the visual element is examined based on the constraints.

5. The method of claim 1, wherein providing the alarm information comprises: The alarm information is displayed at the location associated with the visual element in the interface of the application.

6. The method of claim 1, wherein the alarm information includes at least one of the following: The reason why the visual element failed the interface check; or The location of the visual element within the interface of the application.

7. The method of claim 1, further comprising: In response to receiving an access request for the alarm information, adjustment controls for adjusting the visual elements are provided; as well as In response to receiving an access request for the adjustment control, the visual element is updated based on the access request.

8. The method of claim 1, wherein the constraints associated with the interface of the application include at least one of the following: the appearance, text, color, position of the visual element among the at least one visual element, and the positional relationship between the visual element and another visual element among the at least one visual element.

9. The method of claim 1, wherein determining the at least one visual element in the interface of the application comprises: Based on the interface description, obtain multiple visual elements of the interface; as well as Based on the display attributes of the plurality of visual elements, at least one visual element is selected from the plurality of visual elements.

10. The method of claim 1, further comprising: In response to determining that the at least one visual element conforms to the constraint, confirmation information is provided to instruct the at least one visual element to pass the interface check.

11. The method of claim 1, further comprising: Provide a storage control for storing the inspection results of the interface inspection; as well as In response to receiving an access request for the storage control, the inspection result is stored at the target location specified by the access request.

12. An apparatus for inspecting the interface of an application, comprising: A determination module is configured to determine at least one visual element in the interface of the application based on an interface description of the interface of the application. The acquisition module is configured to acquire constraints associated with the interface of the application; The inspection module is configured to inspect the at least one visual element based on the constraints. as well as A module is configured to provide an alarm message in response to determining that a visual element among the at least one visual element does not conform to the constraint, indicating that the visual element has failed the interface check.

13. An electronic device, comprising: At least one processing unit; as well as At least one memory, coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, which, when executed by the at least one processing unit, cause the electronic device to perform the method according to any one of claims 1 to 11.

14. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 11.

15. A computer instruction product comprising computer instructions, wherein the computer instructions, when executed by a processor, implement the method according to any one of claims 1 to 11.

Images