CN114385514A - Method, equipment and storage medium for detecting webpage elements - Google Patents
Method, equipment and storage medium for detecting webpage elements Download PDFInfo
- Publication number
- CN114385514A CN114385514A CN202210288643.5A CN202210288643A CN114385514A CN 114385514 A CN114385514 A CN 114385514A CN 202210288643 A CN202210288643 A CN 202210288643A CN 114385514 A CN114385514 A CN 114385514A
- Authority
- CN
- China
- Prior art keywords
- clickable
- elements
- dom
- steps
- nodes
- 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
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The application discloses a method, equipment and a storage medium for detecting webpage elements, which relate to the technical field of webpage detection, and the method for detecting the webpage elements comprises the following steps: the method comprises the steps of opening an address of a designated page, obtaining a DOM tree of the designated page, traversing the DOM tree to obtain all DOM nodes, generating a corresponding query link based on a clickable element when the DOM nodes are clickable elements, storing the clickable elements and the query links corresponding to the clickable elements, querying the corresponding clickable elements based on the query links by using a testing tool, and judging whether the clickable elements are effective based on a preset event. The method has the advantages that the method can comprehensively scan and acquire the whole amount of webpage elements to be tested for testing, automatically detect whether clickable elements of the webpage are effective or not, and achieve the purpose of the whole coverage test. Need not to consume the human cost, compare in artifical the detection, this application has promoted detection efficiency and the accuracy that detects by a wide margin.
Description
Technical Field
The present application belongs to the field of web page detection technologies, and more particularly, to a method, an apparatus, and a storage medium for detecting web page elements.
Background
Before a webpage is used by a user, a tester generally opens the webpage, manually clicks a designated element of the webpage, and checks whether a clicking operation is effective, so as to ensure that the user normally interacts with the webpage, and the current technical scheme has the following defects:
firstly, under the conditions of complex service scenes and a large number of page tests, the whole scene is difficult to be covered manually, and omission easily occurs. Secondly, whether the elements are effective or not is detected through manual operation, the cost of consumed labor is high, and the method is more obvious when the project is large or the demand is more frequent.
Disclosure of Invention
The application aims to provide a method, equipment and a storage medium for detecting webpage elements, so as to solve the technical problems that the whole scene is difficult to cover by manpower and the consumed labor cost is high in the prior art.
In order to achieve the technical purpose, the technical scheme adopted by the application is as follows:
a method of detecting web page elements, comprising the steps of:
opening the address of the designated page, acquiring a DOM tree of the designated page, and traversing the DOM tree to obtain all DOM nodes;
when the DOM node is a clickable element, generating a corresponding query link based on the clickable element, and storing the clickable element and the query link corresponding to the clickable element;
and the testing tool queries the corresponding clickable elements based on the query link and judges whether the clickable elements are effective or not based on a preset event.
Preferably, the step of opening the address of the designated page and acquiring the DOM tree of the designated page specifically comprises the following steps:
and starting a nodejs execution script, calling a Chrome DevTools Protocol tool to control a browser to open the address of the specified page, and calling a DOM (document object model) interface of the Chrome DevTools Protocol tool to acquire the DOM tree of the specified page.
Preferably, the method further comprises the steps of:
judging whether the DOM node is bound with a click event or not, and when the DOM node is bound with the click event, continuously judging whether the cursor style of the DOM node is pointer or not;
and when the cursor style is pointer, marking the DOM node as the clickable element.
Preferably, the method further comprises the steps of:
the DOM node binds a click event, and when the cursor pattern is not a pointer, the click event is judged to be a delegation event, and the DOM node is a delegation event element;
and traversing child nodes of the entrusted event element, judging whether the cursor style of the child nodes is pointer, and marking the child nodes as clickable elements when the cursor style is pointer.
Preferably, generating a corresponding query link based on the clickable element specifically includes the following steps:
acquiring the name, ID, style attribute, other attribute and the position of a parent node of the clickable element;
generating a css-like identification of a clickable element based on the name, the ID, the style attribute, the other attributes, and the location at the parent node;
and generating a query link corresponding to the clickable element based on the cs-like identification of the clickable element and the cs-like identification of the parent node of the clickable element.
Preferably, the method further comprises the steps of:
after the designated page is loaded, monitoring abnormal events of the designated page, wherein the abnormal events comprise deletion of DOM nodes, addition of DOM nodes or updating of attributes of the DOM nodes of the designated page;
and adding the deleted DOM nodes, the added DOM nodes and the attribute-updated DOM nodes into a blacklist.
Preferably, the method for judging whether the clickable element is valid or not based on the preset event specifically includes the following steps:
the preset events comprise whether the clickable elements are modified or not, whether jump pages exist or not, whether network requests are sent or not and whether error report exists in a console or not;
if the clickable element is monitored to be modified, judging that the clickable element is effective, if the specified page is not the original address, judging that the clickable element is effective, if a network sending request is detected, judging that the clickable element is effective, and if the console has no error report, judging that the clickable element is effective.
Preferably, the method further comprises the steps of:
when the clickable elements are invalid, collecting the invalid clickable elements and transmitting the invalid clickable elements to the development end;
and circularly judging whether the next clickable element is effective or not until all clickable elements are judged.
An electronic device comprising a memory and a processor, the memory storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement a method of detecting web page elements as described above.
A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method described above.
The application provides beneficial effect lies in:
1. according to the method, all DOM nodes are obtained by traversing the DOM tree, when the DOM nodes are clickable elements, corresponding query links are generated based on the clickable elements, the test tool queries the corresponding clickable elements based on the query links, whether the clickable elements are effective or not is judged based on preset events, the full amount of webpage elements to be tested can be comprehensively scanned and obtained for testing, whether the clickable elements of the pages are effective or not is automatically detected, and the purpose of full-amount coverage testing is achieved. Need not to consume the human cost, compare in artifical the detection, this application has promoted detection efficiency and the accuracy that detects by a wide margin.
2. After the designated page is loaded, monitoring abnormal events of the designated page, wherein the abnormal events comprise deletion of a DOM node, addition of the DOM node or updating of the attribute of the DOM node of the designated page, and adding the deleted DOM node, the added DOM node and the attribute-updated DOM node into a blacklist, so that the accuracy of whether a follow-up simulation user clicks the DOM node is effective or not is guaranteed.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
FIG. 1 is a flow chart of a method of detecting web page elements.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the 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.
Example 1:
as shown in fig. 1, the embodiment includes a method for detecting web page elements, including the following steps: and opening the address of the specified page, acquiring a DOM tree of the specified page, and traversing the DOM tree to obtain all DOM nodes.
And when the DOM node is the clickable element, generating a corresponding query link based on the clickable element, and storing the clickable element and the query link corresponding to the clickable element. The test tool queries the corresponding clickable elements based on the query link, and judges whether the clickable elements are effective or not based on a preset event.
This application can comprehensive scanning and acquire the webpage element that the total volume awaits measuring and test, and whether the clickable element of automated inspection page is effective need not to consume the human cost, compares in artifical the detection, and this application has promoted detection efficiency and the accuracy that detects by a wide margin.
Opening the address of the specified page and acquiring the DOM tree of the specified page, and specifically comprising the following steps: and starting a nodejs execution script, calling a Chrome DevTools Protocol tool to control the browser to open the address of the specified page, and calling a DOM.getdocument interface of the Chrome DevTools Protocol tool to acquire the DOM tree of the specified page.
In this embodiment, the browser is a Chrome browser, the nodejs execution script calls a Chrome DevTools Protocol tool to control the Chrome browser to open the address of the specified page, calls a dom.getdocument interface of the Chrome DevTools Protocol tool to obtain a DOM tree of the specified page, and circularly traverses the DOM tree to obtain all DOM nodes.
Further comprising the steps of: and judging whether the DOM node is bound with the click event or not, and when the DOM node is bound with the click event, continuously judging whether the cursor style of the DOM node is pointer or not. When the cursor style is pointer, the DOM node is marked as a clickable element.
Specifically, whether the DOM node binds the click event is judged through a DOMDebugger. If the DOM node binds the click event, executing window, get computed style (from) cursor by a Chrome DevTools Protocol tool, judging whether the cursor style of the DOM node is pointer, wherein the pointer style represents that a page mouse becomes a finger style when floating, and elements of the finger style are regarded as clickable elements on the webpage specification. When the DOM node binds the click event, and the style has curror: pointer, marks this DOM node as a clickable element.
Further comprising the steps of: and binding the click event by the DOM node, and judging that the click event is a delegation event and the DOM node is a delegation event element when the cursor pattern is not a pointer. And traversing child nodes of the entrusted event element, judging whether the cursor style of the child nodes is pointer, and marking the child nodes as clickable elements when the cursor style is the pointer.
In this embodiment, if the DOM node binds the click event, but the style has no cursor: pointer, the click event is judged as a delegation event, and the DOM node is a delegation event element. And traversing the child nodes of the entrusted event element, and even if the child nodes do not bind the click event, marking the child nodes as clickable elements when the cursor styles of the child nodes are pointers.
Generating a corresponding query link based on clickable elements, specifically comprising the following steps: the name, ID, style attribute, other attributes of the clickable element, and the location at the parent node are obtained. Based on the name, ID, style attribute, other attributes, and location at the parent node, a css-like identification for the clickable element is generated. And generating a query link corresponding to the clickable element based on the css identification of the clickable element and the css identification of the father node of the clickable element.
In this embodiment, the name of the clickable element is div, the ID of the clickable element is app, the styles of the clickable element are class1 and class2, the other attribute of the clickable element is attr =1, the clickable element is the 2 nd child element located in the parent node, and the class css of the clickable element is identified as: div # app. class1.class2[ attr1=1 ]: nth-child (2).
And generating a query link corresponding to the clickable element based on the class cs identification of the clickable element and the class cs identification of the parent node of the clickable element, and storing the clickable element and the query link corresponding to the clickable element.
Further comprising the steps of: after the designated page is loaded, monitoring abnormal events of the designated page, wherein the abnormal events comprise deletion of a DOM node, addition of the DOM node or updating of the attribute of the DOM node of the designated page. And adding the deleted DOM nodes, the added DOM nodes and the attribute-updated DOM nodes into a blacklist.
Specifically, before the simulation user clicks the DOM node, after the designated page is completely loaded, the abnormal event of the designated page is monitored through the MutationObserver, in this embodiment, the monitoring time is ten seconds, the monitoring time can be modified according to the actual service requirement, once the designated page has page changes such as deleting the DOM node, adding the DOM node or updating the attribute of the DOM node, the page change can be monitored by the MutationObserver and triggered to be notified, the page change before the simulation user clicks the DOM node is collected, and the page change in this embodiment is the abnormal event. And adding the deleted DOM nodes, the added DOM nodes and the attribute-updated DOM nodes into a blacklist.
When a page is initialized, animation special effects such as carousel and timer are provided, the animation special effects are page changes generated by the continuous change of the DOM node, and the page changes can be monitored by the MutationObserver, so that the accuracy of whether the DOM node is clicked by a subsequent simulation user is effective or not is influenced, and the animation special effects need to be recorded in a blacklist.
The test tool queries corresponding clickable elements based on the query link, and specifically comprises the following steps: after the clickable elements and the query links corresponding to the clickable elements are saved, the nodejs executes the script to trigger the testing tool, the testing tool queries the corresponding DOM nodes based on the acquired query links, and a user is simulated to click the DOM nodes.
In the present embodiment, the test tool is a UI automation test tool cypress. As another implementation, the Chrome browser is operated by a Chrome DevTools Protocol tool, and the corresponding DOM node can also be queried based on the acquired query link, so as to simulate the user to click on the DOM node.
Judging whether the clickable elements are effective or not based on a preset event, and specifically comprising the following steps of: the preset events include whether the clickable element is modified, whether a jump page exists, whether a network request is sent, and whether a console has an error.
If the clickable element is monitored to be modified, the clickable element is judged to be effective, if the specified page is not the original address, the clickable element is judged to be effective, if a network sending request is detected, the clickable element is judged to be effective, and if the console has no error, the clickable element is judged to be effective.
In this embodiment, whether the clickable element is modified or not is monitored through the MutationObserver, and if the clickable element is modified, it is determined that the clickable element is valid. If the clickable element is not modified, continuously checking whether the window.
And if the clicked element is the original url, detecting whether a network sending request exists after the clicked element is clicked by intercepting the XHR or catch, and if the network sending request exists, judging that the clicked element is effective. And if no network request is sent, monitoring the unhandledrection and error through the window. If the console has an error, the clickable element is determined to be invalid.
Further comprising the steps of: and when the clickable elements are invalid, collecting the invalid clickable elements and transmitting the invalid clickable elements to the development end, and circularly judging whether the next clickable element is valid or not until all clickable elements are judged.
Example 2:
an electronic device comprising a memory and a processor, the memory storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement a method of detecting web page elements as described above. It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working process of the electronic device described above may refer to the corresponding process in the foregoing method embodiment, and is not described herein again.
A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the method of embodiment 1.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that:
reference in the specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. Thus, the appearances of the phrase "one embodiment" or "an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
In addition, it should be noted that the specific embodiments described in the present specification may differ in the shape of the components, the names of the components, and the like. All equivalent or simple changes in the structure, characteristics and principles as described in the patent idea are included in the protection scope of the patent. Various modifications, additions and substitutions for the specific embodiments described herein may occur to those skilled in the art without departing from the scope and spirit of the invention as defined by the accompanying claims.
Claims (10)
1. A method for detecting web page elements, comprising the steps of:
opening the address of the designated page, acquiring a DOM tree of the designated page, and traversing the DOM tree to obtain all DOM nodes;
when the DOM node is a clickable element, generating a corresponding query link based on the clickable element, and storing the clickable element and the query link corresponding to the clickable element;
and the testing tool queries the corresponding clickable elements based on the query link and judges whether the clickable elements are effective or not based on a preset event.
2. The method for detecting web page elements according to claim 1, wherein opening an address of a specified page and obtaining a DOM tree of the specified page specifically comprises the following steps:
and starting a nodejs execution script, calling a Chrome DevTools Protocol tool to control a browser to open the address of the specified page, and calling a DOM (document object model) interface of the Chrome DevTools Protocol tool to acquire the DOM tree of the specified page.
3. The method of detecting web page elements of claim 1, further comprising the steps of:
judging whether the DOM node is bound with a click event or not, and when the DOM node is bound with the click event, continuously judging whether the cursor style of the DOM node is pointer or not;
and when the cursor style is pointer, marking the DOM node as the clickable element.
4. A method for detecting web page elements as claimed in claim 3, further comprising the steps of:
the DOM node binds a click event, and when the cursor pattern is not a pointer, the click event is judged to be a delegation event, and the DOM node is a delegation event element;
and traversing child nodes of the entrusted event element, judging whether the cursor style of the child nodes is pointer, and marking the child nodes as clickable elements when the cursor style is pointer.
5. The method of claim 1, wherein generating the corresponding query link based on the clickable element comprises the following steps:
acquiring the name, ID, style attribute, other attribute and the position of a parent node of the clickable element;
generating a css-like identification of a clickable element based on the name, the ID, the style attribute, the other attributes, and the location at the parent node;
and generating a query link corresponding to the clickable element based on the cs-like identification of the clickable element and the cs-like identification of the parent node of the clickable element.
6. The method of detecting web page elements of claim 1, further comprising the steps of:
after the designated page is loaded, monitoring abnormal events of the designated page, wherein the abnormal events comprise deletion of DOM nodes, addition of DOM nodes or updating of attributes of the DOM nodes of the designated page;
and adding the deleted DOM nodes, the added DOM nodes and the attribute-updated DOM nodes into a blacklist.
7. The method for detecting web page elements according to claim 1, wherein the step of determining whether the clickable element is valid based on a preset event specifically comprises the steps of:
the preset events comprise whether the clickable elements are modified or not, whether jump pages exist or not, whether network requests are sent or not and whether error report exists in a console or not;
if the clickable element is monitored to be modified, judging that the clickable element is effective, if the specified page is not the original address, judging that the clickable element is effective, if a network sending request is detected, judging that the clickable element is effective, and if the console has no error report, judging that the clickable element is effective.
8. The method of detecting web page elements of claim 1, further comprising the steps of:
when the clickable elements are invalid, collecting the invalid clickable elements and transmitting the invalid clickable elements to the development end;
and circularly judging whether the next clickable element is effective or not until all clickable elements are judged.
9. An electronic device comprising a memory and a processor, the memory storing one or more computer instructions, wherein the one or more computer instructions are executed by the processor to implement a method of detecting web page elements according to any one of claims 1 to 8.
10. A readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210288643.5A CN114385514A (en) | 2022-03-23 | 2022-03-23 | Method, equipment and storage medium for detecting webpage elements |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210288643.5A CN114385514A (en) | 2022-03-23 | 2022-03-23 | Method, equipment and storage medium for detecting webpage elements |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114385514A true CN114385514A (en) | 2022-04-22 |
Family
ID=81205864
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210288643.5A Pending CN114385514A (en) | 2022-03-23 | 2022-03-23 | Method, equipment and storage medium for detecting webpage elements |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114385514A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579347A (en) * | 2022-04-24 | 2022-06-03 | 浙江口碑网络技术有限公司 | Page abnormity detection method and device, computer equipment and readable storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011073982A1 (en) * | 2009-12-15 | 2011-06-23 | Seeker Security Ltd. | Method and system of runtime analysis |
| US20160321067A1 (en) * | 2015-04-28 | 2016-11-03 | Google Inc. | Infrastructure for hosting and publishing software packages |
| US20180165184A1 (en) * | 2016-12-13 | 2018-06-14 | Global Healthcare Exchange, Llc | Production-like testing and complex business to business auditing system |
| US20180260310A1 (en) * | 2017-03-13 | 2018-09-13 | Wipro Limited | Method and a system for generation of test automation scripts in real time |
| CN110297752A (en) * | 2018-03-23 | 2019-10-01 | 华为软件技术有限公司 | Acquisition methods and device, automatization test system, the storage medium of control element |
| CN110727603A (en) * | 2019-10-25 | 2020-01-24 | 重庆誉存大数据科技有限公司 | Improved method for automatically testing positioning elements based on UI (user interface) |
| CN111142988A (en) * | 2019-12-03 | 2020-05-12 | 东软集团股份有限公司 | Page testing method and device, storage medium and electronic equipment |
| CN112597031A (en) * | 2020-12-26 | 2021-04-02 | 中国农业银行股份有限公司 | Web page test case generation device and method |
-
2022
- 2022-03-23 CN CN202210288643.5A patent/CN114385514A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011073982A1 (en) * | 2009-12-15 | 2011-06-23 | Seeker Security Ltd. | Method and system of runtime analysis |
| US20160321067A1 (en) * | 2015-04-28 | 2016-11-03 | Google Inc. | Infrastructure for hosting and publishing software packages |
| US20180165184A1 (en) * | 2016-12-13 | 2018-06-14 | Global Healthcare Exchange, Llc | Production-like testing and complex business to business auditing system |
| US20180260310A1 (en) * | 2017-03-13 | 2018-09-13 | Wipro Limited | Method and a system for generation of test automation scripts in real time |
| CN110297752A (en) * | 2018-03-23 | 2019-10-01 | 华为软件技术有限公司 | Acquisition methods and device, automatization test system, the storage medium of control element |
| CN110727603A (en) * | 2019-10-25 | 2020-01-24 | 重庆誉存大数据科技有限公司 | Improved method for automatically testing positioning elements based on UI (user interface) |
| CN111142988A (en) * | 2019-12-03 | 2020-05-12 | 东软集团股份有限公司 | Page testing method and device, storage medium and electronic equipment |
| CN112597031A (en) * | 2020-12-26 | 2021-04-02 | 中国农业银行股份有限公司 | Web page test case generation device and method |
Non-Patent Citations (3)
| Title |
|---|
| （美）JIMR.WILSON等: "《Node.js开发实战》", 30 November 2018, 华中科技大学出版社, pages: 103 * |
| HIROSHI TANAKA ET AL: "X-BROT: Prototyping of Compatibility Testing Tool for Web Application Based on Document Analysis Technology", 《 2019 INTERNATIONAL CONFERENCE ON DOCUMENT ANALYSIS AND RECOGNITION WORKSHOPS (ICDARW)》, 7 November 2019 (2019-11-07) * |
| 姜文等: "基于Selenium的Web软件自动化测试", 《计算机技术与发展》, vol. 28, no. 9, 31 December 2018 (2018-12-31), pages 192 - 193 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579347A (en) * | 2022-04-24 | 2022-06-03 | 浙江口碑网络技术有限公司 | Page abnormity detection method and device, computer equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110442511B (en) | Visual embedded point testing method and device | |
| CN107562620B (en) | Automatic buried point setting method and device | |
| CN109189665B (en) | Method and device for recording, replaying and automatically testing data | |
| CN108459954B (en) | Application program vulnerability detection method and device | |
| WO2016008398A1 (en) | Program performance test method and device | |
| CN110059003B (en) | Automatic test method, device, electronic equipment and readable storage medium | |
| CN104301175A (en) | WEB service system simulation monitoring method based on browser | |
| Choudhary et al. | A cross-browser web application testing tool | |
| CN111552632A (en) | Interface testing method and device | |
| CN113448834A (en) | Buried point testing method and device, electronic equipment and storage medium | |
| CN116841865A (en) | Visual test method and device, electronic equipment and storage medium | |
| CN109101412B (en) | Test file generation method, test file generation device, test file testing method, test file testing device, storage medium and computer equipment | |
| CN114385514A (en) | Method, equipment and storage medium for detecting webpage elements | |
| Peng et al. | Cat: Change-focused android gui testing | |
| CN110543429A (en) | Test case debugging method and device and storage medium | |
| CN114491560A (en) | Vulnerability detection method and device, storage medium and electronic equipment | |
| CN107038117B (en) | Web automatic testing method based on definition-reference between event processing functions | |
| CN109697164A (en) | Test method, device, storage medium and the terminal of App have been adjusted in browser | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112069073A (en) | Test case management method, terminal and storage medium | |
| CN113934617A (en) | Data processing method, device, equipment and storage medium | |
| CN116016270A (en) | Switch test management method and device, electronic equipment and storage medium | |
| CN113031995B (en) | Rule updating method and device, storage medium and electronic equipment | |
| CN109684220A (en) | A kind of browser compatibility analysis method based on event replay | |
| CN116340169A (en) | XPath path detection method and device for page element |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20220422 |