Scenario access method and device for application

Abstract

Embodiments of the present disclosure provide a method and device for accessing a scene of an application, the method comprising: traversing user interfaces of the application to determine information of a jump path between the user interfaces of the application; and determining an available path of a user interface of a first target scene of the application from the jump path between the user interfaces of the application according to the information of the jump path. In this way, the available path of the user interface of the first target scene can be automatically determined, the first target scene can be accessed, and automatic testing of the scene of the application can be implemented, thereby improving the testing speed of the scene in the application.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a method and apparatus for accessing application scenarios. Background Technology

[0002] Applications (APPs) typically require testing before being released to the market to ensure stable operation on various types of terminal devices. APP testing often involves accessing specific scenarios for focused testing.

[0003] In related technologies, when testing a specific scenario within an application on a test terminal, testers need to manually access the scenario to remain within it for testing. For example, if testing the live streaming function of an application is required, testers need to manually access the application's live streaming scenario.

[0004] However, the testing speed of application scenarios is slow because testers manually access the application scenarios. Summary of the Invention

[0005] This disclosure provides an application scenario access method and apparatus to overcome the problem of slow testing speed of application scenarios in the prior art.

[0006] In a first aspect, embodiments of this disclosure provide an access method for an application scenario, applied to a server, the method comprising:

[0007] Traverse the application's user interface to determine information about the navigation paths between the application's user interfaces;

[0008] Based on the information about the jump paths, an available path to access the user interface of the first target scenario of the application is determined from the jump paths between the user interfaces of the application.

[0009] Secondly, embodiments of this disclosure provide an access method for an application scenario, applied to a client, the method comprising:

[0010] Receive information about available paths sent by the server. The available paths are paths to the user interface of the first target scenario of the application. The available paths are determined based on information about the jump paths between the user interfaces of the application.

[0011] Based on the information of the available paths, a recommended path is determined from the available paths;

[0012] Use the recommended path to access the user interface of the first target scene.

[0013] Thirdly, embodiments of this disclosure provide an access device for an application scenario, including:

[0014] The traversal module is used to traverse the application's user interface and determine the information on the navigation paths between the application's user interfaces.

[0015] The determining module is used to determine, based on the information of the jump path, an available path to access the user interface of the first target scene of the application from the jump paths between the user interfaces of the application.

[0016] Fourthly, embodiments of this disclosure provide an access device for an application scenario, including:

[0017] The receiving module is used to receive information about available paths sent by the server. The available paths are paths to the user interface of the first target scenario of the application. The available paths are determined based on information about the jump paths between the user interfaces of the application.

[0018] The determination module is used to determine a recommended path from the available paths based on the information of the available paths;

[0019] An access module is used to access the user interface of the first target scene using the recommended path.

[0020] Fifthly, embodiments of this disclosure provide a server, including: at least one processor and a memory;

[0021] The memory stores computer-executed instructions;

[0022] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the access methods for the application scenarios described in the first aspect and various possible designs of the first aspect.

[0023] Sixthly, embodiments of this disclosure provide a server, including: at least one processor and a memory;

[0024] The memory stores computer-executed instructions;

[0025] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the access methods for the application scenarios described in the second aspect above and various possible designs of the second aspect.

[0026] In a seventh aspect, embodiments of this disclosure provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the access methods for the application scenarios described in the first aspect and various possible designs of the first aspect.

[0027] Eighthly, embodiments of this disclosure provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the access methods for the application scenarios described in the second aspect and various possible designs of the second aspect.

[0028] In a ninth aspect, embodiments of this disclosure provide a computer program product, including computer instructions that, when executed by a processor, implement the access methods for the application scenarios described in the first aspect and various possible designs of the first aspect.

[0029] In a tenth aspect, embodiments of this disclosure provide a computer program product, including computer instructions that, when executed by a processor, implement the access methods for the application scenarios described in the second aspect and various possible designs of the second aspect.

[0030] This embodiment provides an application scenario access method and apparatus. First, it traverses the application's user interfaces to determine information about the navigation paths between them. Then, based on this navigation path information, it determines an available path to access the user interface of the application's first target scenario. This method automatically determines the available path to the user interface of the first target scenario, thereby enabling automated testing of application scenarios and improving the testing speed of application scenarios. Attached Figure Description

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

[0032] Figure 1 A schematic diagram illustrating an application scenario for an access method provided in this embodiment of the present disclosure;

[0033] Figure 2 Signaling interaction diagram of an access method for an application scenario provided in this embodiment of the disclosure;

[0034] Figure 3 A schematic diagram of a page structure tree provided in an embodiment of this disclosure;

[0035] Figure 4 A flowchart illustrating an access method for an application scenario provided in this embodiment of the disclosure;

[0036] Figure 5A flowchart illustrating an access method for another application scenario provided by an embodiment of this disclosure;

[0037] Figure 6 A structural block diagram of an access device for an application scenario provided in this disclosure embodiment;

[0038] Figure 7 A structural block diagram of an access device for another application scenario provided in this disclosure embodiment;

[0039] Figure 8 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0041] Applications (APPs) typically require testing before being released to the market to ensure stable operation on various types of terminal devices. APP testing often involves accessing specific scenarios for focused testing.

[0042] In related technologies, when testing a specific scenario within an application on a test terminal, testers need to manually access the scenario to remain within it for testing. For example, to test the live streaming function in an application, testers need to manually access the application's live streaming scenario. However, because manually accessing application scenarios is slow, the testing speed for that scenario is also slow.

[0043] To address the issue of slow testing speed in application scenarios mentioned above, this disclosure provides an application scenario access method and apparatus. By traversing the application's user interface to determine the jump paths between user interfaces, information on available paths to access the application's first target scenario is determined, thereby achieving automatic access to the first target scenario and improving the application scenario testing speed.

[0044] The following describes the use cases involved in this disclosure.

[0045] Figure 1 This is a schematic diagram illustrating a usage scenario for an application scenario access method provided in an embodiment of this disclosure. For example... Figure 1As shown, server 102 traverses the application's user interface to determine the jump paths between user interfaces, and then determines the available paths to access the user interface of the first target scenario. Subsequently, server 102 sends the information of the available paths to access the user interface of the first target scenario to client 101, so that client 101 can determine the recommended path to access the user interface of the first target scenario from the available paths and access the user interface of the first target scenario.

[0046] The client 101 can be a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in a smart home, etc. In this embodiment, the device for implementing the terminal's functions can be the terminal itself, or a device capable of supporting the terminal in implementing those functions, such as a chip system, which can be installed in the terminal. In this embodiment, the chip system can consist of chips, or it can include chips and other discrete components.

[0047] Server 102 can be, but is not limited to, a single web server, a group of multiple web servers, or a cloud based on cloud computing consisting of a large number of computers or web servers. Cloud computing is a type of distributed computing, consisting of a super virtual computer composed of a group of loosely coupled computers.

[0048] It should be understood that the application scenarios of the technical solutions disclosed herein can be... Figure 1 This can be applied to scenarios in the present invention, but not limited to them; it can also be applied to other scenarios that require application testing.

[0049] It is understood that the above-mentioned application scenario access method can be implemented by the application scenario access device provided in the embodiments of this disclosure. The application scenario access device can be part or all of a device, such as the above-mentioned test terminal and server terminal.

[0050] The technical solutions of the embodiments of this disclosure will be described in detail below with specific examples. These specific examples can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0051] Figure 2This is a signaling interaction diagram for an application scenario access method provided in this embodiment. The process of accessing the application scenario involved in this embodiment is as follows: Figure 2 As shown, the application's scene access methods include:

[0052] S201: The server iterates through the application's user interface to determine the navigation path between user interfaces.

[0053] In this disclosure, after receiving a test request for an application, the server can traverse the application's user interface to collect information on the navigation paths between user interfaces.

[0054] It should be understood that the embodiments of this application do not limit how the user interface of the application is traversed. In some embodiments, the controls of each user interface of the application can be triggered in sequence and the user interface to which the application is jumped can be recorded in order to traverse the user interface of the application.

[0055] This disclosure does not limit the information regarding the jump path between user interfaces. In some embodiments, the jump path information may include the identifier of the starting interface of the jump path, the identifier of the ending interface of the jump path, the page structure tree of the application's user interface, and the control that triggers the jump path.

[0056] The page structure tree of the application's user interface can reflect the navigation relationships between different user interfaces. For example, Figure 3 This is a schematic diagram of a page structure tree provided in an embodiment of this disclosure. Figure 3 As shown, user interface A can jump to user interface B and user interface C in the page structure tree. By triggering the first control on user interface A, one can jump from user interface A to user interface B, and by triggering the second control on user interface A, one can jump from user interface A to user interface C.

[0057] It should be understood that the embodiments of this disclosure do not limit the triggering method of the controls involved in triggering jump paths. For example, the operation performed by the control includes clicking the control or long-pressing the control.

[0058] S202: Based on the information about the redirection paths, the server determines the available path to access the user interface of the first target scenario of the application from the redirection paths between the application's user interfaces.

[0059] In this step, once the server determines the information about the navigation paths between the application's user interfaces, it can determine the available path to access the user interface of the application's first target scenario from the navigation paths between the application's user interfaces.

[0060] It should be understood that the embodiments disclosed herein do not limit the first target scenario, and it can be any scenario in the application. For example, the first target scenario can be a live streaming scenario, a conversation scenario, or a question-and-answer scenario, etc.

[0061] It should be understood that the embodiments of this disclosure do not limit how the available path of the user interface of the first target scenario of the application is determined. In some embodiments, the server may first determine the endpoint interface of the available path based on the identifier of the user interface of the first target scenario. Secondly, the server determines the starting interface of the available path based on the page structure tree. Thirdly, the server finally determines the controls that trigger each jump path between the starting interface and the endpoint interface of the available path.

[0062] For example, continue to refer to Figure 3 User interface A can navigate to user interface B, user interface C can navigate to user interface C, and user interface B can navigate to user interface C. If the first target scenario is user interface C, then the starting point of the available path can be user interface A, and the ending point of the available path can be user interface C. Therefore, there are two available paths: one from user interface A to user interface B to user interface C, and the other from user interface A to user interface C.

[0063] In some embodiments, for the starting screen of an available path, it can be determined whether the current user interface is the starting screen by comparing features extracted from the page structure tree. For the ending screen of an available path, it can be determined whether the available path has reached the user interface of the first target scene by using the recorded identifier of the ending screen.

[0064] In other embodiments, after determining the available path information for the first target scenario of the application, the available path information can be organized, the number of jumps (step size) for each available path can be added, and the available path information can be recorded in the database.

[0065] S203: The server tests the available paths and determines the test results. The test results are used to indicate whether the available paths can be replayed.

[0066] In this step, after determining the available path information to the user interface of the first target scene of the application, the available path can be tested to determine whether the available path is replayable.

[0067] It should be understood that this disclosure does not limit how the available paths are tested. For example, the server can first install a testing tool. Secondly, the server can use the testing tool to test the application described above, determining the required operations for each step from the start to the end of the available path as an operation strategy by using the available path information obtained from the database. Thirdly, the server can use the above operation strategy to test the available paths. Finally, the server uses the testing tool to record the test results for each available path.

[0068] If the test terminal successfully replays the scenario where the available path accesses the first target scene, the test result can be "Successfully replayed". If the test terminal fails to replay the scenario where the available path accesses the first target scene, the test result can be "Unsuccessfully replayed".

[0069] In some embodiments, after testing the available paths and determining the test results of the available paths, the test time of the available paths and the number of jumps of the available paths can also be recorded.

[0070] S204: The server sends information about available paths to the client, including the test results for available paths.

[0071] In this step, after the server completes the test of the available paths, it can send information about the available paths containing the test results to the client.

[0072] The available path information also includes the test time of the available path and the number of jumps to the available path.

[0073] S205: The client determines the recommended path from the available paths based on the available path information.

[0074] In this step, after the client receives the available path information sent by the server, it can determine the recommended path from the available paths based on the available path information.

[0075] It should be understood that the embodiments of this disclosure do not limit how the recommended path is determined. In some embodiments, the recommended path can be determined from the available paths based on the recommendation priority of the information of available paths.

[0076] It should be noted that the recommendation priority of the above test information can be preset. For example, the recommendation priority of test results can be set higher than the recommendation priority of the number of jumps to the available path, and the recommendation priority of the number of jumps to the available path can be set higher than the recommendation priority of the test time to the available path.

[0077] Accordingly, in some embodiments, the client can first determine the available path whose test result is successful playback based on the test information of the available paths. Secondly, the client can determine the available path with the fewest operation steps from the available paths whose test result is successful playback. Thirdly, the client can determine the available path whose test time is closest to the client's current time from the available paths with the fewest operation steps. Finally, the client can determine the recommended path from the available paths whose test time is closest to the current time.

[0078] For example, the client can first identify available paths A, B, and C that have a test result of "successful replay". Then, it compares the number of redirects for available paths A, B, and C to select the path with fewer redirects. If available paths A and B have 3 redirects each, and available path C has 10 redirects, then available path C is not recommended. Next, it compares the test times for available paths A and B to select the path whose test time is closer to the current situation. If available path A was tested 1 day ago, and available path B was tested 10 days ago, then available path A is selected as the recommended path.

[0079] S206: The client uses the recommended path to access the user interface of the first target scenario.

[0080] It should be understood that the client uses the recommended path to access the user interface of the first target scenario, similar to the replay method when testing the available paths, and will not be elaborated here.

[0081] The application scenario access method provided in this disclosure first traverses the application's user interface to determine information about the jump paths between user interfaces. Then, based on the jump path information, it determines an available path to access the user interface of the first target scenario of the application from the jump paths between user interfaces. In this way, the available path to the user interface of the first target scenario can be automatically determined, thereby accessing the first target scenario and achieving automated testing of application scenarios, thus improving the testing speed of application scenarios.

[0082] Based on the above embodiments, the following explains how to determine the recommended path from the available paths. Figure 4 This is a flowchart illustrating an application scenario access method provided in an embodiment of this disclosure. The executing entity in this embodiment is the client, such as... Figure 4 As shown, the application's scene access methods include:

[0083] S301: Receive information about available paths sent by the server.

[0084] The available path is the path to the user interface of the first target scenario of the application, and the available path is determined based on the information of the jump path between user interfaces of the application.

[0085] In some embodiments, the information on available paths includes the test time of the available path, the number of jumps of the available path, and the test results of the available path, the test results of the available path being used to indicate whether the available path is replayable.

[0086] In some embodiments, the recommended priority of the test results of the available path is greater than the recommended priority of the number of jumps of the available path, and the recommended priority of the number of jumps of the available path is greater than the recommended priority of the test time of the available path.

[0087] S302: Based on the test results of the available paths, determine the available paths that can be successfully replayed from the available paths.

[0088] S303: Determine the available path with the fewest jumps from the available paths that have been successfully replayed.

[0089] S304: Determine the available path with the fewest redirects that is closest to the client's current time as the recommended path.

[0090] S305: Access the user interface of the first target scene using the recommended path.

[0091] The technical terms, effects, features, and optional implementation methods of S301-S305 can be found in [reference]. Figure 2 The explanations of S201-S206 shown are redundant and will not be repeated here.

[0092] Based on the above embodiments, the following describes how to perform scene switching after accessing the user interface of the first target scene. Figure 5 This is a flowchart illustrating another application scenario access method provided in this embodiment. The execution entity in this embodiment is the client, such as... Figure 5 As shown, the application's scene access methods include:

[0093] S401: Access the user interface of the first target scene using the recommended path.

[0094] S402: Receive a jump instruction triggered by a target control in the user interface of the first target scene.

[0095] The scene transition indicator includes the identifier of the user interface of the second target scene;

[0096] S403: Determine whether the second target scene is in the scene whitelist.

[0097] If yes, proceed to step S404; otherwise, proceed to step S405.

[0098] S404: Jump from the user interface of the first target scene to the user interface of the second target scene.

[0099] S405: Triggered when the target control is determined to be invalid.

[0100] In this disclosure, after the test terminal successfully accesses the user interface of the first target scene through the recommended path, it can also jump to the user interface of the second target scene through the target control in the user interface of the first target scene.

[0101] It should be understood that in this disclosure, by using a scene whitelist, the client can remain in the user interface of the first target scene and only access scenes in the scene whitelist.

[0102] In some embodiments, if clicking a control within the first target scene or another whitelisted scene causes the user to exit the whitelisted scene, then the control is invalidated. Accordingly, after the invalidated control is triggered, no feedback is required to the user's action.

[0103] This method allows clients to access only those items on the whitelist, thereby improving data security.

[0104] The technical terms, effects, features, and optional implementation methods of S401-S405 can be found in [reference]. Figure 2 The explanations of S201-S204 shown are redundant and will not be repeated here.

[0105] The application scenario access method provided in this disclosure first traverses the application's user interface to determine information about the jump paths between user interfaces. Then, based on the jump path information, it determines an available path to access the user interface of the first target scenario of the application from the jump paths between user interfaces. In this way, the available path to the user interface of the first target scenario can be automatically determined, thereby accessing the first target scenario and achieving automated testing of application scenarios, thus improving the testing speed of application scenarios.

[0106] Corresponding to the stack processing method in the above embodiment, Figure 6 This is a structural block diagram of an access device for an application scenario provided by an embodiment of this disclosure. This access device can execute the access method for the application scenario described above on the server side. For ease of explanation, only the parts relevant to the embodiments of this disclosure are shown. (Refer to...) Figure 6 The scene access device 500 of the application includes: a traversal module 501, a determination module 502, a test module 503, and a sending module 504.

[0107] Traversal module 501 is used to traverse the application's user interface and determine information about the jump paths between user interfaces.

[0108] The determination module 502 is used to determine, based on the jump path information, the available path to access the user interface of the first target scene of the application from the jump paths between user interfaces of the application.

[0109] According to one or more embodiments of this disclosure, the information of the jump path includes an identifier of the starting interface of the jump path, an identifier of the ending interface of the jump path, a page structure tree of the application's user interface, and a control that triggers the jump path.

[0110] According to one or more embodiments of this disclosure, the determining module 502 is specifically configured to determine the endpoint interface of the available path based on the identifier of the user interface of the first target scene; determine the starting interface of the available path based on the page structure tree; and determine the control that triggers each jump path between the starting interface of the available path and the endpoint interface of the available path.

[0111] According to one or more embodiments of this disclosure, the scene access device 500 further includes:

[0112] Test module 503 is used to test the available paths, determine the test results of the available paths, and the test results are used to indicate whether the available paths can be replayed.

[0113] The sending module 504 is used to send information about available paths to the client, including the test results of the available paths.

[0114] According to one or more embodiments of this disclosure, the available path information may also include the test time of the available path and the number of jumps of the available path.

[0115] The application scene access device provided in this embodiment can be used to execute the technical solution of the above-described application scene access method embodiment on the server side. Its implementation principle and technical effect are similar, and will not be described again in this embodiment.

[0116] Corresponding to the stack processing method in the above embodiment, Figure 7 This is a structural block diagram of an access device for another application scenario provided by an embodiment of this disclosure. This access device can execute the access method for the client-side application scenario described above. For ease of explanation, only the parts relevant to the embodiments of this disclosure are shown. (Refer to...) Figure 7 The scene access device 600 of the application includes: a receiving module 601, a determining module 602 and an access module 603.

[0117] The receiving module 601 is used to receive information about available paths sent by the server. The available paths are the paths to the user interface of the first target scenario of the application. The available paths are determined based on the information about the jump paths between user interfaces of the application.

[0118] The determination module 602 is used to determine the recommended path from the available paths based on the information of the available paths;

[0119] Access module 603 is used to access the user interface of the first target scene using the recommended path.

[0120] According to one or more embodiments of this disclosure, the information of the available path includes the test time of the available path, the number of jumps of the available path, and the test result of the available path, the test result of the available path being used to indicate whether the available path is replayable.

[0121] According to one or more embodiments of this disclosure, the determining module 602 is specifically configured to determine the recommended priority of available paths based on the recommended priority of available path information.

[0122] According to one or more embodiments of this disclosure, the recommendation priority of the test results of the available path is greater than the recommendation priority of the number of jumps of the available path, and the recommendation priority of the number of jumps of the available path is greater than the recommendation priority of the test time of the available path.

[0123] According to one or more embodiments of this disclosure, the determining module 602 is specifically configured to determine the available paths for successful replay from the available paths based on the test results of the available paths; determine the available path with the fewest jumps from the available paths for successful replay; and determine the available path with the test time closest to the current time of the client from the available paths with the fewest jumps as the recommended path.

[0124] According to one or more embodiments of this disclosure, the receiving module 601 is further configured to receive a jump instruction triggered by a target control in the user interface of the first target scene, wherein the scene jump instruction includes an identifier of the user interface of the second target scene.

[0125] The determination module 602 is also used to determine whether the second target scene is in the scene whitelist;

[0126] Access module 603 is also used to, if so, jump from the user interface of the first target scene to the user interface of the second target scene.

[0127] According to one or more embodiments of this disclosure, the determining module 602 is further configured to determine, if not, that the target control is invalidally triggered.

[0128] The application scene access device provided in this embodiment can be used to execute the technical solution of the above-described application scene access method embodiment on the client side. Its implementation principle and technical effect are similar, and will not be described again here.

[0129] refer to Figure 8 The diagram illustrates a structural schematic of an electronic device 700 suitable for implementing embodiments of the present disclosure. The electronic device 700 can be a client or a server. The client can include, but is not limited to, mobile terminals such as mobile phones, laptops, digital radio receivers, personal digital assistants (PDAs), portable Android devices (PADs), portable media players (PMPs), in-vehicle terminals (e.g., in-vehicle navigation terminals), wearable electronic devices, and fixed terminals such as digital TVs, desktop computers, and smart home devices. Figure 8 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0130] like Figure 8 As shown, the electronic device 700 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703, to implement the scenario access method of the application described above in the embodiments of this disclosure. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing device 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0131] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic device 700 to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 8An electronic device 700 with various devices is shown; however, it should be understood that it is not required to implement or possess all of the devices shown. More or fewer devices may be implemented or possessed alternatively.

[0132] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 709, or installed from storage device 708, or installed from ROM 702. When the computer program is executed by processing device 701, the scenario access for the application defined in the methods of embodiments of this disclosure is performed.

[0133] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0134] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0135] The aforementioned computer-readable medium carries one or more programs that, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments, such as performing the application scenario access defined in the methods of the embodiments of this disclosure.

[0136] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, and conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a Local Area Network (LAN) or a Wide Area Network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0137] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0138] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The names of the units are not necessarily limiting in certain circumstances; for example, an acquisition module can also be described as a "unit for acquiring portrait images to be processed".

[0139] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0140] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0141] In a first aspect, embodiments of this disclosure provide a method for accessing application scenarios, applied to a server, the method comprising:

[0142] Traverse the application's user interface to determine information about the navigation paths between the application's user interfaces;

[0143] Based on the information about the jump paths, an available path to access the user interface of the first target scenario of the application is determined from the jump paths between the user interfaces of the application.

[0144] According to one or more embodiments of this disclosure, the information of the jump path includes an identifier of the starting interface of the jump path, an identifier of the ending interface of the jump path, a page structure tree of the application's user interface, and a control that triggers the jump path.

[0145] According to one or more embodiments of this disclosure, determining an available path to access the user interface of a first target scenario of the application from the jump paths between user interfaces of the application includes:

[0146] Based on the identifier of the user interface of the first target scene, determine the endpoint interface of the available path;

[0147] Based on the page structure tree, determine the starting interface of the available path;

[0148] Determine the controls that trigger each jump path between the starting screen and the ending screen of the available path.

[0149] According to one or more embodiments of this disclosure, after determining an available path to access the user interface of a first target scenario of the application from the jump paths between user interfaces of the application, the method further includes:

[0150] The available paths are tested to determine the test results, which indicate whether the available paths are playable.

[0151] The available path information is sent to the client, and the available path information includes the test results of the available path.

[0152] According to one or more embodiments of this disclosure, the information of the available path may also include the test time of the available path and the number of jumps of the available path.

[0153] Secondly, embodiments of this disclosure provide a method for accessing application scenarios, applied to a client, the method comprising:

[0154] Receive information about available paths sent by the server. The available paths are paths to the user interface of the first target scenario of the application. The available paths are determined based on information about the jump paths between the user interfaces of the application.

[0155] Based on the information of the available paths, a recommended path is determined from the available paths;

[0156] Use the recommended path to access the user interface of the first target scene.

[0157] According to one or more embodiments of this disclosure, the information of the available path includes the test time of the available path, the number of jumps of the available path, and the test result of the available path, wherein the test result of the available path is used to indicate whether the available path can be replayed.

[0158] According to one or more embodiments of this disclosure, determining a recommended path from the available paths based on the information of the available paths includes:

[0159] The recommendation priority of the available paths is determined based on the recommendation priority of the available path information.

[0160] According to one or more embodiments of this disclosure, the recommendation priority of the test results of the available path is greater than the recommendation priority of the number of jumps of the available path, and the recommendation priority of the number of jumps of the available path is greater than the recommendation priority of the test time of the available path.

[0161] According to one or more embodiments of this disclosure, determining a recommended path from the available paths includes:

[0162] Based on the test results of the available paths, the available paths that can be successfully replayed are determined from the available paths;

[0163] From the available paths that have been successfully replayed, determine the available path with the fewest jumps;

[0164] The recommended path is the one whose test time is closest to the client's current time from the available paths with the fewest redirects.

[0165] According to one or more embodiments of this disclosure, after accessing the user interface of the first target scene using the recommended path, the method further includes:

[0166] Receive a jump instruction triggered by a target control in the user interface of the first target scene, wherein the scene jump instruction contains an identifier of the user interface of the second target scene;

[0167] Determine whether the second target scenario is in the scenario whitelist;

[0168] If so, the user interface of the first target scene will jump to the user interface of the second target scene.

[0169] According to one or more embodiments of this disclosure, after determining whether the identifier of the second target scene is within the scene whitelist, the method further includes:

[0170] If not, then the target control is determined to be invalid.

[0171] Thirdly, embodiments of this disclosure provide an application scenario access device, the device comprising:

[0172] The traversal module is used to traverse the application's user interface and determine the information on the navigation paths between the application's user interfaces.

[0173] The determining module is used to determine, based on the information of the jump path, an available path to access the user interface of the first target scene of the application from the jump paths between the user interfaces of the application.

[0174] According to one or more embodiments of this disclosure, the information of the jump path includes an identifier of the starting interface of the jump path, an identifier of the ending interface of the jump path, a page structure tree of the application's user interface, and a control that triggers the jump path.

[0175] According to one or more embodiments of this disclosure, the determining module is specifically configured to: determine the endpoint interface of the available path based on the identifier of the user interface of the first target scene; determine the starting interface of the available path based on the page structure tree; and determine the control that triggers each jump path from the starting interface of the available path to the endpoint interface of the available path.

[0176] According to one or more embodiments of this disclosure, the scene access device further includes:

[0177] The testing module is used to test the available path and determine the test result of the available path. The test result is used to indicate whether the available path can be replayed.

[0178] The sending module is used to send the information of the available path to the client, the information of the available path including the test results of the available path.

[0179] According to one or more embodiments of this disclosure, the information of the available path may also include the test time of the available path and the number of jumps of the available path.

[0180] Fourthly, embodiments of this disclosure provide an application scenario access device, the device comprising:

[0181] The receiving module is used to receive information about available paths sent by the server. The available paths are paths to the user interface of the first target scenario of the application. The available paths are determined based on information about the jump paths between the user interfaces of the application.

[0182] The determination module is used to determine a recommended path from the available paths based on the information of the available paths;

[0183] An access module is used to access the user interface of the first target scene using the recommended path.

[0184] According to one or more embodiments of this disclosure, the information of the available path includes the test time of the available path, the number of jumps of the available path, and the test result of the available path, wherein the test result of the available path is used to indicate whether the available path can be replayed.

[0185] According to one or more embodiments of this disclosure, the determining module is specifically configured to determine the recommendation priority of the available paths based on the recommendation priority of the information of the available paths.

[0186] According to one or more embodiments of this disclosure, the recommendation priority of the test results of the available path is greater than the recommendation priority of the number of jumps of the available path, and the recommendation priority of the number of jumps of the available path is greater than the recommendation priority of the test time of the available path.

[0187] According to one or more embodiments of this disclosure, the determining module is specifically configured to: determine a successfully replayed available path from the available paths based on the test results of the available paths; determine the available path with the fewest jumps from the successfully replayed available paths; and determine the available path whose test time is closest to the current time of the client from the available paths with the fewest jumps as the recommended path.

[0188] According to one or more embodiments of this disclosure, the receiving module is further configured to receive a jump instruction triggered by a target control in the user interface of the first target scene, wherein the scene jump instruction includes an identifier of the user interface of the second target scene.

[0189] The determining module is further configured to determine whether the second target scene is in the scene whitelist;

[0190] The access module is further configured to, if so, jump from the user interface of the first target scene to the user interface of the second target scene.

[0191] According to one or more embodiments of this disclosure, the determining module is further configured to determine, if not, that the target control is invalidally triggered.

[0192] Fifthly, embodiments of this disclosure provide a server, including: at least one processor and a memory;

[0193] The memory stores computer-executed instructions;

[0194] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the access methods for the application scenarios described in the first aspect and various possible designs of the first aspect.

[0195] Sixthly, embodiments of this disclosure provide a client, including: at least one processor and a memory;

[0196] The memory stores computer-executed instructions;

[0197] The at least one processor executes the computer execution instructions stored in the memory, causing the at least one processor to perform the access methods for the application scenarios described in the second aspect above and various possible designs of the second aspect.

[0198] In a seventh aspect, embodiments of this disclosure provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the access method for the application scenario described in the first or second aspect above.

[0199] Eighthly, embodiments of this disclosure provide a computer program product, including computer instructions that, when executed by a processor, implement the access method for the application scenario described in the first or second aspect.

[0200] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0201] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0202] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A method for accessing application scenarios, characterized in that, Applied to the server side, the method includes: Traverse the application's user interface to determine information about the navigation paths between the application's user interfaces; Based on the information of the jump path, determine the available path to access the user interface of the first target scene of the application from the jump paths between the user interfaces of the application; The system sends the available path information to the client; the client determines a recommended path from the available paths based on the available path information, and uses the recommended path to access the user interface of the first target scene; and receives a jump instruction triggered by a target control in the user interface of the first target scene, the jump instruction containing an identifier of the user interface of the second target scene; determines whether the second target scene is in the scene whitelist; if yes, jumps from the user interface of the first target scene to the user interface of the second target scene; if no, determines that the target control is invalid.

2. The method according to claim 1, characterized in that, The information of the jump path includes the identifier of the starting interface of the jump path, the identifier of the ending interface of the jump path, the page structure tree of the application's user interface, and the control that triggers the jump path.

3. The method according to claim 2, characterized in that, Determining the available path to access the user interface of the first target scenario of the application from the jump paths between the user interfaces of the application includes: Based on the identifier of the user interface of the first target scene, determine the endpoint interface of the available path; Based on the page structure tree, determine the starting interface of the available path; Determine the controls that trigger each jump path between the starting screen and the ending screen of the available path.

4. The method according to any one of claims 1-3, characterized in that, After determining an available path to the user interface of the first target scenario of the application from the jump paths between the user interfaces of the application, the method further includes: The available paths are tested to determine the test results, which indicate whether the available paths can be replayed; the information of the available paths includes the test results.

5. The method according to claim 4, characterized in that, The information about the available paths also includes the test time of the available paths and the number of jumps of the available paths.

6. A method for accessing application scenarios, characterized in that, Applied to a client, the method includes: Receive information about available paths sent by the server. The available paths are paths to the user interface of the first target scenario of the application. The available paths are determined based on information about the jump paths between the user interfaces of the application. Based on the information of the available paths, a recommended path is determined from the available paths; Access the user interface of the first target scene using the recommended path; The method further includes: Receive a jump instruction triggered by a target control in the user interface of the first target scene, wherein the jump instruction contains an identifier of the user interface of the second target scene; Determine whether the second target scenario is in the scenario whitelist; If so, the user interface of the first target scene will jump to the user interface of the second target scene; If not, then the target control is determined to be invalid.

7. The method according to claim 6, characterized in that, The information of the available path includes the test time of the available path, the number of jumps of the available path, and the test result of the available path. The test result of the available path is used to indicate whether the available path can be replayed.

8. The method according to claim 7, characterized in that, The step of determining a recommended path from the available paths based on the available path information includes: The recommendation priority of the available paths is determined based on the recommendation priority of the available path information.

9. The method according to claim 8, characterized in that, The recommendation priority of the test results of the available path is greater than the recommendation priority of the number of jumps of the available path, and the recommendation priority of the number of jumps of the available path is greater than the recommendation priority of the test time of the available path.

10. The method according to claim 9, characterized in that, Determining the recommended path from the available paths includes: Based on the test results of the available paths, the available paths that can be successfully replayed are determined from the available paths; From the available paths that have been successfully replayed, determine the available path with the fewest jumps; The recommended path is the one whose test time is closest to the client's current time from the available paths with the fewest redirects.

11. An application scene access device, characterized in that, The device includes: The traversal module is used to traverse the application's user interface and determine the information on the jump paths between the application's user interfaces; The determining module is used to determine, based on the information of the jumping path, an available path to access the user interface of the first target scene of the application from the jumping paths between the user interfaces of the application; The sending module is used to send the information of the available paths to the client; the client is used to determine a recommended path from the available paths based on the information of the available paths, and use the recommended path to access the user interface of the first target scene; and to receive a jump instruction triggered by a target control in the user interface of the first target scene, the jump instruction containing an identifier of the user interface of the second target scene; determine whether the second target scene is in the scene whitelist; if yes, jump from the user interface of the first target scene to the user interface of the second target scene; if no, determine that the target control is invalid.

12. An application scene access device, characterized in that, The device includes: The receiving module is used to receive information about available paths sent by the server. The available paths are paths to the user interface of the first target scenario of the application. The available paths are determined based on information about the jump paths between the user interfaces of the application. The determination module is used to determine a recommended path from the available paths based on the information of the available paths; An access module is used to access the user interface of the first target scene using the recommended path; The receiving module is further configured to receive a jump instruction triggered by a target control in the user interface of the first target scene, wherein the jump instruction contains an identifier of the user interface of the second target scene. The determining module is further configured to determine whether the second target scene is in the scene whitelist; The access module is further configured to, if so, jump from the user interface of the first target scene to the user interface of the second target scene; The determining module is further configured to determine that the target control is invalid if no such determination is made.

13. A server, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method as described in any one of claims 1 to 5.

14. A client, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method as described in any one of claims 6 to 10.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the method as described in any one of claims 1 to 10.

16. A computer program product comprising computer instructions, characterized in that, When executed by a processor, the computer instructions implement the method described in any one of claims 1 to 10.

Images