CN115174343B - B/S architecture page inspection method and device and page inspection system - Google Patents
B/S architecture page inspection method and device and page inspection system Download PDFInfo
- Publication number
- CN115174343B CN115174343B CN202210740348.9A CN202210740348A CN115174343B CN 115174343 B CN115174343 B CN 115174343B CN 202210740348 A CN202210740348 A CN 202210740348A CN 115174343 B CN115174343 B CN 115174343B
- Authority
- CN
- China
- Prior art keywords
- inspection
- page
- server
- information
- software
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/024—Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0246—Exchanging or transporting network management information using the Internet; Embedding network management web servers in network elements; Web-services-based protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/04—Network management architectures or arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
- H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Databases & Information Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a B/S architecture page inspection method, a device and a page inspection system, wherein software page configuration information needing inspection in a B/S architecture is configured in a QA Server; according to the software page configuration information, splicing to obtain information to be inspected, and initiating inspection access to the QA Server; the QA Server receives the information to be inspected and synchronously returns the information to be inspected to a NodeJS inspection end in a polling mode to request to trigger inspection; and the NodeJS inspection terminal performs page inspection. By using the method, the page to be inspected can be input into the QA Server in a page configuration mode, when the page inspection is carried out, the inspection process can be unattended, the relevant people can be notified after the inspection is finished, inspection results can be directly checked in the QA Server, the labor is reduced, and the time is saved.
Description
Technical Field
The disclosure relates to the technical field of internet, in particular to a B/S architecture page inspection method, a device and a page inspection system.
Background
After the software development is completed and the online deployment is completed, the running state of the software needs to be detected regularly. Under the B/S architecture, the software needs to be run by taking a browser as a client, and after the software is deployed and online, a large amount of manpower is required to be input to carry out regression testing on the software, so that the stability is ensured.
In addition, the basic function of the regression software is a very high-repeatability work, and whether page retrieval errors of continuously opening the software are possible or not is detected, wherein whether the items contain page errors or not is detected, whether the requests of the pages are all loaded successfully or not is detected, and whether the corresponding time consumption of the pages is too long or not is detected. The traditional detection mode is as disclosed in CN111209166A and provides an automatic inspection system for a B/S architecture service system, which comprises a system inspection module and a page inspection module, wherein the system inspection module and the page inspection module are respectively and correspondingly connected with a task configuration scheduling module, the system inspection module and the page inspection module are respectively and correspondingly connected with an inspection result summarizing routing module, and the inspection result summarizing routing module is correspondingly connected with a message notification agent module. According to the method, the server is logged in, original instructions of the server are used, original data are collected to the local area to be divided, converted, checked and compared, a user is simulated to access a system web page, various element information values of the page are checked, a patrol result is finally summarized, and information is notified to operation and maintenance personnel, so that complete operation and check of a B/S architecture service system is automatically achieved, labor cost of operation and maintenance is reduced, timeliness of fault discovery is improved, and normal operation of the service system is effectively guaranteed. Although the inspection can reach a certain inspection, after the inspection result is received, the inspection result needs to be summarized and refined into a conclusion, the inspection items comprise total inspection items, failure item lists and the like, and then a detailed inspection report is generated according to a self-defined report template; and (5) grouping and splicing the result screenshots of the page inspection according to success and failure items to form a plurality of M-N Gong Getu, and finally sending the conclusion, the report and the grid pattern to the message agency according to the notification mode and the notification rule configured by the inspection task set.
Therefore, in the conventional inspection method, more inspection items need to be designed in the inspection process, and after login is required to be completed, timely discovery problems are reported, so that the flow is complicated and excessive manpower is required to be input.
Disclosure of Invention
In order to solve the problems, the application provides a B/S architecture page inspection method, a device and a page inspection system.
In one aspect of the present application, a method for inspecting a B/S architecture page is provided, including the following steps:
s100, acquiring software page configuration information to be inspected in a B/S architecture, and configuring the software page configuration information in a QA Server;
s200, according to the software page configuration information, splicing to obtain information to be inspected, and initiating inspection access to the QA Server;
s300, the QA Server receives the information to be inspected, and synchronously returns the information to be inspected to a NodeJS inspection end in a polling mode to request to trigger inspection;
and S400, the NodeJS inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QA Server.
As an optional implementation manner of the present application, optionally, in step S100, obtaining software page configuration information required to be inspected in the B/S architecture, and configuring the software page configuration information in a QA Server, including:
s101, determining software to be inspected in a B/S architecture;
s102, acquiring and storing software page configuration information of software which is determined to need inspection, wherein the software page configuration information comprises at least one of page routing information, login information and maximum response time information;
s103, inputting and storing the software page configuration information in the QA Server.
As an optional implementation manner of the present application, optionally, in step S200, according to the software page configuration information, the information to be patrolled and examined is obtained by hashing, and the patrolling access is initiated to the QA Server, including:
s201, judging whether the software needs to log in:
if the software needs to log in, acquiring login information according to the software page configuration information and logging in; after successful login, splicing to obtain information to be inspected according to the software page configuration information;
if the software does not need to log in, splicing according to the software page configuration information to obtain information to be inspected;
s202, acquiring the information to be inspected, and initiating inspection access to the QA Server.
As an optional implementation manner of the present application, optionally, in step S300, the QA Server receives the information to be inspected, and synchronously returns the information to be inspected to the nodeb inspection terminal in a polling manner, and requests to trigger inspection, including:
s301, the QA Server acquires the information to be inspected according to the inspection access request;
s302, based on a preset polling mode, the QA Server synchronously requests a request signal for triggering inspection to the NodeJS Server;
s303, the NodeJS Server forwards the request signal for triggering inspection to the NodeJS inspection terminal.
As an optional implementation manner of the present application, optionally, in step S400, the step of receiving, by the nodeb inspection terminal, an inspection trigger request, performing a page inspection on the information to be inspected, and feeding back a page inspection result to the QA Server, including:
s401, the NodeJS routing inspection terminal receives an inspection trigger request;
s402, calling an access port of an automatic test tool configured in the NodeJS inspection terminal according to the inspection trigger request, and accessing a headless browser;
s403, loading the page in the information to be patrolled and examined through the headless browser, and monitoring callback of the page state: and when the callback of the page state is monitored, returning callback page information to the QA Server, and triggering the inspection to finish.
Optionally, in step S403, the returning callback page information to the QA Server includes:
s4031, acquiring a page inspection result in callback;
s4032, the page inspection result is returned to the NodeJS inspection end in a callback mode through the automatic testing tool;
s4033, the NodeJS inspection terminal receives the page inspection result, returns the page inspection result to the NodeJS Server, and returns the page inspection result to the QAServer through the NodeJS Server.
As an optional implementation manner of the present application, optionally, in step S400, the nodeb routing inspection terminal receives an inspection trigger request, performs a page routing inspection on the information to be inspected, and feeds back a page routing inspection result to the QA Server, and further includes:
s410, the QA Server receives the page inspection result and stores the result in a Mysql database;
s420, the QA Server judges whether the page inspection result is abnormal or not according to the configured software page configuration information and outputs a judgment result;
s430, sending the judging result to the user.
As an optional implementation manner of the present application, optionally, in step S400, the nodeb routing inspection terminal receives an inspection trigger request, performs a page routing inspection on the information to be inspected, and feeds back a page routing inspection result to the QA Server, and further includes:
s411, establishing communication connection between the QA Server and the VUE;
s421, the software page configuration information and the judging result are sent to the VUE end, and visual display is carried out through the VUE end.
In another aspect of the present application, a device for implementing the above-mentioned B/S architecture page inspection method is provided, including:
the configuration module is used for acquiring the software page configuration information required to be inspected in the B/S architecture and configuring the software page configuration information on the QA Server;
the patrol access module is used for splicing the information to be patrol according to the software page configuration information and initiating patrol access to the QA Server;
the polling request module is used for receiving the information to be polled by the QA Server, synchronously returning the information to be polled to the NodeJS polling terminal in a polling mode, and requesting to trigger polling;
and the page patrol module is used for receiving the patrol trigger request by the NodeJS patrol terminal, carrying out page patrol on the information to be patrol, and feeding back a page patrol result to the QA Server.
In another aspect of the present application, a system for inspecting a page is further provided, including:
a processor;
a memory for storing processor-executable instructions;
the processor is configured to implement the above-described B/S architecture page patrol method when executing the executable instructions.
The invention has the technical effects that:
the method comprises the steps of obtaining software page configuration information to be inspected in a B/S architecture, and configuring the software page configuration information in a QA Server; according to the software page configuration information, splicing to obtain information to be inspected, and initiating inspection access to the QA Server; the QA Server receives the information to be inspected and synchronously returns the information to be inspected to a NodeJS inspection end in a polling mode to request to trigger inspection; and the NodeJS inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QAServer. The method has the advantages that the inspection can be divided into two ends, one is the inspection end and the other is the QA Server, when the method is used, a page to be inspected is required to be input into the QA Server in a page configuration mode, when the page inspection is carried out, the inspection process can be unattended, relevant people can be notified after the inspection is finished, inspection results can be directly checked in the QA Server, labor is reduced, and time is saved.
Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features and aspects of the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 illustrates a framework diagram of an application layer architecture system of the present invention;
FIG. 2 is a schematic diagram showing the implementation flow of the B/S architecture page inspection method of the present invention;
fig. 3 shows a timing diagram for the inspection and inspection feedback of the present invention.
Detailed Description
Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.
The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
In addition, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements, and circuits well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.
Example 1
Fig. 1 is a schematic diagram of an application layer architecture system for implementing the present application. In this embodiment, the inspection process is mainly divided into two ends, one is a NodeJS inspection end and the other is a QAServer (in order to facilitate visual display of inspection results, a VUE end may be additionally and optionally set). When the system is used, a page to be inspected needs to be input into the QA Server in a page configuration mode, certain preconditions are provided, and meanwhile, a user needs to have certain Java and Web development capability. When the method is used for page inspection, the inspection process can be unattended, the inspection is waited for being notified to related persons after the inspection is finished, inspection results can be directly checked in the QA Server, labor is reduced, and time is saved.
The function of the architecture system will be described in detail below:
(1) The NodeJS patrol terminal is used for providing HTTP service and triggering Playwrite to carry out patrol, and the patrol result is returned to the QA Server;
(2) QA Server provides the back end of page display and functions of configuration and back display, wherein the functions comprise that web provides Http service, core provides Interface, entity and Patrol for business processing;
(3) Downstream uses Mysql as data store;
(4) The uppermost uses the VUE end to perform visual inspection configuration and inspection result display.
The message processing parts configured in the NodeJS patrol terminal and the QA Server can be customized according to the user requirement and the patrol requirement, and the embodiment is not limited.
The implementation method for carrying out the page inspection in the B/S architecture by adopting the architecture system will be specifically described below.
As shown in fig. 2, in one aspect, the present application proposes a B/S architecture page inspection method, which includes the following steps:
s100, acquiring software page configuration information to be inspected in a B/S architecture, and configuring the software page configuration information in a QA Server;
firstly, the software page configuration (namely, software page configuration information) required to be inspected is input into a QA Server, and the final configuration of the software page falls into a Mysql database. As an optional implementation manner of the present application, optionally, in step S100, obtaining software page configuration information required to be inspected in the B/S architecture, and configuring the software page configuration information in a QA Server, including:
s101, determining software to be inspected in a B/S architecture;
s102, acquiring and storing software page configuration information of software which is determined to need inspection, wherein the software page configuration information comprises at least one of page routing information, login information and maximum response time information;
s103, inputting and storing the software page configuration information in the QA Server.
In the B/S architecture, software which needs to be inspected is firstly determined, and then the next software page inspection work can be performed. And after the software is determined, acquiring the software page configuration information of the software which is determined to need to be inspected, and storing the software page configuration information in the QA Server. The software page configuration information, that is, page information that needs to be inspected when the software page is configured, such as page routing information, login information, maximum response time information, and the like, is determined according to the page information contained in the software page and inspection conditions set by a user. This is not limited to only these several inspection items.
The configuration here refers to configuration information in terms of routing of the page, whether to log in, login information, maximum response time, and the like.
S200, according to the software page configuration information, splicing to obtain information to be inspected, and initiating inspection access to the QA Server;
when the configuration of the patrol information is finished, the patrol information is spliced into a patrol configuration URL according to the configuration input before, and a patrol access is initiated to the QA Server (the patrol is not started). As an optional implementation manner of the present application, optionally, in step S200, according to the software page configuration information, the information to be patrolled and examined is obtained by hashing, and the patrolling access is initiated to the QA Server, including:
s201, judging whether the software needs to log in:
if the software needs to log in, acquiring login information according to the software page configuration information and logging in; after successful login, splicing to obtain information to be inspected according to the software page configuration information;
if the software does not need to log in, splicing according to the software page configuration information to obtain information to be inspected;
s202, acquiring the information to be inspected, and initiating inspection access to the QA Server.
Thus in conventional B/S architecture software, the functional rights of login and non-login are different. Therefore, in this embodiment, the present application determines whether to log in:
(1) Requiring login
When software needs to log in, the application needs to acquire login information according to the logged configuration, log in and take to Token, wherein Token is a login certificate and is an identity Token of the login;
(2) No need to log in
When the login is not needed, the configuration URL for patrol is spliced according to the configuration input before, and patrol access is initiated to the QA Server.
S300, the QA Server receives the information to be inspected, and synchronously returns the information to be inspected to a NodeJS inspection end in a polling mode to request to trigger inspection;
when the configuration needing inspection is spliced, the inspection of the NodeJS inspection terminal is triggered. As an optional implementation manner of the present application, optionally, in step S300, the QA Server receives the information to be inspected, and synchronously returns the information to be inspected to the nodeb inspection terminal in a polling manner, and requests to trigger inspection, including:
s301, the QAServer acquires the information to be inspected according to the inspection access request;
s302, based on a preset polling mode, the QA Server synchronously requests a request signal for triggering inspection to the NodeJS Server;
s303, the NodeJS Server forwards the request signal for triggering inspection to the NodeJS inspection terminal.
Specific: when the user triggers the patrol in the QA Server, the user can take the page information to be patrol from the request body. After the QA Server takes the routing inspection information, the routing inspection information is sent to the NodeJS routing inspection terminal in a polling mode through HTTP, and routing inspection is triggered.
In this embodiment, the polling end is triggered preferentially by the polling mode of HTTP.
And S400, the NodeJS inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QA Server.
After the NodeJS inspection terminal receives the inspection trigger request, the inspection of the software page is started. In this process, the request sent by the QA Server is forwarded to the NodeJS inspection terminal through the NodeJS Server. The NodeJS inspection terminal performs inspection, and returns the inspection result to the QA Server in the same mode.
As shown in fig. 3, the following describes the steps of implementation of the inspection and inspection feedback in detail.
As an optional implementation manner of the present application, optionally, in step S400, the step of receiving, by the nodeb inspection terminal, an inspection trigger request, performing a page inspection on the information to be inspected, and feeding back a page inspection result to the QA Server, including:
s401, the NodeJS routing inspection terminal receives an inspection trigger request;
s402, calling an access port of an automatic test tool configured in the NodeJS inspection terminal according to the inspection trigger request, and accessing a headless browser;
s403, loading the page in the information to be patrolled and examined through the headless browser, and monitoring callback of the page state: and when the callback of the page state is monitored, returning callback page information to the QA Server, and triggering the inspection to finish.
The NodeJS inspection terminal calls an API of an automatic testing tool (in the embodiment, playright is preferred) in an asynchronous mode, accesses a URL by a headless browser, loads a page by using the headless browser, and monitors callback of the page state; and when the callback of the page state is monitored, packaging the state information of the page and callback to the QA Server in an HTTP mode. The inspection is completed, and the workflow for triggering the inspection is finished.
Note that: playwrite is an automated test tool that microsoft originated in 2020; headless browser refers to a browser that can run with a graphical interface. The user may choose to use the tool by himself, and the present embodiment is not limited.
Optionally, in step S403, the returning callback page information to the QA Server includes:
s4031, acquiring a page inspection result in callback;
s4032, the page inspection result is returned to the NodeJS inspection end in a callback mode through the automatic testing tool;
s4033, the NodeJS inspection terminal receives the page inspection result, returns the page inspection result to the NodeJS Server, and returns the page inspection result to the QA Server through the NodeJS Server.
Specifically, the playwrite will callback the page inspection result to the NodeJS inspection terminal in a callback manner, where the page inspection result includes information printed by the Console of the software page, error information of the page, request information of the page, and response time of the page.
After the NodeJS inspection end receives the page inspection result, the page inspection result is packaged in an HTTP mode and sent to the QA Server.
As an optional implementation manner of the present application, optionally, in step S400, the nodeb routing inspection terminal receives an inspection trigger request, performs a page routing inspection on the information to be inspected, and feeds back a page routing inspection result to the QA Server, and further includes:
s410, the QA Server receives the page inspection result and stores the result in a Mysql database;
s420, the QA Server judges whether the page inspection result is abnormal or not according to the configured software page configuration information and outputs a judgment result;
s430, sending the judging result to the user.
After receiving callback information of the inspection end, the QA Server stores the information into a Mysql database.
So far, callback is completed, and the flow of QA Server is finished. And sending the result to the user.
When the QA Server receives the callback of the NodeJS patrol terminal, judging whether the patrol task is abnormal according to the software page configuration information, analyzing according to the callback data packet and the patrol configuration, giving a result, warehousing the data, and asynchronously sending the result to a patrol user.
In order to facilitate the visual platform of the QA Server to view reports when relevant personnel, such as patrol users, receive the results.
As an optional implementation manner of the present application, optionally, in step S400, the nodeb routing inspection terminal receives an inspection trigger request, performs a page routing inspection on the information to be inspected, and feeds back a page routing inspection result to the QA Server, and further includes:
s411, establishing communication connection between the QA Server and the VUE;
s421, the software page configuration information and the judging result are sent to the VUE end, and visual display is carried out through the VUE end.
The QA Server can send the software page configuration information and the judging result to the VUE end, and the visual display is carried out through the VUE end, so that the visual inspection process and result are convenient for a user to visually check.
Thus, the present application is directed to
It should be noted that although the above has been described as an example, those skilled in the art will appreciate that the present disclosure should not be limited thereto. In fact, the user can be flexibly set according to the actual application scene, so long as the technical function of the application can be realized according to the technical method.
Example 2
Based on the implementation principle of embodiment 1, in another aspect of the present application, a device for implementing the above-mentioned B/S architecture page inspection method is provided, including:
the configuration module is used for acquiring the software page configuration information required to be inspected in the B/S architecture and configuring the software page configuration information on the QA Server;
the patrol access module is used for splicing the information to be patrol according to the software page configuration information and initiating patrol access to the QA Server;
the polling request module is used for receiving the information to be polled by the QA Server, synchronously returning the information to be polled to the NodeJS polling terminal in a polling mode, and requesting to trigger polling;
and the page patrol module is used for receiving the patrol trigger request by the NodeJS patrol terminal, carrying out page patrol on the information to be patrol, and feeding back a page patrol result to the QA Server.
The specific application of each module is described in embodiment 1, which is not repeated in this embodiment, where the application layer architecture related to each module is also described in embodiment 1.
It should be apparent to those skilled in the art that the implementation of all or part of the above-described embodiments of the method may be implemented by a computer program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, and the program may include the steps of the embodiments of the control methods described above when executed. The modules or steps of the invention described above may be implemented in a general-purpose computing device, they may be centralized in a single computing device, or distributed across a network of computing devices, or they may alternatively be implemented in program code executable by a computing device, such that they may be stored in a memory device and executed by a computing device, or they may be separately fabricated into individual integrated circuit modules, or multiple modules or steps within them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
It will be appreciated by those skilled in the art that implementing all or part of the above-described embodiment methods may be implemented by a computer program for instructing relevant hardware, and the program may be stored in a computer readable storage medium, and the program may include the embodiment flow of each control method as described above when executed. The storage medium may be a magnetic disk, an optical disc, a Read-only memory (ROM), a random access memory (RandomAccessMemory, RAM), a flash memory (flash memory), a hard disk (HDD), or a Solid State Drive (SSD); the storage medium may also comprise a combination of memories of the kind described above.
Example 3
Still further, another aspect of the present application further provides a page inspection system, including:
a processor;
a memory for storing processor-executable instructions;
the processor is configured to implement the above-described B/S architecture page patrol method when executing the executable instructions.
Embodiments of the present disclosure provide a page patrol system that includes a processor and a memory for storing processor-executable instructions. The processor is configured to implement any of the B/S architecture page patrol methods described above when executing the executable instructions.
Here, it should be noted that the number of processors may be one or more. Meanwhile, in the page inspection system of the embodiment of the disclosure, an input device and an output device may be further included. The processor, the memory, the input device, and the output device may be connected by a bus, or may be connected by other means, which is not specifically limited herein.
The memory is a computer-readable storage medium that can be used to store software programs, computer-executable programs, and various modules, such as: a program or module corresponding to a B/S architecture page inspection method in an embodiment of the disclosure. The processor executes various functional applications and data processing of the page patrol system by running software programs or modules stored in the memory.
The input device may be used to receive an input number or signal. Wherein the signal may be a key signal generated in connection with user settings of the device/terminal/server and function control. The output means may comprise a display device such as a display screen.
The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvement of the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Claims (10)
1. A B/S architecture page inspection method is characterized by comprising the following steps:
s100, acquiring software page configuration information to be inspected in a B/S architecture, and configuring the software page configuration information in a QA Server;
s200, according to the software page configuration information, splicing to obtain information to be inspected, and initiating inspection access to the QA Server;
s300, the QA Server receives the information to be inspected, and synchronously returns the information to be inspected to a NodeJS inspection end in a polling mode to request to trigger inspection;
and S400, the NodeJS inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QA Server.
2. The method for inspecting a B/S architecture page according to claim 1, wherein in step S100, obtaining software page configuration information required to be inspected in the B/S architecture, and configuring the software page configuration information in a QA Server, includes:
s101, determining software to be inspected in a B/S architecture;
s102, acquiring and storing software page configuration information of software which is determined to need inspection, wherein the software page configuration information comprises at least one of page routing information, login information and maximum response time information;
s103, inputting and storing the software page configuration information in the QA Server.
3. The B/S architecture page inspection method according to claim 1, wherein in step S200, according to the software page configuration information, the information to be inspected is obtained by splicing, and an inspection access is initiated to the QA Server, including:
s201, judging whether the software needs to log in:
if the software needs to log in, acquiring login information according to the software page configuration information and logging in; after successful login, splicing to obtain information to be inspected according to the software page configuration information;
if the software does not need to log in, splicing according to the software page configuration information to obtain information to be inspected;
s202, acquiring the information to be inspected, and initiating inspection access to the QA Server.
4. The method of claim 1, wherein in step S300, the QA Server receives the information to be inspected, and synchronously returns the information to be inspected to a nodeb inspection terminal in a polling manner, and requests to trigger inspection, including:
s301, the QA Server acquires the information to be inspected according to the inspection access;
s302, based on a preset polling mode, the QA Server synchronously requests a request signal for triggering inspection to the NodeJS Server;
s303, the NodeJS Server forwards the request signal for triggering inspection to the NodeJS inspection terminal.
5. The method of claim 1, wherein in step S400, the node js inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QA Server, including:
s401, the NodeJS routing inspection terminal receives an inspection trigger request;
s402, calling an access port of an automatic test tool configured in the NodeJS inspection terminal according to the inspection trigger request, and accessing a headless browser;
s403, loading the page in the information to be patrolled and examined through the headless browser, and monitoring callback of the page state: and when the callback of the page state is monitored, returning callback page information to the QA Server, and triggering the inspection to finish.
6. The B/S architecture page inspection method according to claim 5, wherein in step S403, the returning callback page information to the QA Server comprises:
s4031, acquiring a page inspection result in callback;
s4032, the page inspection result is returned to the NodeJS inspection end in a callback mode through the automatic testing tool;
s4033, the NodeJS inspection terminal receives the page inspection result, returns the page inspection result to the NodeJS Server, and returns the page inspection result to the QA Server through the NodeJS Server.
7. The method for inspecting a B/S architecture page according to claim 6, wherein in step S400, the nodeb inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QA Server, and further comprising:
s410, the QA Server receives the page inspection result and stores the result in a Mysql database;
s420, the QA Server judges whether the page inspection result is abnormal or not according to the configured software page configuration information and outputs a judgment result;
s430, sending the judging result to the user.
8. The method for inspecting a B/S architecture page according to claim 7, wherein in step S400, the nodeb inspection terminal receives an inspection trigger request, performs page inspection on the information to be inspected, and feeds back a page inspection result to the QA Server, and further comprising:
s411, establishing communication connection between the QA Server and the VUE;
s421, the software page configuration information and the judging result are sent to the VUE end, and visual display is carried out through the VUE end.
9. An apparatus for implementing the B/S architecture page inspection method of any one of claims 1-8, comprising:
the configuration module is used for acquiring the software page configuration information required to be inspected in the B/S architecture and configuring the software page configuration information on the QA Server;
the patrol access module is used for splicing the information to be patrol according to the software page configuration information and initiating patrol access to the QA Server;
the polling request module is used for receiving the information to be polled by the QA Server, synchronously returning the information to be polled to the NodeJS polling terminal in a polling mode, and requesting to trigger polling;
and the page patrol module is used for receiving the patrol trigger request by the NodeJS patrol terminal, carrying out page patrol on the information to be patrol, and feeding back a page patrol result to the QA Server.
10. A page inspection system, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor is configured to implement the B/S architecture page patrol method of any one of claims 1 to 8 when executing the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210740348.9A CN115174343B (en) | 2022-06-27 | 2022-06-27 | B/S architecture page inspection method and device and page inspection system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210740348.9A CN115174343B (en) | 2022-06-27 | 2022-06-27 | B/S architecture page inspection method and device and page inspection system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115174343A CN115174343A (en) | 2022-10-11 |
| CN115174343B true CN115174343B (en) | 2023-05-16 |
Family
ID=83488183
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210740348.9A Active CN115174343B (en) | 2022-06-27 | 2022-06-27 | B/S architecture page inspection method and device and page inspection system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115174343B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113313851A (en) * | 2021-04-15 | 2021-08-27 | 浙江大华技术股份有限公司 | Equipment inspection method, device, system, electronic device and storage medium |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103544739B (en) * | 2013-10-25 | 2015-12-30 | 国电南瑞科技股份有限公司 | Based on the method for inspecting of the visual subway equipment routing inspection management system of B/S framework |
| JP6743657B2 (en) * | 2016-11-04 | 2020-08-19 | 横河電機株式会社 | Patrol inspection system, patrol inspection device, patrol inspection method, program, and recording medium |
| CN110019203B (en) * | 2017-10-19 | 2022-10-11 | 国网辽宁省电力有限公司沈阳供电公司 | Automatic server inspection system and method based on knowledge base |
| US10999075B2 (en) * | 2019-06-17 | 2021-05-04 | Advanced New Technologies Co., Ltd. | Blockchain-based patrol inspection proof storage method, apparatus, and electronic device |
| CN111209166B (en) * | 2020-01-06 | 2023-06-13 | 深圳市同洲电子股份有限公司 | Automatic inspection system for B/S architecture service system |
| CN111835582B (en) * | 2020-06-19 | 2022-04-15 | 深圳奇迹智慧网络有限公司 | Configuration method and device of Internet of things inspection equipment and computer equipment |
| CN114298343A (en) * | 2021-12-28 | 2022-04-08 | 中电金信软件有限公司 | Management method and device for equipment inspection process, electronic equipment and storage medium |
| CN114594984A (en) * | 2022-03-03 | 2022-06-07 | 未鲲(上海)科技服务有限公司 | Inspection method, inspection device, computer equipment and storage medium |
-
2022
- 2022-06-27 CN CN202210740348.9A patent/CN115174343B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113313851A (en) * | 2021-04-15 | 2021-08-27 | 浙江大华技术股份有限公司 | Equipment inspection method, device, system, electronic device and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 李征明 ; 许童羽 ; 王立地 ; 丛伟波 ; .基于J2EE的电力线路巡检后台管理信息***.农业网络信息.2009,(第01期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115174343A (en) | 2022-10-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107608901B (en) | Jmeter-based testing method and device, storage medium and electronic equipment | |
| CN109995612B (en) | Service inspection method and device and electronic equipment | |
| CN110784374A (en) | Method, device, equipment and system for monitoring operation state of service system | |
| CN110659198A (en) | Application program test case execution method and device and software test system | |
| CN115643112B (en) | Safety protection capability testing method and device | |
| CN110221948A (en) | Test script generation method, device, computer installation and storage medium | |
| CN112732499A (en) | Test method and device based on micro-service architecture and computer system | |
| CN108200132A (en) | Resource acquiring method, device, equipment and computer readable storage medium | |
| CN107360036B (en) | Network fault positioning method, terminal and server | |
| CN110618853B (en) | Detection method, device and equipment for zombie container | |
| CN117608825A (en) | Resource management method based on multi-cloud management platform and related equipment | |
| CN111526038A (en) | Service request distribution method and device, computer equipment and readable storage medium | |
| CN109165147A (en) | Log print control program, device, system, back-end server and headend equipment | |
| CN115174343B (en) | B/S architecture page inspection method and device and page inspection system | |
| CN112068935A (en) | Method, device and equipment for monitoring deployment of kubernets program | |
| CN112583660B (en) | Main domain and standby domain test comparison method, device and system of recommendation platform | |
| CN111737129A (en) | Service control method, service control device, computer readable medium and electronic equipment | |
| CN106850245B (en) | Diagnostic test message processing method and device | |
| CN110401719A (en) | Method, apparatus, system and the storage medium of web terminal upload data | |
| CN110618943A (en) | Security service test method and device, electronic equipment and readable storage medium | |
| CN111324846B (en) | Information processing method, information processing device, electronic equipment and computer readable storage medium | |
| CN112486755B (en) | Server detection method, detection device, electronic equipment and storage medium | |
| JP5364932B2 (en) | Timeout monitoring system and timeout monitoring program | |
| CN113515403B (en) | Micro-service state checking method, computer device and storage medium | |
| CN117608891A (en) | Online accident investigation method and device, electronic equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: B/S architecture page inspection method, device, and page inspection system Effective date of registration: 20230718 Granted publication date: 20230516 Pledgee: Hangzhou United Rural Commercial Bank Co.,Ltd. Gudang Sub branch Pledgor: Hangzhou Diji Intelligent Technology Co.,Ltd. Registration number: Y2023980048826 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |