CN110515514B

CN110515514B - Data processing method, device and storage medium

Info

Publication number: CN110515514B
Application number: CN201910816748.1A
Authority: CN
Inventors: 李浩成; 张林悦
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-08-30
Filing date: 2019-08-30
Publication date: 2023-11-07
Anticipated expiration: 2039-08-30
Also published as: CN110515514A

Abstract

The embodiment of the application discloses a data processing method, a device and a storage medium, wherein the method comprises the following steps: responding to task confirmation operation triggered by the task creation interface, and acquiring filling parameter information filled in the task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from the address database; sending a screenshot instruction carrying N screenshot addresses and K machine type information to a service server so that the service server executes a target screenshot task based on the screenshot instruction; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address; receiving a screenshot result returned by the service server based on each sub-screenshot task; and the screenshot result comprises screenshot pictures of the target page corresponding to the screenshot address in the K machine type information respectively. By adopting the method and the device, the screenshot efficiency and the screenshot accuracy can be improved.

Description

Data processing method, device and storage medium

Technical Field

The present application relates to the field of internet technologies, and in particular, to a data processing method, apparatus, and storage medium.

Background

The existing web page screenshot mainly refers to a manual screenshot, for example, a developer can manually intercept the size of a specific page (i.e. a target page) through a button, a keyboard and the like.

For example, in the process of capturing the target page by the manual capturing method, for a certain terminal device, the size of the captured image needs to be repeatedly adjusted (for example, the captured area needs to be enlarged or reduced multiple times). Therefore, multiple shots must be taken separately for different terminal devices. However, due to the difference of manual screenshot, the size of the screenshot picture intercepted each time is difficult to be accurately matched with the size of the corresponding model by the manual screenshot mode, so that the accuracy of screenshot is reduced. In addition, if a large number of web pages need to be subjected to screenshot processing, the workload of developers is necessarily greatly increased, and a long manual screenshot time is required, so that the screenshot efficiency is reduced.

Disclosure of Invention

The embodiment of the application provides a data processing method, a data processing device and a storage medium, which can improve the accuracy of screenshot and the efficiency of screenshot.

An aspect of an embodiment of the present application provides a data processing method, where the method is applied to a terminal, and includes:

Responding to task confirmation operation triggered by aiming at a task creation interface, and acquiring filling parameter information filled in the task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer;

sending a screenshot instruction carrying the N screenshot addresses and the K machine types of information to a service server so that the service server executes a target screenshot task based on the screenshot instruction; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

receiving a screenshot result returned by the service server based on each sub-screenshot task; and the screenshot result comprises screenshot pictures of the target page corresponding to the screenshot address in the K machine type information respectively.

Wherein the method further comprises:

responding to task creation operation triggered by a historical task list, and jumping a display interface where the historical task list is positioned to a task creation interface to be filled;

and responding to filling operation aiming at the task creation interface to be filled, determining filling parameter information associated with the task creation interface to be filled, and determining the task creation interface to be filled carrying the filling parameter information as a task creation interface.

Wherein, in response to the filling operation for the task creation interface to be filled, determining filling parameter information associated with the task creation interface to be filled, determining the task creation interface to be filled carrying the filling parameter information as a task creation interface, including:

determining the task creation interface to be filled as a filling interface of a target screenshot task; the filling interface comprises a plurality of areas to be filled;

responding to filling operation aiming at each area to be filled in the filling interface, and acquiring filling parameter information filled in each area to be filled; the filling parameter information comprises at least one of the following parameter information: task name, N screenshot addresses, user identification information and K machine type information; the user identification information is used for simulating to log in a target page of each screenshot address when the business server executes the target screenshot task;

and determining a filling interface carrying the task name, the N screenshot addresses, the user identification information and the K machine type information as the task creation interface.

The response to the filling operation of each area to be filled in the filling interface obtains filling parameter information filled in each area to be filled, and the method comprises the following steps:

Responding to a first filling operation triggered by aiming at a first area in the filling interface, and acquiring a task name of the target screenshot task;

responding to a second filling operation triggered for a second area in the filling interface, acquiring an address database associated with the second area from a service server, and determining N screenshot addresses associated with the target screenshot task based on the addresses in the address database;

responding to a third filling operation triggered by aiming at a third area in the filling interface, and acquiring user identification information of a target page for simulating login of each screenshot address;

responding to a fourth filling operation triggered by aiming at a fourth area in the filling interface, and acquiring K machine type information from a plurality of machine type information contained in the fourth area;

and determining the task name, the N screenshot addresses, the user identification information and the K machine types as filling parameter information filled in the filling interface.

The responding to a second filling operation triggered by a second area in the filling interface obtains an address database associated with the second area from a service server, determines N screenshot addresses associated with the target screenshot task based on the addresses in the address database, and comprises the following steps:

Responding to a second filling operation triggered for a second area in the filling interface, acquiring an address database associated with the second area from a service server, and jumping the filling interface to a resource display interface for displaying the address of the address database;

responding to a label acquisition operation triggered by the resource display interface, acquiring target label information, and screening M addresses matched with the target label information from the addresses of the address database based on the target label information;

and responding to the selection operation aiming at the M addresses, acquiring N addresses from the M addresses as addresses to be shot, copying each address to be shot to a second area of the filling area, and obtaining N screenshot addresses associated with the target screenshot task.

Wherein the method further comprises:

adding the target screenshot task with the task name to the historical task list to obtain a target task list, and displaying the task state of the target screenshot task associated with the N screenshot addresses in the target task list;

and receiving progress notification information returned by the service server when the target screenshot task is executed, and adjusting the task state of the target screenshot task based on the progress notification information.

The task state of the target screenshot task comprises at least one of the following states: task waiting state, task executing state, task ending state; the task end state includes a task success state and a task failure state.

In one aspect, an embodiment of the present application provides a data processing method, where the method is applied to a service server, and includes:

receiving a screenshot instruction sent by a terminal based on filling parameter information in a task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer;

adding the N screenshot addresses and the K machine type information to a task queue for executing a target screenshot task based on the screenshot instruction; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

and sequentially executing each sub-screenshot task in the task queue to obtain a screenshot result corresponding to each sub-screenshot task, and returning the screenshot result corresponding to each sub-screenshot task to the terminal.

The step of sequentially executing each sub-screenshot task in the task queue to obtain a screenshot result corresponding to each sub-screenshot task, and returning the screenshot result corresponding to each sub-screenshot task to the terminal comprises the following steps:

determining a sub-screenshot task at the head of the queue as a task to be screenshot in the task queue, and determining a screenshot address corresponding to the task to be screenshot as a screenshot address;

taking the user identification information in the filling parameter information, the identification information of the address to be captured and the size information of the K machine types as task parameters;

the task parameters are transmitted into a browser, so that the target page of the address to be captured is simulated to be logged in the browser through the user identification information;

performing screenshot operation on the target page of the address to be screenshot through the K machine type information to obtain a screenshot result corresponding to the task to be screenshot;

and when the task to be captured is completed, outputting the task to be captured to the task queue until each sub-capture task in the task queue is used as the address to be captured, and obtaining a capture result corresponding to each sub-capture task.

Wherein the method further comprises:

and when the screen capturing operation is carried out on the target page of the address to be captured through the K machine type information, monitoring the screen capturing progress of the task to be captured, and sending progress notification information to the terminal based on the screen capturing progress.

Wherein the method further comprises:

if the machine type information with the failed screenshot exists in the K machine type information, determining the machine type information with the failed screenshot as target machine type information;

repeating the screenshot operation on the target page of the address to be screenshot based on the target model information, and counting the times of repeated screenshot failure according to the screenshot state corresponding to the repeated screenshot operation;

and when the times are greater than a failure threshold, ending the task to be shot, and informing the terminal to identify the task state of the target screenshot task as a task failure state in a target task list where the task to be shot is located.

An aspect of an embodiment of the present application provides a data processing apparatus, where the apparatus is applied to a terminal, including:

the task confirmation module is used for responding to task confirmation operation triggered by aiming at a task creation interface and acquiring filling parameter information filled in the task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer;

The screenshot instruction sending module is used for sending screenshot instructions carrying the N screenshot addresses and the K machine type information to a service server so that the service server can execute a target screenshot task based on the screenshot instructions; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

the screenshot result receiving module is used for receiving screenshot results returned by the service server based on each sub-screenshot task; and the screenshot result comprises screenshot pictures of the target page corresponding to the screenshot address in the K machine type information respectively.

Wherein the apparatus further comprises:

the page jumping module is used for responding to task creation operation triggered by the historical task list and jumping the display interface where the historical task list is positioned to a task creation interface to be filled;

the interface filling module is used for responding to the filling operation of the task creation interface to be filled, determining filling parameter information associated with the task creation interface to be filled, and determining the task creation interface to be filled carrying the filling parameter information as a task creation interface.

Wherein, the interface filling module includes:

The filling interface determining unit is used for determining the task creation interface to be filled as a filling interface of the target screenshot task; the filling interface comprises a plurality of areas to be filled;

the region filling unit is used for responding to the filling operation of each region to be filled in the filling interface and acquiring filling parameter information filled in each region to be filled; the filling parameter information comprises at least one of the following parameter information: task name, N screenshot addresses, user identification information and K machine type information; the user identification information is used for simulating to log in a target page of each screenshot address when the business server executes the target screenshot task;

and the interface determining unit is used for determining a filling interface carrying the task name, the N screenshot addresses, the user identification information and the K machine type information as the task creation interface.

Wherein the region filling unit includes:

the name acquisition subunit is used for responding to a first filling operation triggered for a first area in the filling interface and acquiring a task name of the target screenshot task;

an address obtaining subunit, configured to obtain, from a service server, an address database associated with a second area in the filling interface in response to a second filling operation triggered for the second area, and determine N screenshot addresses associated with the target screenshot task based on an address in the address database;

The identification acquisition subunit is used for responding to a third filling operation triggered by aiming at a third area in the filling interface and acquiring user identification information of a target page for simulating login of each screenshot address;

the machine type obtaining subunit is used for responding to a fourth filling operation triggered by aiming at a fourth area in the filling interface and obtaining K machine type information from a plurality of machine type information contained in the fourth area;

and the parameter determination subunit is used for determining the task name, the N screenshot addresses, the user identification information and the K machine type information as filling parameter information filled in the filling interface.

Wherein the address acquisition subunit includes:

a database acquisition subunit, configured to respond to a second filling operation triggered for a second area in the filling interface, acquire an address database associated with the second area from a service server, and jump the filling interface to a resource display interface for displaying an address of the address database;

the label acquisition subunit is used for responding to label acquisition operation triggered by the resource display interface, acquiring target label information, and screening M addresses matched with the target label information from the addresses of the address database based on the target label information;

And the address determination subunit is used for responding to the selection operation aiming at the M addresses, acquiring N addresses from the M addresses as addresses to be shot, copying each address to be shot to a second area of the filling area, and obtaining N screenshot addresses associated with the target screenshot task.

Wherein the apparatus further comprises:

the screenshot task adding module is used for adding the target screenshot task with the task name to the history task list to obtain a target task list, and displaying the task state of the target screenshot task associated with the N screenshot addresses in the target task list;

and the task state adjustment module is used for receiving progress notification information returned by the service server when the target screenshot task is executed, and adjusting the task state of the target screenshot task based on the progress notification information.

An aspect of an embodiment of the present application provides a data processing apparatus, where the apparatus is applied to a terminal, including: a processor, a memory, and a network interface;

The processor is connected to a memory for providing network communication functions, and a network interface for storing program code for invoking the program code to perform the method as in one aspect of the embodiments of the present application.

An aspect of the present application provides a computer storage medium storing a computer program comprising program instructions which, when executed by a processor, perform a method as in an aspect of the present application.

An aspect of an embodiment of the present application provides a data processing apparatus, where the apparatus is applied to a service server, including:

the screenshot instruction receiving module is used for receiving a screenshot instruction sent by the terminal based on the filling parameter information in the task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer;

the task queue determining module is used for adding the N screenshot addresses and the K machine type information to a task queue for executing a target screenshot task based on the screenshot instruction; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

And the screenshot result returning module is used for sequentially executing each sub-screenshot task in the task queue to obtain a screenshot result corresponding to each sub-screenshot task, and returning the screenshot result corresponding to each sub-screenshot task to the terminal.

The screenshot result returning module comprises:

the to-be-screened-image determining unit is used for determining a sub-screened-image task at the head of a queue in the task queue as a to-be-screened-image task and determining a screened-image address corresponding to the to-be-screened-image task as a to-be-screened-image address;

the task parameter determining unit is used for taking the user identification information in the filling parameter information, the identification information of the address to be captured and the size information of the K machine types as task parameters;

the parameter input unit is used for inputting the task parameters into a browser so as to simulate logging in the target page of the address to be captured through the user identification information in the browser;

the page screenshot unit is used for performing screenshot operation on the target page of the address to be screenshot through the K machine type information so as to obtain screenshot results corresponding to the task to be screenshot;

and the task output unit is used for outputting the task to be screened to the task queue when the task to be screened is completed, and obtaining a screen capture result corresponding to each sub-screen capture task when each sub-screen capture task in the task queue is used as the address to be screened.

The screenshot result returning module further comprises:

and the progress monitoring unit is used for monitoring the screenshot progress of the task to be screenshot when the target page of the address to be screenshot is subjected to screenshot operation through the K machine type information, and sending progress notification information to the terminal based on the screenshot progress.

The screenshot result returning module further comprises:

the target model determining unit is used for determining the model information with the failed screenshot as target model information if the model information with the failed screenshot exists in the K model information;

the target machine type multiplexing unit is used for repeatedly carrying out screenshot operation on the target page of the address to be screenshot based on the target machine type information, and counting the times of repeated screenshot failure according to screenshot states corresponding to the repeated screenshot operation;

and the screenshot ending unit is used for ending the task to be screenshot when the times are greater than a failure threshold value, and notifying the terminal to identify the task state of the target screenshot task as a task failure state in a target task list where the task to be screenshot is located.

The embodiment of the application provides a data processing device, which is applied to a service server and comprises: a processor, a memory, and a network interface;

In the embodiment of the application, a terminal can respond to task confirmation operation triggered by a task creation interface to acquire filling parameter information filled in the task creation interface; the filling parameter information can comprise N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer; further, after receiving the screenshot instruction sent by the terminal, the service server can obtain N screenshot addresses for performing screenshot processing (also called screenshot processing), and can multiplex the sizes of different models (namely, K model information) to automatically execute the target screenshot task; the target screenshot task may include a plurality of sub-screenshot tasks; one sub-screenshot task may correspond to one screenshot address; it can be understood that in the process of executing the target screenshot task, the service server may sequentially execute each sub-screenshot task to obtain a screenshot result corresponding to each sub-screenshot task, where one screenshot result may include screenshot pictures of a target page corresponding to one screenshot address in the K model information respectively. Therefore, according to the embodiment of the application, the size of the picture intercepted each time is not required to be manually adjusted, namely, the terminal can control the service server to intelligently intercept the pictures adapting to different machine types through the screenshot instruction, so that the accuracy of screenshot can be improved. In addition, the business server can realize batch screenshot on target pages with different screenshot addresses, so that screenshot efficiency can be improved.

Drawings

In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic structural diagram of a network architecture according to an embodiment of the present application;

FIG. 2 is a schematic view of a scenario of data interaction provided by an embodiment of the present application;

FIG. 3 is a schematic flow chart of a data processing method according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a new screenshot task in developing test applications provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a determination task creation interface provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of obtaining N screenshot addresses according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a screenshot instruction provided by an embodiment of the present application;

FIG. 8 is a schematic view of a scenario featuring review of screenshot results associated with a target screenshot task provided by an embodiment of the present application;

FIG. 9 is a flowchart of another data processing method according to an embodiment of the present application;

FIG. 10 is a schematic diagram of a scenario for obtaining a target task list according to an embodiment of the present application;

FIG. 11 is a schematic diagram of an overall flow of performing a target screenshot task provided by an embodiment of the present application;

FIG. 12 is a schematic view of a scenario in which a large graph is viewed on a task detail page, provided by an embodiment of the present application;

FIG. 13 is a schematic diagram of a comparison history screenshot provided by an embodiment of the present application;

FIG. 14 is a schematic diagram of a data processing apparatus according to an embodiment of the present application;

FIG. 15 is a schematic diagram of a computer device according to an embodiment of the present application;

FIG. 16 is a schematic diagram of another data processing apparatus according to an embodiment of the present application;

FIG. 17 is a schematic diagram of another computer device according to an embodiment of the present application;

FIG. 18 is a schematic diagram of another data processing system according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

Fig. 1 is a schematic structural diagram of a network architecture according to an embodiment of the present application. As shown in fig. 1, the network architecture may be applied to a web page screenshot system, which may include a service server 2000 and a user terminal cluster; the user terminal cluster may include a plurality of user terminals, as shown in fig. 1, and specifically may include a user terminal 3000a, user terminals 3000b, …, and a user terminal 3000n;

any one of the plurality of user terminals shown in fig. 1 may communicate data with the service Server 2000 based on Browser/Server (B/S) or Client/Server (C/S) mode.

As shown in fig. 1, the user terminals 3000a, 3000b, …, 3000n may be respectively connected to the service server 2000 in a network manner, and the plurality of user terminals may implement interaction between service data through a service platform and the service server 2000. It should be understood that, in the embodiment of the present application, each user terminal may control, through the service platform, the service server 2000 to perform a unified screen capturing process, so as to intercept specific pages with different sizes in batches, for example, the specific pages (i.e. target pages) may be intercepted in batches, so as to help a user obtain screenshot pictures with different sizes, thereby enriching the display effect of the pictures obtained after the screen capturing.

For easy understanding, the embodiment of the present application takes one user terminal of the plurality of user terminals as a target user terminal as an example, to illustrate a specific process of performing data interaction between the target user terminal and the service server 2000 in a target application scenario. It may be understood that the target application scenario in the embodiment of the present application may include an image processing scenario, a development test scenario, and other application scenarios that need to be batched for screenshot, which are not limited herein. Wherein, the target user terminal may include: and the intelligent mobile phone, the tablet personal computer, the notebook personal computer and other physical devices.

For example, in the case that the target application scene is an image processing scene, the target user terminal may respond to a task confirmation operation triggered by the task creation interface to obtain filling parameter information filled in the task creation interface; the filling parameter information may include N screenshot addresses and K model information; the task creation interface may be a display interface where a business service platform corresponding to a target application (e.g., an image processing application) is located. For example, in this image processing scenario, each screenshot address may be used to obtain a target picture stored after image processing (e.g., filter processing). In order to understand the display effect of the image-processed target pictures in different devices, the target user terminal may send a screenshot instruction carrying N screenshot addresses and K model information to the service server 2000, so that the service server executes a target screenshot task based on the screenshot instruction, where the target screenshot task may be understood as capturing, in the service server 2000, screenshot pictures of each image-processed target picture in different devices in batches. For example, the screenshot pictures of the target page (i.e., the H5 page where the target picture is located) corresponding to each screenshot address in the K model information may be automatically intercepted, so that the user may be helped to know the display effects of the image-processed target picture in different devices in the target user terminal.

Optionally, for example, in a development test scenario, the service server platform may be used to perform development test on a target project, that is, the embodiment of the present application may also refer to the service server platform for performing development test as a development test framework. The development test framework may be used in a browser in the form of a web page, or may be transplanted to a client (i.e., an application program for performing development test), which is not limited herein. In the embodiment of the application, the application program for performing development test can be collectively called as development test application, and in a development test scene, the development test application can face developers, testers, designers and the like, and the embodiment of the application is not limited.

It may be appreciated that, in the development test scenario, the target user terminal and the service server 2000 may be used together to perform intelligent screenshot processing on different pages under the target item (for example, an H5 page, a web page written in the H5 language displayed in the entity device). For example, the target user terminal may send a screenshot instruction to the service server 2000 through the development test framework (i.e. the service platform described above), so that the service server may be remotely controlled to intelligently intercept screenshot pictures of different H5 pages in different devices through a screenshot tool associated with the service platform, so as to implement batch screenshot, and thus, may analyze and mine a display effect of different H5 pages in the same device. In addition, the embodiment of the application can intelligently intercept screenshot pictures of the same H5 page in different devices through the screenshot tool so as to analyze and mine the compatibility of the same H5 page in different devices.

For easy understanding, the embodiment of the application takes the target application scene as an example of a development test scene to illustrate a specific process of realizing batch screenshot on the H5 pages in the target project through the business service platform.

The target item may include H5 items such as a WeChat reading item or a QQ mailbox book city item, which have a large number of electronic books (e.g., electronic books, electronic novels), and each of the H5 items may correspond to a URL (Uniform Resource Locator ) address. Each URL address may be used to access a target page (i.e., H5 page) of a particular electronic reading. In a development test scenario, in order to help a developer quickly understand the compatibility of target pages corresponding to URL addresses in different devices, the embodiment of the present application may create a target screenshot task for performing automatic screenshot through a service platform (e.g., development test framework) integrated in the target application (e.g., development test application), so as to automatically intercept a screenshot result corresponding to each sub-screenshot task in the target screenshot task in the service server 2000, and further help the developer understand the display effect of the target pages of each screenshot address in different entity devices (e.g., mobile phones).

For example, the embodiment of the application can manufacture and use the business service platform based on compatibility problems and scenes frequently encountered in the development process of the H5 page under the WeChat reading item, so that the business server 2000 can be remotely controlled through the business server platform. The above-mentioned web page screenshot system including the target user terminal and the service server 2000 may include the following two functional parts:

1) URL pools. The URL pool can be used for recording URL addresses of all H5 pages in the current H5 project, so that the embodiment of the application can refer to the address set recorded with a large number of URL addresses as the URL pool, and also can refer to the address database, and each URL address in the address database can be collectively referred to as an address.

In the embodiment of the application, the list display interface corresponding to the URL pool displayed in the terminal may be collectively referred to as resource display interfaces, each resource display interface may include a plurality of URL addresses (for example, may include 10 URL addresses, each URL address may be used to access a detail page of a book), and the URL addresses displayed in each resource display interface may be continuously updated. It can be understood that the URL addresses in the URL pool are URL addresses provided with corresponding tag information. It can be understood that a developer can set corresponding tag information for URL addresses in the URL pool, and write corresponding header information for URL addresses in the URL pool, so that M URL addresses can be quickly retrieved and matched in the URL pool based on the obtained target tag information in a subsequent testing process of target pages corresponding to the URL addresses, and N screenshot addresses for testing can be quickly obtained from the M URL addresses. Therefore, according to the embodiment of the application, through setting the corresponding tag information for the URL addresses with different attributes, N screenshot addresses for testing can be obtained online in the screenshot task creation process, so that the data searching efficiency can be effectively improved, and the process of creating the target screenshot task can be accelerated in the development terminal.

2) A screenshot tool. The screenshot tool in the development test framework can be a service process for providing an automatic screenshot function, and can be integrally installed in the service server 2000, so that after a terminal creates a target screenshot task, the service server 2000 can be controlled to organize each sub screenshot task of the target screenshot task in a task mode, and the screenshot tool is called in a task queue mode to realize batch screenshot so as to obtain screenshot results corresponding to N screenshot addresses respectively.

It should be understood that, a developer may select a screenshot address of a specific page from a resource display interface associated with a URL pool, for example, N screenshot addresses for performing a test may be screened from a resource display interface where the searched M addresses are located, that is, the URL pool may support further selection of the screened URL addresses; optionally, the developer may also manually enter the screenshot address required to be screenshot in the URL pool, that is, the URL pool also supports directly filling in the screenshot address.

In addition, the screenshot tool with an association relationship with the development test framework can multiplex the sizes of a plurality of devices in the screenshot process to sequentially obtain screenshot pictures of each screenshot address in different devices, and the screenshot results can be organized in a task form to help developers to know the compatibility of the same screenshot address in different devices.

For easy understanding, further, please refer to fig. 2, which is a schematic diagram of a scenario of data interaction provided by an embodiment of the present application. The terminal as shown in fig. 2 may be a terminal integrated with a development test framework in a development test application. Wherein, the development test framework can create the target screenshot task and can also help a target user (such as a developer shown in fig. 2) to remotely control the business server to execute the created target screenshot task. For example, a developer shown in fig. 2 may perform man-machine interaction through the task creation interface 100a in the terminal, so that when the terminal obtains a task confirmation operation (for example, a trigger operation) of the developer for confirming the creation target screenshot task in the task creation interface 100a, N screenshot addresses (for example, 3 URL addresses) may be obtained from the task creation interface 100a displayed in the terminal. In addition, in order to help a developer to know the display effect of the target page of each screenshot address in different terminal devices, the embodiment of the present application may further obtain K machine type information (for example, 6 machine type information) from the task creation interface 100a, so that a screenshot instruction carrying N screenshot addresses and K machine type information may be sent to the service server shown in fig. 2, so that the service server may uniformly construct, based on N screenshot addresses (i.e., 3 URL addresses, for example, the three URL addresses may be address 1, address 2 and address 3) and K machine type information (i.e., 6 machine type information) in the screenshot instruction, to obtain the task queue a for executing the target screenshot task shown in fig. 2. As shown in fig. 2, the task queue a may include a plurality of sub-screenshot tasks shown in fig. 2, where the plurality of sub-screenshot tasks may specifically include a sub-screenshot task 10a, a sub-screenshot task 20a, and a sub-screenshot task 30a. Further, the service server shown in fig. 2 may multiplex the 6 model information during the process of executing each sub-screenshot task, so as to automatically intercept and obtain the screenshot pictures of the target page of each screenshot address (i.e. each URL address) in different devices. For example, 6 screenshot pictures corresponding to the target page of the address 1 can be automatically intercepted in the service server, 6 screenshot pictures corresponding to the target page of the address 2 can be automatically intercepted in the service server, and 6 screenshot pictures corresponding to the target page of the address 3 can be automatically intercepted in the service server, so that a developer can be helped to quickly know the display effect of the same screenshot address in different devices, namely the compatibility of the same screenshot address in different devices. In addition, the screenshot results (namely, 6 screenshot pictures corresponding to each URL address) intercepted in batches can be returned to the terminal shown in FIG. 2 in a task mode. The embodiment of the application can inform the terminal to dynamically adjust the task state of the target screenshot task associated with the 3 screenshot addresses in the display interface where the target task list is located when the service server automatically completes each sub screenshot task. The adjustment of the task state of the target screenshot task is determined based on progress notification information returned by the service server in the process of executing the target screenshot task.

The task state of the target screenshot task may include at least one of the following states: task waiting state, task executing state, task ending state; the task end state includes a task success state and a task failure state.

When executing each sub-screenshot task shown in fig. 2, the service server 2000 needs to transmit an input parameter to the browser, so that the browser integrated in the service server 2000 can log in the target page of each screenshot address through the user identification information in the input parameter, and thus, the screenshot operation can be performed on the target page of each screenshot address by multiplexing the K model information, and thus, the screenshot result associated with each screenshot address can be obtained respectively. The screenshot result may include screenshot pictures of the target page corresponding to the screenshot address in the K model information, respectively.

Therefore, the embodiment of the application can multiplex the sizes of different machine types through the screenshot tool, so that pictures applicable to different machine types can be intercepted in batch in the service server 2000, the display effect of different webpage pages in different devices can be obtained quickly, and development can be facilitated to know the compatibility of different webpage pages in different devices quickly. It can be understood that, for other application scenarios for performing batch screenshot, the specific implementation manner of implementing batch screenshot by the service platform may refer to the specific process of implementing batch screenshot in the development test scenario in the embodiment corresponding to fig. 2, which will not be described in detail herein.

The specific process of the target user terminal obtaining the filling parameter information and obtaining the screenshot result corresponding to each sub-screenshot task when the service server 2000 executes the target screenshot task may be referred to as embodiments corresponding to fig. 3 to fig. 12 below.

Further, please refer to fig. 3, which is a flowchart illustrating a data processing method according to an embodiment of the present application. The method may be applied to a terminal, as shown in fig. 3, and the method may include:

step S101, responding to task confirmation operation triggered by a task creation interface, and acquiring filling parameter information filled in the task creation interface;

the filling parameter information can comprise N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n may be a positive integer less than or equal to M; k may be a positive integer.

The address database may be a URL pool in the embodiment corresponding to fig. 1, where the URL pool may be used to record URL addresses of H5 pages in all H5 items. In other words, in the process that the target user (for example, a developer, etc.) needs to perform intelligent screen capturing (i.e., intelligent screen capturing) on the H5 pages in the H5 projects, the URL addresses of the specific pages can be screened out of the URL addresses recorded in the URL pool through the target tag information, that is, M addresses matched with the target tag information can be screened out of the URL pool (i.e., the address database), so that it can be ensured that the target user can quickly determine the screen capturing addresses of the specific pages for performing screen capturing from the M addresses. It can be understood that when the terminal obtains all the filling parameter information filled in the task creation interface, step S102 may be further performed, so that the service server may call, based on the screenshot instruction, the screenshot pictures of the specific pages (target pages) of the URL addresses automatically intercepted by the screenshot tool in different devices. The terminal described in the embodiment of the present application may be the above-mentioned target user terminal.

The business service platform in the embodiment of the application can be integrated in an application program in the entity equipment, the application program can be the target application, and the target application can be understood as an internal application which can be used for carrying out unified screen capturing on web pages in all H5 projects in a target application environment.

It may be understood that, before executing step S101, the terminal may also create a new screenshot task through the business service platform integrated in the target application. For example, when the target application environment is a development test environment, the terminal can create a new screenshot task through a development test framework integrated in the development test application.

For easy understanding, further, please refer to fig. 4, which is a schematic diagram of a new screenshot task in developing a test application according to an embodiment of the present application. As shown in fig. 4, the business service platform (i.e., development test framework) integrated in the development test application may include a plurality of functional modules, which may include a task list module 10a, a task creation module 10b, a URL pool sub-module 10c, and a user management module 10d. The task list module 10 may be configured to add a new screenshot task to the task list, and may refer to the new screenshot task as a target screenshot task. Wherein the task creation module 10b may be configured to populate fill parameter information associated with the target screenshot task in the task creation interface to generate screenshot instructions based on the fill parameter information. The URL pool sub-module 10c may be configured to store all URL addresses with tag information, and determine N screenshot addresses associated with the target screenshot task from the URL pool during the process of creating the target screenshot task. The user management module 10d may be configured to manage a user list using the development test framework (service platform), that is, a user (for example, a developer, a tester, a designer, etc.) in the user list has a right to use the development test framework, for example, the user 1 and the user 2 shown in fig. 4 each have a right to use the service platform.

For ease of understanding, the embodiment of the present application takes the user in the usage list as a developer, to further illustrate a specific process of creating a target screenshot task by a target user (e.g., user 1) through a development test framework (i.e., a business service platform) shown in fig. 4. In this embodiment of the present application, the task list before creating the new screenshot task may be referred to as a history task list, where a plurality of history screenshot tasks shown in fig. 4 may be recorded. The plurality of historical screenshot tasks may include screenshot tasks created by the same user (e.g., the same developer) or screenshot tasks created by different users (e.g., different developers), and no specific limitation is placed on the user using the business service platform.

The plurality of history screenshot tasks may specifically include, as shown in fig. 4, a screenshot task 9 with a task name of task 40a created by user 1, a screenshot task 8 with a task name of task 40b created by user 1, a screenshot task 7 with a task name of task 40c created by user 1, a screenshot task 6 with a task name of task 40d created by user 1, a screenshot task 5 with a task name of task 40e created by user 1, a screenshot task 4 with a task name of task 40f created by user 2, a screenshot task 3 with a task name of task 40g created by user 2, a screenshot task 2 with a task name of task 40h created by user 2, and a screenshot task 1 with a task name of task 40i created by user 1. In other words, the screenshot task 9, screenshot task 8, screenshot task 7, screenshot task 6, screenshot task 5, screenshot task 4, screenshot task 3, screenshot task 2, and screenshot task 1 in the history task list may all be arranged from bottom to top according to the sequence of creating the timestamps of the screenshot tasks.

It may be understood that each historical screenshot task in the historical task list is determined according to a time stamp of a screenshot task, for example, the time stamp of the screenshot task 1 in the historical task list is smaller than the time stamp of the screenshot task 2, so that the screenshot task 2 may be listed above the screenshot task 1 in the historical task list, and so on, the embodiment of the present application may list the latest screenshot task (i.e., the target screenshot task) created above the screenshot task 9 to obtain the target task list. The embodiment of the application can determine the historical task list of the target screenshot task as a target task list.

Wherein, as shown in fig. 4, the target user (for example, user 1) may perform a trigger operation on the "create screenshot task" button in the task list (the task list here may be a history task list) in the service platform shown in fig. 4, and at this time, the trigger operation performed on the "create screenshot task" button may be collectively referred to as a task creation operation. Further, the user terminal (abbreviated as terminal) used by the target user may respond to the task creation operation triggered by the history task list, and jump the display interface where the history task list shown in fig. 4 is located to the task creation interface to be filled. The task creation interface to be filled may be a filling interface 100a as shown in fig. 4.

Further, the terminal may determine filling parameter information associated with the task creation interface to be filled in response to a filling operation for the task creation interface to be filled (i.e., the filling interface 100a shown in fig. 4), and may determine the task creation interface to be filled, which carries the filling parameter information, as a task creation interface.

It can be understood that, the user 1 may quickly select N screenshot addresses that can be filled in the area 2 shown in fig. 4 from a URL pool (i.e., an address database that records all URL addresses in the H5 project) through the service platform shown in fig. 4 (in a development test scenario, the service platform may be referred to as a development test framework).

As shown in fig. 4, the filling interface 100a may include a plurality of areas to be filled, where the plurality of areas to be filled may specifically include: region 1, region 2, region 3, region 4 shown in fig. 4. The area 1 shown in fig. 4 may be used to receive a task name of a target screenshot task entered by a target user. The area 3 shown in fig. 4 may be used to receive user identification information entered by a target user, and the area 4 shown in fig. 4 may be used to receive K model information selected by the target user. In addition, the area 2 shown in fig. 4 may be used to receive N screenshot addresses screened and determined by the target user from the address database. Each screenshot address of the N screenshot addresses is an address selected from M addresses that match the target identification information.

For ease of understanding, further, please refer to fig. 5, which is a schematic diagram illustrating a task creation interface according to an embodiment of the present application. The filling interface 200a shown in fig. 5 may be the filling interface 100a in the embodiment corresponding to fig. 4. In other words, the task creation interface to be filled in the embodiment of the present application may be referred to as a filling interface (such as the filling interface 200a shown in fig. 5) of the target screenshot task.

In this embodiment of the present application, the area 1 shown in fig. 5 may be referred to as a first area, the area 2 shown in fig. 5 may be referred to as a second area, the area 3 shown in fig. 5 may be referred to as a third area, and the area 4 shown in fig. 5 may be referred to as a fourth area.

The description of filling the regions 1, 2, 3, 4 in the interface 100a is based on the corresponding embodiment of fig. 4. As shown in fig. 5, the user 1 (i.e., the target user) may perform a filling operation in the terminal for each to-be-filled area, so that when each to-be-filled area of the plurality of to-be-filled areas shown in fig. 5 is filled with corresponding filling parameter information, a task creation interface to be filled (i.e., the filling interface 200a shown in fig. 5) carrying the filling parameter information may be further referred to as a task creation interface, so that step S101 may be further performed, so that the terminal may acquire the filling parameter information filled in the task creation interface in response to a task confirmation operation triggered for the task creation interface, and at this time, the filling parameter information may include N screenshot addresses in the area 2 shown in fig. 5 and K model information in the area 4. In addition, the filling parameter information may further include a task name (e.g., AAABBB) in the area 1 shown in fig. 5, the text AAABBB in the area 1 may be used to represent a task name of a target screenshot task that is subsequently displayed in the history task, and further, the filling parameter information may further include user identification information (e.g., a character string 10352) in the area 3 shown in fig. 5, which may be account information of a registered user that is subsequently used to simulate logging in each screenshot address, and so on.

Wherein the N screenshot addresses in the task creation interface 200b shown in fig. 5 are determined by the target user from M addresses screened from the address database (i.e., the URL pool sub-module) associated with the region 2 (i.e., the second region). The terminal used by the target user (for example, user 1) may be referred to as a terminal, and the background server having a network connection relationship with the terminal may be referred to as a service server.

For easy understanding, please refer to fig. 6, which is a schematic diagram of acquiring N screenshot addresses according to an embodiment of the present application. The target user may perform a trigger operation on the "URL pool" button in the filling interface 300a shown in fig. 6, so as to obtain an address database (i.e., the URL pool described above) associated with the second area (the area 2 shown in fig. 6) from the service server, and display the obtained address in the address database on each page in a paging manner. For example, 10 addresses may be displayed on each page, and any one address on each page may be referred to as an example. One of the pages may be referred to as a resource display interface.

In this embodiment of the present application, the triggering operation performed on the "URL pool" button may be referred to as a second filling operation, so the terminal may quickly acquire, from the service server, the address database associated with the second area in response to the second filling operation triggered on the second area in the filling interface, and further jump the filling interface (i.e., the filling interface 300a shown in fig. 6) to a resource display interface for displaying the address of the address database (for example, the resource display interface 300b shown in fig. 6, where 10 addresses may be displayed in the resource display interface 300 a). It can be understood that, in the embodiment of the present application, 10 examples displayed in each resource display interface may be continuously updated, so that a new resource display interface may be formed.

Further, as shown in fig. 6, the target user (e.g., developer) may manually enter the target tag information in the resource display interface 300b, for example, in the embodiment of the present application, the tag 1 and the tag 2 in the tag entry area shown in fig. 6 may be collectively referred to as the target tag information, so that M addresses matched with the target tag information (i.e., the tag 1 and the tag 2) may be screened from the addresses in the address database (i.e., the URL pool shown in fig. 6) based on the target tag information. For example, m=8 addresses shown in fig. 6 can be obtained. The 8 addresses shown in fig. 6 may be specifically address 30a, address 30b, address 30c, address 30d, address 30e, address 30f, address 30g, and address 30h. The 8 addresses may be addresses that are searched intelligently from each resource display interface to carry at least tag 1 and tag 2.

The resource display interface 300a shown in fig. 6 may be a micro letter novel label, the label 2 may be a book detail label, the label 3 may be a short introduction label, the label 4 may be a to-be-put-on label, the label 5 may be a public number label, the label 6 may be a micro letter reading label, the label 7 may be a toolbar-attached label, etc., and the classification dimension to which a specific label belongs will not be limited.

It can be understood that in the embodiment of the application, corresponding tag information can be set for the URL addresses according to different attributes of each address in the address database, so that URLs with the tag information can be input into a screenshot system, and a developer can acquire all recorded addresses carrying the tag information from the screenshot system when triggering the URL pool button, and then the addresses carrying the tag information can be displayed in a corresponding page in a paging mode.

The embodiment of the application can set corresponding tag information for each URL address received in the URL pool, and in the process of setting the tag information of each URL address, the corresponding tag can be obtained by dividing the attribute of different dimensions. For easy understanding, in the embodiment of the present application, an electronic reading (e.g., electronic book) may be taken as an example, and each electronic book may correspond to one URL address, and then the tag of the electronic book may be divided by the following dimensions, in other words, the tag portion of the URL address of each electronic book may include at least one of the following dimensions:

1) The modules (such as WeChat novelties module, mailbox book module and the like) can be divided according to first dimensions;

2) The page content (such as second dimension of book details, reader, idea details, etc.) can be divided;

3) The UI (user interaction interface) performance (with Bar, alert and other third dimensions) can be divided;

4) The data may be divided into several dimensions, such as data type (e.g., fourth dimension such as public number);

in addition, it will be appreciated that in addition to pre-setting tag information for each URL address in the URL pool, the present application may also manually add some new tags for the corresponding URL address during address screening using the URL pool. It will be appreciated that these tags and titles carried by each URL can help a target user (e.g., developer) quickly find a desired page when developing a test. For short-brief introduction books, a short-brief introduction label can be manually edited and added on a label column of a related URL address of the book details, so that a proper use case can be quickly found when the brief introduction of the book details is tested.

In addition, the URL pool shown in fig. 6 may support some of the following features:

1) The title and the label of the page corresponding to the search URL address can be synchronously supported while the URL address is searched through the keyword (namely the target label information); as shown in fig. 6, a space or english comma may be used to separate a plurality of keywords, for example, a comma may be used to separate a tag 1 and a tag 2 in a tag entry area.

2) In support of selecting URL addresses in a page-crossing manner, as the addresses in the URL pool can be displayed in a page-crossing manner, namely 10 URL addresses can be displayed on each page-crossing page, when the number of M addresses matched with target tag information is searched to be greater than the threshold value (for example, 10) of each page-crossing page, a developer selects N screenshot addresses from the M addresses to form a target screenshot task, and can select URLs in different resource display interfaces in a page-crossing manner to form a task.

3) Each existing URL address, as well as title and tag information, is supported to be edited directly on the list field in the resource display interface where the URL pool is located.

4) The modification method supports batch modification of the tag information of a plurality of URLs in the resource display interface where the URL pool is located, and the modification method can specifically comprise batch addition of new tag information, batch deletion of existing tag information, batch replacement of tag information and the like.

Step S102, a screenshot instruction carrying the N screenshot addresses and the K machine type information is sent to a service server, so that the service server executes a target screenshot task based on the screenshot instruction;

the target screenshot task can comprise a plurality of sub-screenshot tasks; one sub-screenshot task may correspond to one screenshot address;

it can be understood that, after the target user performs the filling operation on each area to be filled, the task creation interface 200b in the embodiment corresponding to fig. 5 may be obtained, where the task creation interface 200b may include N screenshot addresses and K model information. For easy understanding, further, please refer to fig. 7, which is a schematic diagram of a scenario of a screenshot instruction according to an embodiment of the present application. The task creation interface 200c shown in fig. 7 is a display interface obtained after the target user completes the filling operation on each area to be filled through the service platform. The N screenshot addresses shown in fig. 7 may be n=4 addresses selected from m=8 addresses in the embodiment corresponding to fig. 6, and the 4 screenshot addresses may be the address 30a, the address 30b, the address 30c, and the address 30d in the embodiment corresponding to fig. 6, for example, the screenshot address 1 shown in fig. 7 may be an address filled in the area 2 after the copy operation is performed on the address 30a in the embodiment corresponding to fig. 6, and so on, so as to obtain the 4 screenshot addresses shown in fig. 7.

The K model information shown in fig. 7 may be k=6 model information selected from the 8 model information in the embodiment corresponding to fig. 6, and the 6 model information may be model information 1, model information 2, model information 3, model information 4, model information 7, and model information 8 in the embodiment corresponding to fig. 6.

As shown in fig. 7, the target user may perform a task confirmation operation with respect to the task creation interface 200c, so that the filling parameter information in the task creation interface 200c may be added to a screenshot instruction, so that the screenshot instruction carrying the filling parameter information is sent to the service server shown in fig. 7, so that the service server may perform, based on the screenshot instruction, a target screenshot task associated with the N screenshot addresses, where the target screenshot task may include a plurality of sub-screenshot tasks; each sub-screenshot task may correspond to a screenshot address; for example, the task queue created by the service server shown in fig. 7 may include a plurality of sub-screenshot tasks; the plurality of sub-screenshot tasks may specifically include a sub-screenshot task 60a, a sub-screenshot task 70a, a sub-screenshot task 80a, and a sub-screenshot task 90a. The sub-screenshot task 60a in the task queue may be a sub-screenshot task corresponding to the screenshot address 1; the sub-screenshot task 70a in the task queue may be a sub-screenshot task corresponding to the screenshot address 2; the sub-screenshot task 80a in the task queue may be a sub-screenshot task corresponding to the screenshot address 3; the sub-screenshot task 90a in the task queue may be a sub-screenshot task corresponding to screenshot address 4. It may be understood that, in the embodiment of the present invention, the sub-screenshot task 60a may be a sub-screenshot task located at the head of the queue, and the sub-screenshot task 90a may be a sub-screenshot task located at the tail of the queue.

The method and the device can effectively reduce the interaction times by organizing a plurality of screenshot addresses together in the form of tasks, namely, the method and the device can remotely control the service server to execute each sub-screenshot task in the target screenshot task under the condition that a screenshot instruction is sent to the service server once.

In addition, in order to ensure that the service server cannot cause excessive resource loss to the service server in the screenshot process, the embodiment of the application can sequentially execute each sub-screenshot task in the form of the task queue shown in fig. 7 until all sub-screenshot tasks are executed, and can obtain a screenshot result corresponding to each sub-screenshot task. Furthermore, the embodiment of the application can organize the screenshot pictures obtained by multiplexing different machine type information in the form of tasks (namely sub screenshot tasks) so as to further execute the step S103, thereby helping a developer to quickly know the display effect of the target page of each screenshot address in different devices.

Step S103, receiving a screenshot result returned by the service server based on each sub-screenshot task;

specifically, the terminal may receive a screenshot result returned by the service server based on each sub-screenshot task, where one screenshot result may include screenshot pictures of a target page corresponding to one screenshot address in the K model information respectively.

For ease of understanding, further, please refer to fig. 8, which is a schematic view of a scenario for referring to a screenshot result associated with a target screenshot task according to an embodiment of the present application. The task states of the target screenshot tasks associated with the N screenshot addresses may be dynamically displayed in the target task list shown in fig. 8. As shown in fig. 8, the target user may view the task details of the target screenshot task by triggering the screenshot task (i.e., the target screenshot task) with a task name of task 40 j.

For example, when the terminal receives a trigger operation for the list field where the target screenshot task is located, the trigger operation corresponding to the target screenshot task may be referred to as a task detail viewing operation, so that the task details of the target screenshot task may be displayed on the task detail page 400a shown in fig. 8. It can be understood that the terminal may also receive the progress notification information returned by the service server when executing the target screenshot task, so that the task state of the target screenshot task shown in fig. 8 may be dynamically adjusted based on the received progress notification information.

When the service server successfully executes the target screenshot task, that is, when the service server determines that the screenshot operation of each screenshot address in the target screenshot task under K machine types of information is completed, the target screenshot task can be ended, and the terminal is notified to adjust the task state of the target screenshot task to the task success state in the list field of the target screenshot task shown in fig. 8. At this time, when the terminal receives the task detail viewing operation for the target screenshot task, screenshot results corresponding to each sub-screenshot task may be displayed in the task detail page 400a shown in fig. 8, that is, K screenshot pictures associated with each sub-screenshot task may be displayed respectively. For example, the screenshot result corresponding to the sub-screenshot task 1 may be displayed in the task detail page 400a, and the screenshot result corresponding to the sub-screenshot task 2 may be displayed.

The screenshot task 1 may be a sub-screenshot task corresponding to the screenshot address 1 in the embodiment corresponding to fig. 7, as shown in fig. 8, where the screenshot task 1 may organize K screenshot pictures associated with the target page of the screenshot address 1 in the form of a task, so as to obtain k=6 screenshot pictures associated with the screenshot task 1 shown in fig. 8. The target user (for example, the user 1) may refer to the display effects of the target page of the screenshot address 1 in k=6 devices in the task detail page 400a shown in fig. 8, so that the target user may be helped to quickly know the compatibility of the target page of the screenshot address 1 in different devices. And so on, the target user can also refer to the display effects of the target page of the screenshot address 2 in k=6 devices in the task detail page 400a shown in fig. 8, so that the target user can be helped to quickly know the compatibility of the target page of the screenshot address 2 in different devices. Therefore, the embodiment of the application can intercept the screenshot pictures of the target page corresponding to each screenshot address in different devices in batches by multiplexing K machine type information when each sub-screenshot task is executed, so that the screenshot efficiency can be improved.

The task state of the target screenshot task shown in fig. 8 includes at least one of the following states: task waiting state, task executing state, task ending state; the task ending state comprises a task success state and a task failure state.

For example, when the target user performs a task confirmation operation for the task creation interface at time T1, the target screenshot task with the task name of task 40j may be added to the historical task list associated with the task creation interface at time T2 to obtain the target task list shown in fig. 8. At this time, the terminal may send a screenshot instruction carrying N screenshot addresses and K model information to the service server. Further, when the service server receives the screenshot instruction sent by the terminal at the time T2, a sub-screenshot task corresponding to each screenshot address may be created in the embodiment corresponding to fig. 7 based on the screenshot instruction, so as to obtain a task queue corresponding to the target screenshot task.

Before each sub-screenshot task is executed sequentially, the terminal may adjust the task state of the target screenshot to a task waiting state in the task bar where the target screenshot task shown in fig. 8 is located. Further, when the service server sequentially executes each sub-screenshot task, the terminal may adjust the task state of the target screenshot to the task execution state in the task bar where the target screenshot task shown in fig. 8 is located. It can be understood that when each sub-screenshot task is sequentially executed, the service server can monitor the screenshot progress of each sub-screenshot task, so that progress notification information can be sent to the terminal based on the monitored screenshot progress of each sub-screenshot task. It will be appreciated that the progress notification information may be used to reflect whether the business server has performed each of the sub-screenshot tasks in the target screenshot task.

If the service server determines that the screenshot operation on each sub-screenshot task has been completed, the terminal may adjust the task state of the target screenshot to the task end state in the task bar where the target screenshot task shown in fig. 8 is located. As shown in fig. 8, the task end state may include a task success state and a task failure state.

In the embodiment of the present application, as shown in fig. 8, when it is determined that the task is successfully executed, that is, when the target screenshot task is successfully executed, the terminal may be notified to determine, in the target task list shown in fig. 8, the task state of the target screenshot task as the task success state in the task end state. That is, as shown in fig. 8, the terminal may display a task status of "task execution succeeded" in the task bar where the task name is the task 40 j.

In addition, as shown in fig. 8, the service server may further notify the terminal to determine the task state of the target screenshot task as the task failure state in the task ending state in the target task list described in fig. 8. That is, as shown in fig. 8, the terminal may display a task status of "task execution failure" in a task bar where the task name is the task 40 c.

It can be seen that the target user (e.g., user 1 in the embodiment corresponding to fig. 4 above) may send a screenshot instruction to the service server through the terminal to remotely control the service server to perform each sub-screenshot task in the task queue. In the process of executing each sub-screenshot task, a browser in the service server can simulate logging in the target page of each screenshot address through the user identification information in the filling parameter information, so that the target page of each screenshot address can be intelligently intercepted in the browser of the service server to capture the screenshot pictures in different devices, and the screenshot efficiency can be improved. In addition, K machine type information can be multiplexed for each sub-screenshot task, so that screenshot pictures of a target page of each screenshot address can be intercepted in batches in a browser, and a subsequent target user can simulate and present the largest screenshot picture of the screenshot picture in corresponding equipment in a terminal by triggering the corresponding screenshot picture.

Further, please refer to fig. 9, which is a flowchart illustrating another data processing method according to an embodiment of the present application. As shown in fig. 9, the method involves a terminal and a service server participating in the screenshot, and the method may include:

step S201, responding to task creation operation triggered by a historical task list, and jumping a display interface where the historical task list is positioned to a task creation interface to be filled;

the terminal can respond to task creation operation triggered by the historical task list, and jump the display interface where the historical task list is located to a task creation interface to be filled. The specific process of skipping the display interface where the history task list is located to the task creation interface to be filled may refer to the description of skipping the display interface where the history task list is located to the filling interface 100a in the embodiment corresponding to fig. 4, and will not be described in detail here.

Step S202, in response to a filling operation for the task creation interface to be filled, filling parameter information associated with the task creation interface to be filled is determined, and the task creation interface to be filled carrying the filling parameter information is determined as a task creation interface;

The terminal can respond to the filling operation of the task creation interface to be filled, determine filling parameter information associated with the task creation interface to be filled, and determine the task creation interface to be filled carrying the filling parameter information as the task creation interface.

The filling parameter information associated with the task creation interface to be filled may include the task name in the area 1, the N screenshot addresses in the area 2, the user identification information in the area 3, and the K model information in the area 4 in the embodiment corresponding to fig. 5.

It may be understood that, when the target user performs the triggering operation for the "task creation" button in the task creation interface in the embodiment corresponding to fig. 4, the terminal may further perform step S203 described below, and may add the target screenshot task with the task name "AAABBB" to the history task list synchronously when performing step S203 described below, so as to obtain a target task list, so that the task states of the target screenshot tasks associated with the N screenshot addresses may be displayed in the target task list.

Step S203, responding to task confirmation operation triggered by a task creation interface, and acquiring filling parameter information filled in the task creation interface;

The filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer.

Optionally, when executing step S203, the terminal may further add a target screenshot task having the task name to the history task list to obtain a target task list, and display a task state of the target screenshot task associated with the N screenshot addresses in the target task list; further, the terminal can also receive progress notification information returned by the service server when the target screenshot task is executed, and can adjust the task state of the target screenshot task based on the progress notification information.

For easy understanding, further, please refer to fig. 10, which is a schematic diagram of a scenario for acquiring a target task list according to an embodiment of the present application. The historical task list shown in fig. 10 may be the task list under the task list module 10a in the embodiment corresponding to fig. 4. As shown in fig. 10, the target user may trigger a "create screenshot task" button in the history task list shown in fig. 10 in the business services platform. At this time, the terminal may jump the display interface where the history task list shown in fig. 10 is located to the task creation interface corresponding to the task creation module 10b in the embodiment corresponding to fig. 4 in response to the triggering operation. Further, the target user may perform a trigger operation for a "task creation" button in the task creation interface, so that the target screenshot task with the task name AAABBB (i.e., the task name is a full-scale task) may be added to the historical task list shown in fig. 10.

In the embodiment of the present application, each screenshot task in the history task list shown in fig. 10 may be collectively referred to as a history screenshot task, and a screenshot task newly created in the history task list may be referred to as a target screenshot task. Further, as shown in fig. 10, in the embodiment of the present application, the history task list where the target screenshot task carrying the task name as the full-volume task is located may be referred to as a target task list. And so on, when the target user needs to create a new target screenshot task in the target task list, the target task list can be determined to be a new history task list, and the screenshot task with the task name of the full task in the new history task list is called a new history screenshot task, so that the new history task list can be updated by the new target screenshot task. The specific process of updating the new historical task list by the terminal based on the new target screenshot task may refer to a specific implementation manner of updating the historical task list under the task list module 10b to the target task list in the embodiment corresponding to fig. 10, and will not be described in detail here.

Step S204, a screenshot instruction carrying the N screenshot addresses and the K machine type information is sent to a service server;

it may be understood that after the terminal performs the step S203, a screenshot instruction may be generated according to N screenshot addresses and K model information in the filling parameter information, so that the screenshot instruction may be sent to a service server, so that the service server may further perform the step S204, that is, the service server may perform a target screenshot task based on the screenshot instruction; the target screenshot task can comprise a plurality of sub-screenshot tasks; one sub-screenshot task may correspond to one screenshot address;

step S205, adding the N screenshot addresses and the K model information to a task queue for executing a target screenshot task based on the screenshot instruction;

specifically, the service server may extract the N screenshot addresses and the K model information based on the received screenshot instruction, so that the N screenshot addresses and the K model information may be added to a task queue for executing the target screenshot task.

It can be understood that the task queue may include a plurality of sub-screenshot tasks, so as to avoid waste of computing resources of the server, and in an embodiment of the present application, each sub-screenshot task in the task queue may be sequentially executed to obtain a screenshot result corresponding to each sub-screenshot task.

For example, a sub-screenshot task at the head of the queue may be first acquired in the task queue as a task to be screenshot, so as to execute the sub-screenshot task at the head of the queue preferentially. It can be understood that when the service server finishes executing the sub-screenshot task located at the head of the queue in the task queue, the next sub-screenshot task adjacent to the sub-screenshot task located at the head of the queue can be further used as a new task to be screenshot, until each sub-screenshot task in the task queue is selected as the task to be screenshot, the screenshot result corresponding to each sub-screenshot task can be obtained.

The specific process of sequentially executing each sub-screenshot task in the task queue by the service server to obtain a screenshot result corresponding to each sub-screenshot task and returning the screenshot result corresponding to each sub-screenshot task to the terminal may be described as:

the business server can determine a sub-screenshot task at the head of a queue in the task queue as a task to be screenshot, and determine a screenshot address corresponding to the task to be screenshot as a screenshot address; taking the user identification information in the filling parameter information, the identification information of the address to be captured and the size information of the K machine types as task parameters; further, the service server can transmit the task parameters to a browser so as to simulate logging in the target page of the address to be captured through the user identification information in the browser; further, the service server can perform screenshot operation on the target page of the address to be screenshot through the K machine type information to obtain screenshot results corresponding to the task to be screenshot; further, when the task to be captured is completed, the service server may output the task to be captured to the task queue until each sub-capture task in the task queue is used as the address to be captured, so as to obtain a capture result corresponding to each sub-capture task.

For ease of understanding, further, please refer to fig. 11, which is a schematic diagram of an overall flow of executing a target screenshot task according to an embodiment of the present application. The screenshot tool in step 10 shown in fig. 11 may be understood as a process integrated in a service server and capable of providing a screenshot service, where the screenshot tool may be in a starting state in the service server all the time, so that when a screenshot instruction sent by a terminal having a network connection relationship with the service server is received, a process for providing a screenshot service in the service server may be triggered to be invoked to perform a screenshot task. For providing an automatic screenshot service in a service server.

The steps 20 to 30 shown in fig. 11 may be referred to the descriptions of the steps S204 to S205, and will not be described in detail here. Further, as shown in step 40 of fig. 11, when the service server sequentially executes each sub-screenshot task in the task queue, the task parameters required for the screenshot may be input into the browser of the service server, for example, the user identification information (for example, 10352 shown in fig. 7) in the filling parameter information, the identification information of the address to be screenshot (for example, the identification information at the tail of each screenshot address shown in fig. 7) and the size information of the K model information may be input into the browser as the task parameters. Thus, when the browser is successfully started in the service server, step 60 shown in fig. 11 may be executed, for example, a sub-screenshot task located at the head of the queue may be determined as a task to be screenshot in the task queue, and a screenshot address (for example, screenshot address 1 described in fig. 7) corresponding to the task to be screenshot may be determined as an address to be screenshot, so as to log in the target page of the address 1 to be screenshot through the user identification information. Further, the service server may execute step 70 to intercept and store the screenshot pictures corresponding to the K model information (for example, the 6 model information shown in fig. 7 above) in the browser, respectively.

It will be appreciated, among other things, that for each sub-screenshot task, independent execution of each screenshot may be ensured by step 110 described in fig. 11. For example, each time the service server completes a screenshot of model information, the browser tab currently in the browser may be closed, and a new browser tab may be created synchronously, so as to repeatedly execute steps 60-80 shown in fig. 11, until the service server confirms that the sub-screenshot tasks corresponding to all screenshot addresses have been completed, and step 100 shown in fig. 11 may be further executed.

It can be understood that if the service server intercepts the screenshot pictures of the target page of the screenshot address 1 in the model information 1, the current tag in the browser can be closed, a new browser tag can be created to intercept the screenshot pictures of the target page of the screenshot address 1 in the model information 2, and the like, the screenshot pictures of the screenshot address 1 in the K model information can be sequentially obtained, namely, the service server can perform screenshot one model by one model in the process of performing screenshot on the target bowl surface of the screenshot address 1, so as to ensure the independence of each screenshot. Similarly, the process of acquiring the screenshot pictures of other screenshot addresses in the K model information may refer to the description of capturing the screenshot pictures of the screenshot address 1 in the K model information, which will not be described in detail here.

As shown in fig. 11, the service server may further execute step 140, that is, needs to notify the terminal to display the task status as the task failure status in the task bar where the target screenshot task is located, in the case that the browser fails to start. In addition, as shown in fig. 11, the service server may further perform step S120 when the target page for a certain screenshot address is screenshot and the screenshot fails, and may perform step S140 when the number of retries exceeds 3 (i.e., the failure threshold).

For example, in order to facilitate understanding, taking a sub-screenshot task at the head of a team as an example of a task to be screenshot, if a service server detects that machine type information (for example, machine type information 3 in the embodiment corresponding to fig. 7) with screenshot failure exists in K machine type information in the process of performing screenshot on a target page corresponding to screenshot address 1 (i.e., the address to be screenshot corresponding to the task to be screenshot), the machine type information 3 may be referred to as target machine type information, and screenshot operation may be repeatedly performed on the target page of the address to be screenshot based on the target machine type information, so that the number of times of repeated screenshot failure is counted according to the screenshot state corresponding to the repeated screenshot operation, and then the task to be screenshot is ended when the number of times is greater than a failure threshold (i.e., 3 times), and the terminal is notified to identify the task state of the target screenshot task as a task failure state in a target task list where the task to be screenshot is located.

It may be understood that, as shown in step 150 of fig. 11, when the service server performs the screenshot operation on the target page of the address to be screenshot through the K machine types of information, the monitoring process may monitor the screenshot progress of the task to be screenshot, and send progress notification information to the terminal based on the screenshot progress, for example, the service server may synchronize the task progress to the terminal every several seconds, so as to update the task state of the target screenshot task in the target task list. In other words, the terminal may receive progress notification information returned by the service server when the target screenshot task is executed, and may adjust a task state of the target screenshot task based on the progress notification information.

Step S206, receiving a screenshot result returned by the service server based on each sub-screenshot task;

the screenshot result may include screenshot pictures of the target page corresponding to the screenshot address in the K model information, respectively.

In order to facilitate understanding, the embodiment of the present application uses the above-mentioned target application scenario as a development test scenario, under the development test scenario, the service platform integrated in the above-mentioned target application may be a development test framework with a screenshot task creation function, and at this time, the target application may be a development test application. Therefore, the user terminal (e.g., the user terminal 3000a in the embodiment corresponding to fig. 1 described above) where the development test application is deployed in the integration may be used to create a new screenshot task, and the created new screenshot task may be collectively referred to as a target screenshot task. Meanwhile, the embodiment of the application can execute the target screenshot task through a screenshot tool in the service server.

The screenshot tool integrally installed in the service server may include two functional modules, where one functional module (e.g., the first functional module) may be integrally deployed in a user terminal (e.g., the user terminal 3000a shown in fig. 1) used by a target user (e.g., a developer), for example, when a target screenshot task is created by the development test framework, the terminal may generate a screenshot instruction corresponding to the target screenshot task, so as to remotely control the service server to create a task queue corresponding to the target screenshot task; another functional module (e.g., a second functional module) may be integrally deployed in a business server for providing an automatic screenshot service for executing each sub-screenshot task in the task queue. The terminal integrated with the first functional module can be called as a Web front end corresponding to the screenshot tool; the service server 2000 integrated with the second functional module may be referred to as a background terminal corresponding to the screenshot tool.

The Web front end may be a visual interface for human-computer interaction for a target user (e.g., a development user, a test user, a design user), that is, the Web front end may be used to provide a visual display interface for the target user, so as to help the target user create a new screenshot task in the Web front end, refresh the task progress of the newly created screenshot task in real time, and the background terminal is used to provide an automatic screenshot service when receiving a screenshot instruction, and return the screenshot result for each sub-screenshot task to the terminal in real time, so that automatic screenshot for a batch of Web pages can be implemented in the business server, so as to help the target user to understand the display effect of a target page corresponding to each screenshot address in different devices.

Optionally, the target user may further view, in obtaining a screenshot result corresponding to each sub-screenshot task, a maximum screenshot of a screenshot picture under a certain sub-screenshot task in a corresponding device on a task detail page corresponding to the target screenshot task. For ease of understanding, further, please refer to fig. 12, which is a schematic view of a scene of looking up a large chart on a task detail page according to an embodiment of the present application. As shown in fig. 12, the target user may trigger the screenshot picture of the screenshot address 1 in the model information 2 in the task detail page 400b, so that the largest screenshot picture of the target page of the screenshot address 1 in the device corresponding to the model information 2 may be presented in the display interface 400c shown in fig. 12. Since the screenshot results corresponding to each sub-screenshot task are organized in the form of a task, the target user can view the maximum screenshot picture of the previous model information (for example, model information 1) adjacent to the model information 2 through the trigger button a or view the maximum screenshot picture of the next model information (for example, model information 3) adjacent to the model information 2 through the trigger button B on the display interface 400c shown in fig. 12.

It can be appreciated that, when the target user (e.g., developer) views the maximum screenshot picture of a certain model information, the size of each device displayed in the display interface 400c can be ensured to be the same as the size of the entity device (e.g., mobile phone), and the real device pixel ratio can be simulated, and the background picture of the device can be matched to more truly simulate the effect of the content page of the maximum screenshot picture on the mobile phone.

Optionally, the target user can also view all screenshot results associated with the screenshot address by triggering the region where the screenshot address is located on the task detail page. For ease of understanding, further, please refer to fig. 13, which is a schematic diagram illustrating a comparison history screenshot result provided in an embodiment of the present application. As shown in fig. 13, the target user may trigger the region where the screenshot address 1 (e.g., http:///-)/752512) is located in the task detail page 400a of the terminal, so that all the historical screenshot results associated with the screenshot address 1 may be obtained from the service server, and all the historical screenshot results associated with the screenshot address 1 (e.g., the historical screenshot result 1 associated with the task name 40j and the historical screenshot result 2 associated with the task name 40 b) may be displayed in the comparison page 500a shown in fig. 13 to compare the page's change over time in the comparison page 500 a. In other words, the embodiment of the application can help a target user (for example, a development user) to quickly know the change condition of the user interaction interface (namely, the UI interface) associated with the screenshot address by means of screenshot comparison, and further can help the target user to quickly locate the change condition of the corresponding UI element searched in the UI interface.

Further, please refer to fig. 14, which is a schematic structural diagram of a data processing apparatus according to an embodiment of the present application, the data processing apparatus 1 may be integrally applied to a terminal, which may be the user terminal 3000a in the embodiment corresponding to fig. 1. As shown in fig. 14, the data processing apparatus 1 may include: the task confirmation module 10, the screenshot instruction sending module 20 and the screenshot result receiving module 30; further, the data processing apparatus 1 may further include: the system comprises a page jumping module 40, an interface filling module 50, a screenshot task adding module 60 and a task state adjusting module 70;

the task confirmation module 10 is used for responding to task confirmation operation triggered by aiming at a task creation interface and acquiring filling parameter information filled in the task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer;

the screenshot instruction sending module 20 is configured to send a screenshot instruction carrying the N screenshot addresses and the K model information to a service server, so that the service server executes a target screenshot task based on the screenshot instruction; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

The screenshot result receiving module 30 is configured to receive a screenshot result returned by the service server based on each sub-screenshot task; and the screenshot result comprises screenshot pictures of the target page corresponding to the screenshot address in the K machine type information respectively.

Optionally, the page skip module 40 is configured to skip a display interface where the history task list is located to a task creation interface to be filled in response to a task creation operation triggered for the history task list;

the interface filling module 50 is configured to determine filling parameter information associated with the task creation interface to be filled, and determine the task creation interface to be filled carrying the filling parameter information as a task creation interface in response to a filling operation for the task creation interface to be filled.

Wherein the interface filling module 50 includes: a filling interface determination unit 501, a region filling unit 502, and an interface determination unit 503;

a filling interface determining unit 501, configured to determine the task creation interface to be filled as a filling interface of a target screenshot task; the filling interface comprises a plurality of areas to be filled;

an area filling unit 502, configured to obtain filling parameter information filled in each area to be filled in response to a filling operation for each area to be filled in the filling interface; the filling parameter information comprises at least one of the following parameter information: task name, N screenshot addresses, user identification information and K machine type information; the user identification information is used for simulating to log in a target page of each screenshot address when the business server executes the target screenshot task;

Wherein the region filling unit 502 includes: a name acquisition subunit 5021, an address acquisition subunit 5022, an identification acquisition subunit 5023, a model acquisition subunit 5024, and a parameter determination subunit 5025;

the name acquisition subunit 5021 is configured to respond to a first filling operation triggered for a first area in the filling interface, and acquire a task name of the target screenshot task;

an address obtaining subunit 5022, configured to obtain, from a service server, an address database associated with a second area in the filling interface in response to a second filling operation triggered for the second area, and determine N screenshot addresses associated with the target screenshot task based on an address in the address database;

wherein the address acquisition subunit 5022 comprises: a database acquisition subunit 5026, a tag acquisition subunit 5027, an address determination subunit 5028;

a database obtaining subunit 5026, configured to obtain, from a service server, an address database associated with a second area in the filling interface in response to a second filling operation triggered for the second area, and jump the filling interface to a resource display interface for displaying an address of the address database;

The tag obtaining subunit 5027 is configured to obtain target tag information in response to a tag obtaining operation triggered by the resource display interface, and screen M addresses matched with the target tag information from the addresses of the address database based on the target tag information;

the address determining subunit 5028 is configured to obtain N addresses from the M addresses as addresses to be captured respectively in response to the selection operation for the M addresses, copy each address to be captured to the second area of the filling area, and obtain N capturing addresses associated with the target capturing task.

The specific implementation manner of the database obtaining subunit 5026, the tag obtaining subunit 5027 and the address determining subunit 5028 may refer to the description of the specific process of obtaining the N screenshot addresses in the embodiment corresponding to fig. 3, which will not be further described herein.

The identifier obtaining subunit 5023 is configured to obtain user identifier information for simulating to log in to a target page of each screenshot address in response to a third filling operation triggered for a third area in the filling interface;

a model obtaining subunit 5024, configured to obtain K model information from a plurality of model information contained in a fourth area in response to a fourth filling operation triggered for the fourth area in the filling interface;

And the parameter determining subunit 5025 is configured to determine the task name, the N screenshot addresses, the user identification information, and the K model information as filling parameter information filled in the filling interface.

The specific implementation manner of the name obtaining subunit 5021, the address obtaining subunit 5022, the identifier obtaining subunit 5023, the model obtaining subunit 5024, and the parameter determining subunit 5025 may refer to the description of each filling area in the embodiment corresponding to fig. 3, and will not be further described herein.

An interface determining unit 503, configured to determine a filling interface carrying the task name, the N screenshot addresses, the user identification information, and the K model information as the task creation interface.

The specific implementation manner of the filling interface determining unit 501 and the area filling unit 502, and the interface determining unit 503 may refer to the description of the task creation interface in the embodiment corresponding to fig. 3, which will not be described in detail here.

The screenshot task adding module 60 is configured to add a target screenshot task with the task name to the history task list to obtain a target task list, and display a task state of the target screenshot task associated with the N screenshot addresses in the target task list;

The task state adjustment module 70 is configured to receive progress notification information returned by the service server when the target screenshot task is executed, and adjust a task state of the target screenshot task based on the progress notification information.

The specific implementation manner of the task confirmation module 10, the screenshot instruction sending module 20, and the screenshot result receiving module 30 may refer to the description of step S101 to step S103 in the corresponding embodiment of fig. 3, and the description will not be repeated here; in addition, the specific implementation manner of the page skip module 40, the interface filling module 50, the screenshot task adding module 60 and the task state adjusting module 70 may refer to the description of step S201 to step S204 in the embodiment corresponding to fig. 9, and the detailed description will not be repeated here.

Further, please refer to fig. 15, which is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 15, the computer apparatus 1000 may be applied to a terminal, which may be the user terminal 3000a in the corresponding embodiment of fig. 1, and the computer apparatus 1000 may include: processor 1001, network interface 1004, and memory 1005, in addition, the computer device 1000 may further comprise: a user interface 1003, and at least one communication bus 1002. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display (Display), a Keyboard (Keyboard), and the optional user interface 1003 may further include a standard wired interface, a wireless interface, among others. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1004 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 1005 may also optionally be at least one storage device located remotely from the processor 1001. As shown in fig. 15, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 1005, which is one type of computer storage medium.

The network interface 1004 in the computer device 1000 may send screenshot instructions to the service server and the optional user interface 1003 may also include a Display screen (Display), a Keyboard (Keyboard). In the computer device 1000 shown in FIG. 15, the network interface 1004 may provide network communication functions; while user interface 1003 is primarily used as an interface for providing input to a user; and the processor 1001 may be used to invoke a device control application stored in the memory 1005 to implement:

It should be understood that the computer device 1000 described in the embodiment of the present application may perform the description of the data processing method in the embodiment corresponding to fig. 3 and fig. 9, and may also perform the description of the data processing apparatus 1 in the embodiment corresponding to fig. 14, which is not repeated herein. In addition, the description of the beneficial effects of the same method is omitted.

Furthermore, it should be noted here that: the embodiment of the present application further provides a computer storage medium, in which the aforementioned computer program executed by the data processing apparatus 1 is stored, and the computer program includes program instructions, when executed by the processor, can execute the description of the data processing method in the embodiment corresponding to fig. 3 and 9, and therefore, will not be described herein. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer storage medium according to the present application, please refer to the description of the method embodiments of the present application.

Further, please refer to fig. 16, which is a schematic diagram of another data processing apparatus according to an embodiment of the present application, the data processing apparatus 2 may be integrally applied to a service server, which may be the service server 2000 in the embodiment corresponding to fig. 1. As shown in fig. 16, the data processing apparatus 2 may include: the screenshot instruction receiving module 100, the task queue determining module 200 and the screenshot result returning module 300; further, the data processing apparatus 2 may further include: the system comprises a page jumping module 40, an interface filling module 50, a screenshot task adding module 60 and a task state adjusting module 70;

the screenshot instruction receiving module 100 is used for receiving a screenshot instruction sent by the terminal based on the filling parameter information in the task creation interface; the filling parameter information comprises N screenshot addresses and K machine type information; the N screenshot addresses are determined based on M addresses screened from an address database; n is a positive integer less than or equal to M; k is a positive integer;

a task queue determining module 200, configured to add the N screenshot addresses and K model information to a task queue for executing a target screenshot task based on the screenshot instruction; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

And the screenshot result returning module 300 is configured to sequentially execute each sub-screenshot task in the task queue, obtain a screenshot result corresponding to each sub-screenshot task, and return the screenshot result corresponding to each sub-screenshot task to the terminal.

Wherein, the screenshot result returning module 300 includes: the system comprises a to-be-screenshot determining unit 3001, a task parameter determining unit 3002, a parameter transmitting unit 3003, a page screenshot unit 3004, a task output unit 3005, a progress monitoring unit 3006, a target model determining unit 3007, a target model multiplexing unit 3008 and a screenshot ending unit 3009;

the to-be-captured determining unit 3001 is configured to determine, in the task queue, a sub-capture task located at the head of the queue as a to-be-captured task, and determine a capture address corresponding to the to-be-captured task as a to-be-captured address;

a task parameter determining unit 3002, configured to take, as task parameters, user identification information in the filling parameter information, identification information of an address to be captured, and size information of the K model information;

a parameter input unit 3003, configured to input the task parameter into a browser, so as to log in the browser through the user identification information in a simulation manner to a target page of the address to be captured;

The page screenshot unit 3004 is configured to perform screenshot operation on the target page of the address to be screenshot according to the K model information, so as to obtain a screenshot result corresponding to the task to be screenshot;

and the task output unit 3005 is configured to output the task to be captured to the task queue when the task to be captured is completed, until each sub-capture task in the task queue is used as the address to be captured, and obtain a capture result corresponding to each sub-capture task.

The progress monitoring unit 3006 is configured to monitor a screenshot progress of the task to be screenshot when the target page of the address to be screenshot is subjected to screenshot operation according to the K model information, and send progress notification information to the terminal based on the screenshot progress.

A target model determining unit 3007, configured to determine, if it is detected that there is model information with failed screenshot in the K model information, the model information with failed screenshot as target model information;

the target model multiplexing unit 3008 is configured to repeat the screenshot operation on the target page of the address to be screenshot based on the target model information, and count the number of repeated screenshot failures according to the screenshot state corresponding to the repeated screenshot operation;

And the screenshot ending unit 3009 is configured to end the task to be screenshot when the number of times is greater than the failure threshold, and notify the terminal to identify the task state of the target screenshot task as a task failure state in a target task list where the task to be screenshot is located.

The specific implementation manner of the to-be-screenshot determining unit 3001, the task parameter determining unit 3002, the parameter inputting unit 3003, the page screenshot unit 3004, the task outputting unit 3005, the progress monitoring unit 3006, the target model determining unit 3007, the target model multiplexing unit 3008, and the screenshot ending unit 3009 may refer to the above description of the specific process of obtaining the screenshot result corresponding to each sub-screenshot task, and will not be described in detail herein.

The specific implementation manner of the screenshot instruction receiving module 100, the task queue determining module 200, and the screenshot result returning module 300 may refer to the description of step S101 to step S103 in the embodiment corresponding to fig. 3, and the description will not be repeated here.

In addition, the description of the beneficial effects of the same method is omitted.

Further, please refer to fig. 17, which is a schematic diagram illustrating another computer device according to an embodiment of the present application. As shown in fig. 17, the computer device 4000 may be applied to a service server, which may be the service server 2000 in the corresponding embodiment of fig. 1, and the computer device 4000 may include: a processor 4001, a network interface 4004 and a memory 4005, and in addition, the computer apparatus 4000 may further include: a user interface 4003, and at least one communication bus 4002. Wherein the communication bus 4002 is used to enable connection communications between these components. The user interface 4003 may include a Display screen (Display), a Keyboard (Keyboard), and the optional user interface 4003 may further include a standard wired interface, a wireless interface, among others. The network interface 4004 may optionally comprise a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 4004 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one magnetic disk memory. The memory 4005 may also optionally be at least one memory device located remotely from the aforementioned processor 4001. As shown in fig. 17, an operating system, a network communication module, a user interface module, and a device control application program may be included in the memory 4005 as one type of computer storage medium.

The network interface 4004 in the computer apparatus 4000 may receive a terminal sending screenshot instruction, and the optional user interface 4003 may further include a Display screen (Display), a Keyboard (Keyboard). In the computer device 4000 shown in fig. 17, the network interface 4004 may provide network communication functions; while the user interface 4003 is primarily an interface for providing input to a user; and the processor 4001 may be used to invoke the device control application stored in the memory 4005 to implement:

It should be understood that the computer device 4000 described in the embodiment of the present application may perform the description of the data processing method in the embodiment corresponding to fig. 3 and fig. 9, and may also perform the description of the data processing apparatus 2 in the embodiment corresponding to fig. 16, which is not repeated herein. In addition, the description of the beneficial effects of the same method is omitted.

Furthermore, it should be noted here that: the embodiment of the present application further provides a computer storage medium, in which the aforementioned computer program executed by the data processing apparatus 2 is stored, and the computer program includes program instructions, when executed by the processor, can execute the description of the data processing method in the embodiment corresponding to fig. 3 and fig. 9, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the computer storage medium according to the present application, please refer to the description of the method embodiments of the present application.

Further, referring to FIG. 18, a schematic diagram of another data processing system according to an embodiment of the present application is shown. The data processing system 3 may comprise a data processing device 1a and a data processing device 1b. The data processing device 1a may be the data processing device 1 in the embodiment corresponding to fig. 14, it is understood that the data processing device 1a may be integrated in the user terminal 3000a in the embodiment corresponding to fig. 1, and therefore, a detailed description will not be given here, wherein the data processing device 1b may be the data processing device 2 in the embodiment corresponding to fig. 16 in the embodiment corresponding to fig. 1, and it is understood that the data processing device 1b may be integrated in the service server 2000 in the embodiment corresponding to fig. 1, and therefore, a detailed description will not be given here. In addition, the description of the beneficial effects of the same method is omitted. For technical details not disclosed in the embodiments of the data processing system according to the present application, please refer to the description of the method embodiments of the present application.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), or the like.

The foregoing disclosure is illustrative of the present application and is not to be construed as limiting the scope of the application, which is defined by the appended claims.

Claims

1. A data processing method, which is applied to a terminal, comprising:

responding to task confirmation operation triggered by aiming at a task creation interface, and acquiring filling parameter information which is filled in the task creation interface and is associated with a target screenshot task; the filling parameter information comprises N screenshot addresses filled and displayed in the second area, user identification information filled and displayed in the third area and K machine type information filled and displayed in the fourth area; the K machine type information is selected by a target user from a plurality of machine type information displayed in the fourth area; the second region, the third region and the fourth region are regions in a plurality of regions to be filled of the task creation interface; the N screenshot addresses are determined from M addresses which are screened in an address database and matched with target tag information; n is a positive integer less than or equal to M; k is a positive integer; the target tag information is tag information input by the target user; the address database is used for recording addresses carrying tag information in an H5 project under a development test scene; the H5 project comprises a WeChat reading project;

Sending a screenshot instruction carrying the N screenshot addresses, the user identification information and the K machine type information to a service server, so that the service server builds a task queue for executing the target screenshot tasks based on the screenshot instruction, invokes a screenshot tool for carrying out batch screenshot through the task queue, when each sub-screenshot task in the task queue is executed sequentially through the screenshot tool, logs in a target page of each screenshot address corresponding to each sub-screenshot task through the user identification information in a simulated manner, multiplexes size information of the K machine type information, acquires screenshot pictures of the target page of each screenshot address in the K machine type information in batches, acquires screenshot results of each sub-screenshot task based on screenshot pictures of the target page of each screenshot address in the K machine type information obtained by batch interception; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address; the screenshot result comprises screenshot pictures of a target page corresponding to a screenshot address which is intercepted in batches in the K machine type information;

And receiving a screenshot result of each sub screenshot task returned by the service server, and displaying the screenshot result of each sub screenshot task in a task detail page corresponding to the target screenshot task when receiving task detail viewing operation of the target user for the target screenshot task.

2. The method as recited in claim 1, further comprising:

3. The method of claim 2, wherein determining filling parameter information associated with the task creation interface to be filled in response to a filling operation for the task creation interface to be filled, determining the task creation interface to be filled that carries the filling parameter information as a task creation interface, comprises:

4. A method according to claim 3, wherein said obtaining filling parameter information filled in each region to be filled in response to a filling operation for each region to be filled in the filling interface comprises:

5. The method of claim 4, wherein the responding to a second fill operation triggered for a second region in the fill interface, obtaining an address database associated with the second region from a service server, determining N screenshot addresses associated with the target screenshot task based on addresses in the address database, comprises:

6. The method as recited in claim 2, further comprising:

7. The method of claim 6, wherein the task state of the target screenshot task comprises at least one of: task waiting state, task executing state, task ending state; the task end state includes a task success state and a task failure state.

8. A data processing method, the method being applied to a service server, comprising:

the method comprises the steps that a receiving terminal sends a screenshot instruction based on filling parameter information associated with a target screenshot task in a task creation interface; the filling parameter information comprises N screenshot addresses filled and displayed in the second area, user identification information filled and displayed in the third area and K machine type information filled and displayed in the fourth area; the K machine type information is selected by a target user from a plurality of machine type information displayed in the fourth area; the second region, the third region and the fourth region are regions in a plurality of regions to be filled of the task creation interface; the N screenshot addresses are determined based on M addresses which are screened from an address database and matched with target tag information; n is a positive integer less than or equal to M; k is a positive integer; the target tag information is tag information input by the target user; the address database is used for recording addresses carrying tag information in an H5 project under a development test scene; the H5 project comprises a WeChat reading project;

Adding the N screenshot addresses, the user identification information and the K machine type information to a task queue for executing a target screenshot task based on the screenshot instruction, and calling a screenshot tool for performing batch screenshot through the task queue; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

when each sub-screenshot task in the task queue is sequentially executed through the screenshot tool, logging in a target page of each screenshot address corresponding to each sub-screenshot task through the user identification information in a simulation mode, multiplexing size information of the K machine type information, intercepting in batches to obtain screenshot pictures of the target page of each screenshot address in the K machine type information, acquiring screenshot results of each sub-screenshot task based on screenshot pictures of the target page of each screenshot address in the K machine type information obtained by intercepting in batches, and returning the screenshot results of each sub-screenshot task to the terminal, so that the terminal displays screenshot results of each sub-screenshot task in a task detail page corresponding to the target screenshot task when receiving task checking operation of the target user for the target screenshot task; and the screenshot result comprises screenshot pictures of the target page corresponding to the screenshot address intercepted in batches in the K machine type information.

9. The method of claim 8, wherein when each sub-screenshot task in the task queue is sequentially executed by the screenshot tool, the user identification information simulates to log in a target page of each screenshot address corresponding to each sub-screenshot task, and multiplexes size information of the K model information, and batch intercepts to obtain screenshot pictures of the target page of each screenshot address in the K model information, and based on the screenshot pictures of the target page of each screenshot address in the K model information obtained by batch intercept, obtains a screenshot result of each sub-screenshot task, and returns the screenshot result of each sub-screenshot task to the terminal, including:

when each sub-screenshot task in the task queue is sequentially executed through the screenshot tool, determining the sub-screenshot task at the head of the queue as a task to be screenshot in the task queue, and determining a screenshot address corresponding to the task to be screenshot as a screenshot address;

multiplexing the size information of the K machine type information, carrying out screenshot operation on the target page of the address to be screenshot, obtaining screenshot pictures of the target page of the address to be screenshot in the K machine type information in batches, and taking the screenshot pictures of the target page of the address to be screenshot in the K machine type information in batches as screenshot results of the task to be screenshot;

and when the task to be captured is completed, outputting the task to be captured to the task queue until each sub-capture task in the task queue is used as the task to be captured, and obtaining the capture result of each sub-capture task.

10. The method as recited in claim 9, further comprising:

and when the size information of the K machine types is multiplexed, and the screenshot operation is carried out on the target page of the address to be screenshot, monitoring the screenshot progress of the task to be screenshot, and sending progress notification information to the terminal based on the screenshot progress.

11. The method as recited in claim 10, further comprising:

12. A data processing apparatus, the apparatus being applied to a terminal, comprising:

the task confirmation module is used for responding to task confirmation operation triggered by aiming at a task creation interface and acquiring filling parameter information which is filled in the task creation interface and is associated with a target screenshot task; the filling parameter information comprises N screenshot addresses filled and displayed in the second area, user identification information filled and displayed in the third area and K machine type information filled and displayed in the fourth area; the K machine type information is selected by a target user from a plurality of machine type information displayed in the fourth area; the second region, the third region and the fourth region are regions in a plurality of regions to be filled of the task creation interface; the N screenshot addresses are determined based on M addresses which are screened from an address database and matched with target tag information; n is a positive integer less than or equal to M; k is a positive integer; the target tag information is tag information input by the target user; the address database is used for recording addresses carrying tag information in an H5 project under a development test scene; the H5 project comprises a WeChat reading project;

The screenshot instruction sending module is used for sending screenshot instructions carrying the N screenshot addresses, the user identification information and the K machine type information to a service server, so that the service server builds a task queue for executing target screenshot tasks based on the screenshot instructions, a screenshot tool for carrying out batch screenshot is called through the task queue, when each sub-screenshot task in the task queue is executed sequentially through the screenshot tool, a target page of each screenshot address corresponding to each sub-screenshot task is simulated and logged in through the user identification information, size information of the K machine type information is multiplexed, screenshot pictures of the target page of each screenshot address in the K machine type information are obtained through batch interception, and screenshot results of each sub-screenshot task are obtained based on screenshot pictures of the target page of each screenshot address in the K machine type information obtained through batch interception; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address; the screenshot result comprises screenshot pictures of a target page corresponding to a screenshot address which is intercepted in batches in the K machine type information;

And the screenshot result receiving module is used for receiving the screenshot result of each sub-screenshot task returned by the service server, and displaying the screenshot result of each sub-screenshot task in a task detail page corresponding to the target screenshot task when receiving the task detail checking operation of the target user for the target screenshot task.

13. A data processing apparatus, the apparatus being applied to a service server, comprising:

the screenshot instruction receiving module is used for receiving a screenshot instruction sent by the terminal based on filling parameter information associated with a target screenshot task in the task creation interface; the filling parameter information comprises N screenshot addresses filled and displayed in the second area, user identification information filled and displayed in the third area and K machine type information filled and displayed in the fourth area; the K machine type information is selected by a target user from a plurality of machine type information displayed in the fourth area; the second region, the third region and the fourth region are regions in a plurality of regions to be filled of the task creation interface; the N screenshot addresses are determined based on M addresses which are screened from an address database and matched with target tag information; n is a positive integer less than or equal to M; k is a positive integer; the target tag information is tag information input by the target user; the address database is used for recording addresses carrying tag information in an H5 project under a development test scene; the H5 project comprises a WeChat reading project;

The task queue determining module is used for adding the N screenshot addresses, the user identification information and the K machine type information to a task queue for executing a target screenshot task based on the screenshot instruction, and calling a screenshot tool for performing batch screenshot through the task queue; the target screenshot task comprises a plurality of sub screenshot tasks; one sub-screenshot task corresponds to one screenshot address;

the screenshot result returning module is used for simulating and logging in a target page of each screenshot address corresponding to each sub-screenshot task through the user identification information when each sub-screenshot task in the task queue is sequentially executed through the screenshot tool, multiplexing size information of the K machine type information, intercepting batched screenshot pictures of the target page of each screenshot address in the K machine type information, acquiring screenshot results corresponding to each sub-screenshot task based on screenshot pictures of the target page of each screenshot address in the K machine type information obtained through batched interception, returning the screenshot results corresponding to each sub-screenshot task to the terminal, and enabling the terminal to display the screenshot results of each sub-screenshot task in the task detail page corresponding to the target screenshot task when receiving task detail viewing operation of the target user for the target screenshot task; and the screenshot result comprises screenshot pictures of the target page corresponding to the screenshot address intercepted in batches in the K machine type information.

14. A computer device, comprising: a processor, a memory, and a network interface;

the processor is connected to a memory for providing data communication functions, a network interface for storing program code, and for invoking the program code to perform the method according to any of claims 1-11.

15. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program comprising program instructions which, when executed by a processor, perform the method of any of claims 1-11.