A method and apparatus for processing association of a production line interface and positioning

Abstract

The application relates to the technical field of front-end development, and discloses a production line interface association processing method and device and a positioning method and device, which comprise the following steps: acquiring a plurality of page information of a production line, wherein each piece of page information comprises screenshot information, a routing string information and interface information; identifying the screenshot information of the plurality of pieces of page information to generate corresponding page portrait information; performing encryption processing on the routing string information of the plurality of pieces of page information to generate corresponding intermediate routing data; the interface information of each piece of page information corresponds to the intermediate routing data; the intermediate routing data of each piece of page information corresponds to the page portrait information; and a total level relationship table of the interface information, the intermediate routing data and the page portrait information of the plurality of pieces of page information is established. The application can effectively improve the positioning efficiency of the production line interface and reduce the labor cost.

Description

Technical Field

[0001] This invention relates to the field of front-end development technology, and in particular to a method, method and apparatus for associating and locating production line interfaces. Background Technology

[0002] Micro-frontends are an architectural framework that transforms a single monolithic application into multiple smaller frontend applications aggregated into a single system. In a micro-frontend architecture, each smaller frontend application can run, be developed, and deployed independently, while these multiple applications are combined into a single, unified application. Within these smaller applications, each application corresponds to a project, and these projects form a development pipeline. Each project within this pipeline can be developed and run independently. As micro-frontends become more widespread, the number of projects within the development pipeline gradually increases, with each project having multiple project pages, and each project page containing multiple access interfaces.

[0003] Currently, locating APIs among the numerous pages in the development line is becoming increasingly difficult. Improving the efficiency of API location and reducing labor costs are pressing issues that need to be addressed. Summary of the Invention

[0004] In view of the shortcomings of the prior art described above, the purpose of this invention is to provide a method, a positioning method and a device for associating production line interfaces, which can improve the positioning efficiency of production line interfaces.

[0005] In a first aspect, the present invention provides a method for associating production line interfaces, comprising:

[0006] Obtain multiple page information of the production line, wherein each page information includes screenshot information, routing string information and interface information;

[0007] Identify screenshots of multiple page information to generate corresponding page profile information;

[0008] The routing string information of multiple page information is encrypted to generate corresponding intermediate routing data, wherein the interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information;

[0009] Establish a hierarchical relationship table for the interface information, intermediate routing data, and page profile information of the multiple pages.

[0010] Secondly, a method for locating production line interfaces is provided, including:

[0011] Obtain exception log information;

[0012] Obtain the corresponding interface information based on the exception log information;

[0013] Based on the interface information, query the top-level relationship table described in any of the first aspects to obtain the corresponding intermediate route data and page profile information;

[0014] The abnormal log information and the corresponding page profile information are summarized to generate a production line interface location table.

[0015] Thirdly, a production line interface association processing device is provided, including:

[0016] The acquisition module is used to acquire multiple page information of the production line, each of which includes screenshot information, routing string information, and interface information.

[0017] The recognition module is used to recognize screenshots of multiple page information and generate corresponding page profile information.

[0018] The processing module is used to encrypt the routing string information of multiple page information to generate corresponding intermediate routing data. The interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information.

[0019] A module is established to create a hierarchical relationship table for the interface information, intermediate routing data, and page profile information of the multiple pages.

[0020] Fourthly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the aforementioned associated processing method for the production line interface or the aforementioned positioning method for the production line interface.

[0021] Fifthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the aforementioned associated processing method for the production line interface or the aforementioned positioning method for the production line interface.

[0022] The aforementioned solution, implemented by the method, location method, and device for associating production line interfaces, firstly acquires multiple page information from the production line, including screenshot information, routing string information, and interface information, where each page's screenshot information, routing string information, and interface information correspond. Then, the screenshot information is identified to generate page profiles for multiple pages, each page profile representing a corresponding page. Next, the routing string information is encrypted to generate intermediate routing data. Irregular characters in the routing string information are removed after pre-encryption, improving subsequent query efficiency. A hierarchical relationship table is then established for the interface information, intermediate routing data, and page profiles of multiple pages. When an interface experiences an anomaly and requires maintenance, the corresponding page profile can be retrieved through the hierarchical relationship table to determine the page location of the interface. By summarizing the anomaly log information of this interface and the corresponding page profile, a production line interface location table can be generated. This production line interface location table is transmitted to the backend project manager, who can then send it to subordinate developers. Developers can use this location table to locate the target interface on the corresponding page and quickly maintain the interface. In this invention, a top-level relationship table of multiple pages and interfaces in the production line is first generated. When an interface malfunctions and requires maintenance, a production line interface location table can be generated based on the top-level relationship table. Developers can quickly locate the target interface of the corresponding page based on the production line interface location table and perform maintenance in a timely manner, thereby effectively improving the location efficiency of production line interfaces and reducing labor costs. Attached Figure Description

[0023] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of an application environment for a production line interface association processing method in one embodiment of the present invention;

[0025] Figure 2 This is a flowchart illustrating a method for associating production line interfaces in one embodiment of the present invention;

[0026] Figure 3 yes Figure 2 A schematic diagram of a specific implementation method for step S20;

[0027] Figure 4 yes Figure 3 A flowchart illustrating a specific implementation of step S22;

[0028] Figure 5 yes Figure 2A schematic diagram of a specific implementation of step S40;

[0029] Figure 6 This is an exemplary structural diagram of a top-level relationship table in one embodiment of the present invention;

[0030] Figure 7 This is a flowchart illustrating a method for locating a production line interface according to an embodiment of the present invention;

[0031] Figure 8 yes Figure 7 A schematic diagram of a specific implementation method for step S51;

[0032] Figure 9 yes Figure 7 A flowchart illustrating a specific implementation of step S53;

[0033] Figure 10 This is a schematic diagram of the structure of the associated processing device for the production line interface in one embodiment of the present invention;

[0034] Figure 11 This is a schematic diagram of the structure of a computer device according to an embodiment of the present invention;

[0035] Figure 12 This is another structural schematic diagram of a computer device according to one embodiment of the present invention. Detailed Implementation

[0036] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0037] The production line interface association processing method provided in this embodiment of the invention can be applied to, for example... Figure 1In this application environment, terminal device 110 communicates with server 120 via a network. Server 120 can first obtain multiple page information from the production line. Each page information can include screenshot information, routing string information, and multiple interface information, with each page's screenshot information, routing string information, and interface information corresponding to each other. This interface information can correspond to the corresponding routing string information, and the routing string information can correspond to the corresponding page. Then, the screenshot information is identified to generate a page profile, with each page profile representing a corresponding page. The routing string information is then encrypted to generate intermediate routing data. Irregular characters are removed after the routing string information is pre-encrypted. When the corresponding intermediate routing data is obtained based on the interface information and the corresponding page profile is queried based on the intermediate routing data, there is no need to process irregular characters again, improving the efficiency of query and location. The interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information. A master-level relationship table of interface information, intermediate routing data, and page profile can be established. When a certain interface information needs to be maintained or an abnormal log information occurs, the page profile corresponding to that interface can be queried through the master-level relationship table to locate the page position of that interface. Developers can locate the interface based on the page profile corresponding to that interface and fix it promptly. This invention eliminates the need for project managers to be familiar with the project pages to locate the interface; the interface location can be determined based on the hierarchical relationship table, reducing labor costs. Furthermore, it effectively shortens the time required to locate production line interfaces and improves the efficiency of interface location.

[0038] It should be noted that terminal device 110 may include various electronic devices such as smartphones, tablets, laptops, and desktop computers. Server 120 may be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The network may be a communication medium of various connection types that can provide a communication link between terminal device 110 and server 120, such as a wired communication link or a wireless communication link.

[0039] Depending on the implementation requirements, the system architecture in this application embodiment can have any number of terminal devices, networks, and servers. For example, server 120 can be a server group composed of multiple server devices. In addition, the technical solutions provided in this application embodiment can be applied to terminal device 110, or to server 120, or can be implemented jointly by terminal device 110 and server 120. This application does not impose any special limitations on this.

[0040] The above section introduced the exemplary application environment of this application. Next, we will continue to introduce the association processing method of the production line interface of this application.

[0041] Please see Figure 2 As shown, Figure 2 A flowchart illustrating the association processing method for a production line interface provided in an embodiment of this application is shown.

[0042] S10. Obtain multiple page information of the production line, each page information including screenshot information, routing string information and multiple interface information;

[0043] S20. Identify screenshots of multiple page information to generate corresponding page profile information;

[0044] S30. Encrypt the routing string information of multiple page information to generate corresponding intermediate routing data. The interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information.

[0045] S40. Establish a hierarchical relationship table for the interface information, intermediate routing data, and page profile information of the multiple page information.

[0046] Regarding step S10, it's important to note that in the context of micro-frontend applications, a micro-frontend application is a microservice architecture. This architecture combines multiple micro-applications into a single application, with each application corresponding to a project. These projects form a development pipeline, and each project can be developed and run independently. Each project can have a corresponding project manager. Each project can include multiple pages, and each page can include multiple API interfaces. For example, in a financial micro-frontend application, it might include a cashier project, a wealth management project, and other projects. The wealth management project pages might include a wealth management product details page (providing users with detailed product descriptions), a payment page (for user purchases and top-ups), an announcement page (for promotional announcements), and other pages. The APIs under each page can be user access interfaces, allowing users to access the corresponding pages through multiple APIs. A set of interface information for a specific page can be something like ×××××: / / ×.×××.××× / ×××-××× / ×× / ××××××, ×××××: / / ×.×××.××× / ××××××× / ×××××× / ×××××, etc. Each page also has a route string, so a set of interface information for each page corresponds to that page's route string. When an interface on a page encounters an exception, such as an error, by locating the route string corresponding to that interface and then using that route string to retrieve the corresponding page, the project manager for that page can be notified to arrange for developers to fix the error promptly, thus improving the efficiency of locating abnormal interfaces. Furthermore, screenshots of each page can be obtained to generate a page profile, representing each page. By querying the page profile corresponding to the abnormal interface, the corresponding page can be located.

[0047] It's worth mentioning that on different users' terminal devices 110, the same page may have different screenshots, i.e., different page profiles. For example, user A's financial product details page is set to the original version 15.0, while user B's financial product details page is updated to the newer version 15.2. User A's financial product details page and user B's financial product details page are different versions of the same page. In this case, the same page can correspond to two different page profiles, but the routing string information under the different page profiles remains unchanged. Therefore, each routing string information can correspond to multiple page profiles.

[0048] It should be further explained that, to improve the efficiency of API locating, a one-to-one correspondence can be established between API information, routing strings, and screenshots across multiple pages. When an API malfunctions, the malfunctioning API information can be mapped to the routing string information, and the corresponding page's screenshot information can be located based on the routing string information. This locating method eliminates the need to check each API sequentially, thus improving the efficiency of locating malfunctioning APIs.

[0049] It's worth mentioning that screenshots, routing strings, and API information for each page can be recorded using a pre-defined script. When a project starts, the script automatically records the routing string information for each page, captures screenshots of the pages, and captures all API information for each page. If an API encounters an error, the script automatically logs the exception information for that API.

[0050] Regarding step S20, it should be noted that since screenshot information is only image information, it is very difficult to find and locate the corresponding page through the image. However, a page profile can display information about various components of a page, with each page corresponding to different component information and their arrangement. Therefore, screenshot information can be processed and converted into a page profile, which can then be mapped to each page.

[0051] It's worth mentioning that the component information of a page can be the various components that make up the page. For example, button information, icon information, text information, or other information on the page.

[0052] Regarding step S30, it should be noted that when an interface information encounters an anomaly, such as an error, this interface information can be mapped to a corresponding route string, which in turn can be mapped to a specific page profile, thus leading to a particular page. Further explanation is needed: the route string may contain irregular characters. These irregular characters can be removed after pre-encryption, generating intermediate route data free of irregular characters. Subsequently, when retrieving the corresponding intermediate route data based on the anomaly interface and then querying the corresponding page profile based on this intermediate route data, it is unnecessary to process the irregular characters again, improving the efficiency of query and location.

[0053] As an example, the route string information can be set to lc / productList, which contains irregular characters such as " / ", uppercase letters such as "L", and lowercase letters such as "c", making the route string information relatively complex. When querying the corresponding page profile based on this route string information, it is also necessary to process the irregular characters, which reduces the efficiency of query location. If the route string information "lc / productList" is encrypted to generate intermediate route data such as 4352MD4562, the irregular characters in the intermediate route data are removed, and the overall structure is simpler, which can improve the efficiency of subsequent query location.

[0054] It is worth mentioning that the encryption here can be hash algorithm encryption. When the routing string information is encrypted using a hash algorithm, the generated intermediate routing data is irreversible. For example, the routing string information can be set to lc / productList, and the generated intermediate routing data can be set to 4352MD4562. Because the intermediate routing data is irreversible, the original routing string information cannot be deduced from the intermediate routing data, thus improving the confidentiality of the routing string information. The specific process of encryption using a hash algorithm in this embodiment will not be elaborated here, but can be obtained from existing literature.

[0055] Regarding step S40, it should be noted that this master-level relationship table reflects the correspondence between interface information, intermediate routing data, and page profiles for multiple pages. When an interface experiences an anomaly, such as an error, this erroneous interface information corresponds to the corresponding intermediate routing data in the master-level relationship table. The intermediate routing data, in turn, corresponds to the relevant page profile in the master-level relationship table. This page profile reflects the page containing the abnormal interface, thus allowing for the location of the page containing the abnormal interface and improving the efficiency of interface location on the production line.

[0056] It's worth mentioning that on different users' terminal devices 110, the same page may have different screenshots, i.e., different page profiles. For example, user A's financial product details page is set to the original version 15.0, while user B's financial product details page is updated to the newer version 15.2. User A's financial product details page and user B's financial product details page are different versions of the same page. In this case, the same page can correspond to two different versions of the page profile, but the interface information and routing string information under the page remain unchanged. Since one routing string corresponds to one intermediate routing data, the intermediate routing data under a page also remains unchanged. In this example, each set of interface information can correspond to one intermediate routing data, and one intermediate routing data can correspond to multiple page profiles of the same page.

[0057] As another exemplary embodiment, the aforementioned master-level relationship table can also be used for interface queries. Specifically, when querying interface information for a specific page, a screenshot of that page can be uploaded. A preset automated script will automatically recognize the screenshot and generate a corresponding page profile. Based on this page profile, the master-level relationship table can be searched for page profiles that match it. Then, the intermediate route data corresponding to that page profile in the master-level relationship table is queried sequentially, and the interface information is then queried based on the intermediate route data to obtain all interface information for that page, thus achieving fast querying of page interfaces.

[0058] As another exemplary embodiment, the aforementioned master-level relationship table can also be used for green light testing during page development. It should be noted that green light testing can refer to testing each interface of a page. Specifically, when performing green light testing on each page, an automated script can automatically access each interface under each page to verify whether each interface is functioning correctly. When an interface encounters an exception, such as an error, the automated script automatically records the interface information and exception log information. Based on the error interface information, the intermediate route data corresponding to the error interface information in the master-level relationship table can be queried first, and then the corresponding page profile can be queried based on the intermediate route data to locate the page containing the abnormal interface. Finally, based on the exception log information of the abnormal interface, the abnormal interface can be debugged specifically.

[0059] It should be noted that the exception log information can include the interface name, error message, and time of the exception. The page profile corresponding to the error interface indicates the page where the exception interface is located. By summarizing the page profiles and exception log information corresponding to the error interfaces, a production line interface location table can be generated to display the specific page, error message, and time of the exception interface. Based on the page information of the exception interface, this production line interface location table can be sent to the project manager of the corresponding page. The project manager can then send the production line interface location table to their subordinate developers. Developers can quickly find the exception interface on the corresponding page using the page information and interface name information in the location table, and perform targeted repairs based on the error message and time. Furthermore, this production line interface location table can be quickly synchronized to the project manager via email, shortening the reporting time for exception interfaces.

[0060] In one exemplary embodiment, such as Figure 3 As shown, the process of identifying screenshots of multiple page information and generating corresponding page profile information may include,

[0061] Step S21: Perform image recognition processing on the screenshot information to obtain the page layout information corresponding to the screenshot information.

[0062] Step S22: Based on the page layout information, generate page profile information of the screenshot information.

[0063] It should be noted that the process of generating page profile information from a screenshot can be described as follows: First, obtain the page layout information from the screenshot. This layout information can be the layout of various components on the page, including text components, image components, icon components, or other components. Then, based on the page layout information, describe the detailed attributes of each component to generate page profile information.

[0064] It is worth mentioning that a neural network-based image prediction model can be used to obtain page layout information from screenshots. Specifically, the neural network model can first be trained using a user interface dataset, which can be set to include 70,000 page screenshots and the component layout information of each page screenshot. Using the 70,000 page screenshots as the input set and the component layout information of each page screenshot as the output set, the neural network model can be trained. After training, the mature neural network model can be set as the image prediction model. The screenshot information to be recognized and processed is input into the image prediction model, which outputs the component layout information in the screenshot information, i.e., the page layout information. The specific training method of the neural network model in this embodiment will not be elaborated here, but can be obtained from existing literature.

[0065] In one exemplary embodiment, such as Figure 4 As shown, the process of generating page profile information based on the page layout information includes the following steps:

[0066] Step S221: Based on the page layout information, generate page description information, which includes page component type information, page component position information, and page component size information.

[0067] Step S222: Based on the page description information, generate page profile information of the screenshot information.

[0068] It's important to note that, based on the component layout identified in the screenshot, detailed attributes of each component can be described to generate page description information, thus improving the page profile. Specifically, for each component on each page, attribute descriptions can be added, generating component type information, component position information, and component size information. Component type information can include text, numbers, symbols, or icons within the component; component position information indicates the component's coordinate position on the page; and component size information indicates the component's length and width.

[0069] As an exemplary embodiment, if a component in a page layout is a Status Bar, attribute descriptions can be added to that component. For example, the component type information can be set to "Notification Icon Area," "Battery Area," or "Time Area," etc. For the "Notification Icon Area," its component position information can be set to "X=100, Y=100." For the "Battery Area," its component position information can be set to "X=200, Y=100," and for the "Time Area," its component position information can be set to "X=300, Y=100." The origin of the coordinates can be set as needed, and can be set to a certain position in the page layout. No limitations are imposed here. For the "Notification Icon Area," its component size information can be set to "Length 20mm, Width 10mm." For the "Battery Area," its component size information can be set to "Length 15mm, Width 8mm." For the "Time Area," its component size information can be set to "Length 15mm, Width 6mm."

[0070] In one exemplary embodiment, such as Figure 5 As shown, the process of establishing the master-level relationship table of the interface information, intermediate routing data, and page profiles for multiple pages may include,

[0071] Step S41: Establish a sub-relationship table for the interface information, intermediate routing data, and page profile information of each page.

[0072] Step S42: Summarize the child-level relationship tables of each page to generate a master-level relationship table.

[0073] It should be noted that by aggregating the sub-level relationship tables of each page's interface information, intermediate routing data, and page profile information, a master-level relationship table can be generated. Specifically, for example... Figure 6As shown, the interface information for each page can be set as the first level of the child relationship table for each page. The intermediate routing data for each page can be set as the second level of the child relationship table for each page. The page profile information for each page can be set as the third level of the child relationship table for each page. After summarizing the child relationship tables for each page, the first level of the master relationship table can be set as a set of interface information A1, A2, A3 for page A, a set of interface information B1, B2, B3 for page B, and a set of interface information C1, C2, C3 for page C. The second level can be set as the intermediate routing data P1 for page A, P2 for page B, and P3 for page C. The third level can be set as the page profile information S1 for page A, S2 for page B, and S3 for page C. The mapping relationship between the first, second and third levels of the general hierarchy table can be represented as: (A1, A2, A3) → P1 → S1, (B1, B2, B3) → P2 → S2, (C1, C2, C3) → P3 → S3.

[0074] Based on the above method embodiments, the present invention provides a method for locating production line interfaces, such as... Figure 7 As shown, Figure 7 A flowchart illustrating a method for locating a production line interface according to an embodiment of this application is shown.

[0075] Step S51: Obtain exception log information.

[0076] Step S52: Obtain the corresponding interface information based on the exception log information.

[0077] Step S53: Query the top-level relationship table based on the interface information to obtain the corresponding intermediate route data and page profile information.

[0078] Step S54: Summarize the abnormal log information and the corresponding page profile information to generate a production line interface location table.

[0079] It should be further noted that when an interface generates an exception, such as an error, a pre-defined automated script can automatically record exception log information. This log information can include the interface name, error message, and time of the error. After locating the page profile information of the exception interface based on the hierarchical relationship table, the page profile information and exception log information can be aggregated to generate a production line interface location table. The backend, based on this table, can quickly find the exception interface on that page using the interface name information from the exception log. Based on the interface error message and time from the exception log, the exception interface can be quickly and effectively repaired, significantly reducing the time and efficiency of production line interface location.

[0080] It's worth mentioning that the server can also retrieve exception log information from multiple interfaces based on pre-defined automated scripts, satisfying the recording of exception log information for multiple abnormal interfaces. In this case, the exception log information from multiple interfaces can be merged into an exception dataset. Based on the interface information corresponding to multiple abnormal interfaces in the exception dataset, the intermediate route data corresponding to the interface information of multiple abnormal interfaces can be queried from the master-level relationship table. When the interface information of multiple abnormal interfaces is under the same page, it corresponds to one intermediate route data. When the interface information of multiple abnormal interfaces is under different pages, it corresponds to multiple intermediate route data. Then, based on the intermediate route data corresponding to the interface information of multiple abnormal interfaces, the corresponding page profile can be queried to locate the page where the multiple abnormal interfaces are located.

[0081] When multiple abnormal interfaces exist, after recording the exception log information for each interface, the server-side 120 can also filter the recorded exception log information to remove unimportant exception log information. This allows for targeted processing of exception log information for multiple interfaces, improving the efficiency of repairing multiple abnormal interfaces. For example, when two abnormal interfaces exist, the corresponding interface error messages in the exception log information can be set to "Incorrect request address" and "Parsing error occurred while processing the request." When the interface error message in the exception log information is "Incorrect request address," it can be set as unimportant exception log information, meaning that the error recorded in the log information does not affect the operation of the interface. When the interface error message in the exception log information is "Parsing error occurred while processing the request," it can be set as important exception log information, meaning that the error recorded in the log information affects the operation of the interface. The server-side 120 can remove unimportant exception log information. Based on the remaining important exception log information, the corresponding interface information can be obtained. Subsequently, the page where this interface information is located can be located according to the master-level relationship table, and repair can be carried out. There is no need to process the exception interfaces corresponding to the less important exception log information, thus improving the processing efficiency of multiple exception interfaces.

[0082] It's important to note that when locating abnormal APIs, the hierarchical relationship table can be structured as follows: API information for multiple pages can be set as the first level, intermediate route data for each page as the second level, and page profile information for each page as the third level. When querying the page profile information corresponding to the erroneous API, a pre-defined automated script sequentially queries the corresponding second-level data from the first-level data, and then queries the third-level data based on the second-level data to obtain the corresponding page profile information. This allows the identification of the page corresponding to the abnormal API. This method of locating abnormal APIs eliminates the need for backend personnel to manually browse and sequentially check the pages corresponding to the abnormal APIs, reducing their time costs and improving the efficiency of abnormal API location.

[0083] As an example, all project pages can be designated as Page A, Page B, and Page C. The first level of the hierarchical relationship table can be set as a set of interface information A1, A2, and A3 for Page A, a set of interface information B1, B2, and B3 for Page B, and a set of interface information C1, C2, and C3 for Page C. The second level can be set as intermediate route data P1 for Page A, P2 for Page B, and P3 for Page C. The third level can be set as page profile information S1 for Page A, S2 for Page B, and S3 for Page C. It should be noted that for the same Page A, there may be different versions of page screenshots, such as the original page in version 15.0 or the updated page in version 15.2, meaning there will be different page profile information, such as page profile information S1 and page profile information S12.

[0084] In one exemplary embodiment, such as Figure 8 As shown, the process of obtaining exception log information may include,

[0085] Step S511: Obtain the interface name, interface error information, and error time of a certain interface information;

[0086] Step S512: Summarize the interface name information, the interface error information, and the error time to generate exception log information.

[0087] It should be noted that when an interface information is abnormal, such as an error, the server 120 can record the interface name, interface error information and error time based on a pre-set automated script. By summarizing the interface name, interface error information and error time, an exception log information can be generated. The backend can then repair the interface based on the detailed exception log information.

[0088] Interface error messages can specify the cause of the error, such as an incorrect request address, a parsing error during request processing, a service unavailability error, a connection timeout error, or other errors. Each interface error message can correspond to a code; for example, an incorrect request address is represented by case 400, a parsing error during request processing is represented by case 403, and a service unavailability error is represented by case 404.

[0089] In one exemplary embodiment, such as Figure 9 As shown, the process of querying the master-level relationship table based on the interface information to obtain the corresponding intermediate route data and page profile information may include,

[0090] Step S521: Based on the interface information, query the intermediate routing data corresponding to the interface information in the master-level relationship table to obtain the corresponding intermediate routing data.

[0091] Step S522: Based on the corresponding intermediate routing data, query the page profile information corresponding to the intermediate routing data in the general-level relationship table to obtain the corresponding page profile information.

[0092] It should be noted that in the master-level relationship table, the interface information, intermediate route data, and page profile information of multiple pages can be presented in a corresponding relationship. When it is necessary to locate the page containing the abnormal interface, the intermediate route data corresponding to the interface information in the master-level relationship table can be queried based on the interface information corresponding to the abnormal log information, and then the corresponding page profile information can be queried based on the intermediate route data to locate the page containing the abnormal interface.

[0093] It's worth mentioning that the master-level relationship table can also be used in API search scenarios to query API information corresponding to a specific page screenshot. Specifically, a page screenshot can be identified and processed to generate a page profile. Based on this page profile, the master-level relationship table can be queried to obtain the corresponding intermediate routing data. Then, this intermediate routing data can be used to query the corresponding abnormal API in the master-level relationship table.

[0094] As can be seen, the above solution first generates a relationship table between each page and its corresponding interface. When an interface experiences an anomaly, such as an error, the page containing the anomaly can be located based on this table, generating a production line interface location table. This table is then sent to the backend project manager, who can promptly assign subordinate developers to fix the issue. Developers can quickly locate the anomaly on the corresponding page using the location table, effectively improving the efficiency of identifying production line interfaces. This eliminates the need for the project manager to rely on their project familiarity to locate the page containing the anomaly, reducing the project manager's time cost. Furthermore, the production line interface location table can be synchronized to the project manager via email, shortening the reporting time for anomaly issues and reducing labor costs.

[0095] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0096] In one embodiment, a production line interface association processing device is provided, which corresponds one-to-one with the production line interface association processing method in the above embodiments. For example... Figure 10 As shown, the associated processing device for the production line interface includes an acquisition module 101, an identification module 102, a processing module 103, and an establishment module 104.

[0097] In one embodiment, the identification module 102 is specifically used for:

[0098] Image recognition processing is performed on screenshots of multiple page information to obtain the page layout information corresponding to the screenshot information.

[0099] Based on the page layout information, page profile information of the screenshot information is generated.

[0100] In one embodiment, the identification module 102 is further configured to:

[0101] Based on the page layout information, page description information is generated, which includes page component type information, page component position information, and page component size information.

[0102] Based on the page description information, page profile information of the screenshot information is generated.

[0103] In one embodiment, module 104 is specifically used for:

[0104] Establish a child-level relationship table for each page's interface information, intermediate routing data, and page profile.

[0105] The sub-level relationship tables of each page's information are summarized to generate the master-level relationship table.

[0106] This invention provides a device for associating production line interfaces. It generates a hierarchical relationship table between each page and each interface. This table allows for querying the page profile corresponding to each interface, thus locating the interface's position on the page. When an abnormal interface occurs, the hierarchical relationship table allows for quick retrieval of the corresponding page profile. Developers can then locate the interface based on this profile and promptly repair it using error log information. This invention eliminates the need for project managers to rely on their familiarity with project pages to locate interfaces; the hierarchical relationship table alone is sufficient, improving the efficiency of production line interface location and reducing labor costs.

[0107] Specific limitations regarding the associated processing device for the production line interface can be found in the limitations of the associated processing method for the production line interface described above, and will not be repeated here. Each module in the aforementioned associated processing device for the production line interface can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0108] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 11As shown. The computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile and / or volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The network interface is used to communicate with external clients via a network connection. When executed by the processor, the computer program implements the functions or steps of a production line interface association processing method on the server side, or implements the functions or steps of a production line interface positioning method on the server side.

[0109] In one embodiment, a computer device is provided, which may be a client, and its internal structure diagram may be as follows: Figure 12 As shown, the computer device includes a processor, memory, network interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The network interface is used to communicate with an external server via a network connection. When executed by the processor, the computer program implements client-side functions or steps of a production line interface association processing method, or client-side functions or steps of a production line interface positioning method.

[0110] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of an association processing method for a production line interface.

[0111] Obtain multiple page information from the production line, each page information including screenshot information, routing string information, and multiple interface information;

[0112] Identify screenshots of multiple page information entries and generate corresponding page profile information;

[0113] The routing string information of multiple page information is encrypted to generate corresponding intermediate routing data. The interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information.

[0114] Establish a hierarchical relationship table for the interface information, intermediate routing data, and page profile information of the multiple pages.

[0115] Alternatively, the steps for implementing the positioning method of the production line interface when the processor executes a computer program:

[0116] Obtain exception log information;

[0117] Obtain the corresponding interface information based on the exception log information;

[0118] Query the top-level relationship table based on the interface information to obtain the corresponding intermediate route data and page profile information;

[0119] The abnormal log information and the corresponding page profile information are summarized to generate a production line interface location table.

[0120] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, wherein when the computer program is executed by a processor, the steps of an association processing method for a production line interface are implemented:

[0121] Obtain multiple page information from the production line, each page information including screenshot information, routing string information, and multiple interface information;

[0122] Identify screenshots of multiple page information entries and generate corresponding page profile information;

[0123] The routing string information of multiple page information is encrypted to generate corresponding intermediate routing data. The interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information.

[0124] Establish a hierarchical relationship table for the interface information, intermediate routing data, and page profile information of the multiple pages.

[0125] Alternatively, the steps for implementing the positioning method of the production line interface when a computer program is executed by a processor:

[0126] Obtain exception log information;

[0127] Obtain the corresponding interface information based on the exception log information;

[0128] Query the top-level relationship table based on the interface information to obtain the corresponding intermediate route data and page profile information;

[0129] The abnormal log information and the corresponding page profile information are summarized to generate a production line interface location table.

[0130] It should be noted that the functions or steps that can be implemented by the computer-readable storage medium or computer device described above can be referred to the relevant descriptions on the server side and client side in the foregoing method embodiments. To avoid repetition, they will not be described one by one here.

[0131] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0132] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0133] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included within the protection scope of the present invention.

Claims

1. A method for associating production line interfaces, characterized in that, include: Obtain multiple page information of the production line, wherein each page information includes screenshot information, routing string information and interface information; Identify screenshots of multiple page information to generate corresponding page profile information; The routing string information of multiple page information is encrypted to generate corresponding intermediate routing data, wherein the interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information; A hierarchical relationship table is established for the interface information, intermediate routing data, and page profile information of the multiple page information. The hierarchical relationship table is used to query the corresponding intermediate routing data based on the interface information and to query the corresponding page profile information based on the intermediate routing data in order to locate the page where the interface is located.

2. The method for associating production line interfaces according to claim 1, characterized in that, The step of identifying screenshots of multiple page information and generating corresponding page profile information includes: Image recognition processing is performed on screenshots of multiple page information to obtain page layout information corresponding to the screenshots. Based on the page layout information, page profile information of the screenshot information is generated.

3. The method for associating production line interfaces according to claim 2, characterized in that, The page profile information used to generate the screenshot information based on the page layout information includes: Based on the page layout information, page description information is generated, which includes page component type information, page component position information, and page component size information. Based on the page description information, page profile information of the screenshot information is generated.

4. The method for associating production line interfaces according to claim 1, characterized in that, The hierarchical relationship table for establishing multiple page information, including the interface information, intermediate routing data, and page profile information, comprises: Establish a child-level relationship table for each page's interface information, intermediate routing data, and page profile information; The sub-level relationship tables of each page's information are summarized to generate the master-level relationship table.

5. A method for locating a production line interface, characterized in that, include: Obtain exception log information; Obtain the corresponding interface information based on the exception log information; Based on the interface information, query the top-level relationship table in the association processing method of the production line interface according to any one of claims 1-4 to obtain the corresponding intermediate routing data and page profile information; The abnormal log information and the corresponding page profile information are summarized to generate a production line interface location table.

6. The method for locating production line interfaces according to claim 5, characterized in that, The acquisition of abnormal log information includes: To retrieve information about a specific interface, including the interface name, error message, and error time. The interface name information, the interface error information, and the error time are summarized to generate exception log information.

7. The method for locating production line interfaces according to claim 5, characterized in that, The step of querying the top-level relationship table based on the interface information to obtain the corresponding intermediate route data and page profile information includes: Based on the interface information, query the intermediate route data corresponding to the interface information in the top-level relationship table to obtain the corresponding intermediate route data; Based on the corresponding intermediate routing data, query the page profile information corresponding to the intermediate routing data in the general-level relationship table to obtain the corresponding page profile information.

8. A production line interface association processing device, characterized in that, include: The acquisition module is used to acquire multiple page information of the production line, wherein each page information includes screenshot information, routing string information and interface information; The recognition module is used to recognize screenshots of multiple page information to generate corresponding page profile information; The processing module is used to encrypt the routing string information of multiple page information to generate corresponding intermediate routing data, wherein the interface information of each page information corresponds to the intermediate routing data, and the intermediate routing data of each page information corresponds to the page profile information; A module is established to create a hierarchical relationship table for the interface information, intermediate routing data, and page profile information of multiple page information. The hierarchical relationship table is used to query the corresponding intermediate routing data based on the interface information and to query the corresponding page profile information based on the intermediate routing data in order to locate the page where the interface is located.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the associated processing method of the production line interface as described in any one of claims 1 to 4, or the positioning method of the production line interface as described in any one of claims 5 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the association processing method of the production line interface as described in any one of claims 1 to 4, or the positioning method of the production line interface as described in any one of claims 5 to 7.

Images