CN107918575A - The monitoring method and device of a kind of page status - Google Patents

Abstract

The present invention provides a method and device for monitoring page status. The method is to obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, and the configuration information includes the URL of the page to be tested, crawling subpage URL rules, Control attribute rules, inspection rules, JavaScript switches, and client information; read URLs in the URL list, and generate document object model information for pages corresponding to URLs through client information and JavaScript switches for URLs; crawl subpage URL rules, The control attribute rules and checking rules check the document object model information of the page corresponding to the URL, and generate checking results. The invention can check a specific page or all pages according to the needs of users, find out the problems of the pages to be tested in time, and give feedback to the website maintenance personnel in time.

Description

Method and device for monitoring page status

technical field

The invention relates to the field of computer networks and computer software, in particular to a method and device for monitoring page status.

Background technique

When the user browses the web, the page displayed by the browser often displays abnormal pages due to various reasons, such as missing commodity prices, expired active pages, and inaccessible active pages. Therefore, it is necessary to use technical means to be able to When a page exception occurs, obtain the failure status of the page at the first time.

At present, in order to be able to obtain the failure status of the page, it is usually to check the specific page by manually opening the page at regular intervals. The disadvantage of this method is that the entire inspection work is not only time-consuming, but also the inspection work is inefficient, and it is difficult to meet the requirements of enterprises on the status of the website. monitoring work.

Contents of the invention

In view of this, the purpose of the present invention is to provide a method and device for monitoring page status, so as to obtain all associated pages, page information and page control attributes of the target page at the first time, and provide timely feedback to website maintenance personnel.

The technical solution of the present invention is to provide a method for monitoring page status, the method comprising:

Step S101: Obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, wherein the configuration information in the external configuration file includes the URL of the page to be tested, crawling subpage URL rules, and control attributes Rules, inspection rules, JavaScript switches, and client information;

Step S102: read the URL in the URL list of the page to be tested, and generate document object model information of the page corresponding to the URL for the URL through the client information and the JavaScript switch;

Step S103: Check the document object model information of the page corresponding to the URL according to the crawling subpage URL rule, the control attribute rule, and the checking rule, and generate a checking result.

Optionally, the crawling subpage URL rule is set to detect domain name information or a specific URL;

The control attribute rule is to obtain the control information of the page to be tested;

The inspection rule is to obtain prompt information about problems that appear on the page to be tested;

The JavaScript switch is used to judge whether the checking page needs to execute the JavaScript script;

The client information is used to simulate client attributes of the accessed page.

Optionally, step S102 further includes: when reading the URL in the URL list of the page to be tested, judging whether the page to be tested needs to execute JavaScript, and executing the page to be tested through the page request simulation tool according to the client information page.

Optionally, step S103 further includes: acquiring and saving the URL conforming to the crawling subpage URL rule from the document object model information of the page to be tested by using a regular expression;

Introducing CSS content in the document object model information into the document object model information to generate introverted document object model information;

According to the control attribute rules and the checking rules, the restrained document object model information is checked using a regular expression, and the checking result is generated.

Optionally, the method further includes: saving the final inspection result and the problem prompt information into a database, and notifying the page maintainer of the detection result and the prompt information of the problem page by email.

Optionally, the configuration information in the external configuration file further includes: crawling depth, which is used to set the level of the inspection page.

Optionally, the method further includes: according to the crawling subpage URL rule, crawling the URL corresponding to the crawling depth, thereby generating a new URL list of the page to be tested, and then repeatedly executing steps S102 and S103. After checking all the URLs in the URL list of the pages to be tested, a final checking result is obtained.

The present invention also provides a device for monitoring page status, the device comprising:

The configuration information module is used to obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, wherein the configuration information in the external configuration file includes the URL of the page to be tested, crawling subpage URL rules , control attribute rules, inspection rules, JavaScript switches, client information and crawling depth;

A URL parsing module, configured to read the URL in the URL list of the page to be tested, and for the URL, generate the document object model information of the page corresponding to the URL through the client information and the JavaScript switch;

A page checking module, configured to check the document object model information of the page corresponding to the URL according to the crawling subpage URL rules, the control attribute rules and the checking rules, and generate checking results;

Page monitoring module, for if the crawling depth of the page to be tested is greater than 1, crawl the URL corresponding to the crawling depth according to the crawling subpage URL rule, thereby generating a new page to be tested URL list, and then repeatedly execute the URL parsing module and the page checking module, until the URLs in the URL list of all the pages to be tested are checked, and the final checking result is obtained.

Optionally, the crawling subpage URL rule is set to detect domain name information or a specific URL;

The control attribute rule is to obtain the control information of the page to be tested;

The inspection rule is to obtain prompt information about problems that appear on the page to be tested;

The JavaScript switch is used to judge whether the checking page needs to execute the JavaScript script;

The client information is used to simulate the client attributes of the accessed page;

The crawling depth is used to set the level of inspection pages.

Optionally, it also includes: a page judging module, configured to judge whether the page to be tested needs to execute JavaScript when reading the URL in the URL list, and execute the JavaScript through a page request simulation tool according to the client information. The page to be tested.

Optionally, the first page checking module also includes:

A URL acquisition module, configured to obtain and save the URL that meets the crawling subpage URL rule from the document object model information of the page to be tested by using a regular expression;

A CSS restraint module, configured to restrain CSS content in the document object model information into the document object model information, and generate restrained document object model information;

The DOM checking module is configured to check the introverted document object model information using regular expressions according to the control attribute rules and the checking rules, and generate the checking result.

Optionally, the device further includes: a data processing module, configured to save the final inspection result and the question prompt information in a database, and pass the test result and the prompt information of the question page through Email the page maintainer.

Optionally, the configuration information in the external configuration file further includes: crawling depth, which is used to set the level of the inspection page.

Optionally, the device further includes: a page monitoring module, configured to crawl the URL corresponding to the crawling depth according to the crawling subpage URL rule, so as to generate a new URL list of the page to be tested, and then Step S102 and Step S103 are repeatedly executed until all the URLs in the URL list of the pages to be tested are checked to obtain the final checking result.

Through the monitoring method and device of the page state provided by the present invention, it is possible to check a specific page or all pages according to the needs of the user, and timely find problems of the page to be tested, such as page expiration, link error, invalid content, access error, etc. In addition, the page maintenance personnel can set the inspection depth of the page and whether to enable JavaScript loading on the page to be tested according to the requirements, and write the monitoring results to the database for later query.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort. In the attached picture:

FIG. 1 is a schematic flow diagram of a method for monitoring page status according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of a device for monitoring page status according to an embodiment of the present invention.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention more clear, the embodiments of the present invention will be further described in detail below in conjunction with the accompanying drawings. Here, the exemplary embodiments and descriptions of the present invention are used to explain the present invention, but not to limit the present invention.

Those skilled in the art know that the embodiments of the present invention can be implemented as a system, device, device, method or computer program product. Therefore, the present disclosure may be embodied in the form of complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

In this article, it is to be understood that among the terms involved:

URL: Uniform Resource Locator (Uniform Resource Locator) is a concise representation of the location and access methods of resources that can be obtained from the Internet, and is the address of standard resources on the Internet. Every file on the Internet has a unique URL, which contains information indicating where the file is located and what the browser should do with it;

JavaScript: A scripting language used in web pages, which is often used to add various dynamic functions to web pages to provide users with a smoother and more beautiful browsing effect. Usually JavaScript scripts realize their own functions by embedding them in HTML;

Cookie: A kind of information stored in the local browser, which can be used to directly communicate with the web server and directly obtain user information;

user-agent: part of the http request header, used to inform the server of the current client information;

DOM: Document Object Model (DocumentObjectModel), a model used to describe page code information;

CSS: An external file of web page style, which is used to manage page style information in a unified manner.

exemplary method

The self-service car return method in an exemplary embodiment of the present invention will be introduced below. It should be noted that the embodiments of the present invention are not limited in this regard. On the contrary, the embodiments of the present invention can be applied to any applicable scene.

For example, refer to FIG. 1 , which is a schematic flowchart of a method for monitoring a page status according to an embodiment of the present invention.

As shown, the method includes:

Step S101: Obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, wherein the configuration information in the external configuration file includes the URL of the page to be tested, crawling subpage URL rules, and control attributes Rules, inspection rules, JavaScript switches, and client information;

Step S102: read the URL in the URL list of the page to be tested, and generate document object model information of the page corresponding to the URL for the URL through the client information and the JavaScript switch;

Step S103: Check the document object model information of the page corresponding to the URL according to the crawling subpage URL rule, the control attribute rule, and the checking rule, and generate a checking result.

Optionally, the crawling subpage URL rule is set to detect domain name information or a specific URL;

The control attribute rule is to obtain the control information of the page to be tested;

The inspection rule is to obtain prompt information about problems that appear on the page to be tested;

The JavaScript switch is used to judge whether the checking page needs to execute the JavaScript script;

The client information is used to simulate client attributes of the accessed page.

Optionally, the step S102 further includes: when reading the URL in the URL list, judging whether the page to be tested needs to execute JavaScript, and executing the page to be tested through a page request simulation tool according to the client information page.

Optionally, the step S103 includes: acquiring and saving the URL conforming to the crawling subpage URL rule from the document object model information of the page to be tested by using a regular expression;

Introducing CSS content in the document object model information into the document object model information to generate introverted document object model information;

According to the control attribute rules and the checking rules, the restrained document object model information is checked using a regular expression, and the checking result is generated.

Optionally, the method further includes: saving the final inspection result and the problem prompt information in a database, and notifying the page maintainer of the detection result and the prompt information of the problem page by email.

Example

The present invention will be specifically described below in conjunction with a specific embodiment, but it should be noted that this specific embodiment is only for better describing the present invention, and does not constitute an improper limitation of the present invention.

Step S101: Obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, wherein the configuration information in the external configuration file includes the URL of the page to be tested, crawling subpage URL rules, and control attributes Rules, inspection rules, JavaScript switches, and client information;

Specifically, the user can pre-configure the configuration information in the external configuration file, and configure to obtain the URL list of the pages to be tested. According to user requirements, the configuration information may include: for example, crawling subpage URL rules, control attribute rules, inspection rules, JavaScript switches, client information, crawling depth, and whether to write to the database.

The configuration information is described in detail below:

(1) The user can define URL as the inspection object in a specific embodiment of the present invention, and the URL of the page to be tested can be configured in the URL list in the external configuration file, such as http://sale.jd.com/app /test.html .

(2) Crawling subpage URL rules, crawling subpage URL rules can match domain name information;

For example, if http://sale.jd.com/ is configured, all URL links starting with http://sale.jd.com/ will be searched in the page according to the crawl subpage URL rule.

In addition, the crawling subpage URL rule can also match a specific URL;

For example, if you configure http://sale.jd.com/abc.html , etc., only the URL link http://sale.jd.com/abc.html will be executed according to the crawl subpage URL rule.

(3) Control attribute rules, because the page control is the script element of each web page, such as <div> represents a region, <table> represents a table, and each control is distinguished by the id attribute, such as <tableid=1><tableid= 2> represent two different tables respectively. At the same time, each control has other properties, such as length, visibility, etc. Therefore, the user can set to check whether the visible property of a control is visible, then according to the control property rules, the program will find the control on the page and judge whether the visible property of the control is consistent with the user's requirements, and if not, it will capture to the question. By configuring the page control information, the purpose of checking the page style in step S104 can be achieved.

(4) Check the rules. The user sets the question type to check whether there is a problem with the page. For example, the question type can be reflected as "a 404 error occurred", "the event has expired" or "the page does not exist", etc., then if the page displays "the event has expired ", according to the inspection rule, the program will capture the problem prompt information of the page to be tested. By configuring the problem prompt information, the purpose of checking page error information in step S104 can be achieved.

(5) JavaScript switch, that is, a JavaScript enable switch (JavaScript Enabled), through which the user can set whether the page to be tested needs to execute the JavaScript script in the page. The page that executes the JavaScript script will see the dynamically generated content in the final page content, but will not see it if the JavaScript script is not executed (provided that the page to be tested has dynamically generated content). By configuring the JavaScript switch, it can be realized whether the document object model information (DOM) generated in step S103 is the document object model information (DOM) generated after executing the JavaScript script.

(6) Client information (user-agent), the user can set the client information (user-agent) to simulate the client information of the access page, for example, if the iPhone is set, it will simulate the browser on the iPhone mobile phone to access the page; For example, if you set up a PC, it will simulate accessing the page through a browser on the computer. By configuring the client information (user-agent), the purpose of simulating the client in step S103 can be achieved.

(7) Database switch (DBSwitch), the user can set and enable the database switch so as to write the captured page prompt information into the database. In addition, the database configuration needs to add the database address, database table name, account and password information to access the database. By configuring the database switch, the purpose of writing the final inspection result into the database in step S105 can be achieved.

In an embodiment of the present invention, the configuration information may further include: crawling depth (Depth), and the user may set the crawling depth for the monitoring program to perform recursive inspection. For example, if the crawling depth is set to 1 layer, the monitoring program will not crawl the links in the page to be tested, and the page that checks the entry will end. However, if the crawling depth is set to 2 layers, the monitoring program will crawl the user-defined link rules and save the crawled links. After checking all the entry pages, check the link you just saved, and so on. The purpose of the recursive inspection in step S104 can be achieved by configuring the crawling depth.

Step S102: Read the URL in the URL list of the page to be tested, and generate document object model information of the page corresponding to the URL for the URL through the client information and the JavaScript switch.

It is worth mentioning that when reading the URLs in the URL list, it is also necessary to determine whether the page to be tested needs to execute JavaScript, and execute the page to be tested through the page request simulation tool according to the client information.

Specifically, JavaScriptEnabled is set by reading, and if JavaScriptEnabled is true, javascript execution is enabled.

For example, the URL of a page to be tested is http://testabc.com/index.html , where the html content is as follows:

<html>

<script>

document.write("Hello");

</script>

</html>

If the page to be tested is executed through a browser, "Hello" will be displayed on the page. Similarly, if JavaScript is executed, we can see "hello" in the document object model information (DOM) of the page to be tested; if JavaScript is not executed, we will not see the keyword "hello".

In addition, through the general http request tool, if the requested page to be tested is a static page, the document object model information (DOM) can be returned, but if the requested page to be tested is a dynamic page, the returned document object model information (DOM ) will not include dynamically generated content.

In an embodiment of the present invention, go to request the page to be tested by phantomjs tool, after opening the JavaScript switch (permission to execute JavaScript), we can all obtain the document object model information (DOM) of no matter be dynamic or static page, so that analyzed later.

In the prior art, the user client is usually simulated mainly by modifying the http request header, which is complicated to operate and easy to input wrongly.

Since user-agent can simulate different user client situations, the scene of user login can be simulated by setting cookie information in the present invention, and the purpose of simulating user client information can be realized by setting the value in user-agent. For example, set the configuration information of <user-agent> iPhone to inform the monitoring and access page to simulate the iPhone mobile terminal.

Take http://www.163.com as an example, the website uses this value to return different page content. In the actual test scenario, we need to check the output of the specific client. If we want to know whether the user can see the sports section when visiting http://www.163.com through the iPhone mobile terminal. Then by setting the value of user-agent, you can simulate an iPhone user.

Finally, through the client information and the JavaScript switch, the document object model information (DOM) of the page to be tested can be generated, and the document object model information (DOM) can be saved for further analysis.

Step S103: Check the document object model information of the page corresponding to the URL according to the crawling subpage URL rule, the control attribute rule, and the checking rule, and generate a checking result.

First, by using regular expressions, obtain and save the URL that meets the crawling subpage URL rules from the Document Object Model information (DOM) of the page to be tested; the present invention utilizes the regular expression algorithm of page matching , you can filter out page problem descriptions, sub-activity links, properties of specific controls, image links, etc. to be analyzed.

Secondly, by analyzing the document object model information (DOM) before introversion, the CSS content of the URL is introverted into the document object model information (DOM) to generate introverted document object model information. Through this Document Object Model information (DOM), we can directly view the style properties of a specific control.

For example, before the document object model information (DOM) is introverted, the way to check the display properties of a certain control is to check the mark in the CSS file. After introversion, we can directly view the control properties, such as: <span display:block> you Good</span>.

Finally, according to the control attribute rules and the checking rules, the regular expression is used to check the introverted Document Object Model information (DOM), and a checking result is generated.

Specifically, through the inspection rules set by the user, use regular expressions to check whether the introverted Document Object Model information (DOM) contains problem description content (for example, "404 error occurred", "activity has expired" or "page Does not exist", etc.), if the problem description content is included, record the problem description content. For example, if the configuration check page in the external configuration file expires, if the page to be tested contains keywords such as page expiration, the expiration problem of the URL link of the active page is recorded.

Through the control attribute inspection rules in the configuration information in the external configuration file, through regular expressions, match the control attributes that need to be checked in the DOM tree structure after the CSS is introverted. For example: if you need to check that the attribute of a certain link (<a> tag) is invisible, if the tag is matched and its display attribute is visible, record the error problem

Step S104: If the crawling depth of the page to be tested is greater than 1, crawl the URL corresponding to the crawling depth according to the crawling subpage URL rule, thereby generating a new URL list of the page to be tested, Then step S102 and step S103 are repeatedly executed until all the URLs in the URL list of the pages to be tested are checked to obtain the final checking result.

If all the URLs are checked, the problems can be classified and recorded in the database through the externally configured database information. At the same time, the problem is sent to the responsible person by email through the externally configured email responsible person receiving list.

FIG. 2 is a schematic diagram of a device for monitoring page status according to an embodiment of the present invention. The device 2 includes:

Configuration information module 21, is used for obtaining external configuration file, and described external configuration file comprises the URL list of page to be tested, and wherein, the configuration information in the described external configuration file comprises the URL of described page to be tested, crawls sub-page URL Rules, control attribute rules, inspection rules, JavaScript switches, client information and crawling depth;

The URL parsing module 22 is configured to read the URL in the URL list of the page to be tested, and for the URL, generate the document object model information of the page corresponding to the URL through the client information and the JavaScript switch ;

The page checking module 23 is configured to check the document object model information of the page corresponding to the URL according to the crawling subpage URL rule, the control attribute rule and the checking rule, and generate a checking result.

Optionally, the crawling subpage URL rule is set to detect domain name information or a specific URL;

The control attribute rule is to obtain the control information of the page to be tested;

The inspection rule is to obtain prompt information about problems that appear on the page to be tested;

The JavaScript switch is used to judge whether the checking page needs to execute the JavaScript script;

The client information is used to simulate client attributes of the accessed page.

Optionally, it also includes: a page judging module 24, which is used to judge whether the page to be tested needs to execute JavaScript when reading the URL in the URL list, and execute the JavaScript by the page request simulation tool according to the client information. Describe the page to be tested.

Optionally, the page checking module 23 also includes:

The URL obtaining module 231 is used to obtain and save the URL that conforms to the crawling subpage URL rule from the document object model information of the page to be tested by using a regular expression;

A CSS restraint module 232, configured to restrain the CSS content in the document object model information into the document object model information, and generate restrained document object model information;

The DOM checking module 233 is configured to check the introverted document object model information using a regular expression according to the control attribute rule and the checking rule, and generate the checking result.

Optionally, the device further includes: a data processing module 25, configured to save the final inspection result and the question prompt information in a database, and pass the test result and the prompt information of the question page through Email the page maintainer.

Optionally, the configuration information in the external configuration file further includes: crawling depth, which is used to set the level of the inspection page.

Optionally, the device also includes: a page monitoring module 26, configured to crawl the page corresponding to the crawling depth according to the crawling subpage URL rule if the crawling depth of the page to be tested is greater than 1. URL, thereby generating a new URL list of the page to be tested, then repeatedly executing the URL parsing module and the page inspection module, until all URLs in the URL list of the page to be tested are checked, to obtain the final inspection result.

Since the device for monitoring the page status provided by the present invention is a device corresponding to the above method, it will not be described in detail here.

Through the monitoring method and device of the page state provided by the present invention, it is possible to check a specific page or all pages according to the needs of the user, and timely find problems of the page to be tested, such as page expiration, link error, invalid content, access error, etc. In addition, the page maintenance personnel can set the inspection depth of the page and whether to enable JavaScript loading on the page to be tested according to the requirements, and write the monitoring results to the database for later query.

Additionally, while operations of the methods of the present invention are depicted in the figures in a particular order, this does not require or imply that all illustrated operations must be performed to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution.

The specific embodiments described above have further described the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above descriptions are only specific embodiments of the present invention and are not intended to limit the scope of the present invention. Protection scope, within the spirit and principles of the present invention, any modification, equivalent replacement, improvement, etc., shall be included in the protection scope of the present invention.

Claims (14)

1. A monitoring method of page state, is characterized in that, described method comprises: Step S101: Obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, wherein the configuration information in the external configuration file includes the URL of the page to be tested, crawling subpage URL rules, and control attributes Rules, inspection rules, JavaScript switches, client information; Step S102: read the URL in the URL list of the page to be tested, and generate document object model information of the page corresponding to the URL for the URL through the client information and the JavaScript switch; Step S103: Check the document object model information of the page corresponding to the URL according to the crawling subpage URL rule, the control attribute rule, and the checking rule, and generate a checking result. 2. The method of claim 1, wherein, The crawling sub-page URL rule is set to detect domain name information or a specific URL; The control attribute rule is to obtain the control information of the page to be tested; The inspection rule is to obtain prompt information about problems that appear on the page to be tested; The JavaScript switch is used to judge whether the checking page needs to execute the JavaScript script; The client information is used to simulate client attributes of the accessed page. 3. The method according to claim 1, wherein step S102 further comprises: When reading the URL in the URL list of the page to be tested, it is judged whether the page to be tested needs to execute JavaScript, and the page to be tested is executed through the page request simulation tool according to the client information. 4. The method according to claim 1, characterized in that the step S103 comprises: Obtaining and storing the URL conforming to the crawling subpage URL rule from the document object model information of the page to be tested by using a regular expression; Introducing CSS content in the document object model information into the document object model information to generate introverted document object model information; According to the control attribute rules and the checking rules, the restrained document object model information is checked using a regular expression, and the checking result is generated. 5. The method of claim 2, further comprising: The final inspection result and the problem prompt information are saved in the database, and the test result and the prompt information of the problem page are notified to the page maintainer by email. 6. The method according to claim 1, wherein the configuration information in the external configuration file further comprises: Crawl depth, used to set the level of inspection pages. 7. The method according to claim 6, further comprising: According to the crawling subpage URL rule, crawl the URL corresponding to the crawling depth, thereby generating a new URL list of the page to be tested, and then repeatedly execute steps S102 and S103, and wait for the inspection to be completed. URLs in the URL list of the page to get the final check result. 8. A monitoring device for page status, characterized in that the device comprises: The configuration information module is used to obtain an external configuration file, the external configuration file includes a URL list of the page to be tested, wherein the configuration information in the external configuration file includes the URL of the page to be tested, crawling subpage URL rules , control attribute rules, inspection rules, JavaScript switches, client information and crawling depth; A URL parsing module, configured to read the URL in the URL list of the page to be tested, and for the URL, generate the document object model information of the page corresponding to the URL through the client information and the JavaScript switch; A page checking module, configured to check the document object model information of the page corresponding to the URL according to the crawling subpage URL rules, the control attribute rules and the checking rules, and generate checking results; Page monitoring module, for if the crawling depth of the page to be tested is greater than 1, crawl the URL corresponding to the crawling depth according to the crawling subpage URL rule, thereby generating a new page to be tested URL list, and then repeatedly execute the URL parsing module and the page checking module, until the URLs in the URL list of all the pages to be tested are checked, and the final checking result is obtained. 9. The device of claim 8, wherein: The crawling sub-page URL rule is set to detect domain name information or a specific URL; The control attribute rule is to obtain the control information of the page to be tested; The inspection rule is to obtain prompt information about problems that appear on the page to be tested; The JavaScript switch is used to judge whether the checking page needs to execute the JavaScript script; The client information is used to simulate client attributes of the accessed page. 10. The device according to claim 8, further comprising: a page judging module, for judging whether the page to be tested needs to execute JavaScript when the URL in the URL list of the page to be tested is used, according to the The client information executes the page to be tested through a page request simulation tool. 11. The device according to claim 8, wherein the page checking module further comprises: A URL acquisition module, configured to obtain and save the URL that meets the crawling subpage URL rule from the document object model information of the page to be tested by using a regular expression; A CSS restraint module, configured to restrain CSS content in the document object model information into the document object model information, and generate restrained document object model information; The DOM checking module is configured to check the introverted document object model information using regular expressions according to the control attribute rules and the checking rules, and generate the checking result. 12. The device of claim 9, further comprising: The data processing module is used to save the final inspection result and the prompt information of the problem in the database, and notify the page maintenance personnel of the detection result and the prompt information of the problem page by email. 13. The device according to claim 9, wherein the configuration information in the external configuration file further comprises: Crawl depth, used to set the level of inspection pages. 14. The device according to claim 13, further comprising: The page monitoring module is used to crawl the URL corresponding to the crawling depth according to the crawling sub-page URL rule, thereby generating a new URL list of the page to be tested, and then repeatedly executing steps S102 and S103, to be checked Complete all the URLs in the URL list of the page to be tested to obtain the final inspection result.