A page text defect determination method, system and related device

Abstract

One or more embodiments of the specification disclose a page text defect determination method, system and related device, the method comprising: a client initiates a defect determination request to a server to request the server to obtain a matched text defect from a text defect pool, and to obtain page data of a page where the text defect is located from a page data set according to the text defect, so that the client restores the page according to the page data, determines the defect content corresponding to the marked text defect in the restored page, takes a screenshot of the page marked with the defect content, and sends the page screenshot to the server for storage. Thus, the defect is reproduced by the page restoration, the defect content is determined and marked in the restored page according to the text defect, and the screenshot is stored, which facilitates the developers to quickly and accurately obtain the defect content, improves the detection performance of the text defect, accurately determines and marks the text defect, and realizes comprehensive, complete and effective detection of the text defect.

Description

Technical Field

[0001] This document relates to the field of computer technology, and in particular to a method, system and related apparatus for determining defects in page text. Background Technology

[0002] Detecting missing translations in multilingual text on web pages is a complex and challenging technical project, especially for pages of applications (APPs) with a large audience. There are often text defects such as missing translations or font errors in the multilingual text.

[0003] The commonly used detection method is to obtain the text language configuration file of the app and compare each language text item with the others. However, this method has high manual costs, a limited scope of inspection, cannot cover all text on the page, and has poor detection performance and efficiency. Summary of the Invention

[0004] The purpose of one or more embodiments of this specification is to provide a method, system, and related apparatus for determining page text defects, so as to improve the detection performance of text defects, accurately determine and mark text defects, and achieve comprehensive and complete effective identification of text defects.

[0005] To solve the above-mentioned technical problems, one or more embodiments of this specification are implemented as follows:

[0006] Firstly, a method for identifying defects in page copywriting is proposed, applicable to client-side applications. The method includes:

[0007] A defect determination request is initiated to the server, wherein the defect determination request is used to instruct the server to obtain a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and to obtain the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect.

[0008] Receive the text defects and page data returned by the server;

[0009] The page data is parsed, and the page containing the text defect is reconstructed based on the parsing results;

[0010] Identify and mark the defective content corresponding to the copywriting defect on the restored page, and upload a screenshot to the server.

[0011] Secondly, a method for determining page text defects is proposed, applicable to the server side. The method includes:

[0012] Receive defect determination requests initiated by clients;

[0013] Based on the application identifier carried in the defect determination request, a matching copy defect is obtained from the copy defect pool, and based on the copy defect, the page data of the page where the copy defect is located is obtained from the retrieved page data set.

[0014] The copywriting defect and page data are sent to the client so that the client can parse the page data, reconstruct the page where the copywriting defect is located based on the parsing result; and identify the defective content corresponding to the copywriting defect in the reconstructed page, and upload a screenshot to the server.

[0015] The system receives a screenshot of a page uploaded by the client, wherein the defective content in the screenshot is marked.

[0016] Thirdly, a device for determining page text defects is proposed, including:

[0017] The sending module is used to initiate a defect determination request to the server. The defect determination request is used to instruct the server to obtain a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and to obtain the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect.

[0018] The receiving module is used to receive the text defects and page data returned by the server;

[0019] The restoration module is used to parse the page data and restore the page where the copywriting defect is located based on the parsing results;

[0020] The tagging module is used to identify and tag the defective content corresponding to the copywriting defect in the restored page, and upload a screenshot to the server.

[0021] Fourthly, a device for determining defects in page text is proposed, comprising:

[0022] The receiving module is used to receive defect determination requests initiated by the client;

[0023] The acquisition module is used to obtain a matching copywriting defect from the copywriting defect pool based on the application identifier carried in the defect determination request, and to obtain the page data of the page where the copywriting defect is located from the retrieved page data set based on the copywriting defect.

[0024] The sending module is used to send the text defect and page data to the client, so that the client can parse the page data, reconstruct the page where the text defect is located based on the parsing result; and identify and mark the defective content corresponding to the text defect in the reconstructed page, and take a screenshot.

[0025] The receiving module is also used to receive a screenshot of a page uploaded by the client, wherein the defective content in the screenshot carries a mark.

[0026] Fifthly, a system for identifying defects in page text is proposed, comprising: a client-side and a server-side component; wherein,

[0027] The client is used to initiate a defect determination request to the server;

[0028] The server is used to receive a defect determination request initiated by the client, and retrieve a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and retrieve the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect.

[0029] The client is also configured to receive the copywriting defects and page data returned by the server; parse the page data, reconstruct the page where the copywriting defects are located based on the parsing results; identify and mark the defective content corresponding to the copywriting defects in the reconstructed page, and upload a screenshot to the server.

[0030] The server is also used to receive screenshots of pages uploaded by the client, wherein the defective content in the screenshots carries a marker.

[0031] Sixthly, an electronic device is proposed, comprising:

[0032] Processor; and

[0033] A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the page text defect determination method described in the first or second aspect.

[0034] In a seventh aspect, a computer-readable storage medium is proposed, which stores one or more programs that, when executed by an electronic device including multiple applications, cause the electronic device to perform the page text defect determination method described in the first or second aspect.

[0035] As can be seen from the technical solutions provided by one or more embodiments in the above specification, the client initiates a defect determination request to the server, requesting the server to retrieve a matching text defect from the text defect pool. Based on the text defect, the server retrieves the page data of the page containing the text defect from the retrieved page data set. Then, the text defect and page data are returned to the client, allowing the client to reconstruct the page based on the page data. The client then identifies the defect content corresponding to the marked text defect in the reconstructed page, takes a screenshot of the page with the marked defect content, and sends the screenshot to the server for archiving. Thus, by reproducing the defect through page reconstruction, identifying the marked defect content in the reconstructed page based on the text defect, and taking a screenshot for archiving, developers can quickly and accurately identify the defect content, improving the detection performance of text defects, accurately identifying and marking text defects, and achieving comprehensive and effective detection of text defects. Attached Figure Description

[0036] To more clearly illustrate the technical solutions in one or more embodiments or prior art of this specification, the accompanying drawings used in the description of one or more embodiments or prior art will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a schematic diagram of the system architecture to which the page text defect determination scheme provided in the embodiments of this specification applies.

[0038] Figure 2 This is one of the step diagrams of a method for determining page text defects provided in the embodiments of this specification.

[0039] Figure 3 This is the second schematic diagram of the steps of a method for determining page text defects provided in the embodiments of this specification.

[0040] Figure 4 This is an interactive flowchart of a page text defect determination scheme provided in the embodiments of this specification.

[0041] Figure 5 This is a flowchart illustrating a method for determining page text defects, as provided in the embodiments of this specification.

[0042] Figure 6 This is one of the structural schematic diagrams of the page text defect determination device provided in the embodiments of this specification.

[0043] Figure 7 This is the second structural schematic diagram of the page text defect determination device provided in the embodiments of this specification.

[0044] Figure 8 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this specification. Detailed Implementation

[0045] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described one or more embodiments are only some embodiments of this specification, and not all embodiments. All other embodiments obtained by those skilled in the art based on one or more embodiments of this specification without creative effort should fall within the protection scope of this document.

[0046] Given the poor detection performance and efficiency of current page text defect identification schemes, this specification proposes a targeted solution. The general idea is as follows: The client initiates a defect identification request to the server, requesting the server to retrieve a matching text defect from a text defect pool. Based on this defect, the server retrieves the page data of the page containing the defect from the retrieved page data set. Then, the client returns the text defect and page data to the client, allowing the client to reconstruct the page based on the page data. The client then identifies and marks the defective content corresponding to the text defect on the reconstructed page, takes a screenshot of the marked page, and sends the screenshot to the server for archiving. Thus, by reproducing the defect through page reconstruction, identifying and marking the defective content on the reconstructed page based on the text defect, and taking a screenshot for archiving, developers can quickly and accurately identify the defective content, improving the detection performance of text defects, accurately identifying and marking text defects, and achieving comprehensive and effective detection of text defects.

[0047] Reference Figure 1The diagram illustrates the system architecture applicable to the page text defect determination scheme provided in this embodiment. This system architecture may include a client 102 and a server 104. The client 102 can initiate a defect determination request to the server 104. The server 104 receives the request and retrieves a matching text defect from a text defect pool based on the application identifier carried in the request. Based on the text defect, the server retrieves the page data of the page containing the text defect from the retrieved page data set. Next, the client 102 receives the text defect and page data returned by the server 104, parses the page data, and reconstructs the page containing the text defect based on the parsing results. Then, the client 102 identifies and marks the defect content corresponding to the text defect in the reconstructed page and uploads a screenshot to the server 104. The server 104 receives and retains the screenshot, enabling developers to quickly and accurately identify the defect content, improve the detection performance of text defects, accurately determine and mark text defects, and achieve comprehensive and effective detection of text defects.

[0048] In the embodiments of this specification, client 102 can be a client of various application software, such as social software clients, news clients, shopping clients, tool clients, etc. It should be understood that, in addition to the functions inherent in the client type itself, client 102 also possesses the aforementioned functions to detect and locate defects in page text. Server 104 can be, for example, a conventional server, cloud server, cloud host, virtual center, etc. The composition of server 104 mainly includes a processor, hard disk, memory, system bus, etc., similar to a general computer architecture.

[0049] Example 1

[0050] Reference Figure 2 The diagram shown illustrates the steps of a method for determining page text defects according to an embodiment of this specification. It should be understood that this method can be applied to client-side applications, and the method may include the following steps:

[0051] Step 202: Initiate a defect determination request to the server, wherein the defect determination request is used to instruct the server to obtain a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and to obtain the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect.

[0052] Combination Figure 4 and Figure 5As shown, a defect determination request can carry the application identifier of the client's corresponding application to request the server for the corresponding text defects. This is because the text defect pool can consist of multiple text defects identified in advance through text defect identification of target pages with text defects uploaded by clients in user or test environments. In this text defect pool, each text defect can correspond to a page identifier, meaning there is a one-to-one mapping relationship between text defects and page identifiers. However, considering that the server collects and stores similar text defects not only for clients of a single app, but may face text defects from clients of multiple or even various apps, the text defect pool may contain text defects identified from page text uploaded by clients of different apps. Alternatively, the server can set up different text defect pools for different apps, i.e., one text defect pool for each app. When the server receives a page text, it can save the text defects identified based on that page text to the corresponding text defect pool according to the application identifier in the page text. Thus, after the client sends a copy defect determination request to the server, the server can retrieve a matching copy defect from the copy defect pool based on the application identifier carried in the request. The copy defect pool can be stored locally on the server or in the corresponding cloud space.

[0053] After obtaining the text defect on the server side, the page data of the page containing the defect can be retrieved from the page data set based on the defect. Since the text defect carries a page identifier, and each page data in the page data set is mapped to a unique page identifier, the page data corresponding to that page identifier can be retrieved from the page data set based on the page identifier in the text defect. The page data set can consist of multiple page data uploaded in advance by the client in a user environment or a test environment. In this page data set, each page data can correspond to a page identifier, meaning there is a one-to-one mapping relationship between page data and page identifiers. Similarly, considering that the server may collect and store page data from multiple or even various types of app clients, the page data set may contain page data uploaded by clients belonging to different apps. Alternatively, the server can set different page data sets for different apps, meaning each app corresponds to a separate page data set.

[0054] It should be understood that in the embodiments of this specification, the copywriting defects may include one or more combinations of defects such as missing translations of multilingual copywriting, incorrect font, or incorrect font size.

[0055] It should be understood that defect determination requests can be initiated periodically by the client's test users, i.e., developers, with the specific initiation cycle set according to testing requirements. Alternatively, they can be triggered by a notification sent to the client based on an update to the defect task on the server. The embodiments in this specification do not limit this approach.

[0056] Step 204: Receive the text defects and page data returned by the server.

[0057] Step 206: Analyze the page data and reconstruct the page where the copywriting defect is located based on the analysis results.

[0058] After receiving the page data, it can be parsed, and the page containing the copywriting defect can be reconstructed through page rendering based on the parsing results. The method of page reconstruction is not limited, as long as the page scenario containing the copywriting defect can be reproduced based on the parsing results.

[0059] Step 208: Identify and mark the defective content corresponding to the copywriting defect in the restored page, and upload a screenshot to the server.

[0060] Optionally, when determining and marking the defective content corresponding to the copywriting defect in the restored page and uploading a screenshot to the server in step 208, the page location of the copywriting defect can be extracted from the restored page based on the defective content of the copywriting defect; the defective content corresponding to the copywriting defect in the restored page can be marked based on the extracted page location; a screenshot of the marked page can be taken and uploaded to the server.

[0061] Alternatively, you can first take a screenshot of the restored page, then determine the page location of the copywriting defect from the screenshot based on the defective content of the copywriting defect, mark the corresponding defective content in the screenshot, and then upload it to the server for storage.

[0062] It should be understood that steps 202-208 above can be a copywriting defect determination scheme executed in the client's test environment.

[0063] Optionally, before step 202, or during the execution of steps 202-208 above, the client may also upload the page data of the target page to the server, so that the server updates the page data set with the received page data; wherein, the page data in the page data set is mapped with page identifiers. In this case, the client can be in a user environment or a test environment, and there is no limitation on this.

[0064] Optionally, before step 202, or during the execution of steps 202-208 above, the client may also extract the page text of the target page and upload it to the server, so that the server can identify text defects based on the page text and update the identified text defects to the text defect pool; wherein, the text defects in the text defect pool are mapped with page identifiers. In this case, the client can be in a user environment or a test environment, and there is no limitation on this.

[0065] It should be noted that the storage and retrieval of page data in the embodiments of this specification can be implemented offline or executed in real time.

[0066] The client initiates a defect detection request to the server, requesting the server to retrieve a matching text defect from the text defect pool. Based on this defect, the server then retrieves the page data of the page containing the defect from the retrieved page data set. The client then returns the text defect and page data to the client, allowing the client to reconstruct the page based on the page data. The client then identifies and marks the defective content corresponding to the text defect on the reconstructed page, takes a screenshot of the marked page, and sends the screenshot to the server for archiving. Thus, by reproducing defects through page reconstruction, identifying and marking the defective content on the reconstructed page based on the text defect, and taking a screenshot for archiving, developers can quickly and accurately identify the defective content, improving the performance of text defect detection, accurately locating and marking text defects, and achieving comprehensive and effective detection of text defects.

[0067] Reference Figure 3 The diagram shown illustrates the steps of a method for determining page text defects according to an embodiment of this specification. It should be understood that this method can be applied to the server side, and the method may include the following steps:

[0068] Step 302: Receive the defect determination request initiated by the client.

[0069] Step 304: Based on the application identifier carried in the defect determination request, retrieve the matching copy defect from the copy defect pool, and based on the copy defect, retrieve the page data of the page where the copy defect is located from the retrieved page data set.

[0070] Combination Figure 4 and Figure 5As shown, the copywriting defect pool can consist of multiple copywriting defects identified in advance through copywriting defect identification of target pages uploaded by clients in user or test environments. In this pool, each copywriting defect corresponds to a page identifier, meaning there is a one-to-one mapping between copywriting defects and page identifiers. However, considering that the server may collect and store similar copywriting defects not only for clients of a single app but also for clients of multiple or even various apps, the copywriting defect pool may contain copywriting defects identified from page text uploaded by clients of different apps. Alternatively, the server can set up different copywriting defect pools for different apps, with one pool for each app. When the server receives a page text, it can save the copywriting defects identified based on that page text to the corresponding copywriting defect pool according to the application identifier in the page text. Thus, when a client sends a copywriting defect identification request to the server, it can retrieve the matching copywriting defect from the copywriting defect pool based on the application identifier carried in the request. The copywriting defect pool can be stored locally on the server or in the corresponding cloud space on the server.

[0071] After obtaining the text defect on the server side, the page data of the page containing the defect can be retrieved from the page data set based on the defect. Since the text defect carries a page identifier, and each page data in the page data set is mapped to a unique page identifier, the page data corresponding to that page identifier can be retrieved from the page data set based on the page identifier in the text defect. The page data set can consist of multiple page data uploaded in advance by the client in a user environment or a test environment. In this page data set, each page data can correspond to a page identifier, meaning there is a one-to-one mapping relationship between page data and page identifiers. Similarly, considering that the server may collect and store page data from multiple or even various types of app clients, the page data set may contain page data uploaded by clients belonging to different apps. Alternatively, the server can set different page data sets for different apps, meaning each app corresponds to a separate page data set.

[0072] Step 306: Send the copywriting defect and page data to the client so that the client can parse the page data, restore the page where the copywriting defect is located based on the parsing result; and identify and mark the defective content corresponding to the copywriting defect in the restored page, and upload a screenshot to the server.

[0073] The specific implementation of step 306 can be referred to step 206, and will not be elaborated here.

[0074] Step 308: Receive a screenshot of the page uploaded by the client, wherein the defective content in the screenshot carries a mark.

[0075] In the embodiments of this specification, the server may also receive page data of the target page uploaded by the client before step 202, or during the execution of steps 202-208, and update the page data set; wherein the page data in the page data set is mapped with a page identifier.

[0076] In the embodiments of this specification, the server may also receive the page text of the target page uploaded by the client before step 202, or during the execution of steps 202-208, identify text defects based on the page text, and update the identified text defects to the text defect pool; wherein, the text defects in the text defect pool are mapped with page identifiers.

[0077] When identifying text defects based on page text, text detection algorithms can be used to identify text defects, or machine learning models can be trained to detect and identify text defects.

[0078] It should be understood that in the embodiments of this specification, copywriting defects may include one or more combinations of defects such as: missing translation of multilingual copywriting, incorrect copywriting font or font size, copywriting quality optimization, and copywriting truncation.

[0079] Optionally, after each update of the copywriting defect pool, the copywriting defects contained in the copywriting defect pool can be scanned periodically; the copywriting defects in the copywriting defect pool can be aggregated based on the page identifier mapped by the copywriting defects; specifically, copywriting defects with the same page identifier can be aggregated together to form aggregated copywriting defects, and the aggregation here can be simply understood as summarization.

[0080] Furthermore, for the aggregated copywriting defect pool, when retrieving a matching copywriting defect from the copywriting defect pool based on the application identifier carried in the defect determination request, the matching aggregated copywriting defect can be retrieved from the copywriting defect pool based on the application identifier carried in the defect determination request. The subsequent steps are similar to those described above and will not be repeated here.

[0081] Considering that when identifying and marking textual defects on the client-side, it may be technically impossible to identify and mark all textual defects on the restored page at once, resulting in omissions, the server can perform compensatory marking after receiving the page screenshot uploaded by the client. Specifically, based on the content of the textual defects, the server can verify whether there are any unmarked textual defects in the page screenshot; if so, the server can mark the unmarked textual defects in the page screenshot according to the page location determined by the verification result.

[0082] The client initiates a defect detection request to the server, requesting the server to retrieve a matching text defect from the text defect pool. Based on this defect, the server then retrieves the page data of the page containing the defect from the retrieved page data set. The client then returns the text defect and page data to the client, allowing the client to reconstruct the page based on the page data. The client then identifies and marks the defective content corresponding to the text defect on the reconstructed page, takes a screenshot of the marked page, and sends the screenshot to the server for archiving. Thus, by reproducing defects through page reconstruction, identifying and marking the defective content on the reconstructed page based on the text defect, and taking a screenshot for archiving, developers can quickly and accurately identify the defective content, improving the performance of text defect detection, accurately locating and marking text defects, and achieving comprehensive and effective detection of text defects.

[0083] Reference Figure 4 The diagram shown is a flowchart illustrating the process for determining page text defects according to an embodiment of this specification.

[0084] The page text defect detection function can be integrated into various apps via a Software Development Kit (SDK) to interact with the corresponding detection server and identify page text defects. The SDK can be functionally categorized into a page data reporting SDK, a page text reporting SDK, and a page restoration SDK. Therefore, in an app with page text defects to be detected, all three SDKs can be integrated. Alternatively, in an app used in a testing environment, only the page restoration SDK can be integrated. Furthermore, in apps used in testing or user environments, both the page data reporting SDK and the page text reporting SDK can be integrated.

[0085] Considering the limited volume of page data and text collected in the test environment, the solution illustrated in this detection process diagram can involve data interaction under different environments. Specifically, the page data set and text defect pool maintained by the server can be determined through interaction between the client and server in the user environment (i.e., user scenario). Based on the determined page dataset and text defect pool, reconstructing the page and identifying text defects is achieved through interaction between the client and server in the test environment (i.e., test scenario).

[0086] like Figure 4 As shown, the left side represents the client-side, which could be, for example, the client of one type of app among various types of apps containing page text; the right side represents the server-side, where the server can be any processing platform capable of handling page data and page text, and collaborating with the client to detect and determine defects in the page text. No specific limitations are made here. Figure 4 The process can mainly include two workflows. The first workflow involves creating or updating the page data set and the copywriting defect pool. This workflow can be a continuous online real-time process or an offline periodic process. Figure 4 This first process is conducted within a user scenario. The second processing step involves restoring the page and identifying any textual defects. Figure 4 This process is performed in a test scenario.

[0087] In user scenarios, the client intercepts page data requests from users accessing pages via the page data reporting SDK and reports the intercepted page data to the server. It should be understood that in the embodiments of this specification, page data requests can be implemented through gateway middleware. The page data reported by the client may include: page data request ID, request parameters, result information, page URL, page ID, etc. Considering that the server can simultaneously determine text defects in page text for multiple types of apps, the server can maintain page data for multiple applications simultaneously. Specifically, this can be achieved by creating different application page data sets for differentiated maintenance, or by maintaining page data for all types of apps in one page data set by marking application identifiers. Furthermore, in addition to the above information, the page data may also include application identifiers. After receiving the page data, the server can organize the page data and save it to the corresponding page data set according to the page data set creation rules. The page data set can be stored locally on the server or in the server's cloud storage space. In fact, after saving the page data on the server, it can also return a successful reporting response to the client.

[0088] Similarly, in user scenarios, after reporting the page data accessed by the user each time via the page data reporting SDK, the client can also report the page text of the accessed page via the copy reporting SDK. The page text reported by the client can include: page text request ID, page URL, page ID, and supplementary information such as text language, text location, and text ID. The reported page text can be a single-screen display or a full-screen display (composed of multiple single screens arranged sequentially). Upon receiving the page text, the server performs defect identification. Specifically, it can use pre-defined processing rules in the rule center to pre-process and post-process the page text. Pre-processing can use various filtering rules to perform simple word filtering in the page text. Then, post-processing rules include text rules and XML Path Language (XPath) rules for text processing, followed by dictionary matching, terminology database matching, and language detection. Finally, a Natural Language Processing (NLP) model is used for identification and detection to ultimately determine text defects. It should be understood that this only introduces one feasible copywriting defect identification scheme. In addition, defect identification can be performed through other methods, or other types of defects (font errors, font size errors, etc.). After identifying copywriting defects for each page, these defects can be saved. Similar to the method of saving the page data set mentioned above, different copywriting defect pools can be created according to different application types. For example, APP1 corresponds to copywriting defect pool 1, APP2 corresponds to copywriting defect pool 2, APP3 corresponds to copywriting defect pool 3, and so on. Alternatively, copywriting defects for page texts corresponding to different types of applications can be stored uniformly in a single copywriting defect pool. This is not a limitation and can be flexibly configured according to actual needs. When saving each copywriting defect, a correspondence can be established between the page ID and the defect content (e.g., defective copywriting language, defective copywriting location, defective copywriting details, etc.). This allows for searching based on the page ID.

[0089] Based on the above, a page data set and a copywriting defect pool can be created. Furthermore, the page data set and copywriting defect pool can be updated online in real-time through client-side reporting of user page visits, allowing clients in the test environment to promptly and accurately detect and locate copywriting defects. After creating the copywriting defect pool, defects can be aggregated based on page ID, allowing defects belonging to the same page to be grouped together as a single task. It should be noted that the copywriting defect pool contains multiple defects; each defect can function as a separate defect task, or multiple defects belonging to the same page can be grouped together as a single defect task using the aggregation method described above.

[0090] Once the server has created the page data set and the copywriting defect pool, the second processing flow can begin. This involves using a client in the test scenario (which is part of the same app as the client in the user scenario) to interact with the server and detect and locate copywriting defects. Specifically, in the test scenario, developers can use the page restoration SDK on the client to retrieve defect tasks from the server. This can be done periodically through polling or triggered whenever a defect task aggregation is updated. The client in the test scenario sends a defect task retrieval request via the page restoration SDK. The server, based on this request, searches for defect tasks in the aggregated defect task set or directly from the defect task pool. This search can be done sequentially according to the defect tasks' order, such as page order or time order. After retrieving the defect task, the server searches for the matching page data in the page data set based on the page ID corresponding to the copywriting defect in that task and sends it to the client in the test scenario. The client then parses the page data using the page restoration SDK and restores the page based on the parsing results to obtain the original page corresponding to the defect task. Furthermore, based on the content of each copywriting defect in the defect task, the defects can be identified and marked on the reconstructed page. For example, they can be marked with colored boxes or highlighted using other methods. This allows for precise location of the defects on the reconstructed page, facilitating quick and timely identification by developers. After marking the defects, the client-side page reconstruction SDK can be used to take a screenshot of the current page and upload it to the server for storage. If the current page is a full-screen page, one screenshot can be uploaded at a time, then the user can swipe to the next screen and continue uploading screenshots until all defects for the entire screen are marked and uploaded successfully. The server can associate and store the screenshots with each corresponding copywriting defect for easy viewing and analysis.

[0091] In fact, considering that the client may miss identifying and marking certain copywriting defects, or that the client may be unable to locate copywriting defects, after the server receives the page screenshots, it can also perform compensation processing on some page screenshots. That is, it can compare and analyze the copywriting defects with the copywriting defects marked in the page screenshots to see if there are any missing copywriting defects that have not been located and marked. If so, the server can identify and mark the missing copywriting defects in the page screenshots. If not, it can be saved directly.

[0092] It should be understood that, whether identifying and marking copywriting defects in the restored page or in a page screenshot, this instruction manual can extract or determine the location of the copywriting defects in the restored page or page screenshot based on the defect details and defect location information contained in the defect content, so as to achieve location marking.

[0093] Reference Figure 5 The diagram shows the server-side processing flow for determining page text defects in a test scenario. This process may include: generating defect tasks; obtaining defect tasks; and reporting page screenshots.

[0094] In the process of generating defect tasks, a timer can be used to scan the copywriting defect pool for copywriting defects, aggregate copywriting defects with the same page ID into a defect task, generate a task record, and update the status of the defect task to Reday.

[0095] Then, in the process of obtaining defect tasks, if the current defect task status is Reday, the page data of the page where the defect task is located is obtained, and the defect task and page data are sent to the client for page restoration processing. The defect is then detected and located in the restored page, and the defective text is marked as faulty. Simultaneously, the defect task status is changed to running.

[0096] After receiving a screenshot of the page, the server can query the status of the defect task. If the defect task is successfully completed, its status is updated, for example, changed to "ending". If there are any missing text defects in the defect task, the location of the text defects can be identified and marked in the screenshot by performing text defect identification, and the results are saved and associated. If the defect task is not successfully completed, it can be determined whether the defect task can be retried. If so, the status of the defect task can be changed back to "Reday" so that it can be resent to the client for page restoration and text defect detection. If it cannot be retried, the defect task is terminated directly. In fact, after the server sends the defect task to the client, that is, when the defect task status is "running", the server can start monitoring the processing time of the defect task. If the processing time exceeds the limit, it can determine whether the defect task can be retried; if the processing time does not exceed the limit, the defect task is terminated directly.

[0097] Therefore, by restoring the page, the defect can be reproduced, and the defective content can be identified and marked on the restored page based on the text defect. A screenshot can be saved, which makes it easier for developers to quickly and accurately know the defective content, improve the detection performance of text defects, accurately locate and mark text defects, and achieve comprehensive and complete effective detection of text defects.

[0098] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0099] Example 2

[0100] Reference Figure 6 As shown, this is a page text defect determination device provided in an embodiment of this specification. The device 600 may include:

[0101] The sending module 602 is used to initiate a defect determination request to the server, wherein the defect determination request is used to instruct the server to obtain a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and to obtain the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect.

[0102] The receiving module 604 is used to receive the text defects and page data returned by the server.

[0103] The restoration module 606 is used to parse the page data and restore the page where the text defect is located based on the parsing results.

[0104] The marking module 608 is used to identify the defective content corresponding to the marked text defect in the restored page, and upload a screenshot to the server.

[0105] Optionally, as an embodiment, the sending module 602 is further configured to upload the page data of the target page to the server, so that the server updates the page data set with the received page data; wherein, the page data in the page data set is mapped with a page identifier.

[0106] In one specific implementation of the embodiments of this specification, the sending module 602 is further configured to extract the page text of the target page and upload it to the server, so that the server can identify text defects based on the page text and update the identified text defects to the text defect pool; wherein, the text defects in the text defect pool are mapped with page identifiers.

[0107] In another specific implementation of the embodiments of this specification, when the marking module 608 determines and marks the defective content corresponding to the copywriting defect in the restored page and uploads a screenshot to the server, it is specifically used to extract the page position of the copywriting defect from the restored page based on the defective content of the copywriting defect; mark the defective content corresponding to the copywriting defect in the restored page based on the extracted page position; take a screenshot of the marked page and upload it to the server.

[0108] Reference Figure 7 As shown, this is a page text defect determination device provided in an embodiment of this specification. The device 700 may include:

[0109] The receiving module 702 is used to receive defect determination requests initiated by the client;

[0110] The acquisition module 704 is used to obtain a matching copywriting defect from the copywriting defect pool based on the application identifier carried in the defect determination request, and to obtain the page data of the page where the copywriting defect is located from the retrieved page data set based on the copywriting defect.

[0111] The sending module 706 is used to send the text defect and page data to the client, so that the client can parse the page data, restore the page where the text defect is located based on the parsing result; and identify and mark the defect content corresponding to the text defect in the restored page, and upload a screenshot to the server.

[0112] The receiving module 702 is also used to receive a screenshot of a page uploaded by the client, wherein the defective content in the screenshot carries a mark.

[0113] Optionally, as an embodiment, the receiving module 702 is further configured to receive page data of the target page uploaded by the client and update the page data set; wherein, the page data in the page data set is mapped with a page identifier.

[0114] In one specific implementation of the embodiments of this specification, the receiving module 702 is further configured to receive the page text of the target page uploaded by the client, identify text defects based on the page text, and update the identified text defects to the text defect pool; wherein, the text defects in the text defect pool are mapped with page identifiers.

[0115] In another specific implementation of the embodiments of this specification, the device 700 further includes: an aggregation module, configured to periodically scan the copywriting defects contained in the copywriting defect pool; and aggregate the copywriting defects in the copywriting defect pool based on the page identifiers mapped by the copywriting defects;

[0116] When the acquisition module 704 retrieves a matching copywriting defect from the copywriting defect pool based on the application identifier carried in the defect determination request, it is specifically used to retrieve a matching aggregated copywriting defect from the copywriting defect pool based on the application identifier carried in the defect determination request.

[0117] In another specific implementation of the embodiments of this specification, the device 700 further includes: a compensation module, configured to, after the receiving module 702 receives the page screenshot uploaded by the client, verify whether there is an unmarked text defect in the page screenshot based on the defect content of the text defect; if so, mark the unmarked text defect in the page screenshot according to the page position of the unmarked text defect determined by the verification result.

[0118] The client initiates a defect detection request to the server, requesting the server to retrieve a matching text defect from the text defect pool. Based on this defect, the server then retrieves the page data of the page containing the defect from the retrieved page data set. The client then returns the text defect and page data to the client, allowing the client to reconstruct the page based on the page data. The client then identifies and marks the defective content corresponding to the text defect on the reconstructed page, takes a screenshot of the marked page, and sends the screenshot to the server for archiving. Thus, by reproducing defects through page reconstruction, identifying and marking the defective content on the reconstructed page based on the text defect, and taking a screenshot for archiving, developers can quickly and accurately identify the defective content, improving the performance of text defect detection, accurately locating and marking text defects, and achieving comprehensive and effective detection of text defects.

[0119] Example 3

[0120] Figure 8 This is a schematic diagram of the structure of an electronic device according to one embodiment of this specification. Please refer to it. Figure 8 At the hardware level, the electronic device includes a processor, and optionally also an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include hardware required for other services.

[0121] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 8 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0122] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0123] The processor reads the corresponding computer program from non-volatile memory into main memory and then runs it, forming a page content defect determination device at the logical level. The processor executes the program stored in memory and specifically performs the following operations:

[0124] A defect determination request is initiated to the server, wherein the defect determination request instructs the server to retrieve a matching text defect from the text defect pool based on the application identifier carried in the defect determination request, and to retrieve the page data of the page containing the text defect from the retrieved page data set based on the text defect; the server receives the text defect and page data returned by the server; the server parses the page data, and reconstructs the page containing the text defect based on the parsing results; the server identifies and marks the defective content corresponding to the text defect in the reconstructed page, and uploads a screenshot to the server. Alternatively,

[0125] The server receives a defect determination request initiated by the client; retrieves a matching text defect from the text defect pool based on the application identifier carried in the defect determination request, and retrieves the page data of the page containing the text defect from the retrieved page data set based on the text defect; sends the text defect and page data to the client so that the client can parse the page data and reconstruct the page containing the text defect based on the parsing result; identifies and marks the defect content corresponding to the text defect in the reconstructed page, and uploads a screenshot to the server; and receives the page screenshot uploaded by the client, wherein the defect content in the page screenshot carries a mark.

[0126] The above is as described in this instruction manual. Figure 2 and Figure 3The methods performed by the apparatus disclosed in the illustrated embodiments can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in one or more embodiments of this specification. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in one or more embodiments of this specification can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0127] The electronic device can also perform Figure 2 and Figure 3 The method, and implement the corresponding device in Figure 2 and Figure 3 The functions of the embodiments shown are not described in detail here.

[0128] Of course, in addition to the software implementation, the electronic devices in the embodiments of this specification do not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0129] Example 4

[0130] This specification also provides an embodiment of a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by a portable electronic device including multiple applications, enable the portable electronic device to perform... Figure 2 and Figure 3 The method of the illustrated embodiment is specifically used to perform the following method:

[0131] A defect determination request is initiated to the server, wherein the defect determination request instructs the server to retrieve a matching text defect from the text defect pool based on the application identifier carried in the defect determination request, and to retrieve the page data of the page containing the text defect from the retrieved page data set based on the text defect; the server receives the text defect and page data returned by the server; the server parses the page data, and reconstructs the page containing the text defect based on the parsing results; the server identifies and marks the defective content corresponding to the text defect in the reconstructed page, and uploads a screenshot to the server. Alternatively,

[0132] The server receives a defect determination request initiated by the client; retrieves a matching text defect from the text defect pool based on the application identifier carried in the defect determination request, and retrieves the page data of the page containing the text defect from the retrieved page data set based on the text defect; sends the text defect and page data to the client so that the client can parse the page data and reconstruct the page containing the text defect based on the parsing result; identifies and marks the defect content corresponding to the text defect in the reconstructed page, and uploads a screenshot to the server; and receives the page screenshot uploaded by the client, wherein the defect content in the page screenshot carries a mark.

[0133] In summary, the above description is merely a preferred embodiment of this specification and is not intended to limit the scope of protection of this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

[0134] The systems, apparatuses, modules, or units described in one or more of the above embodiments may be implemented by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer. Specifically, a computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0135] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0136] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0137] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0138] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

Claims

1. A method for determining defects in page text, applicable to client-side applications, the method comprising: A defect determination request is initiated to the server, wherein the defect determination request is used to instruct the server to obtain a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and to obtain the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect. Receive the text defects and page data returned by the server; The page data is parsed, and the page containing the text defect is reconstructed based on the parsing results; Identify and mark the defective content corresponding to the copywriting defect on the restored page, and upload a screenshot to the server.

2. The method for determining page text defects as described in claim 1 further includes: The page data of the target page is uploaded to the server so that the server updates the page data set with the received page data. The page data set contains page data mapped with page identifiers.

3. The method for determining page text defects as described in claim 1 further includes: Extract the page text of the target page and upload it to the server so that the server can identify text defects based on the page text and update the identified text defects to the text defect pool. The copy defect mapping in the copy defect pool has a page identifier.

4. The method for determining page text defects as described in claim 1, wherein the defective content corresponding to the text defect is identified and marked in the restored page, and a screenshot is uploaded to the server, specifically including: Based on the defective content of the aforementioned copywriting flaw, the page location of the copywriting flaw is extracted from the restored page; Based on the extracted page location, the defective content corresponding to the aforementioned text defects in the restored page is marked; Take a screenshot of the marked page and upload it to the server.

5. A method for determining defects in page text, applicable to the server side, the method comprising: Receive defect determination requests initiated by clients; Based on the application identifier carried in the defect determination request, a matching copy defect is obtained from the copy defect pool, and based on the copy defect, the page data of the page where the copy defect is located is obtained from the retrieved page data set. The copywriting defect and page data are sent to the client so that the client can parse the page data and reconstruct the page where the copywriting defect is located based on the parsing results; And in the restored page, identify and mark the defective content corresponding to the copywriting defect, and upload a screenshot to the server; The system receives a screenshot of a page uploaded by the client, wherein the defective content in the screenshot is marked.

6. The method for determining page text defects as described in claim 5 further includes: Receive page data of the target page uploaded by the client and update the page data set; The page data set contains page data mapped with page identifiers.

7. The method for determining page text defects as described in claim 5 further includes: Receive the page text of the target page uploaded by the client, identify text defects based on the page text, and update the identified text defects to the text defect pool; The copy defect mapping in the copy defect pool has a page identifier.

8. The method for determining page text defects as described in claim 7, further comprising: Periodically scan the copywriting defect pool for copywriting defects; The copywriting defects in the copywriting defect pool are aggregated based on the page identifiers of the copywriting defect mapping. Then, based on the application identifier carried in the defect determination request, a matching copy defect is retrieved from the copy defect pool, specifically including: Based on the application identifier carried in the defect determination request, the matching aggregated copy defects are obtained from the copy defect pool.

9. The method for determining page text defects as described in any one of claims 5-8, further comprising, after receiving the page screenshot uploaded by the client: Based on the content of the aforementioned copywriting defects, verify whether there are any unmarked copywriting defects in the page screenshot; If present, the unmarked copywriting defects are marked in the page screenshot based on the page location determined by the verification results.

10. A device for determining defects in page text, comprising: The sending module is used to initiate a defect determination request to the server. The defect determination request is used to instruct the server to obtain a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and to obtain the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect. The receiving module is used to receive the text defects and page data returned by the server; The restoration module is used to parse the page data and restore the page where the copywriting defect is located based on the parsing results; The tagging module is used to identify and tag the defective content corresponding to the copywriting defect in the restored page, and upload a screenshot to the server.

11. A device for determining defects in page text, comprising: The receiving module is used to receive defect determination requests initiated by the client; The acquisition module is used to obtain a matching copywriting defect from the copywriting defect pool based on the application identifier carried in the defect determination request, and to obtain the page data of the page where the copywriting defect is located from the retrieved page data set based on the copywriting defect. The sending module is used to send the text defect and page data to the client, so that the client can parse the page data and reconstruct the page where the text defect is located based on the parsing result; And identify and mark the defective content corresponding to the aforementioned text defect in the restored page, and take a screenshot; The receiving module is also used to receive a screenshot of a page uploaded by the client, wherein the defective content in the screenshot carries a mark.

12. A system for determining defects in page text, comprising: Client and server; among them, The client is used to initiate a defect determination request to the server; The server is used to receive a defect determination request initiated by the client, and retrieve a matching copy defect from the copy defect pool according to the application identifier carried in the defect determination request, and retrieve the page data of the page where the copy defect is located from the retrieved page data set according to the copy defect. The client is also configured to receive the copywriting defects and page data returned by the server; parse the page data, reconstruct the page where the copywriting defects are located based on the parsing results; identify and mark the defective content corresponding to the copywriting defects in the reconstructed page, and upload a screenshot to the server. The server is also used to receive screenshots of pages uploaded by the client, wherein the defective content in the screenshots carries a marker.

13. An electronic device, comprising: processor; as well as A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the page text defect determination method according to any one of claims 1-9.

14. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of applications, cause the electronic device to perform the page text defect determination method according to any one of claims 1-9.

Images