CN113254343A - User interface test assertion method and device, electronic equipment and storage medium - Google Patents

User interface test assertion method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN113254343A
CN113254343A CN202110629898.9A CN202110629898A CN113254343A CN 113254343 A CN113254343 A CN 113254343A CN 202110629898 A CN202110629898 A CN 202110629898A CN 113254343 A CN113254343 A CN 113254343A
Authority
CN
China
Prior art keywords
test
user interface
screenshot
interface
sub
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202110629898.9A
Other languages
Chinese (zh)
Inventor
王璐
李洪浩
陈盼
王超
段奇
何渝君
邬明罡
舒忠玲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hanyun Technology Co Ltd
Original Assignee
Hanyun Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hanyun Technology Co Ltd filed Critical Hanyun Technology Co Ltd
Priority to CN202110629898.9A priority Critical patent/CN113254343A/en
Publication of CN113254343A publication Critical patent/CN113254343A/en
Pending legal-status Critical Current

Links

Images

Classifications

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

Landscapes

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

Abstract

The application discloses a user interface test assertion method, a device, electronic equipment and a storage medium, which relate to the technical field of software testing, and the method comprises the following steps: intercepting a target interface screenshot containing a test object from a user interface by utilizing a pre-configured test case aiming at the test object; searching whether an interface screenshot matched with the target interface screenshot exists from a preset image library based on a preset image identifier of the test object indicated by the test case; and outputting the test result of the test case based on the search result. By adopting the user interface test assertion method, the user interface test assertion device, the electronic equipment and the storage medium, the problems that the test script is complicated to compile and the test script is high in maintenance cost in the prior art are solved.

Description

User interface test assertion method and device, electronic equipment and storage medium
Technical Field
The present application relates to the field of software testing technologies, and in particular, to a method and an apparatus for asserting a user interface test, an electronic device, and a storage medium.
Background
The User Interface (UI) test is to test whether the layout of each functional module in the User Interface is reasonable, whether the overall style is consistent, whether the placement positions of each control conform to the use habits of the User, and the like, so as to ensure that the User Interface provides corresponding access and browsing functions for the User through the function of the test object, and ensure that the User Interface conforms to the standards of companies or industries. UI testing is therefore important for a variety of human-computer interaction scenarios. Meanwhile, because the cost and the time spent on manually testing the user interface are both large, the UI automation test plays an important role in the user interface test. The current UI automation test method needs to traverse each element in the user interface, position each element, and then compile a test script according to the service flow logic and element positioning information.
In the existing user interface test assertion method, the compiling process of the test script is complex, and meanwhile, after the version is iterated or the interface is updated, the test script needs to be updated and debugged, which also increases the maintenance cost of the test script.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for asserting a user interface test, an electronic device, and a storage medium, and aims to solve the problems of complicated test script compiling and high test script maintenance cost in the prior art by using an image matching instead of element positioning.
In a first aspect, an embodiment of the present application provides a method for testing assertion on a user interface, including:
intercepting a target interface screenshot containing a test object from a user interface by utilizing a pre-configured test case aiming at the test object;
searching whether an interface screenshot matched with the target interface screenshot exists from a preset image library based on a preset image identifier of the test object indicated by the test case;
and outputting the test result of the test case based on the search result.
Optionally, the test object may include at least one checkpoint in the user interface, the test case may include a plurality of test sub-cases, each test sub-case corresponding to the at least one checkpoint in the user interface, and the target interface screenshot may include a plurality of sub-images; wherein a sub-image containing any one of each checkpoint is intercepted by: and intercepting the sub-image containing any checkpoint from the user interface by utilizing a pre-configured test sub-case aiming at any checkpoint.
Optionally, interface screenshots corresponding to at least one check point in the user interface are stored in the preset image library, and an image identifier for indicating the check point is inserted into each interface screenshot; the method comprises the following steps of constructing a preset image library in the following mode: based on the position of each check point in the user interface, performing a partition screenshot on the user interface to obtain an interface screenshot corresponding to each check point; and numbering each acquired interface screenshot, and inserting the number of each interface screenshot into the corresponding interface screenshot as an image identifier.
Optionally, the step of searching whether an interface screenshot matching the target interface screenshot exists from a preset image library based on the preset image identifier of the test object indicated by the test case may include: searching whether an image identifier consistent with the preset image identifier exists in a preset image library; and if the image identifier consistent with the preset image identifier exists, matching the interface screenshot corresponding to the searched image identifier with the target interface screenshot.
Optionally, based on the search result, the step of outputting the test result of the test case may include: if the interface screenshot matched with the target interface screenshot exists in the preset image library, determining that the test case passes the test aiming at the test object; and if the interface screenshot matched with the target interface screenshot is not found from the preset image library, outputting notification information indicating that the test is not passed, wherein the notification information comprises a preset image identifier.
Optionally, when the test case includes a plurality of test sub-cases, the user interface test assertion method is sequentially executed for each test sub-case.
In a second aspect, an embodiment of the present application provides an assertion device for a user interface test, including:
the intercepting module is used for intercepting a target interface screenshot containing a test object from a user interface by utilizing a pre-configured test case aiming at the test object;
the matching module is used for searching whether an interface screenshot matched with the target interface screenshot exists in a preset image library based on a preset image identifier of the test object indicated by the test case;
and the output module is used for outputting the test result of the test case based on the search result.
Optionally, the test object includes at least one checkpoint in the user interface, the test case includes a plurality of test sub-cases, each test sub-case corresponds to at least one checkpoint in the user interface, and the target interface screenshot includes a plurality of sub-images; wherein the intercepting module is further operable to intercept the sub-image containing any of each checkpoint by: and intercepting the sub-image containing any checkpoint from the user interface by utilizing a pre-configured test sub-case aiming at any checkpoint.
In a third aspect, an embodiment of the present application provides an electronic device, including: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is operating, the machine-readable instructions when executed by the processor performing the steps of the user interface test assertion method as described above.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to perform the steps of the user interface test assertion method.
The embodiment of the application brings the following beneficial effects:
the embodiment of the application provides a user interface test assertion method, which comprises the following steps: intercepting a target interface screenshot containing a test object from a user interface by utilizing a pre-configured test case aiming at the test object; searching whether an interface screenshot matched with the target interface screenshot exists from a preset image library based on a preset image identifier of the test object indicated by the test case; and outputting the test result of the test case based on the search result. According to the method and the device, the problems that the compiling of the test script is complex and the maintenance cost of the test script is high in the prior art are solved by replacing an element positioning mode with image matching.
In order to make the aforementioned objects, features and advantages of the present application more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments are briefly described below, and it is obvious that the following drawings are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other related drawings without creative efforts.
Fig. 1 is a schematic flowchart of a user interface test assertion method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a user interface test assertion device provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the accompanying drawings, and it is obvious that the described embodiments are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the prior art, when testing is performed on colors and positions of elements such as a chart and a button in a user interface, the test script is compiled in an element positioning mode, so that the compiling process of the test script is complex, the number of predicates is large, and the problem of low success rate of test case execution is caused. Meanwhile, after the version of the user interface is iterated or updated each time, the test script needs to be updated and debugged due to the change of interface information such as the position, size, color and the like of the interface elements, which also causes the problem of high maintenance cost of the test script.
Based on this, the embodiment of the application provides a user interface test assertion method, a device, an electronic device and a storage medium, and a user interface test is completed by directly matching a target image screenshot with an interface screenshot in a preset image library, that is, a mode of replacing element positioning by image matching is used, so that the problem of complicated test script writing is solved. In addition, after the version of the user interface is updated or iterated every time, only the interface screenshot stored in the preset image library can be updated, the test script does not need to be debugged again, and the use case step and the assertion part in the test script do not need to be maintained at the same time, so that the problem of high maintenance cost of the test script is solved, and the test efficiency of the user interface is improved.
To facilitate understanding of the present embodiment, first, a user interface test assertion method disclosed in the embodiment of the present application is described in detail, and fig. 1 is a schematic flow chart of the user interface test assertion method provided in the embodiment of the present application, as shown in fig. 1, the method includes the following steps:
step 101, a pre-configured test case for a test object is utilized to intercept a target interface screenshot containing the test object from a user interface.
Specifically, before testing the user interface, a test case needs to be written according to the design specification and requirements of the user interface, and the test of the user interface is realized by executing the test case. Here, the user interface includes a plurality of test objects, each test object includes at least one checkpoint in the user interface, the test case includes a plurality of test sub-cases, each test sub-case corresponds to at least one checkpoint in the user interface, and each test sub-case is a test script written for the at least one checkpoint, the test sub-case includes a specific operation method for completing a test flow corresponding to the entire test sub-case, profits are obtained, and operations for the user interface such as interface clicking, interface closing, button clicking and the like can be automatically completed to complete the entire test flow, thereby realizing testing of the test objects in the user interface.
For example, a test sub-case may or may not contain an assertion; types of checkpoints include, but are not limited to: font, color, size, type of test object, location.
In an example, when testing a user interface, a sub-image containing any of each checkpoint is intercepted by: and intercepting the sub-image containing any checkpoint from the user interface by utilizing a pre-configured test sub-case aiming at any checkpoint. Here, a target interface screenshot containing the test object may be intercepted from the user interface upon assertion, and the obtained target interface screenshot includes a plurality of sub-images.
And 102, searching whether an interface screenshot matched with the target interface screenshot exists in a preset image library based on a preset image identifier of the test object indicated by the test case.
Specifically, before a pre-configured test case for a test object is used to capture a target interface screenshot containing the test object from a user interface, a preset image library needs to be constructed. Here, the preset image library may be constructed in the following manner: based on the position of each check point in the user interface, performing a partition screenshot on the user interface to obtain an interface screenshot corresponding to each check point; and numbering each acquired interface screenshot, inserting the number of each interface screenshot into the corresponding interface screenshot as an image identifier, and storing all the intercepted interface screenshots in a preset image library.
For example: assuming that the check point is the size of the confirmation button located at the lower right corner of the user interface, the user interface including the button can be captured according to the position of the button, so as to obtain the interface screenshot corresponding to the check point. For example, all interface screenshots may be stored in the same folder, that is, one test object corresponds to one folder, and based on this, when the test case is executed, the storage path of the interface screenshots may be inserted as an image identifier into the interface screenshots, and only from storage.
It can be understood that the preset image library stores interface screenshots corresponding to at least one check point in the user interface, each interface screenshot is inserted with an image identifier for indicating the check point, and the image identifier is used to identify the interface screenshot, and may be a number, a symbol, a character, or a combination of any of the above identifiers, which is not specifically limited in this application.
In the exemplary embodiment of the present application, one interface screenshot stored in the preset image library may correspond to one checkpoint, where an image identifier used to indicate the checkpoint is inserted in the interface screenshot, or one interface screenshot may also correspond to multiple checkpoints, where an image identifier used to indicate multiple checkpoints is inserted in the interface screenshot.
In the exemplary embodiment of the present application, one test sub-case may correspond to one check point, at this time, only the check point is included in a target interface screenshot captured from a user interface, and whether an interface screenshot corresponding to the check point exists is searched from a preset image library based on an image identifier.
However, the present application is not limited to this, and one test sub-case may also correspond to multiple checkpoints, where at this time, the target interface screenshot captured from the user interface includes multiple checkpoints. For the case that one interface screenshot in the preset image library corresponds to one check point, whether interface screenshots corresponding to the check points respectively exist or not may be searched from the preset image library based on the image identifier, and for the case that one interface screenshot in the preset image library corresponds to a plurality of check points, whether interface screenshots (one or more may be possible) corresponding to the check points exist or not may be searched from the preset image library based on the image identifier.
In one example, when the test case is executed to test the test object, the step of searching whether an interface screenshot matching the target interface screenshot exists from a preset image library based on a preset image identifier indicated in the test case includes: searching whether an image identifier consistent with the preset image identifier exists in a preset image library; and if the image identifier consistent with the preset image identifier exists, matching the interface screenshot corresponding to the searched image identifier with the target interface screenshot. When the interface screenshot matched with the target interface screenshot is searched, image identifiers of all the interface screenshots in the preset image library are traversed, and if the image identifiers consistent with the preset image identifiers in the test case are searched, the interface screenshot corresponding to the searched image identifiers is matched with the target interface screenshot.
For example, 100 interface screenshots are stored in the preset image library, the image identifiers are sequentially 1 to 100, and if the preset image identifier in the test case is 10, whether the interface screenshot with the image identifier of 10 exists in the preset image library is searched, the interface screenshot with the image identifier of 10 is matched with the target interface screenshot, and the test result of the test case is determined according to the matching result of the screenshots.
And 103, outputting the test result of the test case based on the search result.
Specifically, if an interface screenshot matched with the target interface screenshot exists in the preset image library, the test case is determined to pass the test of the test object; if the interface screenshot matched with the target interface screenshot is not found from the preset image library, outputting notification information indicating that the test fails, wherein the notification information comprises a preset image identifier, namely the notification information comprises an image identifier of a test object which fails the test.
Here, when the test case includes a plurality of test sub-cases, the above-described user interface test assertion method is sequentially executed for each test sub-case. It should be noted that, when the user interface test assertion method is executed in sequence for each test sub-case, the whole test flow may be stopped and notification information corresponding to the test may be output at the same time when each test fails, or after all test flows are completed, the notification information for each test failure may be output together, that is, only one notification message may be output at this time, and the notification message includes image identifiers of all checkpoints that do not pass the test.
In an example, finding an interface screenshot matching a target interface screenshot from a preset image library requires not only searching an image identifier consistent with a preset image identifier from the preset image library, but also requiring the interface screenshot corresponding to the image identifier to match the target interface screenshot. Here, the degree of matching between the interface screenshot and the target interface screenshot may be calculated through a deep learning model, and when the degree of matching is greater than a set threshold, it may be determined that the interface screenshot and the target interface screenshot are matched, and when the degree of matching is not greater than (less than or equal to) the set threshold, it may be determined that the interface screenshot and the target interface screenshot are unmatched.
Taking the above example as an example, if when each test sub-case is executed, the image identifier consistent with the preset image identifier can be searched from the preset image library, and the matching degree between the target interface screenshot corresponding to each test sub-case and the interface screenshot is greater than the set threshold, it is determined that the test of the test case for the test object passes. If any test sub-case cannot search the image identifier consistent with the preset image identifier from the preset image library and/or the matching degree of the target interface screenshot corresponding to any test sub-case and the interface screenshot is not greater than the set threshold value, determining that the test of the test case for the test object fails, and outputting notification information at the moment, wherein the notification information comprises all the preset image identifiers which cannot be searched and matched with the preset image identifiers and the image identifiers corresponding to the target interface screenshot of which the matching degree of the interface screenshot is not greater than the set threshold value.
In an example, assuming that the test case includes 5 test sub-cases, which are respectively the test sub-case 1, the test sub-case 2, the test sub-case 3, the test sub-case 4, and the test sub-case 5, the user interface test assertion method in the above steps 101 to 103 may be sequentially executed according to the sequence of the test sub-cases. Here, if all the test sub-cases pass, it may be determined that the test of the test sub-case with respect to the test object passes, and if any one of the test sub-cases fails, it may be determined that the test of the checkpoint corresponding to any one of the test sub-cases fails.
Based on the same inventive concept, the embodiment of the present application further provides a user interface test assertion device corresponding to the user interface test assertion method, and since the principle of solving the problem of the device in the embodiment of the present application is similar to that of the user interface test assertion method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and repeated details are not repeated.
Fig. 2 is a schematic structural diagram of a user interface test assertion device provided in an embodiment of the present application, and as shown in fig. 2, the device includes the following modules:
an intercepting module 201, configured to intercept, from a user interface, a target interface screenshot including a test object by using a pre-configured test case for the test object;
the matching module 202 is configured to search whether an interface screenshot matched with the target interface screenshot exists from a preset image library based on a preset image identifier of the test object indicated by the test case;
and the output module 203 is configured to output the test result of the test case based on the search result.
Corresponding to the method for asserting in the user interface test in fig. 1, the embodiment of the present application further provides a schematic structural diagram of an electronic device 300, as shown in fig. 3, where the electronic device 300 includes a processor 310, a memory 320, and a bus 330. The memory 320 stores machine-readable instructions executable by the processor 310, when the electronic device 300 runs, the processor 310 communicates with the memory 320 through the bus 330, and when the machine-readable instructions are executed by the processor 310, the user interface test assertion method can be executed.
Corresponding to the user interface test assertion method in fig. 1, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program performs the steps of the user interface test assertion method.
Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk and the like, when a computer program on the storage medium is run, the user interface test assertion method can be executed, and the user interface test is completed by directly matching the target image screenshot with the preset image, so that the test script does not need to be debugged again after each version update or iteration, the problems of complex test script writing and high test script maintenance cost are solved, and the test efficiency of the user interface is improved.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the foregoing systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, a division of a unit is merely a division of one logic function, and there may be other divisions when actually implemented, and for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some communication interfaces, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments provided in the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing an electronic device (which may be a personal computer, a server, or a network device) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus once an item is defined in one figure, it need not be further defined and explained in subsequent figures, and moreover, the terms "first", "second", "third", etc. are used merely to distinguish one description from another and are not to be construed as indicating or implying relative importance.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the exemplary embodiments of the present application, and are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A user interface test assertion method, characterized in that the user interface test assertion method comprises:
intercepting a target interface screenshot containing a test object from a user interface by utilizing a pre-configured test case aiming at the test object;
searching whether an interface screenshot matched with the target interface screenshot exists from a preset image library based on a preset image identifier of the test object indicated by the test case;
and outputting the test result of the test case based on the search result.
2. The user interface test assertion method of claim 1, wherein the test object comprises at least one checkpoint in a user interface, the test case comprises a plurality of test sub-cases, each test sub-case corresponds to the at least one checkpoint in the user interface, the target interface screenshot comprises a plurality of sub-images;
wherein a sub-image containing any one of each checkpoint is intercepted by:
and intercepting a sub-image containing any checkpoint from a user interface by utilizing a pre-configured test sub-case aiming at the checkpoint.
3. The user interface test assertion method of claim 2, wherein the preset image library stores interface screenshots corresponding to at least one checkpoint in the user interface, each interface screenshot having an image identifier inserted therein for indicating the checkpoint;
wherein the preset image library is constructed in the following manner:
based on the position of each check point in the user interface, performing a partition screenshot on the user interface to obtain an interface screenshot corresponding to each check point;
and numbering each acquired interface screenshot, and inserting the number of each interface screenshot into the corresponding interface screenshot as an image identifier.
4. The method of claim 3, wherein the step of searching for an interface screenshot from a preset image library based on the preset image identifier of the test object indicated by the test case, the interface screenshot matching the target interface screenshot comprises:
searching whether an image identifier consistent with the preset image identifier exists in the preset image library;
and if the image identifier consistent with the preset image identifier exists, matching the interface screenshot corresponding to the searched image identifier with the target interface screenshot.
5. The user interface test assertion method of claim 1, wherein the step of outputting the test result of the test case based on the search result comprises:
if the interface screenshot matched with the target interface screenshot exists in the preset image library, determining that the test case passes the test aiming at the test object;
and if the interface screenshot matched with the target interface screenshot is not found from the preset image library, outputting notification information indicating that the test is not passed, wherein the notification information comprises the preset image identifier.
6. The user interface test assertion method of claim 2, wherein when the test case includes a plurality of test sub-cases, the user interface test assertion method is executed in sequence for each test sub-case.
7. A user interface test assertion device, comprising:
the intercepting module is used for intercepting a target interface screenshot containing a test object from a user interface by utilizing a pre-configured test case aiming at the test object;
the matching module is used for searching whether an interface screenshot matched with the target interface screenshot exists from a preset image library based on a preset image identifier of the test object indicated by the test case;
and the output module is used for outputting the test result of the test case based on the search result.
8. The user interface test assertion apparatus of claim 7, wherein the test object comprises at least one checkpoint in a user interface, the test case comprises a plurality of test sub-cases, each test sub-case corresponds to the at least one checkpoint in the user interface, the target interface screenshot comprises a plurality of sub-images; wherein the intercepting module is further configured to intercept a sub-image containing any one of each checkpoint by:
and intercepting a sub-image containing any checkpoint from a user interface by utilizing a pre-configured test sub-case aiming at the checkpoint.
9. An electronic device comprising a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory communicating over the bus when the electronic device is run, the machine-readable instructions when executed by the processor performing the steps of the user interface test assertion method of any of claims 1-6.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the user interface test assertion method as claimed in any one of claims 1-6.
CN202110629898.9A 2021-06-07 2021-06-07 User interface test assertion method and device, electronic equipment and storage medium Pending CN113254343A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110629898.9A CN113254343A (en) 2021-06-07 2021-06-07 User interface test assertion method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110629898.9A CN113254343A (en) 2021-06-07 2021-06-07 User interface test assertion method and device, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN113254343A true CN113254343A (en) 2021-08-13

Family

ID=77186612

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110629898.9A Pending CN113254343A (en) 2021-06-07 2021-06-07 User interface test assertion method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113254343A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115794632A (en) * 2022-11-28 2023-03-14 天翼数字生活科技有限公司 Application testing method and device, electronic equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109857652A (en) * 2019-01-16 2019-06-07 深圳壹账通智能科技有限公司 A kind of automated testing method of user interface, terminal device and medium
CN112506778A (en) * 2020-12-10 2021-03-16 北京云测信息技术有限公司 WEB user interface automatic test method, device, equipment and storage medium
CN112711526A (en) * 2019-10-25 2021-04-27 腾讯科技(深圳)有限公司 UI test method, device, equipment and storage medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109857652A (en) * 2019-01-16 2019-06-07 深圳壹账通智能科技有限公司 A kind of automated testing method of user interface, terminal device and medium
CN112711526A (en) * 2019-10-25 2021-04-27 腾讯科技(深圳)有限公司 UI test method, device, equipment and storage medium
CN112506778A (en) * 2020-12-10 2021-03-16 北京云测信息技术有限公司 WEB user interface automatic test method, device, equipment and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115794632A (en) * 2022-11-28 2023-03-14 天翼数字生活科技有限公司 Application testing method and device, electronic equipment and storage medium

Similar Documents

Publication Publication Date Title
CN111382070B (en) Compatibility testing method and device, storage medium and computer equipment
CN102567565B (en) Cable parameter processing method and system utilizing same
CN105743736B (en) Automated testing method and system
CN109101410B (en) Risk drive testing method and device and computer readable storage medium
CN111813680B (en) Method and device for generating test script, computer equipment and storage medium
CN106844772A (en) The update method and device of application database
JP2017084082A (en) Simulation device, test scenario file creation method, and test method using test scenario file
US20110016454A1 (en) Method and system for testing an order management system
CN111352782A (en) Interface testing method and device, computer equipment and storage medium
CN111857803A (en) Page updating method, device, server and storage medium
CN113254343A (en) User interface test assertion method and device, electronic equipment and storage medium
CN112069052A (en) Abnormal object detection method, device, equipment and storage medium
CN113778878A (en) Interface testing method and device, electronic equipment and storage medium
CN113360379A (en) Program testing method and program testing device
CN113031967A (en) Code conversion method and device
CN111460235A (en) Atlas data processing method, device, equipment and storage medium
CN109358564B (en) Method and device for detecting configuration software and computer readable storage medium
CN114625663A (en) Test method, test device, computer equipment and storage medium
CN114817047A (en) Compiler test method, case generation method and device and instruction storage structure
CN104881455B (en) A kind of architectural difference processing method and system based on MYSQL
CN113986749A (en) Display method and display device of front-end test information and electronic equipment
CN109213490B (en) Program processing method and device and related equipment
CN113568834A (en) SDK code compatibility detection method, device, computer equipment and medium
CN113220596B (en) Application testing method, device, equipment, storage medium and program product
CN112306838A (en) Page layout compatibility testing method, device and equipment and readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination