WO2018223717A1

WO2018223717A1 - Webpage front-end testing method, device, system, apparatus and readable storage medium

Info

Publication number: WO2018223717A1
Application number: PCT/CN2018/074486
Authority: WO
Inventors: 朱子剑; 陈少杰; 张文明
Original assignee: 武汉斗鱼网络科技有限公司
Priority date: 2017-06-08
Filing date: 2018-01-29
Publication date: 2018-12-13
Also published as: CN107256195B; CN107256195A

Abstract

The present invention provides a webpage front-end testing method, device, system, apparatus, and readable storage medium related to the technical field of Internet technology. The method is applied to a client and a webpage server communicatively connected to each other, and comprises: the client generating access request data in response to a test instruction, wherein the access request data comprises a test identifier used to identify a function to be tested that requires testing; sending the access request data to the webpage server; the webpage server acquiring, according to the test identifier, a test case corresponding to the function to be tested; acquiring, according to the access request data, data to be fed back, wherein the data to be fed back comprises a file to be tested corresponding to the function to be tested; generating response data according to the test case and the data to be fed back; sending the response data to the client; and the client executing the response data to acquire a test result. The present invention reduces coupling of response data, enhances testing accuracy and efficiency, and reduces time and labor costs of testing.

Description

Web front end test method, device, system, device and readable storage medium

Cross-reference to related applications

The present application claims priority to Chinese Patent Application No. JP-A No. No. No. No. No. No. No. No. No. No.

Technical field

The present invention relates to the field of Internet technologies, and in particular, to a web page front end testing method, apparatus, system, device, and readable storage medium.

Background technique

The web front end is an important branch of Internet technology and plays an extremely important role in interface display and user interaction. With the development of the Internet, more and more back-end business logic is gradually front-end, making the front-end business logic increasingly complex.

In the past few years, the front-end technology has been changing with each passing day. As a result, various unit testing programs have emerged in the front-end field, such as jasmine and mocha. These unit test schemes guarantee the quality of the front-end code to a certain extent. However, there are test cases for business functions directly coupled to the business code. The high degree of coupling of the front-end business code makes the maintenance of the front-end unit test cases extremely complicated.

Summary of the invention

It is an object of the present invention to provide a web page front end testing method, apparatus, system, device and readable storage medium for improving the above problems.

Another object of the present invention is to provide a web page front end testing device for improving the above problems.

In order to achieve the above object, the technical solution adopted by the embodiment of the present invention is as follows:

The embodiment of the invention provides a webpage front end testing method. The method is applied to a client and a web server that are in communication with each other. The method includes: the client responding to a test instruction, generating access request data, wherein the access request data includes a test identifier for identifying a function to be tested that needs to be tested; and the client sends the access request data The web server is configured to obtain a test case corresponding to the function to be tested according to the test identifier; the web server obtains data to be fed back according to the access request data, wherein the data to be fed back includes Determining a file to be tested corresponding to the test function; the web server generates response data according to the test case and the data to be fed back; the web server sends the response data to the client; the client executes the Respond to the data to get the test results.

Optionally, the step of generating response data according to the test case and the data to be fed back includes:

The web server dynamically injects the test case into the data to be fed back to generate response data.

Optionally, the test identifier includes a file identifier to be tested and a function identifier to be tested, and the step of the web server dynamically injecting the test case into the data to be fed back includes:

The web server obtains the corresponding test file from the to-be-reviewed data according to the to-be-tested file identifier; the web server injects the test case according to a business rule corresponding to the to-be-tested function identifier Tell the test file.

Optionally, the step of the client responding to the test instruction and generating the access request data includes:

Responding to the test instruction, the client obtains service information to be tested corresponding to the test instruction;

The client generates a test identifier corresponding to the function to be tested according to the service information to be tested;

The client obtains a webpage address corresponding to the webpage server;

The client generates the access request data according to the webpage address and the test identifier.

Optionally, the step of the client sending the access request data to the web server includes:

Determining, according to the webpage address included in the access request data, a webpage server corresponding to the webpage address;

Establishing a communication connection of the web server corresponding to the webpage address;

Sending the test identifier included in the access request data to the web server.

Optionally, the step of the client executing the response data to obtain a test result includes:

The client loads a webpage corresponding to the response data according to the response data;

The client starts a function to be tested corresponding to a webpage corresponding to the response data;

The client runs the to-be-tested file that has been injected with the test case corresponding to the function to be tested, and obtains the test result in the current test environment.

Optionally, the method further includes:

The client sends the test result to the web server;

The web server displays the test results. The embodiment of the present invention further provides a webpage front-end testing method, which is applied to a client that is in communication with a web server, the method comprising: generating access request data in response to a test instruction, wherein the access request data includes being configured to be configured Identify the test identifier of the function to be tested that needs to be tested;

Transmitting the access request data to the webpage server, so that the webpage server obtains a test case corresponding to the function to be tested according to the test identifier, so that the webpage server obtains the feedback to be fed according to the access request data. Data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; and the test data of the web server and the data to be fed back are generated to generate response data;

Receiving response data generated by the web server;

The response data is executed to obtain test results.

The client obtains a webpage address corresponding to the webpage server;

Optionally, the method further includes:

The client sends the test result to the web server;

The web server displays the test results.

The embodiment of the invention further provides a webpage front end testing method. The method is applied to a web server that is in communication with a client, the method comprising: receiving access request data sent by the client, wherein the access request data includes a test identifier for identifying a function to be tested that needs to be tested Obtaining a test case corresponding to the function to be tested according to the test identifier; obtaining data to be fed back according to the access request data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; Testing the use case and the data to be fed back, generating response data; sending the response data to the client to obtain a test result fed back by the client, wherein the test result is executed by the client After generation.

The test case is dynamically injected into the data to be fed back to generate the response data.

Optionally, the test identifier includes a file identifier to be tested and a function identifier to be tested, and the step of dynamically injecting the test case into the data to be fed back includes:

Obtaining, according to the to-be-tested file identifier, the corresponding file to be tested according to the to-be-tested data;

And loading the test case into the file to be tested according to a business rule corresponding to the function identifier to be tested.

Optionally, the method further includes:

The test results are presented.

The embodiment of the present invention further provides a webpage front-end testing device, which is applied to a client that is in communication with a web server, and the device includes: an access request data generating module configured to generate access request data in response to the test instruction, wherein the The access request data includes a test identifier configured to identify a function to be tested that needs to be tested; the access request data sending module is configured to send the access request data to the web server such that the web server is according to the test according to the test Identifying a test case corresponding to the function to be tested, so that the web server obtains data to be fed back according to the access request data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; And the response data receiving module is configured to receive the response data generated by the web server, and the execution module is configured to execute the response data to obtain a test result. The embodiment of the invention further provides a webpage front end testing device. The device is applied to a webpage server that is in communication with a client, and the device includes: a receiving module, an obtaining module, a generating module, and a sending module. The receiving module is configured to receive the access request data sent by the client, where the access request data includes a test identifier for identifying a function to be tested that needs to be tested. The obtaining module is configured to obtain a test case corresponding to the function to be tested according to the test identifier, and is further configured to obtain data to be fed back according to the access request data, where the data to be fed back includes a function corresponding to the function to be tested The file to be tested. And a generating module, configured to generate response data according to the test case and the data to be fed back. And a sending module, configured to send the response data to the client to obtain a test result fed back by the client, where the test result is generated by the client executing the response data.

The embodiment of the present invention further provides a webpage front-end testing system, including a client and a webpage server connected to each other, wherein: the client is configured to generate access request data in response to a test instruction, wherein the access request data includes a test identifier configured to identify a function to be tested that needs to be tested; the client configured to send the access request data to the web server; the web server configured to obtain and test a function according to the test identifier Corresponding test case; the web server is configured to obtain data to be fed back according to the access request data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; the web server is configured according to the Testing the use case and the data to be fed back to generate response data; the web server is configured to send the response data to the client; the client is configured to execute the response data to obtain a test result.

An embodiment of the present invention further provides an electronic device, where the electronic device includes a memory and a processor, the memory is configured to store executable program code, and the processor is configured to read an executable program stored in the memory. The code causes the electronic device to perform the above web page front end testing method as the client and/or web server.

The embodiment of the present invention further provides a readable storage medium, where the readable storage medium stores instructions, when the instruction is run on a computer, causing the computer to execute the webpage front end as the client and the web server testing method.

Compared with the prior art, the present invention provides a web page front end testing method, apparatus, system, device and readable storage medium. It can be applied to clients and web servers that are connected to each other. The method includes the client responding to a test instruction to generate access request data, wherein the access request data includes a test identification for identifying a function to be tested that requires testing. The web server obtains a test case corresponding to the function to be tested according to the test identifier. Accurate and fast find the corresponding test case through efficiency. Acquiring the data to be tested according to the access request data, wherein the data to be fed includes a file to be tested corresponding to the function to be tested; and generating response data according to the test case and the data to be fed back. Thereby reducing the high coupling of the data to be fed back and the test case, improving the maintainability of the test case and the test efficiency.

The above described objects, features and advantages of the present invention will become more apparent from the aspects of the appended claims.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It should be understood that the following drawings show only certain embodiments of the present invention, and therefore It should be seen as a limitation on the scope, and those skilled in the art can obtain other related drawings according to these drawings without any creative work.

FIG. 1 is a schematic diagram showing an application environment of a preferred embodiment of the present invention.

2 is a block diagram of a web server according to a preferred embodiment of the present invention.

FIG. 3 is a flowchart of a webpage front end testing method according to a first embodiment of the present invention.

4 is a flow chart of the sub-steps of step S101 in FIG.

FIG. 5 is a flow chart of the sub-steps of step S105 in FIG.

FIG. 6 is a flowchart of a method for testing a webpage front end according to a second embodiment of the present invention.

FIG. 7 is a block diagram of a webpage front end testing apparatus according to a third embodiment of the present invention.

Icons: 400-user terminal; 401-client; 100-web server; 300-network; 111-memory; 112-processor; 113-communication unit; 200-web front-end test device; 201-receive module; Module; 203-generating module; 204-sending module.

detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The components of the embodiments of the invention, which are generally described and illustrated in the figures herein, may be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the invention in the claims All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

It should be noted that similar reference numerals and letters indicate similar items in the following figures, and therefore, once an item is defined in a drawing, it is not necessary to further define and explain it in the subsequent drawings. Also, in the description of the present invention, the terms "first", "second" and the like are used merely to distinguish a description, and are not to be construed as indicating or implying a relative importance.

The following embodiments of the present invention can be applied to the environment shown in FIG. 1 without any particular description. As shown in FIG. 1, the user terminal 400 and the web server 100 are located in the network 300, and the network 300 includes a wireless network or a wired network. Through the network 300, the user terminal 400 performs data interaction with the web server 100. The web server 100 can be a server or a plurality of servers that perform different tasks.

In the embodiment of the present invention, the user terminal 400 may be a mobile terminal device, and may include, for example, a smart phone, a tablet computer, an e-book reader, a laptop portable computer, a car-mounted computer, a wearable mobile terminal, and the like. The client terminal 401 is installed in the user terminal 400, and corresponds to the web server 100 to provide services for the user. The client 401 is in communication with the web server 100. The client 401 can be a browser or other APP that can access the web server 100.

2 is a block schematic diagram of the web server 100 of FIG. 1. The web server 100 includes a web page front end testing device 200, a memory 111, a processor 112, and a communication unit 113.

The components of the memory 111, the processor 112, and the communication unit 113 are electrically connected directly or indirectly to each other to implement data transmission or interaction. For example, the components can be electrically connected to one another via one or more communication buses or signal lines. The web page front end testing device 200 includes at least one software function module that can be stored in the memory 111 or in an operating system (OS) of the web server 100 in the form of software or firmware. The processor 112 is configured to execute an executable module stored in the memory 111, such as a software function module, a computer program, and the like included in the webpage front end testing device 200.

The memory 111 can be, but not limited to, a random access memory (RAM), a read only memory (ROM), and a programmable read-only memory (PROM). Erasable Programmable Read-Only Memory (EPROM), Electric Erasable Programmable Read-Only Memory (EEPROM), and a storage system that implements data persistence. The memory 111 is used to store programs or data. The communication unit 113 is configured to establish a communication connection between the web server 100 and other communication terminals through the network 300, and is used to send and receive data through the network 300.

It should be understood that the structure shown in FIG. 1 is only a schematic structural diagram of the web server 100, and the web server 100 may further include more or less components than those shown in FIG. 1, or have different from that shown in FIG. Configuration. The components shown in Figure 1 can be implemented in hardware, software, or a combination thereof.

Please refer to FIG. 3 , which is a web page front end testing method provided by a preferred embodiment of the present invention, which is applied to a client 401 and a web server 100 that are connected to each other. The webpage front end testing method includes the following steps:

Step S101, the client 401 generates access request data in response to the test instruction.

In this embodiment, the client 401 acquires data of the loaded webpage and data of various front-end web services from the web server 100 by accessing the request data. The access request data includes a test identifier configured to identify a function to be tested that needs to be tested and a file to be tested corresponding to the function to be tested. It should be noted that the correspondence between the function to be tested and the file to be tested can be preset. The access request data further includes a webpage address corresponding to the webpage server 100 (for example, the webpage address corresponding to the Baidu webpage server 100 is www.baidu.com). The function to be tested may be a function module corresponding to the front-end website service of the webpage. The file to be tested may be a script file that implements the function to be tested, and may be, for example, a front-end javascript script file. As shown in FIG. 4, step S101 includes the following sub-steps:

Sub-step S1011, the client 401 obtains the service information to be tested corresponding to the test instruction in response to the test instruction.

In this embodiment, the test command may be an instruction to trigger testing of one or more front end web services of the web page. The test command may be triggered by the tester via the user terminal 400 or may be triggered according to pre-set rules. The service information to be tested may be service information of a function to be tested corresponding to one or more front-end website services that need to be tested. The service information to be tested includes identification information of the function to be tested and a business rule for implementing the function to be tested. The correspondence between the front-end website service and the service information to be tested may be preset to the user terminal 400.

In sub-step S1012, the client 401 generates a test identifier corresponding to the function to be tested according to the service information to be tested.

In this embodiment, the test identifier includes a file identifier to be tested and a function identifier to be tested. The file identifier to be tested may be the name of the file to be tested. For example, the file name to be tested may be demo.js; the function identifier to be tested may be the name of the function to be tested. For example, the name of the function to be tested may be DemoController.demoFunction. The client 401 generates a to-be-tested file identifier and a to-be-tested function identifier according to the service information to be tested.

Sub-step S1013, the client 401 acquires a webpage address corresponding to the webpage server 100.

Sub-step S1014, the client 401 generates the access request data according to the webpage address and the test identifier.

In this embodiment, the client 401 accesses the web server 100 through the webpage address to obtain data of loading the webpage and data of various front-end web services, for example, multiple front-end JS script files and front ends corresponding to each front-end web service. CSS style files, jpg, png and other image resource files, which can be acquired from the web server 100 at the same time. The test identifier is configured to identify a function to be tested and a file to be tested that need to be tested by accessing the request data. The access request data may include an access address including a webpage address and a test identifier. For example, the access address can be baidu.com? testFile=demo.js&testModule=DemoController.demoFunction.

In step S102, the client 401 sends the access request data to the web server 100.

In this embodiment, the client 401 can automatically send to the web server 100 after generating the access request data. Specifically, the access request data is transmitted to the web server 100 through the network 300. The flow proceeds to step S103.

Step S103: The web server 100 obtains a test case corresponding to the function to be tested according to the test identifier.

In this embodiment, after receiving the access request data, the web server 100 parses the test identifier in the access request data to obtain the file identifier to be tested and the function identifier to be tested in the test identifier. A Test Case is a set of test inputs, execution conditions, and expected results that are compiled for a particular purpose. There is a corresponding test case for each function to be tested. The correspondence between the test case and the test case and the function to be tested may be pre-stored in the web server 100. Therefore, after the function identifier to be tested is parsed from the test identifier, the test case corresponding to the function to be tested is obtained from the pre-stored test case by using the correspondence between the test case and the function to be tested according to the function identifier to be tested. In this way, by accurately establishing the correspondence between the function to be tested and the test case, and determining the corresponding test case by the function identifier to be tested, the accuracy and efficiency of the test case corresponding to the function to be tested can be improved.

In step S104, the web server 100 obtains data to be fed back according to the access request data, where the data to be fed back includes a file to be tested corresponding to the function to be tested.

In this embodiment, the data to be fed back may be feedback to the client 401 for the client 401 to load data of the webpage and data for implementing various front-end web services. The data to be fed back may include, but is not limited to, a file to be tested, a script file corresponding to a function not to be tested, a front end CSS style file, a picture resource file such as jpg, png, and the like.

Step S105, the web server 100 generates response data according to the test case and the data to be fed back.

In this embodiment, the web server 100 dynamically injects the acquired test case into the to-be-feedback data to generate response data. The test case is separated from all the script files. In the test, the test case corresponding to the function to be tested is dynamically injected into the data to be fed back, which effectively reduces the coupling degree of the response data, so that the response data is optimized and the client 401 is lightened. The burden of loading response data. At the same time, by dynamically injecting test cases to reduce or even deviate from the test case's dependence on the operating environment, or by dynamically injecting test cases, the test cases can be separated from the operating environment, and test cases can be introduced in any environment, greatly improving the test case maintainability. And test efficiency. Optionally, as shown in FIG. 5, step S105 includes the following sub-steps:

In the sub-step S1051, the web server 100 obtains the corresponding file to be tested from the to-be-feedback data according to the to-be-tested file identifier.

In this embodiment, the data to be fed includes a script file for implementing each front-end website service, and the file to be tested is found by using the file identifier to be tested from all the script files. It should be noted that even if only one front-end website service is tested, the client 401 needs to access the web server 100 first, and the web server 100 accesses multiple front-end JS script files corresponding to multiple front-end website services.

Sub-step S1052, the web server 100 injects the test case into the file to be tested according to a business rule corresponding to the function identifier to be tested.

In this embodiment, the business rule may be the business logic in the website service implementation process. For example, the business rule of the search service is to display the search interface first, then receive the search content, then search, and finally display the search result. The injection test case can be a script file that adds the test case to the file to be tested. The test case is injected into the file to be tested according to the business rule, and the location of the test case is selected in the file to be tested according to the business rule. For example, when testing the search function, according to the business rules of the search service, the test case of the test search function is injected into the script file that implements the display search interface, so that the file to be tested is executed, when the search interface is displayed, A test case that performs a test search function. This reduces or even eliminates the dependency of test cases on the test environment.

In this embodiment, the file to be tested in which the test case is not injected in the data to be tested may be replaced with the file to be tested that has been injected into the test case to generate response data.

Step S106, the web server 100 sends the response data to the client 401.

In this embodiment, after generating the response data, the web server 100 may send the response data to the client 401 through the network 300.

Step S107, the client 401 executes the response data to obtain a test result.

In this embodiment, the client 401 loads the webpage according to the response data. Start the function to be tested. The test file to be injected with the test case corresponding to the function to be tested may be run to obtain the test result in the current test environment. Alternatively, you can use JavaScript Object Notation for test result collection.

In step S108, the client 401 sends the test result to the web server 100.

In the present embodiment, the collected test results are sent to the web server 100. For example, the test result in JSON format is sent to the web server 100 via ajax.

In step S109, the web server 100 displays the test result.

In this embodiment, the received test result is parsed. Focus on the test results corresponding to different website services. In order to process the test results of different website services, for example, when the test results show that there is a logical problem in the business logic of a website business, the business logic sequence of the website is also adjusted. It can provide web developers with unified monitoring from micro (single front-end business functions) to macro (full-service business functions at the front end of the website), greatly improving business functions and stability and maintainability of the entire website.

The embodiment of the present invention further provides a webpage front-end testing method, which is applied to a client that is in communication with a web server, and the method includes:

Step S201: Generate access request data in response to the test instruction, wherein the access request data includes a test identifier configured to identify a function to be tested that needs to be tested. For details, refer to the description of step S101.

Step S202: Send the access request data to the webpage server, so that the webpage server obtains a test case corresponding to the function to be tested according to the test identifier, so that the webpage server according to the access request data. Obtaining data to be fed, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; and the test data of the web server and the data to be fed back are generated to generate response data. For details, refer to the description of step S102 to step S105.

Step S203: Receive response data generated by the web server. In this embodiment, after generating the response data, the web server 100 may send the response data to the client 401 through the network 300.

Step S204, executing the response data to obtain a test result. For details, refer to the description of step S107.

In a specific implementation manner, the step of the client responding to the test instruction to generate the access request data includes: the client responding to the test instruction, obtaining service information to be tested corresponding to the test instruction; the client And generating, by the terminal, a test identifier corresponding to the function to be tested according to the service information to be tested; the client acquiring a webpage address corresponding to the webpage server; and the client generating the webpage address and the test identifier according to the webpage address and the test identifier The access request data. For details, refer to the description of step S1011 to step S1013.

The step of the client sending the access request data to the webpage server includes: determining, according to the webpage address included in the access request data, a webpage server corresponding to the webpage address; and establishing a webpage corresponding to the webpage address a communication connection of the server; transmitting the test identifier included in the access request data to the web server.

The step of the client executing the response data to obtain a test result includes: the client loading a webpage corresponding to the response data according to the response data; and the client starting corresponding to the response data The webpage corresponds to the function to be tested; the client runs the to-be-tested file that has been injected with the test case corresponding to the function to be tested, and obtains the test result in the current test environment.

After the client obtains the test result, the client may also send the test result to the web server. The web server displays the test results.

The client can implement the test of the front end of the webpage, and can provide web developers with unified monitoring from micro (single front-end business function) to macro (the overall business function of the front-end of the website), greatly improving the business function and the stability of the entire website. Maintainability.

As shown in FIG. 6 , a method for testing a web page front end according to a preferred embodiment of the present invention is applied to a web server 100. The web page front end testing method includes the following steps:

Step S201: Receive access request data sent by the client 401, where the access request data includes a test identifier for identifying a function to be tested that needs to be tested.

In this embodiment, the access request data is parsed, and the test identifier of the function to be tested that needs to be tested is obtained from the access request data. The test identifier includes the file identifier to be tested and the function identifier to be tested. The file identifier to be tested may be the name of the file to be tested. For example, the file name to be tested may be demo.js; the function identifier to be tested may be the name of the function to be tested. For example, the name of the function to be tested may be DemoController.demoFunction. The client 401 generates a to-be-tested file identifier and a function identifier to be tested according to the service information to be tested.

Step S202: Obtain a test case corresponding to the function to be tested according to the test identifier.

In this embodiment, the correspondence between the test case and the test case and the function to be tested may be stored in the web server 100 in advance. Therefore, after the function identifier to be tested is parsed from the test identifier, the corresponding test relationship between the test case and the function to be tested is used to obtain a test corresponding to the function to be tested from the plurality of test cases stored in advance according to the function identifier to be tested. Example. This improves the accuracy and efficiency of finding test cases corresponding to the function to be tested.

Step S203: Acquire data to be fed back according to the access request data, where the data to be fed back includes a file to be tested corresponding to the function to be tested.

Step S204: Generate response data according to the test case and the data to be fed back.

In this embodiment, the web server 100 dynamically injects the acquired test case into the to-be-feedback data to generate response data. The test case is separated from all the script files. In the test, the test case corresponding to the function to be tested is dynamically injected into the data to be fed back, which effectively reduces the coupling degree of the response data, so that the response data is optimized and the client 401 is lightened. The burden of loading response data. At the same time, the dynamic injection test cases reduce or even deviate from the test case's dependence on the operating environment, and realize the introduction of test cases in any environment, which greatly improves the test case maintainability and test efficiency. Optionally, the method of step S204 may be: obtaining, according to the to-be-tested file identifier, the corresponding file to be tested according to the to-be-tested data identifier; and performing the test according to a service rule corresponding to the to-be-tested function identifier. The use case injects the file to be tested.

Step S205: Send the response data to the client 401 to obtain a test result fed back by the client 401, wherein the test result is generated by the client 401 executing the response data.

Step S206, displaying the test result.

In this embodiment, the received test result is parsed. Focus on the test results corresponding to different website services. In order to process the test results of different website services, for example, when the test result shows that there is a logical problem in the business logic of a website business, the business logic sequence of the website is adjusted. It can provide web developers with unified monitoring from micro (single front-end business functions) to macro (full-service business functions at the front end of the website), greatly improving business functions and stability and maintainability of the entire website.

Please refer to FIG. 7 , which is a webpage front end testing apparatus 200 applied to the web server 100 according to a preferred embodiment of the present invention. The web page front end testing device 200 includes a receiving module 201, an obtaining module 202, a generating module 203, and a sending module 204.

The receiving module 201 is configured to receive the access request data sent by the client 401, where the access request data includes a test identifier for identifying a function to be tested that needs to be tested.

In the embodiment of the present invention, step S201 can be performed by the receiving module 201.

The obtaining module 202 is configured to obtain a test case corresponding to the function to be tested according to the test identifier, and is further configured to obtain data to be fed back according to the access request data, where the data to be fed back includes the function to be tested Corresponding files to be tested.

In this embodiment, step S202, step S203, step S103, step S104 may be performed by the obtaining module 202.

The generating module 203 is configured to generate response data according to the test case and the data to be fed back.

In this embodiment, step S204 and step S105 may be performed by the generating module 203. It should be noted that the sub-step S1051 and the sub-step S1051 may also be executed by the generating module 203. The manner in which the generating module 203 performs the step S204 or the step S105 may be: dynamically injecting the acquired test case into the data to be fed back to generate response data. Optionally, the dynamic injection of the test case is performed by: obtaining, according to the to-be-tested file identifier, the corresponding file to be tested from the to-be-reviewed data, and then, according to the service corresponding to the function identifier to be tested. The rule injects the test case into the file to be tested.

The sending module 204 is configured to send the response data to the client 401 to obtain a test result fed back by the client 401, where the test result is generated by the client 401 executing the response data. .

In this embodiment, step S205 and step S106 may be performed by the transmitting module 204.

In this embodiment, the webpage front end testing apparatus 200 further includes a display module, and the display module is configured to display the test result. Optionally, step S109 and step S206 may be performed by a presentation module.

In summary, a webpage front-end testing method, apparatus, system, device, and readable storage medium are provided by embodiments of the present invention. The method is applied to a client and a web server that are in communication with each other. The method includes: the client responds to the test instruction, and generates access request data, where the access request data includes a test identifier for identifying a function to be tested that needs to be tested; and the access request data is sent to the web server; The web server obtains a test case corresponding to the function to be tested according to the test identifier, and obtains data to be fed back according to the access request data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; And generating response data according to the test case and the data to be fed back; sending the response data to the client; and the client executing the response data to obtain a test result. Reduce the coupling degree of the client load data during the test, reduce the dependence of the test case on the test environment, and improve the test efficiency. Test cases are also easier to manage and maintain. In turn, the labor cost and time cost of the web front-end testing work are reduced.

The embodiment of the present invention further provides a webpage front-end testing system, including a client and a webpage server connected to each other, wherein: the client is configured to generate access request data in response to a test instruction, wherein the access request data includes a test identifier configured to identify a function to be tested that needs to be tested; the client configured to send the access request data to the web server; the web server configured to obtain and test a function according to the test identifier Corresponding test case; the web server is configured to obtain data to be fed back according to the access request data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; the web server is configured according to the Testing the use case and the data to be fed back to generate response data; the web server is configured to send the response data to the client; the client is configured to execute the response data to obtain a test result. For details, refer to the description of the above method embodiments.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Industrial applicability

The webpage front-end testing method, device, system, device and readable storage medium provided by the embodiment of the invention reduce the coupling degree of the client loading data during the testing process, reduce the dependence of the test case on the testing environment, and improve the testing efficiency. Test cases are also easier to manage and maintain. In turn, the labor cost and time cost of the web front-end testing work are reduced.

Claims

A method for testing a web page front end, wherein the method is applied to a client and a web server connected to each other, the method comprising:

The client generates access request data in response to the test instruction, wherein the access request data includes a test identifier configured to identify a function to be tested that needs to be tested;

The client sends the access request data to the web server;

The web server obtains a test case corresponding to the function to be tested according to the test identifier;

The web server obtains data to be fed back according to the access request data, where the data to be fed back includes a file to be tested corresponding to the function to be tested;

The web server generates response data according to the test case and the data to be fed back;

Sending, by the web server, the response data to the client;

The client executes the response data to obtain a test result.
The webpage front-end testing method according to claim 1, wherein the step of generating response data according to the test case and the data to be fed back comprises:

The web server dynamically injects the test case into the data to be fed back to generate response data.
The webpage front-end testing method according to claim 2, wherein the test identifier comprises a file identifier to be tested and a function identifier to be tested, and the web server dynamically injects the test case into the data to be fed back include:

The web server obtains the corresponding test file from the to-be-reviewed data according to the to-be-tested file identifier; the web server injects the test case according to a business rule corresponding to the to-be-tested function identifier Tell the test file.
The method for testing a web page front end according to any one of claims 1 to 3, wherein the step of the client responding to the test instruction to generate the access request data comprises:

Responding to the test instruction, the client obtains service information to be tested corresponding to the test instruction;

The client generates a test identifier corresponding to the function to be tested according to the service information to be tested;

The client obtains a webpage address corresponding to the webpage server;

The client generates the access request data according to the webpage address and the test identifier.
The method for testing a web page front end according to any one of claims 1 to 4, wherein the step of the client transmitting the access request data to the web server comprises:

Determining, according to the webpage address included in the access request data, a webpage server corresponding to the webpage address;

Establishing a communication connection of the web server corresponding to the webpage address;

Sending the test identifier included in the access request data to the web server.
The method for testing a web page front end according to any one of claims 1 to 4, wherein the step of the client executing the response data to obtain a test result comprises:

The client loads a webpage corresponding to the response data according to the response data;

The client starts a function to be tested corresponding to a webpage corresponding to the response data;

The client runs the to-be-tested file that has been injected with the test case corresponding to the function to be tested, and obtains the test result in the current test environment.
The method for testing a web page front end according to any one of claims 1 to 6, wherein the method further comprises:

The client sends the test result to the web server;

The web server displays the test results.
A method for testing a web page front end, characterized in that it is applied to a client communicatively connected to a web server, the method comprising: generating access request data in response to a test instruction, wherein the access request data comprises being configured to identify that a test is required Test identification of the function to be tested;

Transmitting the access request data to the webpage server, so that the webpage server obtains a test case corresponding to the function to be tested according to the test identifier, so that the webpage server obtains the feedback to be fed according to the access request data. Data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; and the test data of the web server and the data to be fed back are generated to generate response data;

Receiving response data generated by the web server;

The response data is executed to obtain test results.
The webpage front-end testing method according to claim 8, wherein the step of the client responding to the test instruction to generate the access request data comprises:

Responding to the test instruction, the client obtains service information to be tested corresponding to the test instruction;

The client generates a test identifier corresponding to the function to be tested according to the service information to be tested;

The client obtains a webpage address corresponding to the webpage server;

The client generates the access request data according to the webpage address and the test identifier.
The method for testing a web page front end according to any one of claims 8 to 9, wherein the step of the client transmitting the access request data to the web server comprises:

Determining, according to the webpage address included in the access request data, a webpage server corresponding to the webpage address;

Establishing a communication connection of the web server corresponding to the webpage address;

Sending the test identifier included in the access request data to the web server.
The method for testing a web page front end according to any one of claims 8 to 9, wherein the step of the client executing the response data to obtain a test result comprises:

The client loads a webpage corresponding to the response data according to the response data;

The client starts a function to be tested corresponding to a webpage corresponding to the response data;

The client runs the to-be-tested file that has been injected with the test case corresponding to the function to be tested, and obtains the test result in the current test environment.
The method for testing a web page front end according to any one of claims 8 to 11, wherein the method further comprises:

The client sends the test result to the web server;

The web server displays the test results.
A method for testing a web page front end, wherein the method is applied to a web server connected to a client, the method comprising:

Receiving access request data sent by the client, where the access request data includes a test identifier for identifying a function to be tested that needs to be tested;

Obtaining a test case corresponding to the function to be tested according to the test identifier;

Obtaining data to be fed back according to the access request data, where the data to be fed back includes a file to be tested corresponding to the function to be tested;

Generating response data according to the test case and the data to be fed back;

Sending the response data to the client to obtain a test result fed back by the client, wherein the test result is generated by the client executing the response data.
The method for testing a web page front end according to claim 13, wherein the step of generating response data according to the test case and the data to be fed back comprises:

The test case is dynamically injected into the data to be fed back to generate the response data.
The webpage front-end testing method according to claim 14, wherein the test identifier comprises a file identifier to be tested and a function identifier to be tested, and the step of dynamically injecting the test case into the data to be fed back comprises:

Obtaining, according to the to-be-tested file identifier, the corresponding file to be tested according to the to-be-tested data;

And loading the test case into the file to be tested according to a business rule corresponding to the function identifier to be tested.
The method for testing a web page front end according to any one of claims 13 to 15, wherein the method further comprises:

The test results are presented.
A webpage front-end testing device is characterized in that it is applied to a client that is in communication with a web server, and the device comprises:

The access request data generating module is configured to generate access request data in response to the test instruction, wherein the access request data includes a test identifier configured to identify a function to be tested that needs to be tested;

The access request data sending module is configured to send the access request data to the webpage server, so that the webpage server obtains a test case corresponding to the function to be tested according to the test identifier, so that the webpage server Obtaining data to be tested according to the access request data, wherein the data to be fed back includes a file to be tested corresponding to the function to be tested; and the test case and the data to be fed back are generated by the web server to generate response data;

a response data receiving module configured to receive response data generated by the web server;

An execution module configured to execute the response data to obtain a test result.
A web page front end testing device, wherein the device is applied to a web server connected to a client, the device comprising:

a receiving module, configured to receive the access request data sent by the client, where the access request data includes a test identifier for identifying a function to be tested that needs to be tested;

Obtaining a module, configured to obtain a test case corresponding to the function to be tested according to the test identifier, and configured to obtain data to be fed back according to the access request data, where the data to be fed back includes a function corresponding to the function to be tested Test file to be tested;

Generating a module, configured to generate response data according to the test case and data to be fed back;

And a sending module, configured to send the response data to the client to obtain a test result fed back by the client, where the test result is generated by the client executing the response data.
A web page front end testing system, comprising: a client and a web server connected to each other, wherein:

The client is configured to generate access request data in response to the test instruction, wherein the access request data includes a test identifier configured to identify a function to be tested that requires testing;

The client is configured to send the access request data to the web server;

The web server is configured to obtain a test case corresponding to the function to be tested according to the test identifier;

The web server is configured to obtain data to be fed back according to the access request data, where the data to be fed back includes a file to be tested corresponding to the function to be tested;

The web server is configured to generate response data according to the test case and the data to be fed back;

The web server is configured to send the response data to the client;

The client is configured to execute the response data to obtain a test result.
An electronic device, comprising: a memory for storing executable program code, and a processor for reading executable program code stored in the memory to cause The electronic device performs the method of any one of claims 1-16 as the client and/or web server.
A readable storage medium, wherein the readable storage medium stores instructions therein, and when the instructions are run on a computer, causing the computer to perform as the client and/or web server as claimed in claims 1-16 Any of the methods described.