Interface processing method, system, device, readable storage medium and program product

Abstract

This invention relates to the field of computer technology, specifically to an interface processing method, system, device, readable storage medium, and program product. The method drives a terminal-type electronic device to run a test application through test cases. This execution of test cases collects runtime logs corresponding to multiple frames of interface display without any added display effects, used to analyze the basic load data of the interface without display effects. It also collects runtime logs corresponding to multiple frames of interface display with individual display effects, used to analyze the load data and load increments generated when those effects are applied. Thus, based on the load data extracted from the collected runtime logs, the load increments caused by various individual animations or visual effects can be accurately analyzed for subsequent load data analysis and simulation processes.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more specifically to an interface processing method, system, device, readable storage medium, and program product. Background Technology

[0002] With the rapid development of computer technology and image processing technology, user experience (UX) design has become increasingly sophisticated. In UX design, the combination of motion effects and visual effects can present excellent interface display effects, thereby enhancing the user experience of a product. Motion effects refer to the dynamic changes of interface elements over time, while visual effects refer to the visual presentation effects of interface elements.

[0003] It is understandable that the presentation of the aforementioned animations and visual effects requires the computing power provided by processors such as the central processing unit (CPU) and graphics processing unit (GPU) to execute corresponding programs or algorithms to complete drawing, rendering, and display processing. Therefore, in UX design, adding animations and / or adding animation designs to interface elements will increase the consumption of computing resources provided by processors such as the CPU and GPU when electronic devices display the relevant interfaces and present the corresponding animations and visual effects. In other words, it increases the load on processors such as the CPU and GPU, which in turn leads to performance degradation and increased power consumption of electronic devices.

[0004] Therefore, there is a need for a solution that can accurately measure the load and power consumption impact caused by the display of related interfaces with animation and / or visual effects, to guide the UX design or program development and optimization processes of target applications, so as to improve the rationality and feasibility of UX design. Summary of the Invention

[0005] This application provides an interface processing method, system, device, readable storage medium, and program product. Based on the load data extracted from collected operation logs, it can accurately analyze the load increment brought about by various individual animations or visual effects, and can also accurately analyze the combined load increment brought about by combinations of effects. Furthermore, based on various load increments, combined load increments, and scene load data corresponding to each display scene, it can finely determine the load changes brought to the relevant interface by each animation or visual effect, and each animation and / or combination of visual effects. It can also achieve precise load analysis of the image processing process of each frame of the interface, which is beneficial to improving the accuracy of subsequent data analysis and also facilitates the flexible combination of various types of load data to meet more data analysis needs.

[0006] In a first aspect, this application provides an interface processing method applied to a first electronic device. The method includes: receiving a first test instruction, wherein the first test instruction is used to instruct a load test on the display process of a first interface set, the first interface set including multiple frames of interfaces that change continuously with the interface refresh time; responding to the first test instruction, running a first application to execute a first test case and generating a first running log, wherein the first running log includes at least basic load data corresponding to the display process of the first interface set; receiving a second test instruction, wherein the second test instruction is used to instruct a load test on the display process of a second interface set, each frame of the second interface set corresponding to each frame of the first interface set, and each frame of the second interface set having a corresponding added first display effect; responding to the second test instruction, running the first application to execute a second test case and generating a second running log, wherein the second running log includes at least the first load data corresponding to the display process of the second interface set; and, the basic load data and the first load data are obtained based on application tags corresponding to the first application and interface tags corresponding to each frame of the interface, respectively, the first load data including a first identification parameter corresponding to the first display effect, and the difference between the first load data and the basic load data is a first load increment corresponding to the first display effect.

[0007] For example, the first electronic device mentioned above can be a mobile phone or other electronic device capable of running test applications and target applications, and the first application mentioned above can be a test application, such as a benchmark application. In this case, the first electronic device can be a test device. The first interface set mentioned above can include multiple frames of interfaces with animation effects and / or visual effects added to the relevant interfaces to present specific display effects. Here, the first interface set and the various interface sets described below refer to multiple frames of interfaces that change continuously with the interface refresh time. This application describes the multiple frames of interfaces displayed in different interface refresh time periods using the concept of interface sets, and it should not be regarded as a limitation on the combination of each interface.

[0008] The first test case mentioned above can be a basic test case used to test basic load data. This test case can be a pre-set or pre-loaded test case into the first electronic device. The second test case mentioned above can be a test case used to test individual display effects (e.g., the first display effect). This test case can correspond to the individual display effect to be tested and can be pre-set or pre-loaded into the first electronic device. The first display effect mentioned above can be any one of n display effects added to the relevant interface. The first display effect can be, for example, visual effects such as blur, shadow, brightening, light and shadow, particles, color, shape, size, gradient, etc., or it can be animation effects such as transition animation, loading animation, interactive animation, looping animation, etc. The first load data obtained under the action of the first display effect can be used to analyze the load increment corresponding to the first display effect (i.e., the individual display effect).

[0009] Thus, the interface processing method provided above can accurately analyze the load increment brought about by various dynamic or visual effects individually based on the load data extracted from the collected operation logs, so as to be used for subsequent related load data analysis and simulation processes.

[0010] In one possible implementation of the first aspect described above, the first display effect is configured with a first attribute parameter, and the first load increment corresponds to the first attribute parameter.

[0011] In one possible implementation of the first aspect above, the method further includes: receiving a third test instruction, wherein the third test instruction is used to instruct a load test to be performed on the display process of a third interface set, each frame interface in the third interface set corresponds to each frame interface in the first interface set, each frame interface in the third interface set has a corresponding added first display effect, and the first display effect is configured with a second attribute parameter, the second attribute parameter being different from the first attribute parameter; in response to the third test instruction, running a first application to execute a third test case and generating a third running log, wherein the third running log includes at least the second load data generated corresponding to the display process of the third interface set; and the difference between the second load data and the basic load data is a second load increment corresponding to the first display effect, wherein the second load increment is different from the first load increment.

[0012] For example, the third test case mentioned above can also be a test case for testing a single display effect (e.g., the first display effect). This test case can correspond to the single display effect to be tested and can be preset or pre-loaded into the first electronic device. However, unlike the second test case mentioned above, the attribute parameters configured for the first display effect in this third test case can be different. That is, the load data corresponding to the first display effect can be related to the corresponding configured attribute parameters, including the first load data obtained under the constraint of the first attribute parameter, the second load data obtained under the constraint of the second attribute parameter, etc. Correspondingly, the load increment corresponding to the first display effect also includes the first load increment corresponding to the first attribute parameter and the second load increment corresponding to the second attribute parameter, etc.

[0013] In one possible implementation of the first aspect above, the method further includes: receiving a fourth test instruction, wherein the fourth test instruction is used to instruct a load test to be performed on the display process of a fourth interface set, wherein each frame interface in the fourth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fourth interface set has a corresponding added second display effect, the second display effect being different from the first display effect; in response to the fourth test instruction, running a first application to execute a fourth test case and generating a fourth running log, wherein the fourth running log includes at least third load data corresponding to the display process of the fourth interface set; and the third load data includes a second identification parameter corresponding to the second display effect, the difference between the third load data and the basic load data being a third load increment corresponding to the second display effect.

[0014] For example, the third test case mentioned above could be a test case for testing another separate display effect (e.g., a second display effect), which could correspond to the separate display effect to be tested and be preset or pre-loaded into the first electronic device.

[0015] In one possible implementation of the first aspect above, the method further includes: receiving a fifth test instruction, wherein the fifth test instruction is used to instruct a load test to be performed on the display process of a fifth interface set, each frame interface in the fifth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fifth interface set has a corresponding added first effect combination, the first effect combination including at least two of n display effects, where n is an integer greater than or equal to 2, and the n display effects include the first display effect; in response to the fifth test instruction, running a first application to execute a fifth test case and generating a fifth running log, wherein the fifth running log includes at least fourth load data corresponding to the display process of the fifth interface set; and the fourth load data includes a first combination identification parameter corresponding to the first effect combination, and the difference between the fourth load data and the basic load data is the first combination load increment corresponding to the first effect combination.

[0016] For example, the third test case mentioned above could be a test case for testing a combination of multiple display effects (e.g., the first effect combination). This test case could correspond to the combination of multiple display effects to be tested and could be preset or pre-loaded into the first electronic device. The multiple display effects could include the same display effect under different attribute parameter constraints, or they could include different display effects, which will not be elaborated here.

[0017] Thus, the interface processing method provided above can accurately analyze the combined load increment caused by certain effect combinations based on the load data extracted from the collected operation logs.

[0018] In one possible implementation of the first aspect described above, the fourth load data includes a first scene identifier corresponding to the first effect combination, the first scene identifier being used to indicate a first display scene of the multi-frame interface of the first interface set and the first effect combination, and the fourth load data being the first scene load data corresponding to the first display scene.

[0019] In one possible implementation of the first aspect above, the method further includes: receiving a sixth test instruction, wherein the sixth test instruction is used to instruct a load test to be performed on p display effect combinations corresponding to the p frame interface set of the second application, where p is an integer greater than or equal to 1; running the second application in response to the sixth test instruction, and generating a sixth running log, wherein the sixth running log includes p scene logs corresponding to the p display effect combinations, and each scene log includes corresponding scene load data.

[0020] For example, if the second application mentioned above is a target application to be developed or optimized, the runtime logs generated by this application can be used to extract scene logs corresponding to multiple frames of the interface displayed within one or more interface refresh periods, i.e., the aforementioned p scene logs. Each scene log can include scene load data corresponding to the display scene corresponding to the added display effects or combinations of effects in each frame of the interface. Furthermore, the scene load data extracted from the runtime logs generated by the second application can be directly updated to the second database as scene load data for the corresponding display scene for later use.

[0021] In one possible implementation of the first aspect above, the first scene log in the p scene logs includes second scene load data corresponding to the second display scene, the multi-frame interface corresponding to the second display scene has a corresponding added second effect combination, and the method further includes: providing a sixth runtime log to the server; receiving a sixth test case generated based on the first scene log and a seventh test instruction instructing the execution of the sixth test case, wherein the sixth test case includes a test script corresponding to a sixth interface set with the second effect combination, the multi-frame interface in the sixth interface set corresponds to the multi-frame interface displayed in the second display scene respectively; in response to the seventh test instruction, running the first application to execute the sixth test case and generating a seventh runtime log, wherein the seventh runtime log includes at least fifth load data corresponding to the display process of the sixth interface set; the difference between the fifth load data and the basic load data is the second combination load increment corresponding to the second effect combination.

[0022] In one possible implementation of the first aspect above, the fifth load data includes a second scene identifier for indicating the second display scene, and the second scene identifier corresponds to the second effect combination; and the sixth test case is a test case generated on the server without load increments having the second scene identifier.

[0023] That is, if the scene load data and related load increments for the corresponding scene do not exist in the second database, supplementary tests can be performed on the display scene to obtain the scene load data and related load increments for the corresponding scene, and then updated to the second database for use.

[0024] Secondly, this application provides an interface processing method applied to a second electronic device. The method includes: acquiring first formatted data corresponding to a first running log of a first application, wherein the first running log includes at least basic load data generated corresponding to the display process of a first interface set, and the first interface set includes multiple frames of interfaces that change continuously with the interface refresh time; extracting basic load data from the first formatted data according to the application tag of the first application and the interface tag corresponding to each frame of the interface; and acquiring second formatted data corresponding to a second running log of the first application, wherein the second running log includes at least the first load data generated corresponding to the display process of the second interface set, each frame of the second interface set corresponds to each frame of the first interface set, and each frame of the second interface set has a corresponding added first display effect; extracting first load data from the second formatted data according to the application tag, the interface tag, and a first identification parameter corresponding to the first display effect; and determining a first load increment corresponding to the first display effect according to the difference between the first load data and the basic load data.

[0025] For example, the second electronic device described above can be a server, or it can be referred to as the cloud, on which a load analysis service can be deployed to perform the steps of the interface processing method described above. In other embodiments, the second electronic device described above can also be a server cluster, and there is no limitation here.

[0026] In one possible implementation of the second aspect above, the first display effect is configured with a first attribute parameter, and the first load increment corresponds to the first attribute parameter.

[0027] In one possible implementation of the second aspect above, the method further includes: obtaining third formatted data obtained by converting the third runtime log of the first application, wherein the third runtime log includes at least second load data generated corresponding to the display process of the third interface set, each frame interface in the third interface set corresponds to each frame interface in the first interface set, each frame interface in the third interface set has a corresponding added first display effect, and the first display effect is configured with a second attribute parameter, the second attribute parameter being different from the first attribute parameter; extracting second load data from the third formatted data according to the application tag, interface tag and first identification parameter; determining a second load increment corresponding to the first display effect according to the difference between the second load data and the basic load data, the second load increment corresponding to the second attribute parameter, wherein the second load increment is different from the first load increment.

[0028] In one possible implementation of the second aspect above, the method further includes: obtaining fourth formatted data converted from the fourth runtime log of the first application, wherein the fourth runtime log includes at least third load data generated corresponding to the display process of the fourth interface set, each frame interface in the fourth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fourth interface set has a corresponding added second display effect, the second display effect being different from the first display effect; extracting third load data from the fourth formatted data according to the application tag, the interface tag, and the second identification parameter corresponding to the second display effect; and determining the third load increment corresponding to the second display effect according to the difference between the third load data and the basic load data.

[0029] In one possible implementation of the second aspect above, the method further includes: obtaining fifth formatted data converted from the fifth runtime log of the first application, wherein the fifth runtime log includes at least fourth load data generated corresponding to the display process of the fifth interface set, each frame interface in the fifth interface set corresponds to each frame interface in the first interface set, each frame interface in the fifth interface set has a corresponding added first effect combination, the first effect combination includes at least two display effects from n display effects, where n is an integer greater than or equal to 2, the n display effects include the first display effect, and the fourth load data includes a first combination identification parameter corresponding to the first effect combination; extracting the fourth load data from the fifth formatted data according to the application tag, interface tag and the first combination identification parameter; and determining the first combination load increment corresponding to the first effect combination according to the difference between the fourth load data and the basic load data.

[0030] In one possible implementation of the second aspect above, the second electronic device includes a first database for storing basic load data and load increments, and the method includes: adding a first identification parameter to a first load increment and storing the first load increment having the first identification parameter in the first database; and / or adding a first combination identification parameter to a first combined load increment and storing the first combined load increment having the first combination identification parameter in the first database.

[0031] In one possible implementation of the second aspect above, the method further includes: obtaining the sixth formatted data corresponding to the sixth running log of the second application, wherein the sixth running log includes p scene logs corresponding to the p frame interface set, where p is an integer greater than or equal to 1, the p frame interface set corresponds to p added display effect combinations, and each display effect combination corresponds to scene load data; parsing the sixth formatted data to obtain the p scene logs and the scene load data corresponding to each scene log.

[0032] In one possible implementation of the second aspect above, the second electronic device includes a second database, which is at least used to store scene load data, wherein the first scene log in the p scene logs includes second scene load data corresponding to the second display scene, and the second display scene corresponds to the addition of a second effect combination to the multi-frame interface displayed. Furthermore, the method includes: detecting that no load data with a second scene identifier is matched in the second database, wherein the second scene identifier is used to indicate the second display scene; adding a second scene identifier to the second scene load data; and storing the second scene load data with the second scene identifier in the second database.

[0033] In one possible implementation of the second aspect above, the second database is further used to store load increments corresponding to load data for each scenario, and the method includes: detecting that no load increment with a second scenario identifier is matched in the first database; generating a corresponding test case configuration file according to the second effect combination corresponding to the second scenario identifier, wherein the test case configuration file includes identification parameters and attribute parameters corresponding to the definition of each display effect in the second effect combination, and the test case configuration file is used to generate a sixth test case, the sixth test case including a test script corresponding to a sixth interface set with the second effect combination, the multi-frame interfaces in the sixth interface set corresponding to the multi-frame interfaces displayed in the second display scenario respectively; converting the test case configuration file into a sixth test case through a third electronic device and sending it to the first electronic device; obtaining the seventh formatted data corresponding to the seventh running log of the first application, wherein the seventh running log includes at least the fifth load data generated corresponding to the display process of the sixth interface set, wherein the first application runs on the first electronic device; determining the second combination load increment corresponding to the second effect combination according to the difference between the fifth load data and the basic load data; adding a second scenario identifier to the second combination load increment, and storing the second combination load increment with the second scenario identifier in the first database.

[0034] In one possible implementation of the second aspect above, the method further includes: storing a second combined load increment having a second scenario identifier into a second database.

[0035] In one possible implementation of the first and second aspects described above, the first application is a benchmark application, and the first or second runtime log includes a trace log.

[0036] In one possible implementation of the first and second aspects above, the type of the first display effect includes motion effects or visual effects, wherein the motion effect indicates the effect of the first element in the multi-frame interface changing at least one of position, size and color as the interface refresh time changes, and the attribute parameters of the motion effect include at least the duration of the motion effect related to the interface refresh time; the visual effect indicates the specific visual effect presented when the first element in the multi-frame interface is displayed on the corresponding interface.

[0037] In one possible implementation of the first and second aspects above, the base load data or the first load data includes at least one of the following: central processing unit load data; graphics processor load data; digital signal processor load data; integrated processor load data.

[0038] The load increments corresponding to various display effects or combinations of effects can be stored in a pre-deployed test load database (i.e., the first database mentioned above) in the cloud or on a server. This first database can also store basic load data, such as the load data generated by displaying multiple frames of the interface without any added display effects or combinations of effects during the operation of the test application on the first electronic device. The scene load data corresponding to various effect combinations can be stored in a pre-deployed scene load database (i.e., the second database mentioned above) in the cloud or on a server. In this embodiment, the scene load database can also store the combined load increments resulting from each effect combination.

[0039] It is understood that the aforementioned second electronic device (e.g., a server) can obtain the scene identifier of the display scene corresponding to each interface from the disassembled load data, and use the scene identifier to query the aforementioned first or second database to see if there is a matching load increment, combined load increment, and scene load data. If a matching result is found, the server can provide the matched load increment, combined load increment, and scene load data to a terminal-type electronic device with a simulation client installed, i.e., the aforementioned third electronic device, such as a computer, to simulate and analyze the scene load and device performance. If no matching result is found, the server can, on the one hand, match the relevant basic load, load increment, and / or combined load increment from the first or second database according to the determined display effect or effect combination type and identification parameters, as well as the attribute parameters corresponding to each display effect or effect combination, to estimate the corresponding scene load size; on the other hand, the server can generate a test case configuration file and define the identification parameters and attribute parameters corresponding to each determined display effect or effect combination.

[0040] The test case configuration file generated above can be converted into test cases by terminal electronic devices (i.e., the third electronic devices mentioned below, such as computers) that have deployed the test framework, and then provided to terminal electronic devices with the benchmark application installed. This triggers the electronic devices to run the benchmark application and execute the test cases for supplementary testing. When the corresponding running logs are provided to the server, the load increment or combined load increment of the corresponding display effect or effect combination can be determined through the above test process.

[0041] Thirdly, this application provides an interface processing method applied to a third electronic device. The method includes: receiving an eighth operation log, wherein the eighth operation log corresponds to the process of a first electronic device displaying a multi-frame interface of a sixth interface set, the sixth interface set corresponding to the addition of a fourth effect combination, the fourth effect combination corresponding to a third display scene, and the eighth operation log including a third scene identifier for indicating the third display scene; converting the eighth operation log into eighth formatted data and sending the eighth formatted data to a server; obtaining the third scene identifier extracted according to the eighth formatted data and q display effects included in the fourth effect combination, wherein q is a positive integer; sending a load data acquisition request corresponding to the fourth effect combination to the server, wherein the load data acquisition request includes at least the third scene identifier corresponding to the fourth effect combination and the identification parameters corresponding to the q display effects; receiving scene load data matching the fourth effect combination, as well as the combined load increment matching the fourth effect combination and the load increment corresponding to the q display effects in the fourth effect combination; and displaying a load simulation interface corresponding to the third display scene, wherein the load simulation interface includes at least one control corresponding to the addition, deletion, and modification of the q display effects.

[0042] For example, the aforementioned third electronic device can be a computer. A simulation client and a testing framework can be deployed on this third electronic device. The aforementioned sixth set of interfaces can be the set of interfaces displayed when the benchmark application executes the corresponding test cases, or it can be the set of interfaces displayed during the corresponding interface refresh period of the target application to be developed or optimized.

[0043] In one possible implementation of the third aspect above, if no scene load data matching the fourth effect combination is received, the method further includes: receiving a test case configuration file generated based on the identification parameters corresponding to the q display effects of the fourth effect combination, wherein the test case configuration file includes the identification parameters corresponding to the q display effects and the attribute parameters set for the q display effects, the test case configuration file is used to generate a seventh test case, the seventh test case is used to perform load testing on the fourth display scene corresponding to the fourth effect combination, and the seventh test case corresponds to the fourth scene identifier indicating the fourth display scene; sending the seventh test case to the first electronic device, and obtaining the first electronic device running the first application The ninth runtime log generated by executing the seventh test case includes the sixth load data generated corresponding to the process of the first electronic device displaying multiple frames of the seventh interface set. The multiple frames of the seventh interface set correspond to the multiple frames of the sixth interface set. The ninth runtime log is converted into ninth formatted data and sent to the server. The sixth load data extracted based on the ninth formatted data and the combined load increment corresponding to the fourth effect combination are obtained, and the load increments corresponding to the q display effects are obtained respectively. The load simulation interface corresponding to the fourth display scene is displayed, wherein the load simulation interface includes at least one control corresponding to the addition, deletion and modification of the q display effects.

[0044] In one possible implementation of the third aspect above, the first application is a benchmark application, and the eighth or ninth runtime log includes a trace log.

[0045] The interface processing solution provided in this application can also simulate scene load data and changes, i.e., load simulation. This simulates the load changes generated by the combination of motion effects and / or visual effects on relevant interfaces in more display scenarios. This is beneficial for guiding the UX design, program development, and optimization processes of the target application's related interfaces, thereby improving the rationality and feasibility of the UX design. For example, based on the simulated load changes, the type, quantity, and corresponding attribute parameters of the motion effects and / or visual effects finally added to the relevant multi-frame interfaces of the target application can be determined. This accurately measures and presents the impact of the added motion effects and / or visual effects on the load and power consumption of electronic devices, thereby controlling the balance between the display effect of the target application and the load on terminal electronic devices during runtime.

[0046] Fourthly, this application provides an interface processing system, characterized in that it includes a first electronic device and a second electronic device, wherein the first electronic device is used to respond to a received first test instruction, run a first application to execute a first test case, and generate a first operation log, wherein the first test instruction is used to instruct a load test on the display process of a first interface set, the first interface set including multiple frames of interfaces that change continuously with the interface refresh time, and the first operation log includes at least the basic load data generated corresponding to the display process of the first interface set; and the first electronic device is also used to respond to a received second test instruction, run the first application to execute a second test case, and generate a second operation log, wherein the second test instruction is used to instruct a load test on the display process of a second interface set, each frame of the second interface set corresponds to each frame of the first interface set, each frame of the second interface set has a corresponding added first display effect, the first display effect is configured with a first attribute parameter, and the second operation log includes at least the first load data generated corresponding to the display process of the second interface set; and the first electronic device is also used to respond to a received third test instruction, run the first application to execute a third test case, and generate a third operation log, wherein the third test instruction is used to instruct a load test on the display process of a third interface set, the third interface set... Each frame of the third interface set corresponds to each frame of the first interface set. Each frame of the third interface set has a corresponding added first display effect, and the first display effect is configured with a second attribute parameter. The second attribute parameter is different from the first attribute parameter. The third operation log includes at least the second load data generated corresponding to the display process of the third interface set. The second electronic device is used to extract basic load data from the first formatted data converted from the first operation log based on the application tag corresponding to the first application and the interface tag corresponding to each frame of the first interface. It is also used to extract first load data from the second formatted data converted from the second operation log based on the application tag, the interface tag, and the first identification parameter corresponding to the first display effect. Furthermore, it is used to extract second load data from the third formatted data converted from the third operation log based on the application tag, the interface tag, and the first identification parameter corresponding to the first display effect. The second electronic device is also used to determine the first load increment corresponding to the first display effect based on the difference between the first load data and the basic load data. The first load increment corresponds to the first attribute parameter. It is also used to determine the second load increment corresponding to the first display effect based on the difference between the second load data and the basic load data. The second load increment corresponds to the second attribute parameter. The second load increment is different from the first load increment.

[0047] In one possible implementation of the third aspect described above, the first electronic device is further configured to respond to a received fourth test instruction, run a first application to execute a fourth test case, and generate a fourth operation log, wherein the fourth test instruction is used to instruct a load test on the display process of a fourth interface set, each frame interface in the fourth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fourth interface set has a corresponding added second display effect, the second display effect being different from the first display effect, and the fourth operation log includes at least third load data corresponding to the display process of the fourth interface set; and the second electronic device is configured to extract the third load data from the fourth formatted data converted from the fourth operation log according to the application tag, the interface tag, and the second identification parameter corresponding to the second display effect; and is configured to determine the third load increment corresponding to the second display effect according to the difference between the third load data and the basic load data.

[0048] Fifthly, this application provides an electronic device, including: one or more processors; one or more memories; the one or more memories storing one or more programs, which, when executed by one or more processors, cause the electronic device to perform the interface processing method provided by the first aspect and various possible implementations of the first aspect, the second aspect and various possible implementations of the second aspect, or the third aspect and various possible implementations of the third aspect.

[0049] In a sixth aspect, this application provides a computer-readable storage medium, characterized in that the storage medium stores instructions that, when executed on a computer, cause the computer to perform the interface processing method provided by the first aspect and its various possible implementations, the second aspect and its various possible implementations, or the third aspect and its various possible implementations.

[0050] In a seventh aspect, this application provides a computer program product, including a computer program / instruction that, when executed by a processor, implements the interface processing method provided by the first aspect and various possible implementations thereof, the second aspect and various possible implementations thereof, or the third aspect and various possible implementations thereof.

[0051] The beneficial effects of the second to seventh aspects mentioned above can be referred to the relevant descriptions in the first aspect and its various possible implementations, the second aspect and its various possible implementations, or the third aspect and its various possible implementations, which will not be elaborated here. Attached Figure Description

[0052] Figure 1 The diagram shown is an application scenario illustration of an interface processing method provided in an embodiment of this application.

[0053] Figure 2a The diagram shown is a schematic representation of the implementation principle of an interface processing method provided in an embodiment of this application.

[0054] Figure 2b The diagram shown is a schematic representation of the overall implementation process of an interface processing method provided in an embodiment of this application.

[0055] Figure 3 The diagram shown is a schematic representation of the implementation process of a method for handling interfaces according to an embodiment of this application, which involves load testing of various display effects or combinations of effects.

[0056] Figure 4a The diagram shown is a test interface diagram of a basic load test function provided in an embodiment of this application.

[0057] Figure 4b The diagram shown is a test interface diagram corresponding to the display effect of a visual effect type provided in an embodiment of this application.

[0058] Figure 4c The diagram shown is a test interface diagram corresponding to the display effect of another visual effect type provided in the embodiment of this application.

[0059] Figure 4d The diagram shown is a test interface diagram corresponding to the display effect of a certain type of animation provided in an embodiment of this application.

[0060] Figure 4e The diagram shown is a schematic diagram illustrating the design principle of an effect combination provided in an embodiment of this application.

[0061] Figure 5 The diagram shown is a schematic representation of the implementation process of a scenario load data decomposition method provided in an embodiment of this application.

[0062] Figure 6 The diagram shown is a schematic representation of the implementation process of a load and performance simulation method related to changes in motion effects and / or visual effects provided in an embodiment of this application.

[0063] Figure 7a The figure shown is a schematic diagram of a load simulation interface provided in an embodiment of this application.

[0064] Figure 7b The diagram shown is another load simulation interface provided in an embodiment of this application.

[0065] Figure 8a The diagram shown is a simulation result interface displaying the average load of scene frames, provided in an embodiment of this application.

[0066] Figure 8bThe diagram shown is a schematic of another simulation result interface displaying the average load of scene frames provided in an embodiment of this application.

[0067] Figure 8c The image shown is a schematic diagram of a simulation result interface displaying a single-frame interface load of a scene, provided by an embodiment of this application.

[0068] Figure 9a The image shown is a schematic diagram of a simulation result interface with added "Visual Effect 2" according to an embodiment of this application.

[0069] Figure 9b The diagram shown is a schematic of another simulation result interface with the added "Visual Effect 2" according to an embodiment of this application.

[0070] Figure 10 The diagram shown is a schematic of a load simulation interface displayed on a mobile phone according to an embodiment of this application.

[0071] Figure 11 The figure shown is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0072] Figure 12 The diagram shown is a software structure block diagram of an electronic device provided in an embodiment of this application.

[0073] Figure 13 The figure shown is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0074] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be described in detail below with reference to the accompanying drawings and specific implementation methods.

[0075] The method provided in this application can be applied to any electronic device, including but not limited to mobile stations (MS) and mobile terminals (MT). For example, the electronic device can be a mobile phone, smart TV, wearable device, tablet computer, desktop computer, laptop computer, virtual reality (VR) device, augmented reality (AR) device, terminal in industrial control, terminal in self-driving, terminal in remote medical surgery, terminal in smart grid, terminal in transportation safety, terminal in smart city, terminal in smart home, etc. This application does not limit the specific form of the electronic device.

[0076] To facilitate understanding of the solutions in the embodiments of this application by those skilled in the art, some concepts and terms involved in the embodiments of this application will be explained below.

[0077] (1) Animation-related parameters may include, but are not limited to, animation duration, animation start state, animation end state, etc. The animation start state may include the position, size and other states of the corresponding interface elements at the start of the animation; the animation end state may include the position, size and other states of the corresponding interface elements at the end of the animation.

[0078] Common animation effects, categorized by function, may include, but are not limited to:

[0079] Transition animations are used for the transition between states of interface elements, such as the animation of pop-up windows displayed when switching pages.

[0080] Loading animations are used to display loading progress or waiting status, such as the rotating icon animation displayed on a page that shows a loading bar.

[0081] Interactive animations are animations that respond to user actions, such as an icon enlarging in response to a button click.

[0082] Looping animations are animations that repeat continuously, such as the blinking animation of icons displayed on some pages with background animations.

[0083] (2) Visual effects, including motion blur, shadow, brightening, light and shadow, particles, color, shape, size, gradient, etc., represent the visual presentation effect brought about by one or more combinations of color, shape, size, shadow, gradient, etc. on the interface elements of each frame.

[0084] Dynamic blur, or simply blur, can be used to simulate the blurring effect produced when an object is moving. It includes types such as directional blur, radial blur, and rotational blur. Directional blur corresponds to the blur's direction being the same as the simulated object's direction of motion; radial blur corresponds to the blur spreading outwards from the center point; and rotational blur corresponds to the blur rotating around a point.

[0085] Shadows are dark areas created by the obstruction of light and can be used to enhance the sense of depth and three-dimensionality of an interface.

[0086] Brightening refers to increasing the brightness and contrast of an image (such as each frame of the screen) to make the image brighter and clearer.

[0087] Light and shadow refer to the changes in brightness and darkness produced by light and shadow on the surface of an object. In some embodiments, light and shadow related parameters may include shadow parameters. Similar to shadows, light and shadow can enhance the three-dimensionality, depth, and realism of an object.

[0088] Particles refer to visual effects composed of a large number of tiny elements, including smoke particles, flame particles, water particles, snowflake particles, etc., which are used to simulate the natural phenomena and dynamic changes corresponding to elements such as smoke, flame, water, and snowflakes, making the picture more vibrant and dynamic.

[0089] Both color and shape can be used to distinguish interface elements. Color can also be used to convey information, while shape can be used to create a sense of hierarchy. Size can be used to differentiate the importance of interface elements; for example, larger interface elements can be considered more important, and smaller interface elements can be considered less important. Gradients can be used to create smooth color transitions and visual focal points.

[0090] Figure 1 A schematic diagram illustrating an application scenario of an interface processing method is shown.

[0091] like Figure 1As shown, the scenario includes a first electronic device 10, a server 20, and a second electronic device 30. The first electronic device 10 can be a terminal electronic device, such as a mobile phone, tablet, or watch, that runs an application (APP, including the test application and target application described below) and displays the visual effects of some interface elements. The server 20 can provide a service (hereinafter referred to as the load analysis service) or engine with load analysis capabilities, and can also provide a database to store some load-related data to support the data storage and query needs of the terminal electronic device. The second electronic device 30 can be a terminal electronic device used to design the aforementioned visual effects of the interface elements, such as a laptop or desktop computer. This electronic device can run an integrated development environment (IDE) or UX design tools. An IDE is a software / application that provides a comprehensive set of tools to help developers write, test, and debug code.

[0092] In other embodiments, the scenario may also include terminal-type electronic devices, such as the first electronic device 10 or the second electronic device 30, without limitation.

[0093] exist Figure 1 In the scenario shown, the first electronic device 10 displays certain interface effects while running a target application. This leads to an increase in the load on the processor of the first electronic device 10, such as the CPU and GPU. Furthermore, the degree of processor load increase caused by different animations and / or visual effects during the display process may vary, resulting in different impacts on the performance of the first electronic device 10. For example, the dynamic changes in the startup interface displayed when the phone is running application A may include the application's homepage window growing larger and moving from one diagonal to the center or another diagonal of the screen. Correspondingly, the startup interface display effect when the phone is running application B, in addition to the dynamic changes corresponding to application A, may also include visual effects such as the homepage window of application B gradually becoming clearer from a blurry edge, and some graphic elements within the homepage window rotating and / or scaling. In this case, the processor load generated by the startup interface display effect of application B will be higher than the processor load generated when the phone is running application A.

[0094] Similarly, when a phone is running other applications (such as application C) and displaying its startup screen, or when it receives user instructions to switch pages or switch the focus application while running other applications, the display effect of the corresponding page switching process may increase significantly due to the fact that the relevant application was designed with display effects determined by a variety of visual effects and long animation durations during the UX design phase. This may lead to higher power consumption and degraded performance of the corresponding electronic device.

[0095] As mentioned earlier, there is a need for a solution that can accurately measure the load and power consumption impact caused by the display of related interfaces with motion effects and / or visual effects, to guide the UX design or program development and optimization processes of target applications, so as to improve the rationality and feasibility of UX design.

[0096] To address the aforementioned issues, this application provides an interface processing method. Specifically, this method, on the one hand, drives a terminal-type electronic device to run a test application through test cases to execute corresponding test cases, thereby collecting runtime logs generated during the display of multiple frames of interfaces without any added animations or visual effects. This logs are used to analyze the basic load data of the relevant interfaces without animations or visual effects. On the other hand, it collects runtime logs generated during the display of multiple frames of interfaces with individual animations or visual effects to analyze the load data generated when individual animations or visual effects are applied. Furthermore, it collects runtime logs generated during the display of multiple frames of interfaces with combinations of animations and / or visual effects (hereinafter referred to as effect combinations) to analyze the load data generated when some effect combinations are applied. The aforementioned multiple-frame interfaces can be interfaces that are continuously refreshed and displayed within the same interface refresh time period. Furthermore, based on this load data, the load increment brought about by each individual animation or visual effect can be accurately analyzed, and the combined load increment brought about by some effect combinations can also be accurately analyzed. On the other hand, this method collects log data generated by displaying multiple frames of the interface during the process of running the target application to be optimized on terminal electronic devices, and decomposes the load data corresponding to each frame of the interface. Then, by combining the load increment and combined load increment obtained from the above test, the scene load data of the display scene corresponding to each frame of the interface, the load increment corresponding to the display effect added to each interface, or the combined load increment corresponding to the combined effect can be determined.

[0097] Thus, based on the various load increments, combined load increments, and scene load data corresponding to each display scenario, the load changes brought to the relevant interface by each motion effect or visual effect, and each combination of motion effects and / or visual effects, can be precisely determined. Furthermore, it is possible to accurately analyze the load of the image processing process of each frame of the interface, which is beneficial to improving the accuracy of subsequent data analysis and also facilitates the flexible combination of various types of load data to meet more data analysis needs.

[0098] Based on the interface processing solution provided in this application, simulations can also be performed to simulate the load changes generated by the combination of motion effects and / or visual effects on the relevant interfaces in more display scenarios. This is also beneficial for guiding the UX design, program development, and optimization processes of the target application's relevant interfaces, thereby improving the rationality and feasibility of the UX design. For example, based on the simulated load changes, the type, quantity, and corresponding attribute parameters of the motion effects and / or visual effects finally added to the relevant multi-frame interfaces of the target application can be determined. This accurately measures and presents the impact of the added motion effects and / or visual effects on the load and power consumption of the electronic device, thereby controlling the balance between the display effect of the target application and the load on the terminal electronic device during runtime.

[0099] As can be understood, the aforementioned basic load refers to the load generated by drawing and rendering the interface elements (also known as basic elements) that need to be displayed on the relevant interface at the time of interface refresh. The basic load data is the data related to the basic load, which can reflect the size of the basic load. The animation load refers to the load generated by drawing and rendering the interface elements with added animations on the relevant interface, and the difference between the load generated by drawing the corresponding interface elements without added animations, which can also be called the animation load increment.

[0100] Similarly, visual load refers to the difference between the load generated by drawing and rendering interface elements with added visual effects on the relevant interface and the load generated by drawing the corresponding interface elements without added visual effects. It can also be called visual load increment.

[0101] Based on this, the relationships between the scene load and the base load, the load increment corresponding to a single display effect, and the combined load increment corresponding to a combination of effects, as reflected in the above scene load data, may include, but are not limited to:

[0102] For scenarios where a single animation or visual effect applies to the display of a related interface:

[0103] Scene load = base load + load increment corresponding to individual display effects; where, for animation effects, scene load = base load + animation load increment; for visual effects, scene load = base load + visual effect load increment.

[0104] For scenarios where motion effects and / or visual effects are used in combination for displaying related interfaces:

[0105] Scene load = base load + combined load increment, where scene load < base load + load increment of each motion effect + load increment of each visual effect.

[0106] For ease of description, any kind of motion effect and / or visual effect will be uniformly described as a display effect. For example, the first display effect can be a motion effect or a visual effect. The combination of multiple motion effects and / or visual effects will be uniformly described as an effect combination, and different effect combinations can have different forms. For example, the first effect combination may include a combination of motion effects and visual effects, and the second effect combination may include a combination of multiple motion effects or multiple visual effects, etc., without limitation. Correspondingly, the load data generated when the above-mentioned various motion effects or visual effects act individually, such as the first load data corresponding to the first display effect with the first attribute parameter, the second load data corresponding to the first display effect with the second attribute parameter, the third load data corresponding to the second display effect, etc. Based on the difference between the first load data and the base load data, the first load increment corresponding to the first display effect with the first attribute parameter can be calculated; based on the difference between the second load data and the base load data, the second load increment corresponding to the first display effect with the second attribute parameter can be calculated; based on the difference between the third load data and the base load data, the third load increment corresponding to the second display effect can be calculated, that is, the load increment brought about by various dynamic effects or visual effects under the individual action of one or a group of attribute parameters in the corresponding configuration.

[0107] Similarly, the scene load data generated when the various motion effects and / or visual effects are combined as described above can include, for example, the first scene load data corresponding to a first display scene with the first effect combination added, the second scene load data corresponding to a second display scene with the second effect combination added, and so on. The difference between the first scene load data and the base load data corresponding to multiple frames of the interface set affected by the first effect combination can be used to calculate the first combination load increment corresponding to the first effect combination; similarly, the difference between the second scene load data and the base load data corresponding to multiple frames of the interface set affected by the second effect combination can be used to calculate the second combination load increment corresponding to the second effect combination, and so on.

[0108] It is understood that the above-mentioned first effect combination may include at least two of the n display effects, where n is an integer greater than or equal to 2. The n display effects may include the above-mentioned first display effect, or the above-mentioned second display effect, etc., without limitation.

[0109] It is understood that the load increments corresponding to various display effects or combinations of effects can be stored in a pre-deployed test load database (hereinafter also referred to as the first database) in the cloud or on the server. In this embodiment, the test load database can also store basic load data, such as load data generated by multiple frames of the test application displaying without any added display effects or combinations of effects. The scene load data corresponding to various effect combinations can be stored in a pre-deployed scene load database (hereinafter also referred to as the second database) in the cloud or on the server. In this embodiment, the scene load database can also store the combined load increments brought about by each effect combination.

[0110] It is understood that the load increment brought about by the above-mentioned display effects and combinations of effects can be related to the type of each display effect. The type of each display effect can be determined based on the recognition parameters corresponding to each display effect. The load increment brought about by the above-mentioned display effects and combinations of effects can also be related to the attribute parameters of each display effect. For the same type of display effect, such as a blur effect, different attribute parameters, such as different blur radii, will result in different load increments. Furthermore, different types and attribute parameters of display effects added to the corresponding interface will result in different display effects presented on the corresponding interface, and the corresponding load increments can also be different. For example, some continuously changing interfaces of a test application or target application can present dynamic change effects of a certain duration based on animation attribute parameters such as animation duration. As another example, some continuously changing interfaces of a test application or target application can present richer dynamic change effects of a certain duration based on animation duration and some visual effect attribute parameters. In the embodiments of this application, the above-mentioned attribute parameters may include, but are not limited to, blur (an example of a visual effect) radius, blur degree, and size (e.g., pixel height and pixel width) parameters.

[0111] It is understood that the aforementioned interface sets merely represent multiple frames of interfaces that change continuously with the interface refresh time. This application describes the multiple frames of interfaces displayed within different interface refresh time periods using the concept of interface sets, and this should not be taken as a limitation on the combination of interfaces. For example, in the multiple frames of interfaces described by the first interface set, the refresh display process of each frame is relatively independent, and any display effect can be added to each frame, or any combination of display effects can be added. Furthermore, the test process for load data of different display effects or effect combinations can be implemented by adding each display effect or effect combination to the multiple frames of the same interface set. For example, based on the first interface set without any added display effects or effect combinations, a first display effect can be added to each of the multiple frames in that set, resulting in a second interface set where each interface has the first display effect. Thus, the load increment corresponding to the first display effect can be obtained from the running logs collected based on the display process test of the second interface set.

[0112] It's understandable that the test application upon which the various load increments and load data mentioned above are based could be a benchmark application. When a terminal electronic device runs a benchmark application and executes the corresponding test cases, the resulting runtime logs may include trace logs. A trace is a log file that records a series of events that occur during the execution of a system or application. During performance analysis and optimization, trace data helps developers understand the application's behavior, including function calls, execution time, and system resource usage. For example, the basic load data mentioned above can be extracted or filtered from the trace data generated by executing basic test cases in a benchmark. These basic test cases might correspond to a multi-frame interface display process without any added animations or visual effects. The load data corresponding to each display effect or combination of effects can be extracted or filtered from the trace data generated by executing the test cases corresponding to each display effect or combination of effects. Adding markers to the trace that can identify load data related to animations or visual effects can be called data tagging.

[0113] Based on this, the above extraction or filtering process can be implemented by adding tags corresponding to data points that can identify the load data related to motion or visual effects. In some embodiments, the tags can be, for example, the identification parameters of the motion or visual effects. In other embodiments, the tags can also be other identification parameters preset by developers or UX designers according to data collection needs, which are not limited here.

[0114] Similarly, scene load data can include data extracted or filtered from the trace data generated when the benchmark application runs based on attribute parameters designed according to the combination of various animations and / or visual effects. This scene load data can be combined with the basic load data of the relevant interface display process obtained from the corresponding test of the benchmark application to further determine the combined load increment corresponding to the above-mentioned combination of various animations and / or visual effects.

[0115] In other embodiments, the scene load data may also include data extracted or filtered from trace data generated during the operation of the target application to be developed or optimized. During the operation of the target application, a set of interfaces spanning one or more frame refresh periods may be displayed. Each set of interfaces may have a corresponding design display effect or a combination of effects. After the trace data is provided to the server, the server can use the start and end times of each interface refresh period to extract the load data related to the multi-frame interfaces of each set from the trace data. Based on the identification parameters corresponding to each display effect, the application tag corresponding to the target application, and the interface tags corresponding to each interface, the server can determine the load data generated during the display process of the multi-frame interfaces of each set, and can also determine the type of display effect added to each interface or the type of each display effect in the effect combination.

[0116] In some embodiments, the server can also obtain scene identifiers for the display scenarios corresponding to each interface from the extracted load data. These scene identifiers can be used to query the first or second database to see if there are matching load increments, combined load increments, and scenario load data. If a matching result is found, the server can provide the matched load increments, combined load increments, and scenario load data to terminal electronic devices, such as computers, that have the simulation client installed. If no matching result is found, the server can, on the one hand, match the relevant basic load, load increment, and / or combined load increment from the first or second database based on the determined display effect or effect combination type and identification parameters, as well as the attribute parameters corresponding to each display effect or effect combination, to estimate the corresponding scenario load size; on the other hand, the server can generate test case configuration files and define the identification parameters and attribute parameters corresponding to each determined display effect or effect combination. The test case configuration file generated above can be converted into test cases by terminal electronic devices (such as the computer mentioned above) that have deployed a test framework. It is then provided to terminal electronic devices that have the benchmark application installed to trigger the electronic devices to run the benchmark application and execute the test cases for supplementary testing. When the corresponding running logs are provided to the server, the load increment or combined load increment of the corresponding display effect or effect combination can be determined through the above test process.

[0117] It is understood that the terminal-type electronic devices that run the test application or target application to generate operation logs, as described above, can be referred to as the first electronic device in this application embodiment, including mobile phones, tablet computers, laptops (hereinafter referred to as computers), etc. The processors that perform the processes of refreshing and displaying the relevant interface, rendering, and sending animations and visual effects during the running of the test application or target application on the first electronic device, in addition to the aforementioned CPU and GPU, may also include other processors, such as digital signal processors (DSPs) and accelerated processing units (APUs), etc., without limitation. Correspondingly, the aforementioned scene load data, load increments, and combined load increments may include, but are not limited to, CPU load, GPU load, DSP load, and APU load.

[0118] It is understandable that the process of analyzing the load corresponding to the display effects or combinations of effects based on trace data can be performed by a server (referred to as the second electronic device). A load analysis service can be deployed on this server to perform the aforementioned process of analyzing the load based on trace data.

[0119] In addition, the aforementioned terminal electronic devices equipped with simulation clients, capable of simulating various display effects and the resulting load changes from additions, deletions, or modifications, can be referred to as third electronic devices, and may also include mobile phones, tablets, laptops (hereinafter referred to as computers), etc. This third electronic device can run IDEs or other software tools or applications for UX design, and a testing framework can be deployed on this second electronic device. This testing framework can be used to generate corresponding test cases based on test case configuration files provided by the server. In some embodiments, the testing framework can also convert the runtime logs generated by the first electronic device running the test application or target application into formatted data, such as JSON format data, that can be used by a load analysis service deployed on the server side, and then provide it to the server side for load analysis.

[0120] It is understood that the first electronic device and the third electronic device can be the same type of electronic device, such as a mobile phone or a tablet computer. In other embodiments, the load analysis service deployed on the second electronic device can also be deployed on either the first or second electronic device. When the load analysis service is deployed on the first electronic device, it can enable the integrated execution of processes such as log collection and load analysis based on trace data involved in the test process through the first electronic device. In other embodiments, the simulation client installed on the second electronic device can also be installed on the first electronic device, thus enabling the integrated execution of the test and simulation processes through the first electronic device, achieving a high degree of integration of testing and simulation functions. No limitations are imposed here.

[0121] The following, in conjunction with the accompanying drawings, uses mobile phone 10 as the first electronic device, server 20 as the second electronic device, and computer 30 as the third electronic device to describe in detail the specific implementation process of the interface processing method provided in this application.

[0122] As an example, Figure 2a An embodiment of this application illustrates a schematic diagram of the implementation principle of an interface processing method.

[0123] refer to Figure 2aMobile phone 10 and computer 30 can establish a communication connection via wired or wireless means. Mobile phone 10 can send the first trace data generated during the display of multiple frames of animated or visually enhanced interfaces of a benchmark application to computer 30, based on a preset script for automatically sending log data. The data conversion function provided by the test framework deployed on computer 30 can convert the first trace data into formatted data (such as JSON data) before sending it to server 20. Server 20 can deploy a load analysis service capable of performing load analysis based on the input formatted data, such as the JSON data converted from the first trace data.

[0124] Continue to refer to Figure 2a The load analysis service can analyze the load data of the relevant interface set from the formatted data converted from the first trace data. In some test scenarios, if the first trace data corresponds to the runtime logs generated when the relevant interface set of the benchmark application is running without any animations or visual effects, the load data obtained by the load analysis service in this case can be considered the basic load data. If the first trace data corresponds to the runtime logs generated when a display effect is added to the relevant interface set of the benchmark application, the load data obtained by the load analysis service in this case can be recorded as the first load data. Subtracting the basic load data analyzed when the multiple frames of the interface are not equipped with any animations or visual effects from this first load data yields the load increment when the corresponding animation or visual effect is applied alone.

[0125] It is understood that a first database can be deployed on server 20 to store the basic load data obtained from the above analysis, the load increment corresponding to each display effect, and the combined load increment corresponding to each effect combination. Furthermore, a second database can also be deployed on server 20 to store the scene load data of the display scenes corresponding to the above multiple animation and / or visual effect combinations. Additionally, in some embodiments, a preset test case configuration file, such as a benchmark configuration file, can be used to generate corresponding test cases and provide them to the benchmark application running on mobile phone 10 for loading and execution. The aforementioned test case configuration file can define the identification parameters and attribute parameters corresponding to each display effect included in the display effect or effect combination, and the defined display effect or effect combination can correspond to the display scene to be tested. (See reference...) Figure 2aFor example, the load analysis service of server 20 can generate test case configuration files based on preset parameters related to load testing requirements and send them to computer 30. The test framework of computer 30 can generate test cases for the corresponding scenario based on the received test case configuration files and then send them to mobile phone 10. At this time, mobile phone 10 can run the benchmark application and execute the received test cases for the corresponding scenario, display the interface with added display effects or combinations of effects for that scenario, and generate second trace data. After the second trace data is converted into formatted data by computer 30, it can be sent to server 20 as input data for the load analysis service, so as to extract the scenario load data of the corresponding scenario from the formatted data corresponding to the second trace data and store it in the aforementioned second database.

[0126] Mobile phone 10 can also run target applications that are yet to be developed or optimized. During the display of a multi-frame interface with animation and / or visual effects of the target application, third trace data can be generated and sent to computer 30 to be converted into formatted data required by the load analysis service. After receiving the formatted data corresponding to the third trace data, server 20 can extract trace data corresponding to the set of interfaces displayed within one or more frame refresh periods from the data. Based on the identification parameters and attribute parameters of each display effect, server 20 can analyze the scene load data corresponding to the added display effects or effect combinations for each set of interfaces. It can be understood that the basic load data included in this scene load data can be used to process the CPU load, GPU load, etc., consumed by the relevant interfaces of the target application.

[0127] If no display scene identifier corresponding to the aforementioned interface set is found in the first or second database, the load analysis service of server 20 can generate a test case configuration file corresponding to the display scene of the aforementioned interface set based on the aforementioned identification parameters and attribute parameters of the relevant interface set. This configuration file can generate corresponding test cases via computer 30, and then be provided to the benchmark application running on mobile phone 10 for loading and execution, thereby generating the second trace data used to analyze scene load data. In other embodiments, the process of generating the corresponding scene test case configuration file, generating test cases, and executing test cases to collect second trace data for testing scene load data in the target application can be called a supplementary testing process. The scene load data obtained in this process can also be stored in the aforementioned second database.

[0128] In this way, based on the precise collection of operation logs for various display effects and combinations of effects, the system can finely analyze the basic load data corresponding to the relevant interface set of the test application, the basic load data corresponding to the relevant interface set of the target application, the load increment corresponding to each display effect, the load increment corresponding to each combination of effects, the scene load data corresponding to each display scene, and the combined load increment corresponding to the effect combination of each display scene. This data is then stored in the corresponding database for fine-grained data management, thereby accurately measuring the load and power consumption impact caused by the display of related interfaces with animation and / or visual effects.

[0129] Continue to refer to the above. Figure 2a A simulation client can also be installed on computer 30. When this client runs, it presents a simulation interface (see the description below with accompanying figures), allowing developers or UX designers to add, delete, or modify animations and / or visual effects and corresponding attribute parameters on the interface. Based on this, for some undeveloped target applications, the interface processing method provided in this application can utilize the relevant load data in the aforementioned database to simulate the load during the target application's operation. It can also simulate the load changes after adding / deleting some animations or visual effects to the target application, thereby optimizing the load and performance of the target application before its development, thus guiding the UX design or program development process. This can reduce the waste of human and material resources during the target application development process.

[0130] Furthermore, based on the load analysis and simulation results related to the motion and visual effects in the target application, which show that the optimal state has been reached, the hardware requirements of the first electronic device, such as the computing power resources provided by the processor, can also be determined, so as to provide a reference for the future product design and development of the first electronic device.

[0131] According to the above Figure 2a The implementation principle of the example Figure 2b A schematic diagram illustrating the overall implementation process of an interface processing method is shown in an embodiment of this application.

[0132] like Figure 2b As shown, the overall implementation process of the interface processing method provided in this application can include three parts. Specifically:

[0133] Part 1: Load testing of each display effect or combination of effects.

[0134] The test objectives corresponding to this part of the load testing process can include "1. Load quantification of display effects" and "2. Load quantification of effect combinations". Among them, "1. Load quantification of display effects" corresponds to obtaining single visual effect test data and single motion effect test data. As the name suggests, single visual effect test data refers to the data obtained by running the corresponding test cases for any single motion effect, including the corresponding trace data (such as the first trace data mentioned above) and the load increment corresponding to each display effect (such as the first load increment mentioned above).

[0135] The aforementioned "2. Load Quantization of Effect Combinations" corresponds to obtaining test data for effect combinations. As the name suggests, this refers to the data obtained by running corresponding test cases for effect combinations formed by multiple animations and / or visual effects. This includes corresponding trace data (e.g., the second trace data mentioned above) and the analyzed load increments corresponding to the respective effect combinations (e.g., the first load increment mentioned above). The load increments corresponding to each display effect and the combined load increments corresponding to the respective effect combinations can be stored in the aforementioned first database.

[0136] Part Two: Decomposition of Scenario Load Data.

[0137] This breakdown process can include "3. Multi-interface scene load data acquisition", "4. Frame-by-frame scene load data identification", and "5. Decomposition of basic load, scene load, and corresponding effect combinations". "3. Multi-interface scene load data acquisition" corresponds to filtering scene load data from multiple screen frames. For example, it can utilize key threads (such as the render thread) that perform the drawing, rendering, and display of related screens to identify each frame, obtaining the corresponding screen labels and application labels of each screen. Then, by combining the start and end times of different screen refresh periods, the scene load data corresponding to the multiple screen frames displayed during each refresh period can be filtered from the relevant trace data. Each screen refresh period can correspond to the duration of the added animations for the corresponding screen set, and the multiple screen frames displayed during each refresh period can be described as the corresponding screen set, such as the first screen set, the second screen set, etc. mentioned above.

[0138] The above-mentioned "4. Frame-by-frame scene load data identification" refers to identifying the scene load data of each frame from the scene load data of the selected multi-frame interfaces. Each frame interface corresponds to a display scene when any effect combination is added. Therefore, the scene load data of each frame interface is recorded as the scene load of the corresponding displayable scene, including the sum of the basic load corresponding to each frame interface and the load increment corresponding to the added effect combination.

[0139] The aforementioned "5. Decomposition of Basic Load, Scene Load, and Corresponding Effect Combinations" refers to performing load analysis on the scene load data to decompose the basic load, scene load, and combined effect load increments corresponding to each frame of the interface. For cases where scene load data for a relevant display scene is not matched in the second database, supplementary tests can be performed according to the load testing process described in Part One. The basic load, scene load, and combined load increments for the relevant interfaces obtained from the supplementary tests can also be updated in the second database for future reference.

[0140] Part Three: Load and performance simulation related to the changes in effect combinations for each display scenario.

[0141] This simulation process can include "6. Data Analysis and Visualization" and "7. Load and Performance Simulation of New Effect Combinations, Identifying Risks." Specifically, "6. Data Analysis and Visualization" corresponds to presenting the simulation interface designed based on test data and scenario load data. This simulation interface can include options or controls for adding, deleting, or modifying various display effects. Adding, deleting, or modifying each display effect can change the effect combination and generate a new effect combination.

[0142] The section "7. Load and performance simulation corresponding to the new effect combination, identifying risks" corresponds to determining the load and performance simulation analysis results related to changes in the effect combination, and these results can be presented on the simulation interface. For example, if one or more display effects are added to the new effect combination, the load increment corresponding to the new effect combination can be obtained by matching from the relevant database or through the supplementary testing process described above. This load increment can be presented in relevant graphics or tables on the simulation interface. The specific presentation method will be introduced below with reference to relevant interface diagrams, and will not be elaborated here. It can be understood that the load increment corresponding to the new effect combination will lead to an increase in the scene load data of the display scene corresponding to the new effect combination, which may have a significant impact on the processing performance of the first electronic device running the target application. When there is a risk affecting the processing performance of the first electronic device, the relevant simulation interface can also display reminders or development / design suggestions based on the performance simulation analysis results. These design suggestions can, for example, remind UX designers or developers of the target application that the load is too high and optimization is needed. The reminder method can be, for example, by displaying "The current combination load is high, which may lead to performance degradation of the product running this application," etc.

[0143] The following sections will describe the specific implementation process of each of the above parts, using the corresponding flowcharts.

[0144] Figure 3This application provides an embodiment illustrating a schematic diagram of the implementation process for load testing of various display effects or combinations of effects in an interface processing method. It can be understood that the implementation process for load testing of various display effects or combinations of effects is the specific implementation process involved in the load testing described in the first part above.

[0145] like Figure 3 As shown, the implementation process may specifically include:

[0146] S301: The phone runs a test application and displays the test interface.

[0147] For example, a test application, such as the aforementioned benchmark application, can be installed on the mobile phone 10 to test the load impact of animation and / or visual effects on the corresponding interface. When the mobile phone 10 runs the test application, it displays the user interface (UI) provided by the application, referred to as the test interface. This test interface can display a selection of the type of display effect to be tested, such as visual effects or animation effects; it can also display different attribute parameter configurations for various display effects and corresponding test controls for user operation. The various display effects and their different attribute parameter configurations can be configured by pre-setting or pre-loading corresponding benchmark test cases in the storage space corresponding to the benchmark application. Thus, the mobile phone 10 can respond to the user's click on the corresponding test control, execute the corresponding test cases, and generate corresponding runtime logs for testing the relevant load. It is understood that the user operating on the test interface, in this embodiment, may include the developer of the target application or a UX designer, etc., and is not limited thereto.

[0148] For ease of distinction, the above-mentioned test application can be described as the first application and the target application described below can be described as the second application in this application. In other embodiments, the first application and the second application are not limited to the application examples in the embodiments of this application, and are not limited here.

[0149] As an example, Figures 4a to 4d Some schematic diagrams of test interfaces are shown according to embodiments of this application.

[0150] Figure 4a An embodiment of this application illustrates a test interface diagram that provides basic load testing functionality.

[0151] like Figure 4aAs shown, the test interface 410 may include "Visual Effects" and "Animation Effects" options corresponding to the display effect types, where the "Visual Effects" option can be the type of the currently selected display effect. The display effect control area 411 of the test interface 410 can display various display effects of the "Visual Effects" type and options corresponding to various effect combinations containing the "Visual Effects" type display effects, including but not limited to "General", "Shadow", "Enhanced Background Blur", "Basic Background Blur", "Blur Merge", "Invert Color", "Dynamic Brightening", "Content Blur", "Foreground Material Blur", "Gradient Blur", "Effect Combination I", "Effect Combination II", "Text Shadow", "Grayscale", "Edge Pixel Expansion", etc. The "General" option can correspond to providing basic load testing functions. Corresponding to the selection of the "General" option, the attribute parameter control area 412 of the test interface 410 can display different attribute parameter configurations related to the basic load. For example, "normal" indicates the currently selected "Normal" option, "interface: normal-x0" indicates the interface label of each frame displayed during the test, "width: 180px" indicates the pixel width of each frame interface, "height: 180px" indicates the pixel height of each frame interface, and "sum:1", "sum:2", "sum:5", "sum:10", etc., indicate the number of interfaces. It can be understood that when other attribute parameters are the same, the size of the base load can be related to the number of interfaces.

[0152] Figure 4b According to an embodiment of this application, a schematic diagram of a test interface corresponding to the display effect of a visual effect type is shown.

[0153] like Figure 4bAs shown, the test interface 420 can display the display effect of a visual effect type currently selected for testing, such as "Enhanced Background Blur". Corresponding to this display effect, the attribute parameter control area 421 can display different attribute parameter configurations related to "Enhanced Background Blur", such as "backgroundEffect" indicating the "Enhanced Background Blur" option, the corresponding interface label "interface:backgroundeffect-x0", hash value "Hashcode: 82951666154564897561548574561546857", blur radius "radius:40", mask color "maskColor: 33FFFFFF", color mode "colorMode:0", interface pixel width "width: 1200px", interface pixel height "height: 2600px", brightness "brightness: 1", and the corresponding test control "test x0". Different interfaces may have different attribute parameter configurations for the "Enhanced Background Blur" display effect, which will not be elaborated here.

[0154] Figure 4c According to an embodiment of this application, a schematic diagram of a test interface corresponding to the display effect of another type of visual effect is shown.

[0155] like Figure 4c As shown, the test interface 430 can display the display effect of a visual effect type currently selected for testing, such as "shadow". Corresponding to this display effect, the attribute parameter control area 431 can display different attribute parameter configurations related to "shadow", such as the "Shadow" option, the corresponding interface label "interface: shadow-x0", the hash value "Hashcode: 82951666154564897561548574561546857", the shadow radius "radius: 20", the X-direction offset value "shadowOffsetX: 10.0", the Y-direction offset value "shadowOffsetY: 10.0", the interface pixel width "width: 100px", the interface pixel height "height: 200px", the test base parameter "benchmarkBase: width", and the corresponding test control "test width: 100px". (Continue to refer to...) Figure 4b The test interface 430 can also display another attribute parameter configuration corresponding to the test control "test width: 500px". The attribute parameter of the control that triggers the "shadow" display effect of the test can be configured with different interface pixel widths, such as "width: 500px".

[0156] In other embodiments, other attribute parameters can be configured for testing the aforementioned display effects such as "enhanced background blur" or "shadow," and the corresponding test interface can also be the same as described above. Figure 4b or Figure 4c The interfaces shown may differ, but no restrictions are imposed here.

[0157] Figure 4d According to an embodiment of this application, a schematic diagram of a test interface corresponding to the display effect of a certain type of animation is shown.

[0158] like Figure 4d As shown, the test interface 440 can display attribute parameters corresponding to the animation configuration, such as "Animation type: Attribute animation", "Rotation angle: 80°", "Opacity: 0.5", "X-axis displacement: 45mm", "Curve type: Elastic curve", "Animation duration: 250ms" and the test control "Start Test". In some other embodiments, other attribute parameters can be configured for the above-mentioned animation, such as configuring different animation durations, and the corresponding test interface can also be the same as described above. Figure 4d The interfaces shown may differ, but no restrictions are imposed here.

[0159] S302: Mobile phone 10 detects the first operation of the test control corresponding to the basic load on the test interface.

[0160] As an example, Figure 4a The test interface 410 shown can display test controls corresponding to different numbers of interface sets, such as the test controls corresponding to "Test sum: 1", "Test sum: 2", "Test sum: 5", and "Test sum: 10". The first operation of the test controls corresponding to the basic load on the test interface can include user clicks. Figure 4a The operation of any control among the test controls shown can trigger the test application to continue executing S303 below, loading and executing the corresponding number of test cases for the interface to perform basic load testing.

[0161] It is understood that the above first operation can generate a first test instruction. When the mobile phone 10 receives the first test instruction, it can respond to the first test instruction by running the test application and executing the corresponding test cases, such as the first test case corresponding to the basic load as described below.

[0162] S303: The test application running on the phone 10 loads and executes the first test case corresponding to the basic load.

[0163] For example, the test application running on the mobile phone 10 can respond to the first test instruction generated corresponding to the first operation described above, load and execute a corresponding number of test cases corresponding to the interface (i.e., test cases corresponding to the basic load) to perform basic load testing. The test cases corresponding to the basic load described above can be referred to as the first test case, for example.

[0164] In this embodiment, the benchmark application can execute benchmark test cases designed for basic load, various display effects, and various effect combinations, generating corresponding runtime logs. The load data carried in these runtime logs can be related to the drawing, rendering, and display processing of the corresponding interface. The load data corresponding to the drawing, rendering, and display processing of interfaces without any animation or visual effects can be considered the basic load data of the corresponding interface. The load data corresponding to the drawing, rendering, and display processing of interfaces with one animation or visual effect as a display effect can be considered the load data of the corresponding display effect. The load data corresponding to the drawing, rendering, and display processing of interfaces with multiple display effects forming an effect combination can be considered the load data of the corresponding effect combination. Thus, the load data analyzed from the runtime logs generated according to preset or pre-loaded test cases can have high accuracy. Furthermore, each test case can be configured with different display effects and different attribute parameters according to test requirements, adapting to more load analysis and simulation scenarios. It can also support testing of more granular load data, i.e., supporting testing of load data and load increments corresponding to more display effects or effect combinations.

[0165] S304: Mobile phone 10 generates a runtime log corresponding to the basic load.

[0166] For example, the runtime log corresponding to the basic load can be recorded as a first runtime log, such as the trace data mentioned above, and this first runtime log can correspond to the first test case mentioned above. It is understood that the first runtime log can at least include the basic load data generated corresponding to the display process of the relevant interface. The relevant interface can be, for example, a first interface set formed by multiple frames of interfaces that change continuously with the interface refresh time. In the embodiments of this application, each interface in the first interface set can be, for example, the aforementioned... Figure 4a The example interface label is "interface: normal-x0".

[0167] S305: Mobile phone 10 sends the running log corresponding to the basic load to computer 30.

[0168] For example, mobile phone 10 can send the first runtime log collected during the execution of the first test case to computer 30 via a wired or wireless communication connection. This sending process can be triggered either by the relevant instructions executed after the test application on mobile phone 10 executes the first test case, or by a request for obtaining the corresponding runtime log sent to mobile phone 10 by the test framework on computer 30 according to test requirements; no limitation is imposed here.

[0169] S306: Computer 30 converts the running log into the corresponding formatted data.

[0170] For example, a testing framework supporting load testing and simulation functions can be deployed on computer 30. This testing framework can convert received runtime logs into formatted data, such as JSON data, that can be recognized by the load analysis service deployed on server 20. For instance, computer 30 can convert the aforementioned first runtime log into corresponding first formatted data.

[0171] S307: Computer 30 sends formatted data to server 20.

[0172] For example, computer 30 can send the first formatted data obtained by converting the first runtime log to server 20.

[0173] S308: Server 20 extracts basic load data from the received formatted data and saves it based on the application tag corresponding to the test application and the interface tag corresponding to each interface being tested.

[0174] For example, the load analysis service deployed on server 20 can extract the application tags corresponding to the test application and the interface tags corresponding to each interface under test from the received first formatted data, and then, based on the application tags and interface tags, extract the load data corresponding to the drawing, rendering and display processing of the relevant interfaces from the first formatted data.

[0175] It is understood that the aforementioned first database can be pre-deployed on server 20 to store the basic load data obtained from the tests corresponding to the basic test cases executed by the aforementioned test application. For example, server 20 can add identification parameters to this basic load data, such as the aforementioned interface labels or basic load identification parameters corresponding to the interface labels, and then store the labeled basic load data in the aforementioned first database.

[0176] The aforementioned first database can also be used to store the load increments obtained from the test cases corresponding to each display effect and each combination of effects, without limitation. As mentioned earlier, these load increments may include the load increments corresponding to each display effect and each combination of effects.

[0177] S309: Mobile phone 10 detected a second operation performed on the test control corresponding to the display effect on the test interface.

[0178] For example, taking the first display effect as "background blur enhancement" as an example, refer to the above. Figure 4b The test interface 420 can display the test control "Test x0" for the currently selected visual effect type, "Background Blur Enhancement". The second operation on the test control corresponding to the display effect on the test interface can be, for example, a user clicking the test control "Test x0". This operation can trigger the test application to continue executing S310 below, loading and executing the test cases corresponding to the display effect under the corresponding attribute parameter configuration, to perform load testing on the display effect under the corresponding attribute parameter configuration. As an example, the corresponding attribute parameter configuration for "Background Blur Enhancement" can be referred to above. Figure 4b The configuration and description of each attribute parameter shown are not elaborated here.

[0179] Taking the second display effect as a "shadow" effect as an example, refer to the above. Figure 4c The above-mentioned function corresponds to the second operation of the test control on the test interface, which is the display effect. For example, it can also be the user clicking the test control "test width: 100px" or the test control "test width: 500px", and there is no restriction here.

[0180] It is understood that the aforementioned second operation may, for example, correspond to generating a second test instruction, a third test instruction, or a fourth test instruction to test the second display effect. Correspondingly, when the mobile phone 10 receives the corresponding test instruction, it can run the test application and execute the corresponding test cases in response to the corresponding test instruction. For example, the mobile phone 10 may respond to the second test instruction to execute a second test case corresponding to the first display effect (with the first attribute parameter); the mobile phone 10 may respond to the third test instruction to execute a third test case corresponding to the first display effect (with the first attribute parameter); and, for example, the mobile phone 10 may respond to the fourth test instruction to execute a fourth test case corresponding to the second display effect, without limitation.

[0181] S310: The test application running on the phone loads and executes test cases corresponding to the display effects.

[0182] For example, the test application running on the mobile phone 10 can respond to the response test command generated by the second operation described above, load and execute the test cases corresponding to the display effect under the corresponding attribute parameter configuration. It is understood that for a given display effect, different configured attribute parameters will result in different test cases. For example, for a first display effect configured with the first attribute parameter, the mobile phone 10 can preset or preload a second test case; for a first display effect configured with the second attribute parameter, the mobile phone 10 can preset or preload a third test case, which are different test cases. The first display effect can be, for example, the one described above. Figure 4b The "background blur enhancement" shown may, in other embodiments, be a display effect of other visual or motion effects. Correspondingly, the first attribute parameter may include, for example, the aforementioned... Figure 4b The various attribute parameters above the test control "Test x0" shown above, this second attribute parameter can be related to the above. Figure 4b There are no restrictions on whether the various attribute parameters shown have different attribute items or different attribute values ​​for the same attribute.

[0183] It is understandable that different types of display effects require different test cases. For example, for the second display effect (different from the first display effect mentioned above), a fourth test case can be preset or pre-loaded on the phone 10. This fourth test case is different from both the second and third test cases mentioned above. This second display effect could be, for example, the one described above. Figure 4c The "shadow" example described may, in other embodiments, be a display effect of other visual or motion effects. The attribute parameters configured for this second display effect may include, for example, those described above. Figure 4c The attribute parameters above the test control "test width: 100px" or the attribute parameters above the test control "test width: 500px" are not restricted here.

[0184] S311: Mobile phone 10 generates a running log corresponding to the display effect.

[0185] For example, during the execution of corresponding test cases by the test application running on mobile phone 10, runtime logs corresponding to the corresponding display effects can be collected. These runtime logs corresponding to the display effects may include, for example, a second runtime log collected during the execution of the second test case, a third runtime log collected during the execution of the third test case, or a fourth runtime log collected during the execution of the fourth test case, etc. The second runtime log corresponds to the first display effect configured with the first attribute parameter; the third runtime log corresponds to the first display effect configured with the second attribute parameter. The second or third runtime log may at least include load data generated corresponding to the display process of the relevant interface with the first display effect. In this embodiment, the set of interfaces formed by the relevant interfaces with the first display effect configured with the first attribute parameter can be denoted as the second interface set, corresponding to the second runtime log. The set of interfaces formed by the relevant interfaces with the first display effect configured with the second attribute parameter can be denoted as the third interface set, corresponding to the third runtime log.

[0186] Similarly, the fourth operation log corresponds to the second display effect described above. This fourth operation log may at least include load data generated during the display process of the relevant interfaces having the second display effect. In this embodiment, the set of interfaces formed by relevant interfaces having the first display effect configured with the second attribute parameter can be denoted as the fourth interface set, corresponding to the fourth operation log described above.

[0187] It is understood that each frame in the aforementioned second, third, or fourth interface set can correspond one-to-one with each frame in the first interface set displayed corresponding to the aforementioned test baseline load. The difference between the two interfaces may lie in whether the aforementioned first or second display effect has been added. The difference between the interfaces corresponding to the second and third interface sets may lie in the different attribute parameters configured for the added first display effect.

[0188] S312: Mobile phone 10 sends a running log corresponding to the display effect to computer 30.

[0189] For example, mobile phone 10 can send the second runtime log collected during the execution of the second test case to computer 30. Alternatively, mobile phone 10 can send the third runtime log collected during the execution of the third test case to computer 30. Or, mobile phone 10 can send the fourth runtime log collected during the execution of the fourth test case to computer 30.

[0190] For details on how to trigger the transmission, please refer to the relevant description in S305 above, which will not be repeated here.

[0191] S313: Computer 30 converts the running log into the corresponding formatted data.

[0192] For example, the testing framework deployed on computer 30 can convert the received runtime logs into corresponding formatted data. For instance, computer 30 can convert the aforementioned second runtime log into corresponding second formatted data. As another example, computer 30 can convert the aforementioned third runtime log into corresponding third formatted data. And as yet another example, computer 30 can convert the aforementioned fourth runtime log into corresponding fourth formatted data.

[0193] S314: Computer 30 sends formatted data to server 20.

[0194] For example, computer 30 can send the corresponding formatted data obtained by converting the received running log to server 20, such as the second formatted data, third formatted data, or fourth formatted data.

[0195] S315: Server 20 extracts load data corresponding to the display effect from the received formatted data based on the recognition parameters corresponding to the application tag, interface tag, and display effect.

[0196] For example, the load analysis service deployed on server 20 can perform load analysis on received formatted data and extract corresponding load data from the formatted data. For instance, server 20 can extract the first load data corresponding to the first display effect from the second formatted data of the second runtime log corresponding to the first attribute parameter of the first display effect, based on the application tag of the test application, the interface tag of the relevant interface, and the first identification parameter corresponding to the first display effect. Similarly, server 20 can also extract the second load data corresponding to the first display effect from the third formatted data of the third runtime log corresponding to the second attribute parameter of the first display effect. As another example, server 20 can extract the third load data corresponding to the second display effect from the fourth formatted data of the fourth runtime log corresponding to the second display effect, based on the application tag of the test application, the interface tag of the relevant interface, and the second identification parameter corresponding to the second display effect. These are not exhaustive examples.

[0197] S316: Server 20 determines and saves the load increment based on the difference between the load data corresponding to the display effect and the basic load data.

[0198] For example, the load analysis service deployed on server 20 can analyze and determine the first load increment corresponding to the first attribute parameter of the first display effect based on the difference between the first load data and the basic load data measured in S308. Then, server 20 can add the first identification parameter corresponding to the first display effect to the first load increment before storing it in the first database.

[0199] Similarly, for the first display effect configured with the second attribute parameter, the server 20 can analyze and determine the second load increment corresponding to the second attribute parameter of the first display effect based on the difference between the second load data and the basic load data. This second load increment can also be stored in the first database after adding the first identification parameter. It is understood that, corresponding to different attribute parameters, the server 20 can also add identification tags corresponding to the first and second attribute parameters to the first and second load increments respectively, in order to distinguish them in the first database.

[0200] For the aforementioned second display effect, server 20 can analyze and determine the third load increment corresponding to the second display effect based on the difference between the third load data and the basic load data. This second load increment can also be stored in the first database after adding the second identification parameter corresponding to the second display effect.

[0201] It can be understood that the load testing process implemented in S301 to S316 above can correspond to the above... Figure 2b The first part shown, “1. Load quantization of display effects”, refers to the process of quantifying the load increment corresponding to various display effects.

[0202] S317: Mobile phone 10 detected a third operation on the test interface corresponding to the effect combination test control.

[0203] For example, refer to the above Figure 4a As shown, the above action corresponds to the third operation of the effect combination test control on the test interface. For example, it could be the user selecting the option corresponding to "Effect Combination I" in the display effect control area 411 and clicking the corresponding test control in the corresponding displayed attribute parameter control area (not shown in the figure). This operation can trigger the test application to continue executing the following S318 to load and execute the test cases corresponding to the corresponding effect combination, so as to perform load testing on the corresponding combination effect. "Effect Combination I" can be used as an example of a first combination effect. In other embodiments, the first combination effect can also be... Figure 4a The "Effect Combination II" shown is not limited here.

[0204] The aforementioned third operation could, for example, correspond to generating a fifth test instruction that indicates the testing of the first effect combination. The mobile phone 10 could then respond to the fifth test instruction by executing a fifth test case corresponding to the first effect combination.

[0205] It is understood that the above-mentioned effect combinations may include combinations of motion effects and visual effects, or combinations of multiple motion effects or multiple visual effects, without limitation. For example, the first effect combination may be a combination of the above-mentioned first display effect and motion effect, or a combination of the above-mentioned first display effect and second display effect, etc., without limitation.

[0206] As an example, the design of the above effect combination can be referenced. Figure 4e For example, "Effect Combination I" or "Effect Combination II" can be formed by combining two visual effect types: "background blur enhancement" and "shadow". "Background blur enhancement" can include "y-axis blur". In other embodiments, "Effect Combination I" or "Effect Combination II" can also be other forms of display effect combinations.

[0207] S318: The test application running on the phone 10 loads and executes test cases corresponding to the effect combination.

[0208] For example, the test application running on the mobile phone 10 can respond to the fifth test instruction generated corresponding to the third operation described above, and load and execute test cases for the corresponding effect combination. As an example, the test cases preset or preloaded on the mobile phone 10 corresponding to the first effect combination described above can be referred to as the fifth test case.

[0209] S319: Mobile phone 10 generates a running log corresponding to the effect combination.

[0210] For example, during the execution of corresponding test cases by the test application running on mobile phone 10, runtime logs corresponding to the corresponding effect combinations can be collected. For instance, corresponding to the execution result of the fifth test case mentioned above, mobile phone 10 can collect a fifth runtime log corresponding to the first effect combination. This fifth runtime log can at least include load data generated corresponding to the display process of the relevant interface with the first effect combination. In this embodiment of the application, the set of interfaces formed by configuring the relevant interfaces of the first effect combination can be denoted as the fifth interface set. Each frame of the fifth interface set can correspond one-to-one with each frame of the first interface set displayed corresponding to the basic test load.

[0211] S320: Mobile phone 10 sends the running log corresponding to the effect combination to computer 30.

[0212] For example, mobile phone 10 can send the fifth runtime log collected during the execution of the fifth test case to computer 30.

[0213] S321: Computer 30 converts the running log into the corresponding formatted data.

[0214] For example, the test framework deployed on computer 30 can convert the received fifth runtime log into corresponding fifth formatted data.

[0215] S322: Computer 30 sends formatted data to server 20.

[0216] For example, computer 30 can send the corresponding formatted data obtained by converting the received running log to server 20, such as the fifth formatted data mentioned above.

[0217] S323: Server 20 extracts load data corresponding to the effect combination from the received formatted data based on application tags, interface tags, and combination identification parameters.

[0218] For example, the load analysis service deployed on server 20 can perform load analysis on received formatted data and extract corresponding load data from the formatted data. For instance, server 20 can extract the fourth load data corresponding to the first effect combination from the fifth formatted data of the fifth running log corresponding to the first effect combination based on the application tag of the test application, the interface tag of the relevant interface, and the first combination identification parameter corresponding to the first effect combination.

[0219] It is understood that the load data extracted above corresponding to the effect combination, such as the fourth load data mentioned above, can be stored in the second database of server 20 as the first scene load data corresponding to the first effect combination. A first scene identifier or a first combination identification identifier corresponding to the first effect combination can be added to the first scene load data, wherein the first scene identifier can indicate the relevant interface display scene with the first effect combination mentioned above, and is denoted as the first display scene.

[0220] S324: Server 20 determines and saves the combined load increment based on the difference between the load data corresponding to the combined effect and the basic load data.

[0221] For example, the load analysis service deployed on server 20 can analyze and determine the first combination load increment corresponding to the first effect combination based on the difference between the fourth load data and the basic load data measured in S308. Then, server 20 can add the first combination identification parameter corresponding to the first effect combination to the first combination load increment before storing it in the first database.

[0222] It is understandable that, based on the interaction process from S317 to S324 above, server 20 can also analyze the combined load increment corresponding to more effect combinations, including but not limited to the first effect combination mentioned above, and may also include the second effect combination, etc., without limitation.

[0223] It can be understood that the load testing processes implemented in S301 to S308 and S317 to S324 above can correspond to the above... Figure 2b The first part shown, "2. Load quantification of effect combinations", refers to the process of quantifying the load increment corresponding to various effect combinations.

[0224] The following section will provide a detailed explanation of the specific implementation process involved in the scenario load data decomposition in Part Two, in conjunction with the flowchart.

[0225] Figure 5 This application provides an embodiment illustrating a schematic diagram of the implementation process of a scene load data decomposition method within an interface processing approach. It can be understood that the implementation process of this scene load data decomposition method is the specific implementation process involved in the second part of the above-mentioned scene load data decomposition.

[0226] like Figure 5 As shown, the implementation process may specifically include:

[0227] S501: Mobile phone 10 is running a target application that is yet to be developed or optimized.

[0228] For example, the target application to be developed or optimized, i.e., the second application, may include system applications running on the operating system of the mobile phone 10, such as the desktop, control center, and drop-down menu bar, and may also include third-party applications, such as browsers, instant messaging applications, and video applications, without limitation. It is understood that during startup, operation, and termination of the target application, multiple interfaces with dynamic display effects may be displayed within a continuous interface refresh period, i.e., interfaces presenting specific effects based on animation and / or visual effects. In this embodiment, the display process of interfaces presenting specific effects can be described as a display scene. In this display scene, the drawing, rendering, and display processing of each interface can consume the computing resources of the mobile phone 10, generating a large load. Therefore, it is necessary to design and optimize the display effects or effect combinations added to each frame of the interface in this type of display scene to achieve a balance between UX design effect and load.

[0229] As an example, a display scenario may include the target application's startup page display scenario, page switching scenario, and exit page display scenario when exiting runtime. For instance, when the target application is a desktop, the aforementioned page switching scenario may include the display scenario triggered by the user's instruction to switch to the desktop or return to the desktop with one click, etc., without limitation.

[0230] In other embodiments, a display scenario may also include an interface display scenario for user authentication by collecting facial information or fingerprint information, etc. This interface may display different colored flashing effects to remind the user to follow the prompts, etc., and so on. The flashing effect in the above display scenario may be a combination of motion effects and visual effects.

[0231] S502: Mobile phone 10 generates runtime logs for the target application.

[0232] For example, during the operation of the target application, the mobile phone 10 can generate corresponding operation logs. These logs may include processing records of threads or processes related to interface drawing and rendering, as well as interface labels for each displayed frame, the application label of the target application, and so on. The processing records of the aforementioned threads or processes may include timestamps of the display times of each frame within continuously changing interface refresh periods, and also the start and end times of interface refresh periods corresponding to animation durations. Therefore, based on the aforementioned start and end times, scene logs corresponding to the display of multiple frames within time periods corresponding to animation durations can be extracted.

[0233] For ease of description, the running log generated by the aforementioned mobile phone 10 can be referred to as the sixth running log. The scene logs extracted above can include p logs. These p scene logs can record the scene load data generated by the display scene corresponding to each interface with added animation and / or visual effects within the corresponding animation duration or the corresponding interface refresh time period. Here, p can be an integer greater than or equal to 1.

[0234] S503: Mobile phone 10 sends the running log corresponding to the target application to computer 30.

[0235] For example, mobile phone 10 can send the target application's runtime logs generated during the process of running the target application, i.e., the sixth runtime log, to computer 30. As mentioned above, the sixth runtime log may include p scene logs.

[0236] For details on how to trigger the transmission, please refer to the relevant description in S305 above, which will not be repeated here.

[0237] S504: Computer 30 converts the running log into the corresponding formatted data.

[0238] For example, the test framework deployed on computer 30 can receive runtime logs and convert them into corresponding formatted data. For instance, computer 30 can convert the aforementioned sixth runtime log into corresponding sixth formatted data.

[0239] The sixth running log mentioned above includes p scene logs. The converted sixth formatted data can be used to extract the formatted data corresponding to each of the p scene logs for load analysis on server 20.

[0240] S505: Computer 30 sends formatted data to server 20.

[0241] For example, computer 30 can send the corresponding formatted data obtained by converting the received running log to server 20, such as the sixth formatted data mentioned above.

[0242] It can be understood that the process of the mobile phone 10 sending the generated sixth running log to the computer 30, the computer 30 converting the received sixth running log into sixth formatted data and then sending it to the server 20 is the execution process of the sixth running log generated by the mobile phone 10 being provided to the server 20.

[0243] S506: Server 20, based on the start and end times of one or more interface refresh time periods, filters out the load data corresponding to the multiple frames of the interface displayed during each refresh time period from the received formatted data.

[0244] For example, the load analysis service deployed on server 20 can perform load analysis on the received formatted data and extract the corresponding load data from the formatted data. For the aforementioned sixth formatted data, server 20 can first decompose the formatted data corresponding to p scene logs based on the start and end times of each interface refresh time period. Then, server 20 can filter the load data of the relevant interfaces from the formatted data corresponding to each scene log. The multi-frame interfaces displayed during each interface refresh time period can be described as an interface set. Therefore, the formatted data corresponding to p scene logs can be used to filter the load data corresponding to the display process of the p-frame interface set.

[0245] It can be understood that the content implemented in S501 to S506 above can correspond to the above. Figure 2b The second part shown, "3. Multi-interface scene load data acquisition", refers to the process of acquiring scene load data corresponding to multiple frames of interfaces.

[0246] S507: Server 20 determines the combination of effects to be added to each frame of the multi-frame interface during the refresh time period and extracts the load data corresponding to each frame of the interface.

[0247] For example, server 20 can extract relevant processing records for each frame within the refresh time period based on the interface tags of each frame. These records include scene load data for the display scene corresponding to each frame. That is, load analysis is performed on each frame in the aforementioned set of p frames. By combining the identification parameters corresponding to each display effect, the display effects or effect combinations added to each interface are determined. Based on the determined effect combinations and the interface tags of the relevant interfaces, the scene identifier of the display scene corresponding to each frame can also be determined.

[0248] S508: Server 20 searches for corresponding matching scene load data in the second database based on the recognition parameters corresponding to the determined display effect or effect combination.

[0249] For example, after determining the display effects or effect combinations added to each interface, server 20 can check whether relevant scene load data has been stored in the second database based on the identification parameters corresponding to the corresponding display effects or effect combinations. If not stored, server 20 can continue to execute S509 below to store the currently extracted scene load data, and can execute S510 to S520 below to perform supplementary testing on the display scene corresponding to the corresponding display effect or effect combination and the load increment of the corresponding effect combination. Conversely, if stored, server 20 can stop executing S510 to S520 below. It can be understood that the scene load data stored in the second database of server 20 may include the load data consumed when a single animation or visual effect (i.e., display effect) is displayed on the relevant interface, or it may include the load data consumed when an animation and / or visual effect combination (i.e., effect combination) is displayed on the relevant interface.

[0250] It can be understood that the content implemented in S507 to S508 above can correspond to the above. Figure 2b The second part shown, “4. Frame-by-frame identification of scene load data”, refers to the process of identifying the scene load data of each frame interface.

[0251] S509: If no matching scene load data is found, server 20 will store the scene load data corresponding to the determined effect combination in the second database.

[0252] For example, if the server 20 does not find scene load data corresponding to the determined display effect or effect combination, it can store the load data corresponding to the display effect or effect combination as scene load data of the corresponding display scene in the database, and the server 20 can add a corresponding scene identifier to the load data stored in the second database.

[0253] For ease of description, the display scene corresponding to the aforementioned determined display effect or combination of effects can be described as the second display scene, and the corresponding effect combination can be described as the second effect combination. The scene identifier used to indicate the second display scene is called the second scene identifier, and the corresponding scene load data is called the second scene load data. That is, when the server 20 does not find scene load data corresponding to the aforementioned second effect combination, it can add the second scene identifier to the aforementioned second scene load data and store it in the aforementioned second database.

[0254] S510: If no scene load data is matched, the server 20 generates a test case configuration file corresponding to the effect combination based on the identification parameters and attribute parameters of each display effect included in the determined effect combination.

[0255] For example, if the server 20 does not find scene load data corresponding to the aforementioned determined display effect or effect combination, it can generate a corresponding test case configuration file based on the identification parameters and attribute parameters of each display effect included in the corresponding effect combination. In the aforementioned example, this configuration file can correspond to the second display scene determined by the aforementioned display effect or effect combination, and the configuration file can define the identification parameters and attribute parameters of each display effect. Based on this, after the configuration file is sent to the computer 30, it can generate scene load data for testing the aforementioned second display scene, as well as the second combination load increment of the second effect combination corresponding to the second display scene.

[0256] It is understandable that the test case configuration file mentioned above may also include defined combination identification parameters.

[0257] S511: Server 20 sends test case configuration files to computer 30.

[0258] For example, server 20 can send the test case configuration file corresponding to the second display scenario to computer 30.

[0259] S512: Computer 30 generates corresponding test cases based on the test case configuration file.

[0260] For example, the test framework deployed on computer 30 can generate corresponding test cases based on the received test case configuration file, which can be referred to as the sixth test case.

[0261] S513: Computer 30 sends the corresponding test cases to mobile phone 10.

[0262] For example, computer 30 can send the sixth test case generated according to the test case configuration file to mobile phone 10. This sixth test case can trigger mobile phone 10 to run the test application and load and execute the sixth test case to supplement the testing of the scene load data corresponding to the second display scenario and the combined load increment of the corresponding effect combination. The instruction that triggers mobile phone 10 to run the test application corresponding to the sixth test case can be referred to as the seventh test instruction.

[0263] For details on the supplementary testing process, please refer to the descriptions of each step below; they will not be repeated here.

[0264] S514: The mobile phone 10 runs the test application to load and execute the received test cases for supplementary testing.

[0265] For example, after receiving the sixth test case, the mobile phone 10 can run the test application to load and execute the test case. It can be understood that when the sixth test case is loaded and executed, the corresponding set of interfaces can be the sixth set of interfaces, and the multiple frames of interfaces in the sixth set of interfaces can correspond one-to-one with the multiple frames of interfaces in the first set of interfaces displayed for the execution of the basic test case.

[0266] S515: Mobile Phone 10 generates supplementary test logs.

[0267] For example, the running log generated by the mobile phone 10 during the execution of the sixth test case and the display of the relevant interface set can be used to analyze the scene load data and the combined load increment of the corresponding effect combination corresponding to the second display scenario of the above supplementary test. Therefore, it can be described as the running log of the supplementary test, and can be described as the seventh running log below.

[0268] S516: Mobile phone 10 sends the operation log of supplementary test to computer 30.

[0269] For example, mobile phone 10 can send the runtime log of the supplementary test generated above to computer 30.

[0270] S517: Computer 30 converts the running log into the corresponding formatted data.

[0271] S518: Computer 30 sends formatted data to server 20.

[0272] For example, computer 30 converts the received seventh operation log into seventh formatted data and sends it to server 20 for load analysis.

[0273] S519: Server 20 extracts load data corresponding to the effect combination of supplementary testing from formatted data based on the application tag, interface tag and combination identification parameters of the test application.

[0274] For example, the load analysis service deployed on server 20 can perform load analysis on the received formatted data and extract the corresponding load data from the formatted data. For instance, server 20 can extract the fifth load data corresponding to the second effect combination from the aforementioned seventh formatted data based on the application tag of the test application, the interface tag of the relevant interface in the interface set corresponding to the sixth test case, and the second combination identification parameter corresponding to the second effect combination. This fifth load data can be stored in the second database of server 20 as the second scene load data corresponding to the second display scene for querying.

[0275] S520: Server 20 determines and saves the combined load increment for supplementary testing based on the difference between the load data and the basic load data.

[0276] For example, the load analysis service deployed on server 20 can also determine the second combined load increment corresponding to the second effect combination of the supplementary test based on the difference between the fifth load data and the basic load data analyzed in S308. Specifically, server 20 can add a second scene tag to the fifth load data and store it in the second database as second scene load data corresponding to the second display scene.

[0277] It can be understood that the content implemented in S508 to S520 above can correspond to the above. Figure 2b The second part shown, “5. Decomposition of basic load, scene load and corresponding effect combination”, refers to the process of decomposing or supplementing the test to determine the basic load, scene load and combined load increments corresponding to each frame interface.

[0278] It is understood that, based on the execution process of S501 to S508 described above, the interface processing method provided in this application can perform refined load data decomposition and accurate load analysis on the display process of interfaces with animation and / or visual effects in the target application to be developed or optimized. The analysis results can be applied to the simulation process in the third part, and visually displayed to users, such as developers or UX designers, through the simulation interface to guide the development or optimization process of the target application.

[0279] In addition, according to the execution process of S509 to S520 above, the interface processing method provided by this application can also perform load testing on some effect combinations added to the interface of the target application, and then update the scene load data and corresponding combination load increments obtained from the test to the relevant database. This can also improve the data richness of the relevant database, support the provision of more display scene load data and related load increments, and improve the matching degree of the relevant database to more data query needs.

[0280] The following section will provide a detailed explanation of the specific implementation process involved in Part 3 above, using the flowchart as an example.

[0281] Figure 6 This application provides an embodiment of a flowchart illustrating a method for simulating load and performance changes related to animation and / or visual effects. It is understood that for the display process of interfaces with display effects or combinations thereof in a target application to be developed or optimized, the reasonableness of the load resulting from the designed display effects or combinations thereof, and the corresponding load changes caused by adding or removing display effects from the designed combinations, may lead to performance degradation in some electronic devices. Figure 6 The simulation interface and simulation results provided by the illustrated process can help to present the above-mentioned load and load changes, and provide a reference for the development or optimization design of the relevant interfaces of the target application.

[0282] like Figure 6 As shown, the implementation process may specifically include:

[0283] S601: Mobile phone 10 is running a target application that is yet to be developed or optimized.

[0284] S602: Mobile phone 10 generates runtime logs for the target application.

[0285] For example, the process of generating runtime logs by running the target application on the mobile phone 10 can be triggered by the user performing load simulation operations through the simulation client installed on the computer 30. For instance, in response to the user's relevant operations, the computer 30 can send relevant control commands to the mobile phone 10 to instruct the running of the target application.

[0286] The runtime log generated by the target application running on the mobile phone 10 can be recorded as the eighth runtime log. In some embodiments, after the user performs a load simulation operation to trigger the mobile phone 10 to run the target application, the aforementioned... Figure 5 The process includes load-related data breakdown and supplementary testing. In this case, the eighth running log can also be the same log as the sixth running log mentioned above.

[0287] S603: Mobile phone 10 sends the running log corresponding to the target application to computer 30.

[0288] For example, the mobile phone 10 can send the eighth running log generated above to the computer 30 through a wired or wireless communication connection, so as to use the test framework deployed on the computer 30 to perform data format conversion processing.

[0289] S604: Computer 30 converts the running log into the corresponding formatted data.

[0290] For example, computer 30 can convert the received eighth running log into corresponding eighth formatted data.

[0291] S605: Computer 30 sends formatted data and scene analysis requests to server 20.

[0292] For example, computer 30 can send the converted eighth formatted data, along with a scenario analysis request for the display scenario involved in the eighth running log corresponding to the eighth formatted data, to the load analysis service of server 20.

[0293] S606: Server 20, based on the start and end times of one or more interface refresh time periods, filters out the formatted data corresponding to the multiple frames of the interface displayed during each refresh time period from the received formatted data.

[0294] For example, referring to the description related to the sixth running log in S502 above, the eighth running log generated by the target application to be developed or optimized also includes p scene logs. Each scene log can record the scene load data generated by the display scene corresponding to each interface with added animation and / or visual effects within the corresponding animation duration or the corresponding interface refresh time period. Therefore, based on the start and end times of each interface refresh time period, the scene load data of the interface set corresponding to each scene log can be extracted from the eighth formatted data obtained by converting the above-mentioned eighth running log. This scene load data can be further used in the execution process of S607 to S609 below to determine the display scene, scene load data, effect combination under the corresponding display scene, and corresponding combination identification parameters, etc., corresponding to the display process of each frame interface display process.

[0295] S607: Server 20 determines each frame of the multi-frame interface within the refresh time period of each interface.

[0296] For example, the server 20 can identify each frame of the interface during the refresh time period based on the interface label of each frame, and then extract the relevant processing records of each frame, which include the scene load data of the display scene corresponding to each frame.

[0297] S608: Server 20 extracts the combination recognition parameters and scene identifiers of the corresponding display scenes for the combination of effects added to each frame of the interface, based on the recognition parameters of each display effect.

[0298] For example, the load analysis service of server 20 can combine the identification parameters corresponding to each display effect to determine the display effects or combinations of effects added to each interface, and then determine the corresponding combination identification parameters. Furthermore, based on the determined combination of effects and the interface labels of the relevant interfaces, the load analysis service of server 20 can also determine the scene identifier of the display scene corresponding to each frame interface. Here, the determined display scene can be denoted as the third display scene, and the corresponding scene identifier can be denoted as the third scene identifier.

[0299] S609: Server 20 sends the determined scene identifier and effect combination corresponding to the combination recognition parameters to computer 30.

[0300] For example, server 20 can send the determined scene identifier (e.g., third scene identifier) ​​and the combination recognition parameters corresponding to the effect combination to computer 30. The third scene identifier indicates the effect combination corresponding to the third display scene.

[0301] S610: Computer 30 sends a request to server 20 to obtain load-related data.

[0302] For example, computer 30 sends a request to server 20 to obtain load-related data for the display scene indicated by the received scene identifier (e.g., a third scene identifier). The request may carry the scene identifier, and the requested load-related data may include scene load data, combined load increments, and load increments corresponding to the q display effects included in the related effect combination (e.g., the fourth effect combination mentioned above).

[0303] S611: Server 20 queries the database for load-related data corresponding to the relevant effect combination, including scene load data, combined load increment, and load increment corresponding to the q display effects included in the relevant effect combination.

[0304] For example, server 20 can query load-related data from a first database and a second database in response to a received load-related data retrieval request. As mentioned above, the first database is used to store load increments corresponding to various display effects and combined load increments corresponding to some effect combinations. Server 20 can query from the first database the combined load increments corresponding to the fourth effect combination corresponding to the third display scene, and the load increments corresponding to the q display effects included in the fourth effect combination. The second database is used to store scene load data and combined load increments of effect combinations corresponding to each display scene. Therefore, server 20 can query from the second database the scene load data corresponding to the third display scene and the combined load increments corresponding to the fourth effect combination corresponding to the third display scene. Wherein, when the fourth effect combination corresponds to the second effect combination in the second database, the scene load data corresponding to the third display scene can be the second scene load data corresponding to the second display scene stored in the second database.

[0305] It is understandable that the combined load increment matched in the first database for the third display scenario should be the same as the combined load increment matched in the second database. Therefore, after server 20 matches the combined load increment corresponding to the fourth effect combination from the first database, it can skip the process of querying the combined load increment from the second database. Correspondingly, if server 20 matches the combined load increment corresponding to the fourth effect combination from the second database, it can also skip the process of querying the combined load increment from the first database.

[0306] In some embodiments, the third scene identifier can correspond to a second scene identifier matched in the first database and the second database. The third display scene indicated by the third scene identifier can be matched with the second display scene indicated by the second scene identifier. Furthermore, the fourth effect combination corresponding to the third display scene can be matched one-to-one with various display effects of the second effect combinations in the first database and the second database. Based on this, the combined load increment of the second effect combination corresponding to the second display scene can be used as the combined load increment of the fourth effect combination corresponding to the currently identified third display scene. The second combination identification parameter corresponding to the second effect combination can also be determined as the combination identification parameter corresponding to the fourth effect combination.

[0307] S612: Server 20 sends the retrieved load-related data to computer 30.

[0308] For example, server 20 can retrieve the load-related data, such as the combined load increment corresponding to the fourth effect combination corresponding to the third display scene, the load increment corresponding to each of the q display effects included in the fourth effect combination, and the scene load data corresponding to the third display scene. As mentioned above, the scene load data corresponding to the third display scene can be the second scene load data corresponding to the second display scene stored in the second database.

[0309] S613: A load simulation interface for a display scene corresponding to a combination of display effects on computer 30. The interface content of this load simulation interface includes controls corresponding to at least one of the functions of adding, deleting, and modifying q display effects.

[0310] For example, a simulation client can be installed on computer 30, which can be used to perform load simulation on the display process of the interface with added animation and / or visual effects. When computer 30 runs the simulation client, it can display the load simulation interface of the corresponding display scenario based on the load-related data obtained from server 20.

[0311] As an example, see reference Figure 7a A load simulation interface 710 may include user-operable configuration controls such as product options 711, scene options 712, visual effects schemes 713, attribute parameters 714, and optimization schemes 715. Product options 711 may include the target application currently being tested, such as different versions of the target application, or the terminal products that the target application to be developed will be adapted to, such as mobile phones, tablets, or laptops, and product models of various products. It is understood that different terminal products have different hardware configurations, and the load impact of the target application running on different terminal products will also vary. For example, different terminal products support different resolutions, and the load corresponding to displaying certain interfaces with visual effects will also vary. Scene options 712 may include the display scene corresponding to each frame of the interface determined above. The display scene corresponding to each frame of the interface within different interface refresh time periods can be different. For example, in... Figure 7a On the load simulation interface 710 shown, the user can select "Control Center Drop-down" in the option box corresponding to the scene option 712. In other embodiments, the user can also select other display scenes in this option box, such as page switching, etc., which are not limited here.

[0312] Continue to refer to Figure 7aThe option box 131 corresponding to the visual effect scheme 713 can provide operation controls such as "add", "modify", and "delete". The option box 132 corresponding to the visual effect scheme 713 can provide various display effects adapted to the currently configured display scene, such as blur, grayscale, brightening, and irregular shapes. Combined with the operation controls provided by the aforementioned option box 131, operations such as adding, modifying, and deleting different display effects can be achieved. The option boxes corresponding to the attribute parameters 714 can provide parameter options corresponding to different visual effects, such as the parameter "10sig..." corresponding to blur (radius), "1" corresponding to brightness (brightness), and "grey_coef1", "grey_coef2", and "0" corresponding to grayscale, etc., and can also include the "frame range" applied by the currently designed visual effect scheme, such as "1-10". In some embodiments, Figure 7a The load simulation interface 710 shown may also include an optimization scheme 715, which can provide optimization methods such as "frame skipping". Users can also set the frame refresh rate corresponding to optimization schemes such as "frame skipping" in the option box corresponding to optimization scheme 715, such as "refresh every 5 frames" or others. "Frame skipping" refers to skipping one frame of the interface to add display effects or a combination of effects; that is, it is an optimization method that does not add any display effects to the skipped interface before drawing, rendering, and displaying.

[0313] Continue to refer to Figure 7a The load simulation interface 710 may also include a "Execute Simulation" control 716. After selecting or configuring the product options 711, scene options 712, visual effects schemes 713, attribute parameters 714, and optimization schemes 715, the user can click the "Execute Simulation" control 716. At this time, the computer 30 can obtain the scene load data of the relevant display scene, the combined load increment of the relevant effect combination, and the load increment of various adapted display effects under the corresponding attribute parameters according to the execution process of S601 to S613, and then display the corresponding simulation results.

[0314] As another example, see Figure 7bAnother load simulation interface 720 may include operation controls corresponding to the "visual effects scheme", including "delete visual effects" 721, "add new visual effects" 722, "modify existing visual effects" 723, etc. Furthermore, the load simulation interface 720 may also include a configuration table 724 corresponding to each of the above operation options. For example, for the user selecting the operation "delete visual effects" 721, the user can further select the specific visual effect to be deleted, such as "brighten", in the configuration table 724. The attribute parameters corresponding to the deleted "brighten" can be, for example, "width: 1200px; height: 2600px", and the frame identification number (ID) of the interface it affects can be "2", that is, the "brighten" effect on the second frame of the interface is deleted. Similarly, for the user's "Add New Visual Effect" 722 operation, the user can further select the specific visual effect to be added, such as "Shadow," in configuration table 724. The user can then configure the attribute parameters for this added "Shadow" effect as "width: 100px; height: 200px; radius: 20; shadowOffsetX: 10.0; shadowOffsetY: 10.0" and the corresponding frame ID of the affected interface, such as "1,3,5,7,9,11." For the user's "Modify Existing Visual Effect" 723 operation, the user can further select the specific visual effect to be modified, such as "Enhanced Background Blur," in configuration table 724. The user can change the original parameters "width: 1200px; height: 2600px" to "width: 1200px; height: 2200px" and / or modify the corresponding frame ID of the affected interface, such as "4" or others; no restrictions are placed here.

[0315] Continue to refer to Figure 7b The load simulation interface 720 may also include an "Execute Simulation" control 725. After completing the specific operations of the selected "Delete Visual Effect" 721, "Add New Visual Effect" 722, and "Modify Existing Visual Effect" 723 operations in the configuration table 724, the user can click the "Execute Simulation" control 725. At this time, the computer 30 can obtain the scene load data of the relevant display scene, the combined load increment of the relevant effect combination, and the load increment of various adapted display effects under the corresponding attribute parameters according to the execution process of S601 to S613, and then display the corresponding simulation results.

[0316] As an example, Figures 8a to 8c Some simulation result interface diagrams are shown according to embodiments of this application.

[0317] like Figure 8aAs shown, the simulation results interface 810 can display product information 811, including "Product Series," "Product Model," "Test Version," "Test Time," "Resolution," and "Test Equipment Number," etc. The simulation results interface 810 can also display simulation results such as scene load ranking 812 and scene load details 813. The scene load ranking 812 can include a comparison of the load size of the display scenes corresponding to each interface displayed within multiple interface refresh time periods, and can include CPU load ranking and GPU load ranking, etc. For example, Figure 8a In the example CPU load ranking and GPU load ranking, Scene 1 has the highest load, and Scene 3 has the lowest load. Scene load details 813 can display detailed scene load information for any of the above rankings, such as the scene frame average load. For example, refer to... Figure 8a As shown, corresponding to the user-selected scene 1, scene load details 813 can display the CPU and GPU load details consumed during the display process of each frame of the scene. Among them, the total CPU load (N+M) can include the sum of the base load N and the visual effect load increment M, and the size of M can include the sum of the load increment n corresponding to visual effect 1 and the load increment m corresponding to visual effect 2.

[0318] like Figure 8b As shown, the scene load details 821 displayed on the simulation results interface 820 can be displayed in another form to show the average load of scene frames. For example, scene load details 821 can display the CPU RS load corresponding to the number of tasks and the CPU RT load corresponding to the runtime. For example, the total load corresponding to scene 1 can include CPU RS load "28.17", CPU RT load "86.95", and GPU load "212.81", etc. Among them, the base load can include CPU RS load "5.05", CPU RT load "77.16", and GPU load "169.24", etc. The corresponding visual load increment can include CPU RS load "23.12", CPU RT load "9.79", and GPU load "43.57", etc. The total load is the sum of the base load and the visual load increment, and the CPU load is the sum of the CPU RS load and CPU RT load mentioned above. The above load values ​​are only examples. In actual testing and simulation, the above loads can be any reasonable values, and no restrictions are imposed here.

[0319] like Figure 8c As shown, the simulation results interface 830 can display the scene load details 831 in another form. For example, the scene load details 831 can display the scene load of a single frame in the form of a bar chart, see reference. Figure 8cThe scene load corresponding to Scene 1 shown includes the load of the following frames: “1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 65 67 69” and the load of the frames between each frame. The scene load of each frame includes the corresponding basic load and the load increment corresponding to the animation effects added to each frame, such as shadow (i.e., visual effect 1), brightening (i.e., visual effect 2), and background blur enhancement (i.e., visual effect 3).

[0320] In other embodiments, the simulation results interface presents scene load details in a manner other than those described above. Figure 8a or Figure 8b The example table Figure 8c In addition to the bar charts shown, pie charts or other formats may also be included, without limitation.

[0321] It is understandable that if the user is in the above... Figure 7a or Figure 7b After adding, deleting, or modifying visual effects schemes for related display scenes on the example load simulation interface, clicking the "Execute Simulation" control will enable... Figures 8a to 8c The relevant load data on the example simulation results interface will change accordingly. The changed simulation results interface can be referenced. Figure 9a or Figure 9b As shown.

[0322] For example, taking the addition of "Visual Effect 2" as an example, refer to Figure 9a As shown, the scene load details 911 displayed on the simulation result interface 910 can show that the total load change in the average scene frame load of scene 1 is N+M+i (i.e., the total load increase is i), the visual effect load increment change is M+i (i.e., the visual effect load increment increase is i), the load of visual effect 1 is n, and the load change of visual effect 2 is m+i. In some other embodiments, the above changes can also be presented in another form, see reference. Figure 9bIn the scene load details 921 displayed on the simulation results interface 920, the total load includes CPU RS load changes of "28.22 (+0.05)", CPU RT load changes of "86.97 (+0.02)", and GPU load changes of "212.86 (+0.06)". The base load includes CPU RS load changes of "0 (-5.05)", CPU RT load changes of "82.53 (+5.37)", and GPU load changes of "159.05 (-10.19)". The visual effects load increment includes CPU RS load changes of "69.64 (+46.52)", CPU RT load changes of "4.44 (-5.35)", and GPU load changes of "53.82 (+10.25)".

[0323] In some embodiments, the above Figures 8a to 8c , Figures 9a to 9b The simulation results interface can also display analysis suggestions related to the performance of the target application or the terminal products applicable to the target application, such as "The current combined load is high, which may lead to the performance degradation of the products running this application", etc. There are no restrictions here.

[0324] It is understandable that, based on the implementation process of the load and performance simulation method in the examples S601 to S613 above, and the above... Figures 7a to 7b , Figures 8a to 8c as well as Figures 9a to 9b The simulation-related interface shown in the example, and the interface processing method provided in this application, can provide users with more accurate and direct simulation analysis results, so as to provide reference value for users (such as developers or UX designers) in developing or optimizing the user experience and performance of related target applications.

[0325] Additionally, when executing the query process in S611, server 20 may not be able to find the load-related data corresponding to the relevant effect combination, i.e., it may not be able to match the load-related data. In this case, server 20 can generate a corresponding test case configuration file based on the identification parameters corresponding to the q display effects of the fourth effect combination, and send it to computer 30. The test case configuration file may include the identification parameters corresponding to the q display effects and the attribute parameters configured for each display effect. Correspondingly, after receiving the test case configuration file, computer 30 can generate a corresponding test case (denoted as the seventh test case) based on the test case configuration file. This seventh test case can perform load testing on the fourth display scene corresponding to the fourth effect combination, and this seventh test case may correspond to the fourth scene identifier. The fourth display scene indicated by the fourth scene identifier may be different from the first, second, or third display scene mentioned above.

[0326] Furthermore, computer 30 can send the aforementioned seventh test case to mobile phone 10 and obtain the running log (denoted as the ninth running log) generated by mobile phone 10 running the benchmark application and loading and executing the seventh test case. This ninth running log may include load data (denoted as the sixth load data) generated during the process of mobile phone 10 displaying multiple frames of the corresponding interface set (denoted as the seventh interface set). Computer 30 can convert the received ninth running log into ninth formatted data and send it to server 20, and obtain the sixth load data extracted by server 20 based on the ninth formatted data, the combined load increment corresponding to the aforementioned fourth effect combination, and the load increments corresponding to the aforementioned q display effects. It can be understood that the load data and load increments obtained by computer 30 at this time are supplementary test data implemented by computer 30 through server 20 and mobile phone 10 during the simulation process. Based on this, computer 30 can display the load simulation interface and simulation result interface corresponding to the aforementioned fourth display scenario based on the supplementary test data. The interface content of this load simulation interface can be referred to the above... Figures 7a to 7b The descriptions shown and related information will not be repeated here.

[0327] As mentioned above, in other embodiments, the load analysis service deployed on server 20, the test framework deployed on computer 30, and the simulation client can also be deployed on mobile phone 10 or other terminal electronic devices running the test application or target application, to execute the above-mentioned test process and simulation process in an integrated manner, achieving a high degree of integration of test and simulation functions. In this case, mobile phone 10 can act as the execution subject to implement the interface processing method provided in this application, and there are no limitations on this.

[0328] As an example, Figure 10 A schematic diagram of a load simulation interface displayed on a mobile phone is shown according to an embodiment of this application.

[0329] like Figure 10 As shown, the load simulation interface 010 displayed on the mobile phone 10 may also include product options 011, scene options 012, visual effects schemes 013, attribute parameters 014, optimization schemes 015, and a "Perform Simulation" control 016. The specific functions of each option and control can be found above. Figure 7aThe descriptions and related information are not repeated here. For the aforementioned example, after setting the terminal product (e.g., mobile phone) applicable to the target application in the option box corresponding to product option 711 of the load simulation interface 010, selecting "Control Center Drop-down" in the option box corresponding to scene option 012, selecting "Add", "Blur, Grayscale, Brighten, Irregular Shape" and other visual effects in the option box corresponding to visual effect scheme 013, and setting the parameters related to each display effect and the "Frame Range" of the currently designed visual effect scheme in the option box corresponding to attribute parameter 714, the user can click the "Execute Simulation" control 016.

[0330] Correspondingly, continue to refer to Figure 10 The mobile phone 10 can obtain the load increment corresponding to the newly added visual effects such as "blur, grayscale, brightening, and irregular shape" under relevant attribute parameters from the "first database". It can also obtain the combined load increment corresponding to the combination of the newly added visual effects with other animations or visual effects already added to the interface of the currently analyzed "control center dropdown" scene. Furthermore, the mobile phone 10 can obtain the scene load data of the test scene corresponding to the display scene or effect combination corresponding to the interface of the "control center dropdown" scene from the "second database", as well as the combined load increment of the effect combination corresponding to each display scene. Based on this, the mobile phone 10 can further display the relevant load simulation result interface, and also the relevant performance simulation result interface. The interface content displayed in this simulation result interface can be referred to the above. Figures 8a to 8c The interface shown or refer to the above. Figures 9a to 9b The content of the interface shown is not limited here.

[0331] Figure 11 A schematic diagram of the hardware structure of an electronic device is shown according to an embodiment of this application. This electronic device can be, for example, the first electronic device such as the aforementioned mobile phone 10, or the second electronic device such as the aforementioned computer 30; no limitation is made herein.

[0332] like Figure 11As shown, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identity module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0333] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0334] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

[0335] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0336] In this embodiment of the application, taking mobile phone 10 as an example, processor 110 can be controlled by controller to execute the above-mentioned... Figure 3, Figure 5 and Figure 6 The instructions corresponding to each step implemented by the mobile phone 10 are used to implement the interface processing method provided in this application. In some other embodiments, the electronic device 100 may also be the computer 30 or other terminal-type electronic devices described above.

[0337] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the aforementioned memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0338] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a SIM card interface, and / or a universal serial bus (USB) interface, etc.

[0339] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0340] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0341] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0342] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0343] The electronic device 100 can implement shooting functions through an ISP, a camera 193, a video codec, a GPU, a display 194, and an application processor. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0344] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0345] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phone book, etc.). Processor 110 executes various functional applications and data processing of electronic device 100 by running instructions stored in internal memory 121 and / or instructions stored in memory located in the processor.

[0346] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0347] Touch sensor 180K, also known as a "touch device," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touchscreen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.

[0348] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.

[0349] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback.

[0350] Indicator 192 can be an indicator light, which can be used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0351] The SIM card interface 195 is used to connect a SIM card. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0352] Figure 12 A schematic diagram of the operating system software structure of an electronic device is shown according to an embodiment of this application. The electronic device may be, for example, the one described above. Figure 11 The electronic device 100 shown in the example is not limited here.

[0353] It is understood that the operating system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses the layered architecture Android system as an example to exemplify the system software structure of electronic device 100.

[0354] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, Android... TM The system is divided into four layers, from top to bottom: application layer, application framework layer, and Android. TM runtime (Android) TM runtime and system libraries, as well as the kernel layer.

[0355] like Figure 12 As shown, the application layer may include a series of application packages. These application packages may include third-party applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, SMS, and browsers, instant messaging applications, and video applications. These applications can be run as target applications when they need to be updated or optimized. In this embodiment, the application package may also include a test application (such as the benchmark application mentioned above), used to execute test cases and generate corresponding runtime logs, which are then used to analyze the scene load data corresponding to the display scene of the relevant interface, the load increment or combined load increment corresponding to the added display effects or effect combinations, etc.

[0356] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0357] The application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0358] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0359] Content providers store and retrieve data, making that data accessible to applications. This data can include videos, images, audio, phone calls made and received, browsing history and bookmarks, phone books, etc.

[0360] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0361] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

[0362] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0363] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0364] In other embodiments, the application package may further include a simulation client (shown in the dashed box in the figure), and the application framework layer may further include a test framework (shown in the dashed box in the figure). For example, mobile phone 10 may have the simulation client installed and the test framework deployed, enabling mobile phone 10 to execute the aforementioned... Figure 3 , Figure 5 and Figure 6 The relevant steps implemented for the China Mobile 10 also follow the steps outlined in the above diagram. Figure 5 and Figure 6 The relevant steps for implementation corresponding to the computer 30.

[0365] In other embodiments, the application framework layer may also include a load analysis service (shown in the dashed box in the figure), based on which the mobile phone 10 may also perform the above-described functions. Figure 3 , Figure 5 and Figure 6 The steps performed by the load analysis service on the server 20 are not limited or elaborated here.

[0366] Android TM Runtime includes the core libraries and the virtual machine. Android TM Runtime is responsible for Android. TM System scheduling and management.

[0367] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0368] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0369] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0370] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0371] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0372] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0373] A 2D graphics engine is a graphics engine for 2D drawing.

[0374] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0375] The following example, using a test scenario, illustrates the workflow of the software and hardware of electronic device 100.

[0376] When the touch sensor 180K receives a touch operation, which could be an action on a test control or a related option box or control on the load simulation interface, a corresponding hardware interrupt is sent to the kernel layer. The kernel layer processes the touch operation into a raw input event (including touch coordinates, touch operation timestamp, etc.). The raw input event is stored in the kernel layer. The application framework layer retrieves the raw input event from the kernel layer and identifies the control corresponding to the input event. For example, if the touch operation is a single click, the control corresponding to the single click is as described above. Figures 4a to 4d Taking the test control shown as an example, the benchmark application calls the interface of the application framework layer, and then calls the kernel layer to start the touch driver, collects the capacitance value of the user's touch position to determine the user's touch position and the corresponding input event.

[0377] Figure 13 A schematic diagram of a server hardware structure is shown according to an embodiment of this application. In this embodiment, Figure 13 The server shown can be the aforementioned server 20, and there are no restrictions here.

[0378] like Figure 13As shown, server 20 includes a bus 202, a processor 204, a memory 206, and a communication interface 208. The processor 204, memory 206, and communication interface 208 communicate via the bus 202. Server 20 can be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in server 20.

[0379] Bus 202 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 3 The bus 204 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 204 may include a path for transmitting information between various components of the server 20 (e.g., memory 206, processor 204, communication interface 208).

[0380] Processor 204 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0381] Memory 206 may include volatile memory, such as random access memory (RAM). Memory 206 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0382] The memory 206 stores executable program code, and the processor 204 executes the executable program code to implement the aforementioned interface processing methods. That is, the memory 206 stores instructions for executing the aforementioned interface processing methods.

[0383] Alternatively, the memory 206 stores executable code, and the processor 204 executes the executable code to implement the above-mentioned tasks respectively. Figure 3 , Figure 5 and Figure 6 The server 20 executes various steps to implement the interface processing method provided in this application, thereby saving computing resources, reducing device power consumption, and improving device performance in some animation display scenarios. That is, the memory 206 stores instructions for executing the interface processing method provided in this application.

[0384] The communication interface 208 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the server 20 and other devices or communication networks.

[0385] This application also provides a computer program product for implementing the interface processing methods provided in the above embodiments.

[0386] Various embodiments of the mechanisms disclosed in this application can be implemented in hardware, software, firmware, or combinations of these implementation methods. Embodiments of this application can be implemented as computer program modules or module code executable on a programmable system, the programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0387] Computer program modules or module code can be applied to input instructions to perform the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0388] Module code can be implemented using a high-level modular language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used to implement module code when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

[0389] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored thereon on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or via other computer-readable storage media. Therefore, machine-readable storage media may include any mechanism for storing or transmitting information in a machine-readable (e.g., computer-readable) form, including but not limited to floppy disks, optical disks, optical discs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic cards or optical cards, flash memory, or tangible machine-readable storage for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) using the Internet in the form of electrical, optical, acoustic, or other forms of propagated signals. Therefore, machine-readable storage media include any type of machine-readable storage media suitable for storing or transmitting electronic instructions or information in a machine-readable (e.g., computer-readable) form.

[0390] In this specification, the reference to "an embodiment" or "an embodiment" means that a specific feature, structure, or characteristic described in connection with the embodiment is included in at least one exemplary implementation or technology disclosed according to an embodiment of this application. The appearance of the phrase "in an embodiment" in various places in the specification does not necessarily refer to the same embodiment.

[0391] The disclosure of embodiments of this application also relates to means for performing operations in text. This means may be specifically constructed for the claimed purpose or may include a general-purpose computer selectively activated or reconfigured by a computer program stored in a computer. Such a computer program may be stored in a computer-readable storage medium, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs, magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic or optical cards, application-specific integrated circuits (ASICs), or any type of medium suitable for storing electronic instructions, and each may be coupled to a computer system bus. Furthermore, the computer mentioned in the specification may include a single processor or may be an architecture employing multiple processors for increased computing power.

[0392] Furthermore, the language used in this specification has been primarily chosen for readability and instructional purposes and may not have been chosen to depict or limit the disclosed subject matter. Therefore, the embodiments disclosed herein are intended to illustrate, and not limit, the scope of the concepts discussed herein.

Claims

1. An interface processing method, characterized in that, Applied to a first electronic device, the method includes: A first test instruction is received, wherein the first test instruction is used to instruct a load test to be performed on the display process of a first interface set, the first interface set including multiple frames of interfaces that change continuously with the interface refresh time. In response to the first test instruction, the first application is run to execute the first test case and generate a first runtime log, wherein the first runtime log includes at least the basic load data generated corresponding to the display process of the first interface set; A second test instruction is received, wherein the second test instruction is used to instruct a load test to be performed on the display process of the second interface set, wherein each frame interface in the second interface set corresponds to each frame interface in the first interface set, and each frame interface in the second interface set has a corresponding added first display effect. In response to the second test instruction, the first application is run to execute the second test case and generate a second running log, wherein the second running log includes at least the first load data generated corresponding to the display process of the second interface set; Furthermore, the basic load data and the first load data are obtained based on the application tag corresponding to the first application and the interface tag corresponding to each frame interface, respectively. The first load data includes a first identification parameter corresponding to the first display effect, and the difference between the first load data and the basic load data is the first load increment corresponding to the first display effect.

2. The method according to claim 1, characterized in that, The first display effect is configured with a first attribute parameter, and the first load increment corresponds to the first attribute parameter.

3. The method according to claim 2, characterized in that, The method further includes: A third test instruction is received, wherein the third test instruction is used to instruct a load test to be performed on the display process of the third interface set, wherein each frame interface in the third interface set corresponds to each frame interface in the first interface set, each frame interface in the third interface set has a corresponding added first display effect, and the first display effect is configured with a second attribute parameter, wherein the second attribute parameter is different from the first attribute parameter. In response to the third test instruction, the first application is run to execute the third test case and generate a third runtime log, wherein the third runtime log includes at least the second load data generated corresponding to the display process of the third interface set; Furthermore, the difference between the second load data and the basic load data is the second load increment corresponding to the first display effect, wherein the second load increment is different from the first load increment.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: A fourth test instruction is received, wherein the fourth test instruction is used to instruct a load test to be performed on the display process of the fourth interface set, wherein each frame interface in the fourth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fourth interface set has a corresponding added second display effect, the second display effect being different from the first display effect; In response to the fourth test instruction, the first application is run to execute the fourth test case and generate a fourth running log, wherein the fourth running log includes at least the third load data generated corresponding to the display process of the fourth interface set; Furthermore, the third load data includes a second identification parameter corresponding to the second display effect, and the difference between the third load data and the basic load data is the third load increment corresponding to the second display effect.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: A fifth test instruction is received, wherein the fifth test instruction is used to instruct a load test to be performed on the display process of the fifth interface set, wherein each frame interface in the fifth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fifth interface set has a corresponding added first effect combination, wherein the first effect combination includes at least two of n display effects, where n is an integer greater than or equal to 2, and the n display effects include the first display effect. In response to the fifth test instruction, the first application is run to execute the fifth test case and generate a fifth runtime log, wherein the fifth runtime log includes at least the fourth load data generated corresponding to the display process of the fifth interface set; Furthermore, the fourth load data includes a first combination identification parameter corresponding to the first effect combination, and the difference between the fourth load data and the basic load data is the first combination load increment corresponding to the first effect combination.

6. The method according to claim 5, characterized in that, The fourth load data includes a first scene identifier corresponding to the first effect combination. The first scene identifier is used to indicate the first display scene of the multi-frame interface of the first interface set and the first display scene of the first effect combination. The fourth load data is the first scene load data corresponding to the first display scene.

7. The method according to claim 5 or 6, characterized in that, The method further includes: The sixth test instruction is received, wherein the sixth test instruction is used to instruct a load test to be performed on the p display effect combinations corresponding to the p frame interface set of the second application, where p is an integer greater than or equal to 1; In response to the sixth test instruction, the second application is run, and a sixth operation log is generated, wherein the sixth operation log includes p scene logs corresponding to the p display effect combinations, and each scene log includes corresponding scene load data.

8. The method according to claim 7, characterized in that, The first scene log in the p scene logs includes second scene load data corresponding to the second display scene, the multi-frame interface corresponding to the second display scene has a corresponding added second effect combination, and the method further includes: Provide the sixth runtime log to the server; Receive a sixth test case generated based on the first scene log and a seventh test instruction to execute the sixth test case, wherein the sixth test case includes a test script corresponding to a sixth interface set having the second effect combination, and the multi-frame interfaces in the sixth interface set correspond to the multi-frame interfaces displayed in the second display scene respectively; In response to the seventh test instruction, the first application is run to execute the sixth test case and generate a seventh runtime log, wherein the seventh runtime log includes at least the fifth load data generated corresponding to the display process of the sixth interface set; The difference between the fifth load data and the basic load data is the second combined load increment corresponding to the second effect combination.

9. The method according to claim 8, characterized in that, The fifth load data includes a second scene identifier for indicating the second display scene, and the second scene identifier corresponds to the second effect combination; and, The sixth test case is a test case generated when the server does not include the load increment with the second scenario identifier.

10. An interface processing method, characterized in that, Applied to a second electronic device, the method includes: Obtain the first formatted data corresponding to the first running log of the first application, wherein the first running log includes at least the basic load data generated corresponding to the display process of the first interface set, and the first interface set includes multiple frames of interfaces that change continuously with the interface refresh time. Based on the application tag of the first application and the interface tag corresponding to each frame interface, the basic load data is extracted from the first formatted data; and, Obtain the second formatted data corresponding to the second running log of the first application, wherein the second running log includes at least the first load data generated corresponding to the display process of the second interface set, each frame interface in the second interface set corresponds to each frame interface in the first interface set, and each frame interface in the second interface set has a corresponding added first display effect. Based on the application tag, the interface tag, and the first identification parameter corresponding to the first display effect, extract the first load data from the second formatted data; Based on the difference between the first load data and the basic load data, a first load increment corresponding to the first display effect is determined.

11. The method according to claim 10, characterized in that, The first display effect is configured with a first attribute parameter, and the first load increment corresponds to the first attribute parameter.

12. The method according to claim 11, characterized in that, The method further includes: Obtain third formatted data obtained by converting the third running log of the first application, wherein the third running log includes at least the second load data generated corresponding to the display process of the third interface set, each frame interface in the third interface set corresponds to each frame interface in the first interface set, each frame interface in the third interface set has a corresponding added first display effect, and the first display effect is configured with a second attribute parameter, the second attribute parameter being different from the first attribute parameter. Based on the application tag, the interface tag, and the first identification parameter, extract the second load data from the third formatted data; Based on the difference between the second load data and the basic load data, a second load increment corresponding to the first display effect is determined. The second load increment corresponds to the second attribute parameter, wherein the second load increment is different from the first load increment.

13. The method according to any one of claims 10 to 12, characterized in that, The method further includes: Obtain fourth formatted data obtained by converting the fourth running log of the first application, wherein the fourth running log includes at least the third load data generated corresponding to the display process of the fourth interface set, each frame interface in the fourth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fourth interface set has a corresponding added second display effect, the second display effect being different from the first display effect. Based on the application tag, the interface tag, and the second identification parameter corresponding to the second display effect, the third load data is extracted from the fourth formatted data; Based on the difference between the third load data and the basic load data, a third load increment corresponding to the second display effect is determined.

14. The method according to any one of claims 10 to 13, characterized in that, The method further includes: The fifth formatted data is obtained by converting the fifth running log of the first application. The fifth running log includes at least the fourth load data generated corresponding to the display process of the fifth interface set. Each frame interface in the fifth interface set corresponds to each frame interface in the first interface set. Each frame interface in the fifth interface set has a corresponding added first effect combination. The first effect combination includes at least two display effects from n display effects, where n is an integer greater than or equal to 2. The n display effects include the first display effect. The fourth load data includes a first combination identification parameter corresponding to the first effect combination. Based on the application tag, the interface tag, and the first combined identification parameters, the fourth load data is extracted from the fifth formatted data; Based on the difference between the fourth load data and the basic load data, a first combined load increment corresponding to the first effect combination is determined.

15. The method according to claim 14, characterized in that, The second electronic device includes a first database for storing the base load data and load increments, and, The method includes: Add the first identification parameter to the first load increment, and store the first load increment with the first identification parameter in the first database; and / or, The first combined load increment is added with the first combined identification parameter, and the first combined load increment with the first combined identification parameter is stored in the first database.

16. The method according to claim 15, characterized in that, The method further includes: Obtain the sixth formatted data corresponding to the sixth running log of the second application, wherein the sixth running log includes p scene logs corresponding to the p frame interface set, where p is an integer greater than or equal to 1, and the p frame interface set corresponds to p display effect combinations, and each display effect combination corresponds to scene load data. Parse the sixth formatted data to obtain the p scene logs and the scene load data corresponding to each scene log.

17. The method according to claim 16, characterized in that, The second electronic device includes a second database, which is used to store scene load data at least. The first scene log among the p scene logs includes second scene load data corresponding to the second display scene, and a second effect combination is added to the multi-frame interface displayed corresponding to the second display scene. The method includes: No load data with a second scene identifier was detected in the second database, wherein the second scene identifier is used to indicate the second display scene; Add the second scene identifier to the second scene load data, and store the second scene load data with the second scene identifier in the second database.

18. The method according to claim 17, characterized in that, The second database is also used to store load increments corresponding to load data for each scenario, and, The method includes: No load increment with the second scenario identifier was detected in the first database; Based on the second effect combination corresponding to the second scene identifier, a corresponding test case configuration file is generated. The test case configuration file includes identification parameters and attribute parameters corresponding to the definition of each display effect in the second effect combination. The test case configuration file is used to generate a sixth test case. The sixth test case includes a test script corresponding to a sixth interface set with the second effect combination. The multi-frame interfaces in the sixth interface set correspond to the multi-frame interfaces displayed in the second display scene. The test case configuration file is converted into the sixth test case via a third electronic device and sent to the first electronic device; Obtain the seventh formatted data corresponding to the seventh running log of the first application, wherein the seventh running log includes at least the fifth load data generated corresponding to the display process of the sixth interface set, wherein the first application runs on the first electronic device; Based on the difference between the fifth load data and the basic load data, determine the second combined load increment corresponding to the second effect combination; Add the second scenario identifier to the second combined load increment, and store the second combined load increment with the second scenario identifier in the first database.

19. The method according to claim 18, characterized in that, The method further includes: The second combined load increment with the second scenario identifier is stored in the second database.

20. The method according to any one of claims 1 to 19, characterized in that, The first application is a benchmark application, and the first or second runtime log includes a trace log.

21. The method according to any one of claims 1 to 20, characterized in that, The first display effect can be either a motion effect or a visual effect, wherein, The motion effect indicates the effect of the first element in the multi-frame interface changing its position, size, and color as the interface refresh time changes, and the attribute parameters of the motion effect include at least the motion effect duration related to the interface refresh time. The visual effect refers to the specific visual effect presented when the first element in the multi-frame interface is displayed on the corresponding interface.

22. The method according to any one of claims 1 to 21, characterized in that, The basic load data or the first load data includes at least one of the following: Central processing unit (CPU) load data; graphics processing unit (GPU) load data; digital signal processor (DSP) load data; integrated processor (ICP) load data.

23. An interface processing method, characterized in that, Applied to a third electronic device, the method includes: The eighth operation log is received, wherein the eighth operation log corresponds to the process of the first electronic device displaying a multi-frame interface of the sixth interface set, the sixth interface set corresponds to the addition of a fourth effect combination, the fourth effect combination corresponds to a third display scene, and the eighth operation log includes a third scene identifier for indicating the third display scene. The eighth runtime log is converted into eighth formatted data, and the eighth formatted data is sent to the server; Obtain q display effects included in the third scene identifier and the fourth effect combination extracted according to the eighth formatted data, where q is a positive integer; Send a load data acquisition request corresponding to the fourth effect combination to the server, wherein the load data acquisition request includes at least the third scene identifier corresponding to the fourth effect combination and the identification parameters corresponding to the q display effects respectively; Receive scene load data that matches the fourth effect combination, as well as the combination load increment that matches the fourth effect combination and the load increment that corresponds to the q display effects in the fourth effect combination respectively; Display a load simulation interface corresponding to the third display scenario, wherein the load simulation interface includes at least one control corresponding to the addition, deletion and modification of the q display effects.

24. The method according to claim 23, characterized in that, If no scene load data matching the fourth effect combination is received, the method further includes: A test case configuration file is received, generated according to the recognition parameters corresponding to the q display effects of the fourth effect combination. The test case configuration file includes the recognition parameters corresponding to the q display effects and the attribute parameters set for the q display effects. The test case configuration file is used to generate a seventh test case. The seventh test case is used to perform load testing on the fourth display scene corresponding to the fourth effect combination. The seventh test case corresponds to the fourth scene identifier that indicates the fourth display scene. The seventh test case is sent to the first electronic device, and the ninth running log generated by the first electronic device running the first application and executing the seventh test case is obtained. The ninth running log includes the sixth load data generated corresponding to the process of the first electronic device displaying the multi-frame interface of the seventh interface set. The multi-frame interface included in the seventh interface set corresponds to the multi-frame interface included in the sixth interface set. The ninth runtime log is converted into ninth formatted data, and the ninth formatted data is sent to the server; Obtain the sixth load data extracted based on the ninth formatted data and the combined load increment corresponding to the fourth effect combination, and obtain the load increments corresponding to the q display effects respectively; Display a load simulation interface corresponding to the fourth display scenario, wherein the load simulation interface includes at least one control corresponding to at least one of the functions of adding, deleting, and modifying q display effects.

25. The method according to claim 24, characterized in that, The first application is a benchmark application, and the eighth or ninth runtime log includes a trace log.

26. An interface processing system, characterized in that, Includes a first electronic device and a second electronic device, wherein, The first electronic device is configured to respond to a received first test instruction, run a first application to execute a first test case, and generate a first operation log. The first test instruction is used to instruct a load test on the display process of a first set of interfaces, the first set of interfaces comprising multiple frames that continuously change with the interface refresh time, and the first operation log includes at least the basic load data generated corresponding to the display process of the first set of interfaces. The first electronic device is further configured to respond to a received second test instruction, run the first application to execute a second test case, and generate a second runtime log, wherein the second test instruction is used to instruct a load test on the display process of a second interface set, each frame interface in the second interface set corresponds to each frame interface in the first interface set, each frame interface in the second interface set has a corresponding added first display effect, the first display effect is configured with a first attribute parameter, and the second runtime log includes at least first load data generated corresponding to the display process of the second interface set; and The first electronic device is further configured to respond to a received third test instruction, run the first application to execute a third test case, and generate a third operation log, wherein the third test instruction is used to instruct a load test on the display process of the third interface set, each frame interface in the third interface set corresponds to each frame interface in the first interface set, each frame interface in the third interface set has a corresponding added first display effect, and the first display effect is configured with a second attribute parameter, the second attribute parameter being different from the first attribute parameter, and the third operation log includes at least the second load data generated corresponding to the display process of the third interface set; The second electronic device is configured to extract the basic load data from first formatted data converted from the first runtime log based on application tags corresponding to the first application and interface tags corresponding to each frame interface; and to extract the first load data from second formatted data converted from the second runtime log based on the application tags, the interface tags, and a first identification parameter corresponding to the first display effect; and to extract the second load data from third formatted data converted from the third runtime log based on the application tags, the interface tags, and the first identification parameter corresponding to the first display effect; and, The second electronic device is configured to determine a first load increment corresponding to the first display effect based on the difference between the first load data and the base load data, wherein the first load increment corresponds to the first attribute parameter; and to determine a second load increment corresponding to the first display effect based on the difference between the second load data and the base load data, wherein the second load increment corresponds to the second attribute parameter, wherein the second load increment is different from the first load increment.

27. The system according to claim 26, characterized in that, The first electronic device is further configured to respond to a received fourth test instruction, run the first application to execute a fourth test case, and generate a fourth operation log, wherein the fourth test instruction is used to instruct a load test on the display process of a fourth interface set, each frame interface in the fourth interface set corresponds to each frame interface in the first interface set, and each frame interface in the fourth interface set has a corresponding added second display effect, the second display effect being different from the first display effect; the fourth operation log includes at least third load data corresponding to the display process of the fourth interface set; and... The second electronic device is configured to extract the third load data from the fourth formatted data converted from the fourth operation log based on the application tag, the interface tag, and the second identification parameter corresponding to the second display effect; and to determine the third load increment corresponding to the second display effect based on the difference between the third load data and the basic load data.

28. An electronic device, characterized in that, include: One or more processors; One or more memories; the one or more memories storing one or more programs, which, when executed by the one or more processors, cause the electronic device to perform the interface processing method of any one of claims 1 to 9, 10 to 22, or 23 to 25.

29. A computer-readable storage medium, characterized in that, The readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the interface processing method according to any one of claims 1 to 9, 10 to 22, or 23 to 25.

30. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the interface processing method according to any one of claims 1 to 9, 10 to 22, or 23 to 25.

Images