Debug page display method, device, equipment, storage medium and communication system

Abstract

The present disclosure is about a method, device, equipment, storage medium and communication system for displaying a debugging page, and relates to the field of computers. In the present disclosure, a second device generates and sends first link information to a first device, and accordingly, the first device receives the first link information from the second device, and the first link information is associated with a first debugging page; the first device displays the first link information in a first conversation interface of a preset communication application, and the group corresponding to the first conversation interface includes information of multiple first users; in response to a first operation, the first device displays a first debugging page, and the first operation is an operation of the first user triggering the first link information. In this way, when the first debugging page requires multiple people to debug, it is only necessary to log in to the debugging page once on the second device, and other personnel can directly obtain the debugging page without logging in again, thereby improving debugging efficiency.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a method, device, equipment, storage medium and communication system for displaying a debugging page. Background Art

[0002] With the rapid development of mobile Internet, the business needs of various industries on mobile terminals have exploded. More and more mobile applications (applications, APPs) use the fifth generation of hypertext markup language web pages (web H5) technology to carry business needs. Compared with development technologies such as Android, Web H5 technology has the advantages of strong compatibility, easy transplantation, and low R&D cost.

[0003] During the development and debugging of Web H5 technology, in some scenarios, the same H5 webpage can display different information for different logged-in users. For example, in the scenario of e-commerce business, the order list webpages of different logged-in users appear differently (for example, a user can only see the order card of a product after purchasing it). For another example, in the scenario of online medical consultation business, doctors and patients have different roles, and the information and operation permissions displayed on their corresponding webpages are also different (for example, the webpage corresponding to the doctor role can be used to view the order information of patient consultations, and the webpage corresponding to the patient role can be used for online consultations).

[0004] Usually, developers can debug the H5 webpage corresponding to the account only after logging in to the H5 webpage with the user's account. If the H5 webpage corresponding to the user needs to be debugged by multiple different developers, each developer needs to log in to the H5 webpage corresponding to the user before debugging, which is inefficient. Summary of the invention

[0005] The present invention provides a method, device, equipment, storage medium and communication system for displaying a debugging page, which can improve the efficiency of debugging the H5 web page corresponding to the user.

[0006] The technical solution of the embodiment of the present disclosure is as follows:

[0007] According to a first aspect of an embodiment of the present disclosure, a method for displaying a debugging page is provided, which is applied to a first device, and the method may include: the first device receives first link information associated with a first debugging page from a second device, the first debugging page being a debugging page corresponding to a first account; the first device displays the first link information in a first conversation interface of a preset communication application software that includes information of multiple users; in response to an operation of triggering the first link information by a user among multiple first users who uses the first device, the first device displays the first debugging page.

[0008] Based on the technical solution of the first aspect, the first device can receive the first link information associated with the first debugging page from the second device. The first device can display the first link information on the first session interface of the preset communication application, the corresponding group of which includes information of multiple users. In this way, the multiple users can view the first link information on the first session interface of the first device they use, and obtain the first debugging page through the first link information. In other words, for users who need to debug the first debugging page, they only need to trigger the first link information to display the first debugging page on the first device they use, and there is no need to log in to the debugging page using the information of the first account again, thereby improving debugging efficiency.

[0009] Optionally, the first link information includes file information corresponding to the first debugging page, and the file information includes user credential information corresponding to the first account; the above-mentioned "displaying the first debugging page" specifically includes: the first device writes the file information into the cache of a preset browser; the first device runs the preset browser and displays the first debugging page on the interface of the preset browser.

[0010] Optionally, the first link information also includes information of the first account and device information of the second device, the information of the first account includes one or more of an identity document (ID), type, and name of the first account, and the method also includes: the first device displays the information of the first account and the device information of the second device on the first session interface.

[0011] Optionally, the method also includes: the first device receives second link information associated with a second debugging page from the second device, where the second debugging page is a debugging page corresponding to the second account; the first device displays the second link information on the first session interface; the first device deletes the first debugging page and displays the second debugging page in response to the first user triggering a second operation on the second link information.

[0012] According to a second aspect of an embodiment of the present disclosure, a method for displaying a debugging page is provided, which is applied to a second device, and the method includes: the second device generates first link information associated with a first debugging page, and the first debugging page is a debugging page corresponding to a first account; the second device sends the first link information to the first device in response to a first sending operation, so that the first device displays the first link information in a first session interface of a preset communication application, and the first session interface includes information of multiple first users.

[0013] Optionally, the above-mentioned "generating first link information" includes: the second device obtains user credential information corresponding to the first account in response to the first login operation, and writes the user credential information into file information, and the first login operation is an operation of logging into the first debugging page corresponding to the first account; the second device splices the file information to the first link to generate first link information, and the first link is pre-configured for the second device.

[0014] Optionally, the first link information also includes information of the first account, and the information of the first account includes one or more of the ID and name of the first account and device information of the second device. After the above-mentioned "obtaining user credential information", the method also includes: the second device displays the first debugging page.

[0015] Optionally, the method also includes: in response to a second login operation, the second device generates second link information associated with a second debugging page, and displays a second debugging page corresponding to the second account; in response to a second sending operation, sending the second link information to the first device.

[0016] According to a third aspect of an embodiment of the present disclosure, a display device for a debugging page is provided, which is applied to a first device, and the device may include: a receiving unit and a display unit; the receiving unit is used to receive first link information associated with a first debugging page from a second device, the first debugging page being a debugging page corresponding to a first account; the display unit is used to display the first link information in a first conversation interface of a preset communication application, the corresponding group of which includes information of multiple first users; the display unit is also used to display the first debugging page in response to an operation of triggering the first link information by a user among the multiple first users who uses the first device.

[0017] Optionally, the first link information includes file information corresponding to the first debugging page, the file information includes user credential information corresponding to the first account, and the device also includes a processing unit; the processing unit is used to write the file information into the cache of a preset browser; the processing unit is also used to run the preset browser and control the display unit to display the first debugging page on the interface of the preset browser.

[0018] Optionally, the first link information also includes one or more of the ID and name of the first account and the device information of the second device. The display unit is further used to display the information of the first account and the device information of the second device on the first session interface.

[0019] Optionally, the receiving unit is further used to receive second link information associated with a second debugging page from a second device, where the second debugging page is a debugging page corresponding to the second account; the display unit is further used to display the second link information on the first session interface; the processing unit is further used to delete the first debugging page in response to an operation by the first user to trigger the second link information, and control the display unit to display the second debugging page.

[0020] According to a fourth aspect of an embodiment of the present disclosure, a display device for a debugging page is provided, which is applied to a second device, and the device includes a processing unit and a sending unit; the processing unit is used to generate first link information, and the first link information is associated with a first debugging page corresponding to a first account; the sending unit is used to send the first link information to one or more first devices in response to a first sending operation, so that the one or more first devices display the first link information in a first session interface of a preset communication application, and the first session interface includes information of multiple first users.

[0021] Optionally, the device also includes an acquisition unit, which is used to respond to the operation of logging into the first debugging page corresponding to the first account, obtain the first corresponding user credential information and write the user credential information into file information; a processing unit, which is specifically used to splice the file information to the first link to generate first link information, and the first link is pre-configured for the second device.

[0022] Optionally, the first link information also includes information of the first account, the information of the first account includes one or more of the ID, name, name of the first account, and device information of the second device. The device also includes a display unit; the display unit is used to display the first debugging page.

[0023] Optionally, the processing unit is also used to generate second link information associated with the second debugging page in response to a second login operation, and control the display unit to display the second debugging page, where the second debugging page is the debugging page corresponding to the second account; the processing unit is also used to send the second link information to one or more first devices through the sending unit in response to a second sending operation.

[0024] According to a fifth aspect of an embodiment of the present disclosure, a computing device is provided, which may include: a processor and a memory for storing processor executable instructions; wherein the processor is configured to execute the instructions to implement any one of the optional debugging page display methods in the above-mentioned first aspect.

[0025] According to a sixth aspect of an embodiment of the present disclosure, a computing device is provided, which may include: a processor and a memory for storing processor executable instructions; wherein the processor is configured to execute the instructions to implement any one of the optional debugging page display methods in the above-mentioned second aspect.

[0026] According to a seventh aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which instructions are stored. When the instructions in the computer-readable storage medium are executed by a processor of a computing device, the computing device is enabled to execute any one of the optional methods for displaying a debugging page in the first aspect described above.

[0027] According to an eighth aspect of an embodiment of the present disclosure, a computing device is provided, which may include: a processor and a memory for storing processor executable instructions; wherein the processor is configured to execute the instructions to implement any one of the optional debugging page display methods in the above-mentioned second aspect.

[0028] According to a ninth aspect of an embodiment of the present disclosure, a computer program product is provided, which includes computer instructions. When the computer instructions are executed on a computing device, the computing device executes the method for displaying a debugging page as described in any optional implementation of the first aspect.

[0029] According to a tenth aspect of an embodiment of the present disclosure, a computer program product is provided, which includes computer instructions. When the computer instructions are executed on a computing device, the computing device executes the method for displaying a debugging page as described in any optional implementation of the second aspect.

[0030] According to an eleventh aspect of an embodiment of the present disclosure, a communication system is provided, which includes a second device and one or more first devices, the second device can execute the method for displaying a debugging page as described in any optional implementation manner of the second aspect, and any first device of the one or more first devices can execute the method for displaying a debugging page as described in any optional implementation manner of the first aspect.

[0031] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0033] Figure 1 A schematic diagram of the structure of a communication system provided by an embodiment of the present disclosure is shown;

[0034] Figure 2 A schematic diagram showing a flow chart of a method for displaying a debugging page provided by an embodiment of the present disclosure;

[0035] Figure 3 A schematic diagram showing a sending interface of the VConsole tool provided in an embodiment of the present disclosure is shown;

[0036] Figure 4 A schematic diagram of a first conversation interface provided by an embodiment of the present disclosure is shown;

[0037] Figure 5 A schematic diagram of a first debugging page provided by an embodiment of the present disclosure is shown;

[0038] Figure 6 A schematic diagram showing a flow chart of another method for displaying a debugging page provided by an embodiment of the present disclosure;

[0039] Figure 7 A schematic diagram showing a flow chart of another method for displaying a debugging page provided by an embodiment of the present disclosure;

[0040] Figure 8 A schematic diagram showing a flow chart of another method for displaying a debugging page provided by an embodiment of the present disclosure;

[0041] Fig. 9 An example diagram showing a process of sending first link information provided by an embodiment of the present disclosure;

[0042] Fig.10 A schematic diagram showing a flow chart of another method for displaying a debugging page provided by an embodiment of the present disclosure;

[0043] Fig.11 A schematic diagram of the structure of a display device for a debugging page provided by an embodiment of the present disclosure is shown;

[0044] Fig.12 A schematic diagram showing the structure of another display device for a debugging page provided in an embodiment of the present disclosure is shown;

[0045] Fig.13 A schematic diagram showing the structure of another debugging page display device provided by an embodiment of the present disclosure is shown;

[0046] Fig.14 A structural schematic diagram of another communication system provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0047] In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0048] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0049] It should also be understood that the term “comprising” indicates the presence of described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integers, steps, operations, elements and / or components.

[0050] The data involved in the present disclosure may be data authorized by the user or fully authorized by all parties.

[0051] Before describing the technical solution provided by the embodiment of the present application in conjunction with the accompanying drawings, the process of how the second device displays the H5 page corresponding to the user is described first:

[0052] 1. After the user logs in to the APP of the second device using the account information, the second device sends a first request message to the server. Correspondingly, the server receives the first request message from the second device.

[0053] The account information may be the account name and password registered by the user. The server corresponds to the APP and is used to provide user credential information and page data corresponding to the account. The first request information may include the user's account name and password. For example, the user's account name may be a mobile phone number, WeChat account, Weibo account, etc.

[0054] 2. The server verifies the user's account information.

[0055] The server verifying the user's account information may refer to the server verifying whether the user's account is legitimate. For example, the server may pre-store information of multiple accounts, and the server may compare the account information carried in the first request information with the pre-stored information of the multiple accounts. If the account information carried in the first request information is consistent with the pre-stored account information, it means that the user's account is legitimate; if not, it means that the user's account is illegitimate.

[0056] 3. If the user's account is legitimate, the server sends a first response message to the second device. Correspondingly, the second device receives the first response message from the server.

[0057] Among them, the first response information is used to indicate that the user's account is legal. The first response information may include user credential information (Token) corresponding to the account. The Token can uniquely identify the account. After receiving the Token, the second device can store the Token in the Cookie information of the pre-configured browser. Cookie information can also be used to store debugging page data corresponding to the account. In subsequent embodiments, the description of user credential information and Cookie information can be referred to here and will not be repeated.

[0058] 4. In response to the user's operation of accessing the H5 page, the second device may send a second request message to the server. Correspondingly, the server receives the second request message from the second device.

[0059] The user's operation of accessing the H5 page may refer to the user inputting a URL or triggering a link. The second request information may be used to request page data corresponding to the URL or link. The second request information may include a Token corresponding to the account.

[0060] In a possible implementation, the second device may send the second request information to the server through a data application programming interface (API) interface.

[0061] 5. The server sends the debugging page data corresponding to the Token to the second device. Correspondingly, the second device receives the debugging page data corresponding to the Token from the server.

[0062] The debugging page data corresponding to the Token may refer to the data displayed on the H5 page corresponding to the account.

[0063] 6. After receiving the debugging page data corresponding to the Token, the second device can display the page data on the browser page.

[0064] The above is an explanation of how the second device displays the H5 page corresponding to the user. In the process of using the first device to develop and debug Web H5, the first device can use the following method 1 or method 2 to obtain the H5 page corresponding to the user.

[0065] Method 1: The developer uses the account information to log in to the APP of the second device to obtain the Token corresponding to the account. The second device stores the obtained Token in the cookie information of the browser. The developer exports the cookie information storing the Token in the second device through a specific code snippet (such as document.cookie in JavaScript language) and sends it to the first device. In response to the operation of writing a specific code snippet, the first device can write the cookie information storing the Token to a pre-configured browser. In this way, the developer can view the H5 page corresponding to the account in the browser of the first device, and then debug it.

[0066] In the technical solution of the above method 1, the developer needs to enter an additional code in the second device to obtain the cookie information including the token. Then, the cookie information is imported into the first device. If multiple developers need to debug the H5 page, the multiple developers need to repeat the above operation, which is a cumbersome process.

[0067] Method 2: The first device may be pre-configured with an API interface proxy. The first device may directly access the server through the API interface, log in with the user's account and corresponding password, and obtain the H5 page corresponding to the account.

[0068] In the above method 2, the server needs to support the first device to log in through the API interface. At the same time, if the pages corresponding to different users need to be debugged, the developer also needs to switch accounts. For example, it is necessary to log out of the previous user account first and then log in to another user account. The operation is also more troublesome.

[0069] For example, in the development and debugging process of the H5 page, in some scenarios, the same H5 page can display different information for different logged-in users. For example, in the e-commerce business scenario, for the e-commerce H5 page, when the seller's account information is used to log in to the e-commerce H5 page, the H5 page corresponding to the seller can be displayed, such as the received product order information and the information of each buyer; when the buyer's account information is used to log in to the e-commerce H5 page, the buyer's corresponding H5 page can be displayed, such as the buyer's information and the order information of the purchased product. The buyer's information can be the buyer's nickname, contact information, address information, etc. For another example, in the online medical consultation scenario, for the consultation H5 page, when the doctor's account information is used to log in to the consultation H5 page, the doctor's corresponding H5 page can be displayed, such as the received consultation order and the patient's information; when the patient's account information is used to log in to the consultation H5 page, the patient's corresponding H5 page can be displayed, such as the consultation order initiated by the patient and the patient's information.

[0070] Based on the above scenario, when debugging H5 pages of different accounts is required, developers need to log in to the debugging page using the information of different accounts. When the H5 page of a certain account needs to be debugged by different developers, each developer needs to log in to the debugging page using the information of the account, which is inefficient.

[0071] In view of this, an embodiment of the present application provides a page display method, the method comprising: a second device generates and sends first link information to a first device, and accordingly, the first device receives the first link information from the second device, the first link information being associated with a first debugging page; the first device displays the first link information in a first session interface of a preset communication application, the first session interface including information of multiple first users; in response to a first operation, the first device displays a second debugging page, the first operation being an operation by the first user to trigger the first link information, and the first user being a user among multiple first users who uses the first device.

[0072] In this way, for multiple first users in the group corresponding to the first session interface, if any first user wants to debug the first debugging page, the first link information in the first session interface can be triggered, so that the first device used by the first user can directly display the first debugging page, without having to use the first account information to log in to the original page again. In other words, when a page corresponding to a certain account needs to be debugged by multiple people, it is only necessary to use the first account information to log in to the page once on the second device, and other developers can get the debugging page corresponding to the account without having to log in again, thereby improving the debugging efficiency.

[0073] It should be noted that the debugging page involved in the embodiments of the present application can be the aforementioned H5 page, or it can be other types of debugging pages without limitation.

[0074] The following is an exemplary description of the method for displaying a debugging page provided by an embodiment of the present disclosure in conjunction with the accompanying drawings:

[0075] Figure 1 A communication system schematic diagram provided in an embodiment of the present disclosure is shown in FIG. Figure 1 As shown, the communication system may include: one or more first devices 110 (only two are shown in the figure) and a second device 120. The one or more first devices 110 are in communication connection with the second device 120.

[0076] The first device 110, also called a front-end device, can be used by developers to debug pages. For example, the first device can be a computer, personal computer, desktop, laptop, handheld computer, notebook computer, or ultra-mobile personal computer (UMPC) used by developers.

[0077] Among them, the second device 120, which can also be called a mobile device, can be used to log in to the page that needs to be debugged. For example, the second device 120 can be pre-configured with one or more APPs. The developer and debugger can use the user's account information to log in to the APP and obtain the debugging page through the logged-in APP. The specific process can refer to the above description and will not be repeated here. The second device can be a mobile phone, a tablet computer, a netbook, a cellular phone, a personal digital assistant (PDA), and other devices that can install and use applications.

[0078] The present disclosure does not impose any special restrictions on the specific forms of the first device and the second device. They can perform human-computer interaction with the user through one or more methods such as a keyboard, a touch pad, a touch screen, a remote controller, voice interaction, or a handwriting device.

[0079] In a possible embodiment, Figure 1 As shown, the communication system provided in the embodiment of the present application may further include a server 130. The server 130 may be configured to respond to a request message including account information from the second device 120 and send a token and page data corresponding to the account to the second device 120.

[0080] In some embodiments, the server 130 may be a single server, or a server cluster composed of multiple servers. In some implementations, the server cluster may also be a distributed cluster. The present disclosure does not limit the specific implementation of the server 130.

[0081] When the server 130 is a single server, the server can provide the second device with a token corresponding to the account, and can also provide the second device with the requested page data. When the server 130 is a server cluster consisting of multiple servers, some of the multiple servers can be used to provide the second device with a token corresponding to the account, and another part can be used to provide the second device with the requested page data.

[0082] It should be noted that the execution subject of the debugging page display method provided in the present disclosure is the first device and the second device, and can also be the chip or system on chip in the first device, the chip or system on chip in the second device, etc., without limitation.

[0083] like Figure 2 As shown, the method for displaying a debugging page provided by the embodiment of the present disclosure may include:

[0084] S201: The second device generates first link information.

[0085] The second device may be Figure 1 The second device 120 in the embodiment may also be a device in the second device 120, for example, it may be a chip of the second device 120.

[0086] The first link information may be associated with the first debugging page. The first debugging page is a debugging page corresponding to the first account. For example, the first link information may be information in a lightweight markup language (Markdown) format. The first link information may be a uniform resource locator (URL), for example, http: / / local.example.com:8080 / dev-diy? cookie=Token. Token is a Token corresponding to the first account.

[0087] In a possible implementation, the second device may be configured with a preset tool. The preset tool may be used to send the first link information to the first device. In response to the operation of running the preset tool, the second device may generate the first link information.

[0088] For example, the preset tool may be a VConsole tool. After logging into the first debugging page, the second device may run a custom plug-in function of the VConsole tool to display the following information: Figure 3 The interface shown in FIG. 1 may include a “Send Cookie” button. The button may be used to trigger the second device to send the first link information to the first device.

[0089] It should be noted that before generating the first link information, the second device has already obtained the Token corresponding to the first account and the corresponding page data of the first debugging page. The specific process can be referred to the subsequent description and will not be repeated here.

[0090] S202: In response to a first sending operation, the second device sends first link information to one or more first devices. Correspondingly, the one or more first devices receive the first link information from the second device.

[0091] The first device may be Figure 1The first device 110 that can display the first debugging page may also be a device in the first device 110, for example, a chip of the first device 110. The first sending operation may be an operation of sending the first link information to one or more first devices from the second device.

[0092] In one example, Figure 3 As shown, the first sending operation may be an operation of clicking a “Send Cookie” button of the VConsole tool.

[0093] It should be noted that the first device in the embodiment of the present application may be a first device capable of supporting debugging of the first debugging page. For example, the first device may have a system and tools that support page debugging, etc., which are not limited.

[0094] S203: The first device displays the first link information on a first conversation interface of a preset communication application.

[0095] The first device may refer to the first device that receives the first link information from the second device. The first device may be pre-configured with a preset communication application, which may be used to perform real-time synchronous communication with the VConsole tool of the second device. For example, the preset communication application may be an instant messaging (IM) tool (such as WeChat for Business, KIM, Feishu, etc.) that supports sending messages through an external API interface.

[0096] In a possible implementation, when the second device uses the VConsole tool to send the first link information to the preset communication application of the first device, the preset communication application of the first device may display the information on the corresponding session interface.

[0097] The first link information may carry an identifier for indicating a group corresponding to the conversation interface. The preset communication application may determine the group to receive the first link information based on the identifier, and then the first device may push the first link information to the group, and then display the first link information on the conversation interface corresponding to the group. The group includes multiple users. Each of the multiple users may view the information displayed on the conversation interface through the first device used by each user.

[0098] For example, Figure 4 As shown, an interface for displaying the first link information provided by an embodiment of the present application. The "write cookie information to browser" in the session interface is associated with the first link information. The project start command can be another resource coordinator (yet another resource negotiator, YARN) start (start): medical (health).

[0099] S204: In response to the first operation, the first device displays a first debugging page.

[0100] The first operation may be an operation for a developer to trigger the first link information. Figure 4 The first operation can be for the developer to click [Write Cookie Information to the Browser].

[0101] In one example, taking the online medical consultation field as an example, Figure 5 As shown, a debugging page is provided in an embodiment of the present application. The first debugging page is a debugging page corresponding to a patient account. The debugging page may also include information of the patient account and a plurality of program codes. The plurality of program codes may be used to modify and debug the page data on the first debugging page.

[0102] The technical solution provided by the above embodiment brings at least the following beneficial effects: As can be seen from the above S201-S204, after the second device generates the first link information with the first debugging page, it can send the first link information to one or more first devices. After receiving the first link information from the second device, the first device can display the first link information on the first conversation interface of the preset communication application program including information of multiple users. In this way, the multiple users can view the first link information on the first conversation interface of the first device they use, and obtain the first debugging page through the first link information. In other words, for users who need to debug the first debugging page, they only need to trigger the first link information to display the first debugging page on the first device they use, and there is no need to log in to the debugging page using the information of the first account again, thereby improving debugging efficiency.

[0103] In one possible embodiment, combining Figure 2 ,like Figure 6 As shown, the second device generating the first link information in the above S201 may specifically include S2011 and S2012.

[0104] S2011. In response to the first login operation, the second device obtains user credential information corresponding to the first account, and writes the user credential information into the file information.

[0105] The first login operation may be an operation of logging into the first debugging page corresponding to the first account. For example, the user may enter the account number and the corresponding password of the first account on the login page of the APP. The file information may be Cookie information.

[0106] In a possible implementation, in response to the first login operation, the second device sends a first request message to the server. Accordingly, the server receives the first request message from the second device. When the server verifies that the first account is legitimate, the server sends a token corresponding to the first account to the second device. Accordingly, the second device receives the token from the server. The second device can write / store the token into the cookie information of the browser.

[0107] The server can be Figure 1 The server 130 in the first request information, the user credential information and the Cookie information can all refer to the above description and will not be described in detail.

[0108] S2012. The second device splices the file information to the first link to generate first link information.

[0109] The first link is pre-configured for the second device. For example, it can be pre-configured to the second device by a developer, or it can be configured by a VConsole tool of the second device. The first link can be used to associate the file information.

[0110] For example, the first link may be http: / / local.example.com:8080 / dev-diy?cookie=xxxx. The second device may splice the file information to the first link, which may mean that the second device replaces "xxxx" in the first link with user credential information (such as Token) to obtain the first link information.

[0111] Furthermore, the second device may also splice the information of the first account and the device information of the second device to the first link.

[0112] The information of the first account may include one or more of the ID, type (which may also refer to a role, such as a patient or a doctor), and name of the first account. The device information of the second device may include one or more of the domain name of the debugging page, the system of the device, and the APP version number of the device.

[0113] The technical solution provided by the above embodiment brings at least the following beneficial effects: As can be seen from the above S2011-S2012, the second device can send the file information including the user credential information to the first device at one time in the form of a link, to indicate that the first device can obtain the user credential information and the file information after receiving the link. The first device does not need to obtain the page data of the debugging page from the server again, which reduces the signaling overhead and improves efficiency.

[0114] In a possible embodiment, Figure 7As shown, before S201, the method provided in the embodiment of the present application may further include S701.

[0115] S701. The second device displays a first debugging page.

[0116] In a possible implementation, after the second device obtains the user credential information of the first account, the second device may display the first debugging page on the page of the APP.

[0117] The technical solution provided by the above embodiment brings at least the following beneficial effects: As can be seen from the above S701, the developer can test the page to be debugged on the second device, and send the debug page with abnormalities to the first device. In this way, the first device does not need to search for the page to be debugged again, saving debugging time.

[0118] In a possible embodiment, Figure 8 As shown, the first device displaying the first debugging page in the above S204 may specifically include S2041 and S2042.

[0119] S2041. The first device writes the file information into the cache of a preset browser.

[0120] The preset browser may be pre-configured for the first device, and the preset browser may support displaying the first debugging page.

[0121] The first device may obtain the file information including the user credential information from the first link information, and then the first device may write / store the file information into the cache of the preset browser pre-configured by the first device.

[0122] S2042: The first device runs a preset browser and displays a first debugging page on the interface of the preset browser.

[0123] The preset browser may be a browser pre-installed on the first device, for example, a Chrome browser, etc., without limitation.

[0124] After the first device writes the file information including the user credential information into the cache of the preset browser, the preset browser can be run. Based on the file information, the preset browser can display the first debugging page.

[0125] In one example, Fig. 9As shown, when the second device responds to the user clicking the [Send Cookie] button, the second device sends the first link information to the first device. After the first device receives the first link information, it can display [Write Cookie to Browser] on the first session interface of the IM tool. In response to the developer clicking the [Write Cookie to Browser] button, the first device can run the browser and display the first debugging page.

[0126] The technical solution provided by the above embodiment brings at least the following beneficial effects: As can be seen from the above S2041-S2042, the first device can obtain the Cookie information including the Token corresponding to the first account from the first link information, and display the first debugging page on the preset browser, without having to enter the account and password of the first account again, and quickly open the first debugging page.

[0127] In a possible embodiment, when the first link information also includes information of the first account and device information of the second device, the method may further include: the first device displays the information of the first account and the device information of the second device on the first session interface.

[0128] The technical solution provided by the above embodiment brings at least the following beneficial effects: the developer can verify the first link information through the account information displayed on the session interface and the device information of the second device. For example, verify whether the debugging page associated with the first link information is a page that needs to be debugged. In this way, multiple users in the group corresponding to the first session interface can use the account information and the device information of the second device to accurately determine whether the first debugging page is a page that needs to be debugged.

[0129] In a possible embodiment, Fig.10 As shown, the method provided in the embodiment of the present application may also include S1001-S1004.

[0130] S1001. In response to a second login operation, a second device generates second link information and displays a second debugging page.

[0131] The second link information includes an association with a second debugging page. The second debugging page is a debugging page corresponding to a second account. The second account is different from the first account.

[0132] In a possible implementation, the second device may generate second link information and display a second debugging page in response to the user logging out of the first account and entering the account number and corresponding password of the second account. The method for the second device to generate the second link information and display the second debugging page can refer to the above S201 and S701, and will not be described in detail.

[0133] S1002: In response to a second sending operation, the second device sends second link information to one or more first devices. Correspondingly, the one or more first devices receive the second link information from the second device.

[0134] S1003: The first device displays second link information on the first session interface.

[0135] It should be noted that the specific implementation of the above S1002 and S1003 can refer to the description of the above S202 and S203 and will not be repeated here.

[0136] S1004. In response to the second operation, the first device deletes the first debugging page and displays the second debugging page.

[0137] The first device deleting the second debugging page may refer to the first device deleting file information corresponding to the first debugging page stored in a preset browser.

[0138] In one possible implementation, after the first device obtains the file information including the user credential information corresponding to the second account from the second link information, it can delete the file information including the user credential information corresponding to the first account, and write / store the file information including the user credential information corresponding to the second account into the cache of the preset browser.

[0139] The technical solution provided by the above embodiment brings at least the following beneficial effects: As can be seen from the above S901-S904, when debugging the debugging page corresponding to other accounts is needed, the developer can send the link information of the debugging page corresponding to the account to the first device. In this way, the developer can quickly obtain the debugging page corresponding to the account based on the link information.

[0140] It is understandable that, in actual implementation, the second device described in the embodiment of the present disclosure may include one or more hardware structures and / or software modules for implementing the display method of the corresponding debugging page, and these execution hardware structures and / or software modules may constitute an electronic device. It should be easily appreciated by those skilled in the art that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0141] Based on such understanding, the embodiments of the present disclosure also provide a display device for a debugging page, which is applied to a first device or to a chip in the first device. Fig.11 FIG. 1 is a schematic diagram showing the structure of a display device for a debugging page provided by an embodiment of the present disclosure. Fig.11 As shown, the display device of the debugging page may include: a receiving unit 1101 and a display unit 1102.

[0142] The receiving unit 1101 is configured to receive first link information associated with a first debugging page from a second device, where the first debugging page is a debugging page corresponding to a first account.

[0143] Display unit 1102, for displaying the first link information in the first conversation interface of the preset communication application corresponding to the group including the first plurality of user information.

[0144] The display unit 1102 is further configured to display a first debugging page in response to an operation of triggering the first link information by a user among the plurality of first users who uses the first device.

[0145] Optionally, the first link information includes file information corresponding to the first debugging page, and the file information includes user credential information corresponding to the first account. The device also includes a processing unit 1003. The processing unit 1003 is used to write the file information into the cache of the preset browser. The processing unit 1103 is also used to run the preset browser and control the display unit 1002 to display the first debugging page on the interface of the preset browser.

[0146] Optionally, the first link information further includes one or more of an ID and a name of the first account and device information of the second device. The display unit 1102 is further configured to display the information of the first account on the first session interface.

[0147] Optionally, the receiving unit 1101 is further configured to receive second link information associated with a second debugging page from a second device, where the second debugging page is a debugging page corresponding to the second account. The display unit 1102 is further configured to display the second link information on the first session interface; the processing unit 1003 is further configured to delete the first debugging page in response to the first user triggering the operation of the second link information, and control the display unit to display the second debugging page.

[0148] The embodiment of the present disclosure also provides a display device for a debugging page, which is applied to a second device or to a chip in the second device. Fig.12 FIG. 1 is a schematic diagram showing the structure of a display device for a debugging page provided by an embodiment of the present disclosure. Fig.12 As shown, the display device of the debugging page may include: a processing unit 1201 and a sending unit 1202.

[0149] Processing unit 1201 is used to generate first link information, where the first link information is associated with a first debugging page corresponding to a first account.

[0150] The sending unit 1202 is used to send first link information to one or more first devices in response to a first sending operation to instruct the one or more first devices to display the first link information in a first session interface of a preset communication application, where the first session interface includes information of multiple first users.

[0151] Optional, such as Fig.12 As shown, the apparatus further includes an acquisition unit 1203. The acquisition unit 1203 is configured to, in response to an operation of logging into a first debugging page corresponding to a first account, acquire the first corresponding user credential information and write the user credential information into the file information. The processing unit 1201 is specifically configured to splice the file information to the first link to generate the first link information, where the first link is pre-configured for the second device.

[0152] Optionally, the first link information also includes information of the first account, the information of the first account includes one or more of the ID, name, name of the first account, and device information of the second device. The device also includes a display unit 1204; the display unit 1204 is used to display the first debugging page.

[0153] Optionally, the processing unit 1201 is also used to generate second link information associated with a second debugging page in response to a second login operation, and control the display unit 1204 to display the second debugging page, where the second debugging page is a debugging page corresponding to the second account; the processing unit is also used to send the second link information to one or more first devices through the sending unit 1202 in response to a second sending operation.

[0154] As described above, the embodiment of the present disclosure can divide the display device of the debugging page into functional modules according to the above method example. Among them, the above integrated modules can be implemented in the form of hardware or in the form of software functional modules. In addition, it should be noted that the division of modules in the embodiment of the present disclosure is schematic and is only a logical function division. There may be other division methods in actual implementation. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.

[0155] Regarding the display device of the debugging page in the above embodiment, the specific manner in which each module performs operations and the beneficial effects possessed have been described in detail in the aforementioned method embodiment and will not be repeated here.

[0156] The disclosed embodiment also provides a display device for a debugging page. Fig.13The schematic diagram of the structure of the display device of the debugging page provided by the embodiment of the present disclosure is shown. The display device of the debugging page may include at least one processor 131, a communication bus 132, a memory 133 and at least one communication interface 134.

[0157] Processor 131 may be a processor (central processing unit, CPU), microprocessor unit, ASIC, or one or more integrated circuits for controlling the execution of the program of the disclosed solution. Fig.11 The function implemented by the processing unit 1103 in the display device of the debugging page is the same as Fig.13 The functions implemented by the processor 131 in are the same.

[0158] The communication bus 132 may include a pathway for transmitting information between the above-mentioned components.

[0159] The communication interface 134 uses any transceiver or other device for communicating with other devices or communication networks, such as servers, Ethernet, radio access networks (RAN), wireless local area networks (WLAN), etc. As an example, in combination with Fig.11 The function implemented by the receiving unit 1101 in the display device of the debugging page is the same as Fig.13 The communication interface 134 in FIG.

[0160] The memory 133 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processing unit through a bus. The memory may also be integrated with the processing unit.

[0161] The memory 133 is used to store application code for executing the solution of the present disclosure, and the execution is controlled by the processor 131. The processor 131 is used to execute the application code stored in the memory 133, so as to realize the functions in the method of the present disclosure.

[0162] In a specific implementation, as an embodiment, the processor 131 may include one or more CPUs, such as Fig.13 CPU0 and CPU1 in.

[0163] In a specific implementation, as an embodiment, the second device may include multiple processors, such as Fig.13 1 and 135. Each of these processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0164] In a specific implementation, as an embodiment, the display device of the debugging page may also include an input device 136 and an output device 137. The input device 136 communicates with the output device 137 and can accept user input in a variety of ways. For example, the input device 136 may be a mouse, a keyboard, a touch screen device, or a sensor device. The output device 137 communicates with the processor 131 and can display information in a variety of ways. For example, the output device 137 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, etc.

[0165] Those skilled in the art will understand that Fig.13 The structure shown in the figure does not constitute a limitation on the display device of the debugging page, and may include more or fewer components than those shown in the figure, or combine certain components, or adopt a different component arrangement.

[0166] The present disclosure also provides a computer-readable storage medium including instructions, and the computer-readable storage medium stores instructions. When the instructions in the computer-readable storage medium are executed by the processor of the computer device, the computer can execute the method for displaying the debugging page provided in the above-mentioned embodiment. For example, the computer-readable storage medium may be a memory 133 including instructions, and the above instructions may be executed by the processor 131 of the display device of the debugging page to complete the above method. For another example, the computer-readable storage medium may be a memory 133 including instructions, and the above instructions may be executed by the processor 131 of the server to complete the above method. Optionally, the computer-readable storage medium may be a non-temporary computer-readable storage medium, for example, the non-temporary computer-readable storage medium may be a ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.

[0167] The present disclosure also provides a computer program product, which includes computer instructions. When the computer instructions are executed on a display device of a debugging page, the display device of the debugging page executes the above Figure 2 , Figure 6-Figure 9 A method for displaying a debugging page as shown in any of the accompanying drawings.

[0168] like Fig.14 As shown, the present disclosure also provides a communication system, which may include a second device 141 and a first device 142. The second device 141 may be used to perform the above Figure 2 , Figure 6-Figure 8 The action performed by the second device in any of the figures, for example, can be used to perform S201 and S202. The first device 142 can be used to perform the above Figure 2 , Figure 6-Figure 8 The action performed by the first device in any of the figures, for example, can be used to perform S203 and S204.

[0169] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0170] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for displaying a debugging page, characterized in that: Using a first device, the method includes: Receiving first link information from a second device, where the first link information is associated with a first debugging page, and the first debugging page is a debugging page corresponding to the first account; Displaying the first link information on a first conversation interface of a preset communication application, where the group corresponding to the first conversation interface includes information of a plurality of first users; and the first link information carries an identifier for indicating the group corresponding to the first conversation interface; In response to a first operation, displaying the first debugging page, where the first operation is an operation by a first user triggering the first link information, and the first user is a user among the multiple first users who uses the first device; receiving second link information from the second device, where the second link information is associated with a second debugging page, and the second debugging page is a debugging page corresponding to the second account; Displaying the second link information on the first conversation interface; In response to a second operation, deleting file information of user credential information corresponding to the first account, and displaying the second debugging page, wherein the second operation is an operation by the first user to trigger the second link information; The first link information includes file information corresponding to the first debugging page, the file information includes user credential information corresponding to the first account, and the displaying of the first debugging page includes: Writing the file information into a cache of a preset browser; The preset browser is run, and the first debugging page is displayed on the interface of the preset browser.

2. The method according to claim 1, characterized in that The first link information further includes information of the first account and device information of the second device, the information of the first account includes one or more of an identification ID, a type, and a name of the first account, and the method further includes: The information of the first account and the device information of the second device are displayed on the first session interface.

3. A method for displaying a debugging page, characterized in that: Applied to the second device, the method includes: Generate first link information, where the first link information is associated with a first debugging page corresponding to the first account; In response to a first sending operation, the first link information is sent to one or more first devices to instruct the one or more first devices to display the first link information in a first session interface of a preset communication application, where the group corresponding to the first session interface includes information of a plurality of first users; and the first link information carries an identifier for indicating the group corresponding to the first session interface; In response to the second login operation, display a second debugging page and generate second link information, wherein the second debugging page is a debugging page corresponding to the second account, and the second link information is associated with the second debugging page; In response to a second sending operation, sending the second link information to the one or more first devices; The generating the first link information comprises: In response to a first login operation, obtaining user credential information corresponding to the first account, and writing the user credential information into file information, wherein the first login operation is an operation of logging into a first debugging page corresponding to the first account; The file information is spliced ​​to a first link to generate the first link information, where the first link is pre-configured for the second device.

4. The method according to claim 3, characterized in that The first link information also includes information of the first account and device information of the second device, the information of the first account includes one or more of an identification ID, a type, and a name of the first account, and after obtaining user credential information corresponding to the first account, the method further includes: The first debugging page is displayed.

5. A display device for a debugging page, characterized in that: Applied to a first device, the apparatus comprises: a receiving unit and a display unit; The receiving unit is configured to receive first link information from a second device, where the first link information is associated with a first debugging page, and the first debugging page is a debugging page corresponding to the first account; The display unit is used to display the first link information on a first conversation interface of a preset communication application, wherein the first conversation interface includes information of a plurality of first users; and the first link information carries an identifier for indicating a group corresponding to the first conversation interface; The display unit is further configured to display the first debugging page in response to a first operation, where the first operation is an operation of a first user triggering the first link information, and the first user is a user among the multiple first users who uses the first device; The receiving unit is further configured to receive second link information from a second device, where the second link information is associated with a second debugging page, and the second debugging page is a debugging page corresponding to the second account; The display unit is further configured to display the second link information on the first conversation interface; a processing unit, configured to delete file information of user credential information corresponding to the first account and control the display unit to display the second debugging page in response to a second operation, wherein the second operation is an operation by the first user to trigger the second link information; The first link information includes file information corresponding to the first debugging page, the file information includes user credential information corresponding to the first account, and the device further includes a processing unit; The processing unit is used to write the file information into the cache of a preset browser; The processing unit is further configured to run the preset browser and control the display unit to display the first debugging page on the interface of the preset browser.

6. The device according to claim 5, characterized in that The first link information further includes information of the first account and device information of the second device, and the information of the first account includes one or more of an identification ID, a type, and a name of the first account; The display unit is further configured to display information of the first account and device information of the second device on the first conversation interface.

7. A display device for a debugging page, characterized in that: Applied to a second device, the apparatus comprises a processing unit and a sending unit; The processing unit is configured to generate first link information, wherein the first link information is associated with a first debugging page corresponding to the first account; The sending unit is configured to send the first link information to one or more first devices in response to a first sending operation, so as to instruct the one or more first devices to display the first link information on a first session interface of a preset communication application, where the first session interface includes information of a plurality of first users; and the first link information carries an identifier for indicating a group corresponding to the first session interface; The processing unit is further configured to generate second link information in response to a second login operation, and control the display unit to display a second debugging page, where the second debugging page is a debugging page corresponding to the second account, and the second link information is associated with the second debugging page; The processing unit is further configured to send the second link information to one or more first devices through the sending unit in response to a second sending operation; The device also includes an acquisition unit; The acquisition unit is configured to acquire user credential information corresponding to the first account in response to a first login operation, and write the user credential into file information, wherein the first login operation is an operation of logging into a first debugging page corresponding to the first account; The processing unit is specifically configured to splice the file information into a first link to generate the first link information, where the first link is pre-configured for the second device.

8. The device according to claim 7, characterized in that The first link information further includes information of the first account and device information of the second device, the information of the first account includes one or more of an identification ID, a type, and a name of the first account, and the apparatus further includes a display unit; The display unit is used to display the first debugging page.

9. A computing device, characterized in that The computing device comprises: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instruction to implement the method for displaying a debugging page according to any one of claims 1-2 or any one of claims 3-4.

10. A computer-readable storage medium having instructions stored thereon, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of a computing device, the computing device is enabled to execute the method for displaying a debugging page as claimed in claim 1 or 2, or claim 3 or 4.

11. A computer program product comprising instructions, characterized in that When the instruction is executed on a computing device, the computing device is caused to execute the method for displaying a debugging page as claimed in claim 1 or 2, or claim 3 or 4.

12. A communication system, characterized in that: The communication system includes one or more first devices and a second device, any one of the one or more first devices is used to execute the method for displaying a debugging page as described in claim 1 or 2, and the second device is used to execute the method for displaying a debugging page as described in claim 3 or 4.

Images