Performance test method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a performance testing method and device, equipment and a storage medium, and relates to the technical field of computers. The method comprises the following steps: displaying a first user interface, wherein the first user interface displays at least one first bullet screen; in response to a recording operation for the at least one first bullet screen, a first bullet screen file is obtained, and the first bullet screen file is used for recording the at least one first bullet screen displayed in the first user interface; displaying at least one second bullet screen on a second user interface based on the first bullet screen file, wherein the first application program and the second application program are different application programs; and detecting the performance of the second application program. Through the method, the scene for performing performance detection on the second application program is the same as the scene of the first application program, the obtained performance detection result can better indicate the performance difference between the second application program and the first application program, and the optimization effect on the second application program based on the performance detection result is better.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a performance testing method, apparatus, device, and storage medium. Background Technology

[0002] Performance testing refers to testing the performance of a target application in accordance with its requirements and user needs. During performance testing, another application is typically used as a comparison to assess the target application's performance and allow for appropriate adjustments.

[0003] In related technologies, performance tests are typically performed separately on the application used for comparison and the target application. The performance of the two is then compared to obtain the results, which are then used to optimize the target application. However, in this process, it is difficult to achieve consistency in the test scenarios for the two applications, leading to unsatisfactory optimization results. Summary of the Invention

[0004] This application provides a performance testing method, apparatus, device, and storage medium. The technical solutions provided by this application are as follows:

[0005] According to one aspect of the embodiments of this application, a performance testing method is provided, the method comprising:

[0006] The first user interface is displayed, which is the user interface of the first application, and the first user interface displays at least one first bullet screen.

[0007] In response to the recording operation for the at least one first bullet comment, a first bullet comment file is obtained, the first bullet comment file being used to record the at least one first bullet comment displayed in the first user interface;

[0008] At least one second comment is displayed on the second user interface based on the first comment file. The second user interface is the user interface of the second application, and the first application and the second application are different applications.

[0009] Test the performance of the second application.

[0010] According to one aspect of the embodiments of this application, a performance testing apparatus is provided, the apparatus comprising:

[0011] A first display module is used to display a first user interface, which is the user interface of a first application, and the first user interface displays at least one first bullet screen.

[0012] The module is configured to obtain a first bullet screen file in response to a recording operation for the at least one first bullet screen, wherein the first bullet screen file is used to record the at least one first bullet screen displayed in the first user interface;

[0013] The second display module is used to display at least one second bullet comment based on the first bullet comment file in the second user interface, wherein the second user interface is the user interface of the second application, and the first application and the second application are different applications;

[0014] The detection module is used to detect the performance of the second application.

[0015] According to one aspect of the embodiments of this application, a terminal device is provided, the terminal device including a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the above-described performance testing method.

[0016] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein a computer program is stored in the computer-readable storage medium, the computer program being loaded and executed by a processor to implement the above-described performance testing method.

[0017] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including a computer program, the computer program being loaded and executed by a processor to implement the above-described performance testing method.

[0018] The technical solutions provided in this application embodiment may have the following beneficial effects:

[0019] By recording the first bullet comment displayed on the user interface of a first application, a first bullet comment file is obtained. A second bullet comment is then displayed on the user interface of a second application based on this first bullet comment file, thereby testing the performance of the second application during the display of the second bullet comment. By controlling the display of the second bullet comment using the first bullet comment file, the scenario for performance testing of the second application is the same as that of the first application. The resulting performance test results are more indicative of the performance differences between the two applications, leading to better optimization of the second application based on these results. Attached Figure Description

[0020] Figure 1 This is an architecture diagram of a performance testing system provided in one embodiment of this application;

[0021] Figure 2 This is a flowchart of a performance testing method provided in one embodiment of this application;

[0022] Figure 3 This is a flowchart of a performance testing method provided in another embodiment of this application;

[0023] Figure 4 This is a flowchart of a performance testing method provided in another embodiment of this application;

[0024] Figure 5 This is a flowchart of a performance testing method provided in another embodiment of this application;

[0025] Figure 6 This is a flowchart of a performance testing method provided in another embodiment of this application;

[0026] Figure 7 This is a schematic diagram of a third user interface provided in one embodiment of this application;

[0027] Figure 8 This is a schematic diagram of the main interface of a second application provided in one embodiment of this application;

[0028] Figure 9 This is a schematic diagram of a fourth user interface provided in one embodiment of this application;

[0029] Figure 10 This is a flowchart of a performance testing method provided in another embodiment of this application;

[0030] Figure 11 This is a flowchart of a performance testing method provided in another embodiment of this application;

[0031] Figure 12 This is a schematic diagram illustrating a performance problem class provided in one embodiment of this application;

[0032] Figure 13 This is a schematic diagram illustrating a performance problem analysis provided in one embodiment of this application;

[0033] Figure 14 This is a schematic diagram of the title of a problem feedback form provided in one embodiment of this application;

[0034] Figure 15 This is a schematic diagram of the first prompt information provided in one embodiment of this application;

[0035] Figure 16 This is a schematic diagram of performance test parameters provided in one embodiment of this application;

[0036] Figure 17 This is a graph showing the performance metrics of a first application provided in one embodiment of this application;

[0037] Figure 18 This is a graph showing the performance metrics of a second application provided in one embodiment of this application;

[0038] Figure 19 This is a block diagram of a performance testing apparatus provided in one embodiment of this application;

[0039] Figure 20 This is a block diagram of a performance testing apparatus provided in another embodiment of this application;

[0040] Figure 21 This is a block diagram of a terminal device provided in one embodiment of this application. Detailed Implementation

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

[0042] Please refer to Figure 1 This diagram illustrates a performance testing system according to an embodiment of this application. The performance testing system can be implemented as a system architecture for a performance testing method. The performance testing system may include: a terminal device 10.

[0043] Terminal device 10 includes, but is not limited to, mobile phones, computers, smart home appliances, in-vehicle terminals, PCs (Personal Computers), tablets, wearable devices, VR (Virtual Reality) devices, AR (Augmented Reality) devices, MR (Mixed Reality) devices, and other electronic devices. Terminal device 10 can install and run a client for a first application and a client for a second application. The first application can provide a bullet screen display function for the user, and the second application can also provide a bullet screen display function for the user. For example, the first application can be a live streaming application, a video application, a social application, etc., and this application is not limited in this regard. For example, the second application can be a live streaming application, a video application, a social application, etc., and this application is not limited in this regard. Furthermore, this application does not limit the form of the first and second applications, including but not limited to Apps (Applications), mini-programs, etc., installed on terminal device 10, and can also be in the form of web pages.

[0044] The terminal device 10 has a client application of a first application installed. In some embodiments, the first application provides a bullet screen display function. In some embodiments, the user interface of the first application displays at least one first bullet screen.

[0045] The terminal device 10 also has a client application for the second application installed. In some embodiments, the second application provides a bullet screen display function. In some embodiments, at least one second bullet screen is displayed in the user interface of the second application.

[0046] In some embodiments, the terminal device 10 displays a first user interface, which is the user interface of a first application, and displays at least one first bullet comment; in response to a recording operation for at least one first bullet comment, a first bullet comment file is obtained, which is used to record at least one first bullet comment displayed in the first user interface; based on the first bullet comment file, at least one second bullet comment is displayed in a second user interface, which is the user interface of a second application, and the first application and the second application are different applications; and the performance of the second application is detected.

[0047] In some embodiments, the first application and the second application are applications of the same type. For example, both the first application and the second application are video applications. For example, both the first application and the second application are live streaming applications.

[0048] The performance testing method provided in this application embodiment can be executed by a terminal device 10.

[0049] Please refer to Figure 2 The diagram illustrates a flowchart of a performance testing method provided in one embodiment of this application, which is executed by a terminal device. The method includes at least one of steps 210 to 240.

[0050] Step 210: Display the first user interface, which is the user interface of the first application, and the first user interface displays at least one first bullet screen.

[0051] In some embodiments, the first user interface is the user interface of a first application. In some embodiments, the first user interface can be any user interface of the first application. For example, the first application is a live streaming application, and the first user interface can be the user interface of any live streaming room.

[0052] In some embodiments, at least one first bullet comment is displayed in the first user interface. In some embodiments, the first bullet comment may include multiple bullet comment types. In some embodiments, bullet comment types may be classified in different ways. For example, based on the display effect of the first bullet comment, bullet comment types may include text bullet comments and special effects bullet comments. For example, based on the display position of the first bullet comment, bullet comment types may include banner bullet comments, full-screen bullet comments, and sunken bullet comments, etc. Bullet comments refer to the text, emoticons, and gifts sent by users after watching exciting video content. These can be seen by other users and are distinguished as text bullet comments, emoticon bullet comments, and special effects bullet comments. Performance refers to whether the app will lag or become overheated during user operation, which affects the product's user experience.

[0053] In some embodiments, the first user interface may also display related controls such as the first bullet screen sending control and the first bullet screen control control.

[0054] Step 220: In response to the recording operation for at least one first comment, a first comment file is obtained, which is used to record at least one first comment displayed in the first user interface.

[0055] In some embodiments, in response to a recording operation for at least one first comment, at least one first comment is written to a first comment file.

[0056] In some embodiments, the first bullet comment file stores all the information of at least one first bullet comment. For example, the first bullet comment file stores the user account identifier, user account avatar, first bullet comment identifier, first bullet comment content, first bullet comment display effect, first bullet comment display frequency, and first bullet comment type, etc., corresponding to the first bullet comment.

[0057] In some embodiments, the first bullet comment file stores only partial information of at least one first bullet comment. For example, the first bullet comment file stores at least one of the following information: the user account identifier corresponding to the first bullet comment, the user account avatar, the first bullet comment identifier, the first bullet comment content, the first bullet comment display effect, the display frequency of the first bullet comment, and the bullet comment type of the first bullet comment.

[0058] In some embodiments, the first bullet comment file stores only the display frequency of at least one first bullet comment. In some embodiments, the first bullet comment file may store the display frequencies corresponding to multiple types of first bullet comments.

[0059] In some embodiments, at least one rendering instruction for a first bullet comment is received, and in response to a recording operation for at least one first bullet comment, the at least one first bullet comment included in the rendering instruction is stored in a first bullet comment file. In some embodiments, the rendering instruction for at least one first bullet comment comes from a backend server that provides services to a first application.

[0060] Step 230: Display at least one second bullet comment based on the first bullet comment file on the second user interface. The second user interface is the user interface of the second application, and the first application and the second application are different applications.

[0061] In some embodiments, at least one second comment is displayed in a second user interface based on a first comment file. The at least one second comment may be the same as or different from the at least one first comment.

[0062] In some embodiments, based on a first bullet comment file, at least one second bullet comment displayed in a second user interface is completely identical to at least one first bullet comment displayed in a first user interface. For example, the display frequency, display effect, and content of the second bullet comment are all the same as the first bullet comment.

[0063] In some embodiments, based on a first bullet comment file, at least one second bullet comment displayed in the second user interface is partially identical to at least one first bullet comment displayed in the first user interface. For example, the display frequency of the second bullet comment is the same as that of the first bullet comment, but the content of the second bullet comment differs from the content of the first bullet comment.

[0064] In some embodiments, the first application and the second application can be two completely different applications. In some embodiments, the first application and the second application can be different versions of the same application. In some embodiments, the first application and the second application can also be the same version of the same application running on different terminal devices. Specifically, how the first application and the second application are configured can be referred to the application scenarios of performance testing methods.

[0065] Step 240: Detect the performance of the second application.

[0066] In some embodiments, the performance of the second application is monitored. For example, the performance of the second application is continuously monitored during the display of the second bullet screen.

[0067] In some embodiments, during a first time period, at least one performance metric corresponding to the second application is detected, the performance metric being used to quantify the performance of the application.

[0068] In some embodiments, the first time period includes the period during which the second bullet screen is displayed in the user interface of the second application.

[0069] In some embodiments, performance metrics include at least one of the following: temperature of the terminal device, memory usage, CPU (Central Processing Unit) usage, FPS (Frames Per Second), power consumption of the terminal device, and GPU (Graphics Processing Unit) usage.

[0070] In some embodiments, at least one performance metric corresponding to the first application within a first time period is obtained; at least one performance metric corresponding to the second application is compared with at least one performance metric corresponding to the first application to obtain a first comparison result, the first comparison result being used to describe the performance difference between the second application and the first application; the second application is optimized based on the first comparison result.

[0071] In some embodiments, the performance of the second application is detected by a third application. In some embodiments, the third application may be an application independent of the second application, or it may be a plugin integrated into the second application; this application does not limit this.

[0072] In some embodiments, the above-described performance testing method can assist developers in testing and optimizing the performance of the second application before it is launched, so as to ensure that the performance of the launched second application meets the user's needs.

[0073] In some embodiments, the above-described performance testing method can also assist backend maintenance personnel in testing and optimizing the performance of the second application after it is launched, so as to resolve the performance problems of the second application as soon as possible.

[0074] In some embodiments, the method further includes at least one of steps 250 to 270 (not shown in the figures).

[0075] Step 250: Obtain the performance of the first application.

[0076] Step 260: Compare the performance of the first application with that of the second application to obtain a comparison result. The comparison result is used to describe the performance difference between the second application and the first application.

[0077] Step 270: Optimize the second application based on the comparison results.

[0078] In some embodiments, the performance of the first application may be detected using the same method as that used for the second application.

[0079] In some embodiments, the performance of the first application is detected during the recording of at least one first comment. In some embodiments, the recording operation of at least one first comment is the same as the at least one first comment displayed by the first application during the performance detection of the first application.

[0080] The technical solution provided in this application involves recording a first bullet screen displayed on the user interface of a first application to obtain a first bullet screen file. A second bullet screen is then displayed on the user interface of a second application based on this first bullet screen file, thereby testing the performance of the second application during the display of the second bullet screen. By controlling the display of the second bullet screen using the first bullet screen file, the scenario for performance testing of the second application is the same as that of the first application. This results in performance testing results that better illustrate the performance differences between the second and first applications, leading to better optimization of the second application based on these results.

[0081] In some embodiments, the technical solutions provided in this application can be applied to various performance testing scenarios. For example, they can be applied to testing existing applications, version iteration scenarios, or real-time maintenance scenarios. The following will briefly describe these application scenarios.

[0082] 1. Existing application test scenarios

[0083] In some embodiments, before the second application is launched, the performance differences between the second application and the existing application can be compared. The second application can be optimized based on the performance comparison results to avoid the second application having a worse performance experience than the existing application, which could lead to user churn.

[0084] In some embodiments, an existing application refers to another application that competes with the second application. In this scenario embodiment, the first application is an existing application, and the existing application and the second application are different applications.

[0085] Please refer to Figure 3 The diagram illustrates a flowchart of a performance testing method provided in another embodiment of this application. This method may include at least one of the following steps 310 to 340.

[0086] Step 310: Display the first user interface, which is the user interface of an existing application, and the first user interface displays at least one first bullet screen.

[0087] Step 320: In response to the recording operation for at least one first comment, a first comment file is obtained, which is used to record at least one first comment displayed in the first user interface.

[0088] Step 330: Display at least one second bullet comment based on the first bullet comment file on the second user interface. The second user interface is the user interface of the second application, and the existing application and the second application are different applications.

[0089] Step 340: Detect the performance of the second application.

[0090] In some embodiments, at least one performance metric corresponding to an existing application within a first time period is obtained; at least one performance metric corresponding to a second application is compared with at least one performance metric corresponding to an existing application to obtain a first comparison result, the first comparison result being used to describe the performance difference between the second application and the existing application; the second application is optimized based on the first comparison result.

[0091] In some embodiments, at least one performance metric corresponding to the existing application in the first time period is obtained by testing the existing application in the first time period.

[0092] 2. Version update scenario

[0093] In some embodiments, if the second application needs to be updated, before the new version is launched, the performance difference between the new version and the historical version can be compared. The new version can be optimized according to the performance comparison results between the two to avoid poor performance experience of the new version and loss of users.

[0094] In this scenario embodiment, the first application is a historical version of the second application, and for ease of description, it will be referred to as the historical version in the following embodiments; the second application is a new version of the application, and for ease of description, it will be referred to as the new version in the following embodiments.

[0095] Please refer to Figure 4 The diagram illustrates a flowchart of a performance testing method provided in another embodiment of this application. This method may include at least one of the following steps 410 to 440.

[0096] Step 410: Display the historical user interface. The historical user interface is the user interface of the previous version, and the historical user interface displays at least one historical comment.

[0097] Step 420: In response to the recording operation for at least one historical bullet comment, a historical bullet comment file is obtained. The historical bullet comment file is used to record at least one historical bullet comment displayed in the historical user interface.

[0098] Step 430: Based on the historical bullet comment file, display at least one new version bullet comment in the new version user interface. The new version user interface is the new version user interface.

[0099] Step 440: Test the performance of the new version.

[0100] In some embodiments, at least one performance metric corresponding to a historical version of the second application is obtained; the at least one performance metric corresponding to the second application is compared with the at least one performance metric corresponding to the historical version to obtain a second comparison result, the second comparison result being used to describe the performance difference between the second application and the historical version of the second application; the second application is optimized based on the second comparison result.

[0101] In some embodiments, optimizing the second application based on the performance of historical versions of the second application can prevent the performance of the second application from deteriorating after new versions of the second application add new functional modules or change the display style.

[0102] Table 1: Second Comparison Results

[0103]

[0104]

[0105] For example, the second comparison results obtained by comparing at least one performance metric corresponding to the second application with at least one performance metric corresponding to the historical version are shown in Table 1.

[0106] By maintaining performance metrics data for each version, we can intuitively see the performance changes of the second application in different versions and quickly identify which version's added requirements caused the performance changes.

[0107] 3. Real-time maintenance scenario

[0108] In some embodiments, if users report performance issues with the second application after it goes live, backend maintenance personnel need to perform performance maintenance on the second application. The performance testing method provided in this application embodiment can be used to quickly locate the performance problem and perform precise optimization. For example, a scenario triggering user feedback is used as the scenario for recording at least one first comment. In this case, the first application is the application before maintenance, and the second application is the application after maintenance. Comparing the performance of the application before maintenance with the performance standard allows for precise location of the performance problem. Comparing the performance of the application after maintenance with the performance standard determines whether the performance problem has been resolved. Here, the performance standard refers to the performance standard by which the application meets user needs. In some embodiments, the performance standard can be pre-set. In some embodiments, the performance standards for different applications can be the same or different.

[0109] In this scenario embodiment, the first application is the application before maintenance, and the second application is the application after maintenance.

[0110] Please refer to Figure 5 The diagram illustrates a flowchart of a performance testing method provided in another embodiment of this application. This method may include at least one of the following steps 510 to 540.

[0111] Step 510: Display the user interface before maintenance. The user interface before maintenance is the same as the user interface of the previous version before maintenance. The user interface before maintenance displays at least one bullet screen from before maintenance.

[0112] Step 520: In response to the recording operation for at least one pre-maintenance bullet comment, obtain the pre-maintenance bullet comment file, which is used to record at least one pre-maintenance bullet comment displayed in the pre-maintenance user interface.

[0113] Step 530: Based on the bullet screen file before maintenance, display at least one bullet screen after maintenance on the user interface after maintenance. The user interface after maintenance is the user interface of the application after maintenance. The version before maintenance and the application after maintenance are different applications.

[0114] Step 540: Check the performance of the maintained application.

[0115] In some embodiments, at least one performance metric of the application before maintenance is obtained within a first time period; the at least one performance metric of the application after maintenance is compared with the at least one performance metric of the application before maintenance to obtain a first comparison result, the first comparison result being used to describe the performance difference between the application after maintenance and the application before maintenance; and the second application is optimized based on the first comparison result.

[0116] In some embodiments, at least one performance metric of the application before maintenance during a first time period is obtained by testing the application before maintenance during the first time period.

[0117] In some embodiments, the technical solutions provided in this application can also be applied to other scenarios requiring performance testing, and this application does not limit this application. In some embodiments, the technical solutions provided in this application can also be applied to scenarios involving bullet screen compatibility processing. For example, a first bullet screen in a first scenario is recorded to obtain a first bullet screen file, and the first bullet screen is replayed in a second scenario based on the first bullet screen file. The first scenario and the second scenario are different scenarios. For example, the first scenario is in portrait mode and the second scenario is in landscape mode, or the first scenario and the second scenario are display states on terminal devices of different sizes.

[0118] In some embodiments, at least one second bullet comment is displayed in a second user interface based on a first bullet comment file. The at least one second bullet comment may be exactly the same as or partially the same as the at least one first bullet comment, and this application does not limit this.

[0119] In some embodiments, the first bullet comment file stores all or part of the information of at least one first bullet comment. In some embodiments, the format of the first bullet comment file is pre-set.

[0120] For example, this application provides a possible first bullet screen file format.

[0121] {"uid":112301891*"msgid"1698938353460820815_11634533_112301891_2887060856_1","nickName":"sob7y999","content":{\"id\":520040001,\"num\":1,\"Price\":1}","tm":"1698938353460823335","bulletChatType":5,"programID":"111634533_11634533_1698937227","avatar":"6.png","userName":"sob7y999","roles":[{"roleNam e":"follower","roleType":"AUTH_ROLE_TYPE_CHANNEL_FOLLOWER"}],"ext":{"space_fans_ex":"{\"l\":\"1\",\"s\":\"0\"},"normal_emote_enabled":"gift.speilffectID"."10000050","git_price_info":"{\"currencyTypel\":1,\"number\":1}","local_seq":"2d7120-793-1e-a2a1-5feed01c1b9d","ace_bullet":"{\"show_bullet\":fase,\

[0122] "status\":false,\"user_type\":0}"}}

[0123] Wherein, uid is the user account ID (Identity Document), msgid is the bullet comment ID, nickName is the user account nickname, content is the bullet comment content, num is the number of bullet comments, tm is the bullet comment display time, bulletChatType is the bullet comment display effect, programID is the bullet comment display effect ID, avatar is the user account avatar, userName is the user account nickname, roles are the user account roles (e.g., whether they are fans), space_fans_ex is the user account special title (e.g., whether they are special fans, whether they have joined a fan club, etc.), normal_emote_enabled is whether the bullet comment contains emoticons, gift.speilffectID is the gift ID, and git_price_info is the gift price information.

[0124] In some embodiments, the first bullet screen file is stored in the terminal device as a .json file.

[0125] The technical solution of this application embodiment will be introduced next, taking at least one second bullet comment that is partially the same as at least one first bullet comment as an example.

[0126] In some embodiments, step 230 can be implemented as at least one of steps 231 to 232.

[0127] Step 231: Based on the first bullet screen file, obtain the first display frequency, which is the display frequency of the first bullet screen recorded in the first bullet screen file.

[0128] In some embodiments, since the first bullet screen file records information of at least one first bullet screen, the first display frequency can be determined based on the first bullet screen file.

[0129] In some embodiments, the first display frequency is the number of first bullet comments displayed per unit time. In some embodiments, the unit time can be n seconds, n minutes, n hours, etc., and this application does not limit it. Wherein, n is a positive number.

[0130] In some embodiments, the first display frequency can be the display time of each bullet comment in the user interface. For example, each first bullet comment is displayed in the first user interface for 2 seconds.

[0131] Step 232: Based on the first display frequency, display at least one second bullet screen on the second user interface.

[0132] In some embodiments, at least one second bullet comment is displayed on the second user interface at a first display frequency. In some embodiments, the second display frequency is the same as the first display frequency, and the second display frequency is the frequency at which the second bullet comment is displayed on the second user interface.

[0133] In some embodiments, a second bullet screen file is constructed based on a first display frequency. The second bullet screen file is used to record at least one second bullet screen displayed in the second user interface. Based on the second bullet screen file, at least one second bullet screen is displayed in the second user interface. The at least one second bullet screen is displayed in the second user interface at a second display frequency, which is the same as the first display frequency.

[0134] In some embodiments, the format of the second bullet comment file may be the same as or different from that of the first bullet comment file. For example, the format of the first bullet comment file is set for the first application, and the format of the second bullet comment file is set for the second application.

[0135] In some embodiments, the second bullet comments recorded in the second bullet comment file may be exactly the same as, partially the same as, or completely different from the first bullet comments recorded in the first bullet comment file. This application does not limit this.

[0136] In some embodiments, to save time in constructing the second bullet comment file, the first bullet comment file can be rewritten into a second bullet comment file according to the format of the second bullet comment file. In this way, the test environment constructed by displaying the second bullet comment in the second user interface based on the second bullet comment file is the same as the environment in the first user interface where the first bullet comment is displayed.

[0137] In some embodiments, to reduce the difficulty of constructing the second bullet comment file, the second bullet comments recorded in the second bullet comment file can be set to have the same content, with only the second display frequency being the same as the first display frequency. Since the amount of text contained in the bullet comments has little impact on the performance of the application, it is not necessary for the second bullet comments to be exactly the same as the first bullet comments.

[0138] In some embodiments, the bullet comments include multiple types, with different display frequencies for each type. In some embodiments, different types of bullet comments also have different performance requirements for the application; therefore, the type of bullet comment can be considered when constructing the second bullet comment file. For example, the bullet comment type may include at least one of the following: having display effects, not having display effects, content consisting only of text, content consisting of both text and emoticons, and content consisting only of emoticons.

[0139] Taking the types of bullet comments as examples, including text bullet comments that only contain text and gift bullet comments with display effects, the frequency of text bullet comments is one every 3 seconds, and the frequency of gift bullet comments is one every 5 seconds.

[0140] In some embodiments, based on a first bullet screen file, a first display frequency corresponding to a first bullet screen of multiple bullet screen types is obtained; based on the first display frequency corresponding to a first bullet screen of multiple bullet screen types, a second bullet screen of multiple bullet screen types is displayed on a second user interface.

[0141] In some embodiments, since different types of bullet comments have different performance requirements—for example, bullet comments with display effects have higher performance requirements, while bullet comments without display effects have relatively lower performance requirements—the two types of bullet comments can be distinguished, and their corresponding first display frequencies can be determined separately. Then, based on the first display frequencies corresponding to the first bullet comments of different types, a second bullet comment file is constructed. The second bullet comment file includes second bullet comments of multiple types. The second display frequency corresponding to the second bullet comments of the first type is the same as the first display frequency corresponding to the first bullet comments of the first type. Based on the second bullet comment file, the second bullet comments of multiple types are displayed in the second user interface.

[0142] In some embodiments, at least one second bullet screen can be displayed directly in the second user interface based on the first bullet screen file, without the need to analyze the first bullet screen file or construct the second bullet screen file based on the first bullet screen file. This solution is simpler, but requires both the first application and the second application to be compatible with the format of the first bullet screen file.

[0143] Please refer to Figure 6 The diagram illustrates a flowchart of a performance testing method provided in another embodiment of this application, which can be applied to live streaming applications.

[0144] like Figure 6 As shown, the system first enters a popular live stream room (the first user interface of the first application) and records the comments in the live stream room to obtain a first comment file. Based on the first comment file, a second comment file is constructed, and the second comments included in the second comment file are replayed in the target live stream room (the second user interface of the second application). The second comments are then rendered and displayed, and the performance of the second application is tested.

[0145] In some embodiments, the above process relies on QTA (Quick Test for Android) for execution. In some embodiments, the user interface mentioned in this application may provide at least one of the following functional controls: a send bullet screen control, a send emoticon control, an effect selection control, and a send gift control.

[0146] In some embodiments, both the first and second bullet comment files are generated locally on the terminal device. In some embodiments, the client of the second application controls the rendering of the second bullet comment file generated locally on the terminal device, at which point the content on the terminal device begins to change.

[0147] Using the above method, the second bullet comment file is constructed locally on the terminal device, eliminating the need for server processing, modification of the online database, or access to a backend server. The second bullet comment can also be customized and automatically generated, allowing for diverse formats and control over its frequency. This eliminates the need for manual setup, writing, and sending of the second bullet comment, avoiding unnecessary operations and potential contamination during the process.

[0148] To facilitate operation, this application embodiment also provides a third user interface adapted to the performance testing method. For example, as shown... Figure 7 As shown, the third user interface includes a first control 710, a second control 720, a third control 730, and a fourth control 740. The first control is used to determine the first user interface of the first application, the second control is used to record at least one first bullet comment in the first user interface and generate a first bullet comment file, the third control is used to display at least one second bullet comment in the second user interface based on the first bullet comment file, and the fourth control is used to detect the performance of the second application.

[0149] In some embodiments, the third user interface may be the user interface of the second application. In some embodiments, the third user interface is only accessible to the developers or backend maintainers of the second application, and is inaccessible to the actual users of the second application. For example, the main page of the second application accessible to the actual users of the second application is as follows: Figure 8 As shown, at least one video module 810-820 is displayed.

[0150] In some embodiments, the second user interface may be determined by the tester during testing. For example, in response to an operation on the third control 730, the following is displayed: Figure 9The fourth user interface is shown. In some embodiments, the fourth user interface and the third user interface can be two different user interfaces. In some embodiments, the fourth user interface can also be a sub-interface that floats on the third user interface. In some embodiments, the fourth user interface includes a fifth control 910, a sixth control 920, a seventh control 930, and an eighth control 940. The fifth control 910 is used to jump to the default user interface, using the default user interface as the second user interface, for example, directly jumping to the live stream room with the most feedback and displaying the user interface of that live stream room. The sixth control 920 is used to customize the second user interface to which the user will jump. The seventh control 930 is used to confirm the jump to the second user interface, and the eighth control 940 is used to close the fourth user interface.

[0151] In some embodiments, the first user interface may be determined by the tester during the testing process. In some embodiments, the process of determining the first user interface is similar to the process of determining the second user interface, and will not be described in detail here.

[0152] Using the methods described above, testers can conduct the testing process more conveniently, and the operation is simpler and easier.

[0153] In some embodiments, in addition to performance testing of the second application, the technical solutions provided in this application can also assist the maintenance personnel of the second application in quickly locating problems reported by users.

[0154] Please refer to Figure 10 The diagram illustrates a flowchart of a performance testing method provided in another embodiment of this application.

[0155] In some embodiments, the method further includes at least one of steps 1 to 3 below.

[0156] Step 1: Obtain at least one issue feedback form, which describes a performance issue that occurred in the second application.

[0157] In some embodiments, the issue feedback form is generated from an issue feedback questionnaire completed by a user or developer. In some embodiments, the issue feedback form includes a description by the user or developer of a performance problem occurring in the second application. For example, Figure 11 A flowchart of a performance testing method provided in another embodiment of this application is shown.

[0158] In some embodiments, the problem feedback form has a pre-defined format, and users fill out the problem feedback form according to the pre-defined format.

[0159] In some embodiments, performance issues may include at least one of the following: TB (Terabyte, hard disk capacity) issues, risk control issues, and login issues.

[0160] Step 2: Cluster at least one issue feedback form to obtain at least one performance issue class. Each performance issue class corresponds to one type of performance issue and includes at least one issue feedback form.

[0161] In some embodiments, the problem descriptions included in at least one problem feedback form are obtained; a keyword library is used to search the problem descriptions included in at least one problem feedback form, the keyword library including at least one keyword, each keyword corresponding to a performance problem class; in response to the target keyword being retrieved in the problem description, the problem feedback form is assigned to the performance problem class corresponding to the target keyword.

[0162] In some embodiments, the problem description is used to describe performance issues of the second application. In some embodiments, the keyword library is pre-defined by testers. In some embodiments, the keyword library includes at least one keyword, each keyword corresponding to a performance problem category. Keywords can be used to describe performance problems, such as lag or overheating, or to describe functional modules experiencing performance issues, such as a black screen or malfunction of functional module xx. In some embodiments, testers can maintain the keyword library. For example, if a new functional module is added to the second application, keywords related to that new functional module can be added to the keyword library.

[0163] In some embodiments, if a keyword from a keyword library can be retrieved in the problem description, the problem feedback form corresponding to the problem description is assigned to the performance problem class corresponding to the retrieved keyword. In some embodiments, multiple keywords can be retrieved in the problem description corresponding to a problem feedback form. In this case, the problem feedback form can be included in the performance problem class corresponding to each of the multiple keywords. For example, as shown... Figure 12 As shown, the keywords "elixir" and "redeem" were found in the problem description. Therefore, the problem feedback form was classified into the performance problem categories corresponding to "elixir" and "redeem" respectively.

[0164] In some embodiments, if no keywords from the keyword library are found in the problem description, the problem feedback form is discarded, or it can also be referred to as ignoring the problem feedback form.

[0165] In some embodiments, performance issues reported in the performance feedback form can be analyzed based on performance issue class to determine performance issues in the second application. For example, Figure 13 An example graph showing the results of a performance problem analysis is provided. Figure 13 The distribution of performance issues in the second application can be clearly seen in the data.

[0166] In some embodiments, the language used in the feedback form may differ depending on the target audience of the second application. For example, the language used in the feedback form may be Chinese, English, Spanish, Japanese, Korean, etc.

[0167] In some embodiments, at least one issue feedback form includes an original issue description; if the original issue description is in a first language, the original issue description is determined as an issue description; if the original issue description is in a second language, the original issue description is translated into the first language and then determined as an issue description.

[0168] In some embodiments, the first language may be any of the following languages: Chinese, English, Spanish, Japanese, or Korean.

[0169] In some embodiments, after translating from a second language to a first language, semantic changes may occur, or multiple translations of a single word may result in failure to match keywords in the keyword database. In such cases, one approach is to ignore these feedback forms, thus reducing the processing difficulty. Another approach is to train a translator more suited to the second application based on the feedback forms, thereby improving translation accuracy.

[0170] In some embodiments, to more easily distinguish the performance issue category to which the issue feedback form belongs, keywords retrieved from the issue feedback form can be added to the title of the issue feedback form, or the issue feedback form can be stored in the storage path corresponding to the target keywords.

[0171] In some embodiments, in response to retrieving target keywords from the problem description, the target keywords are added to the title of the problem feedback form. For example, such as... Figure 14 As shown, the keywords elixir and redeem were found in the problem description, so elixir and redeem will be added to the title of the problem feedback form.

[0172] In some embodiments, in response to finding a target keyword in the problem description, the problem feedback form is stored in the storage path corresponding to the target keyword. In some embodiments, one keyword corresponds to one storage path. In some embodiments, the problem feedback form can be copied to the storage path corresponding to the target keyword, or the problem feedback form can be transferred to the storage path corresponding to the target keyword for storage.

[0173] In some embodiments, to avoid inaccurate problem descriptions, the second application can provide keyword tags to the user.

[0174] In some embodiments, the problem feedback interface of the second application displays at least one keyword tag, which is used to describe the performance problem.

[0175] In some embodiments, at least one issue feedback form is identified as having a corresponding keyword tag; the issue feedback form is then classified into the performance issue category corresponding to the keyword tag.

[0176] In some embodiments, after determining the performance issue class corresponding to the issue feedback form based on keyword tags, the issue description of the issue feedback form can be retrieved based on the keyword library. This can avoid the situation where multiple performance issues are reported in an issue feedback form but only some keyword tags are selected.

[0177] Step 3: If the increase in the number of feedback orders for the first performance problem class in at least one performance problem class is greater than or equal to the first threshold in the second time period, then the first prompt message is displayed. The first prompt message is used to indicate that the first performance problem needs to be optimized. The first performance problem is the performance problem corresponding to the first performance problem class.

[0178] In some embodiments, the first threshold is preset. In some embodiments, the first threshold may be set by the developer based on prior experience.

[0179] In some embodiments, the second time period is also preset. For example, the second time period is 7 days.

[0180] In some embodiments, the first prompt message is used to indicate a first performance issue that needs to be optimized. For example, such as... Figure 15 As shown, the first prompt message may display information related to the first performance problem, a processing control 1510, and an ignore control 1520. The processing control 1510 is used to navigate to a user interface for handling the first performance problem, such as a third user interface. The ignore control 1520 is used to ignore the first performance problem. In some embodiments, the information related to the first performance problem may include at least one of the following: number of feedbacks, keywords, feedback time, and feedback area.

[0181] Using the methods described above, developers can be proactively alerted to performance issues, and relevant personnel can be notified to quickly fix them, effectively avoiding the problem of blank periods after performance issues occur.

[0182] Experimental tests were also conducted on the technical solutions provided in the embodiments of this application. For example, as shown... Figure 16 As shown, each performance metric has a corresponding change curve during the testing process. For example... Figure 17 The image shown is a graph illustrating the performance metrics of the first application. Figure 18 The image shows a graph illustrating the performance metrics of the second application. Figure 17The document also shows the analysis results of the first application's performance metrics (1710). Figure 18 The analysis results of the performance metrics of the second application are shown in Figure 1810. It can be seen that the memory usage of the second application, after being tested and optimized using the above method, is better than that of the first application.

[0183] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0184] Please refer to Figure 19 This diagram illustrates a block diagram of a performance testing apparatus according to an embodiment of this application. The apparatus has the functionality to implement the method example described above; this functionality can be implemented in hardware or by hardware executing corresponding software. The apparatus can be the terminal device described above, or it can be installed within a terminal device. For example... Figure 19 As shown, the device 1900 includes: a first display module 1910, a receiving module 1920, a second display module 1930, and a detection module 1940.

[0185] The first display module 1910 is used to display a first user interface, which is the user interface of the first application, and the first user interface displays at least one first bullet screen.

[0186] The module 1920 is configured to obtain a first bullet screen file in response to a recording operation for the at least one first bullet screen, the first bullet screen file being used to record the at least one first bullet screen displayed in the first user interface.

[0187] The second display module 1930 is used to display at least one second bullet comment on a second user interface based on the first bullet comment file. The second user interface is the user interface of a second application, and the first application and the second application are different applications.

[0188] The detection module 1940 is used to detect the performance of the second application.

[0189] In some embodiments, such as Figure 20 As shown, the second display module 1930 includes an acquisition unit 1931 and a display unit 1932.

[0190] The acquisition unit 1931 is used to acquire a first display frequency based on the first bullet screen file, wherein the first display frequency is the display frequency of the first bullet screen recorded in the first bullet screen file.

[0191] Display unit 1932 is used to display the at least one second bullet screen on the second user interface based on the first display frequency.

[0192] In some embodiments, the display unit 1932 is configured to construct a second bullet screen file based on the first display frequency, the second bullet screen file being used to record the at least one second bullet screen displayed in the second user interface; and to display the at least one second bullet screen in the second user interface based on the second bullet screen file; wherein the at least one second bullet screen is displayed in the second user interface at a second display frequency, the second display frequency being the same as the first display frequency.

[0193] In some embodiments, the bullet comments include multiple bullet comment types, and different bullet comment types correspond to different display frequencies;

[0194] The acquisition unit 1931 is used to acquire, based on the first bullet screen file, the first display frequency corresponding to the first bullet screen of the various bullet screen types respectively;

[0195] Display unit 1932 is used to display second bullet comments of various bullet comment types on the second user interface based on the first display frequency corresponding to the first bullet comments of the various bullet comment types.

[0196] In some embodiments, the detection module 1940 is configured to detect at least one performance metric corresponding to the second application during a first time period, the performance metric being used to quantify the performance of the application.

[0197] In some embodiments, the detection module 1940 is further configured to acquire at least one performance metric corresponding to the first application within a first time period; compare the at least one performance metric corresponding to the second application with the at least one performance metric corresponding to the first application to obtain a first comparison result, wherein the first comparison result is used to describe the performance difference between the second application and the first application; and optimize the second application based on the first comparison result.

[0198] In some embodiments, the detection module 1940 is further configured to obtain at least one performance metric corresponding to a historical version of the second application; compare the at least one performance metric corresponding to the second application with the at least one performance metric corresponding to the historical version to obtain a second comparison result, the second comparison result being used to describe the performance difference between the second application and the historical version of the second application; and optimize the second application based on the second comparison result.

[0199] In some embodiments, such as Figure 20 As shown, the device 2000 also includes a third display module 1950.

[0200] The third display module 1950 is used to obtain at least one issue feedback form, which describes a performance problem occurring in the second application; to cluster the at least one issue feedback form to obtain at least one performance problem class, each performance problem class corresponding to a performance problem, and each performance problem class including at least one issue feedback form; if the increase in the number of issue feedback forms included in the first performance problem class in the at least one performance problem class within a second time period is greater than or equal to a first threshold, then a first prompt message is displayed, which is used to indicate that a first performance problem needs to be optimized, and the first performance problem is the performance problem corresponding to the first performance problem class.

[0201] In some embodiments, the third display module 1950 is configured to obtain the problem descriptions included in the at least one problem feedback form; search the problem descriptions included in the at least one problem feedback form based on a keyword library, wherein the keyword library includes at least one keyword, and each keyword corresponds to a performance problem class; and in response to finding a target keyword in the problem description, classify the problem feedback form into the performance problem class corresponding to the target keyword.

[0202] In some embodiments, the third display module 1950 is configured to obtain the original problem descriptions included in the at least one problem feedback form; if the original problem description is in a first language, then the original problem description is determined as the problem description; if the original problem description is in a second language, then the original problem description is translated into the first language and determined as the problem description.

[0203] In some embodiments, the third display module 1950 is further configured to add the target keyword to the title of the problem feedback form in response to retrieving the target keyword in the problem description.

[0204] In some embodiments, the problem feedback interface of the second application displays at least one keyword tag, which is used to describe performance problems;

[0205] The third display module 1950 is used to determine the keyword tags corresponding to the at least one problem feedback form; and to classify the problem feedback form into the performance problem category corresponding to the keyword tag.

[0206] The technical solution provided in this application involves recording a first bullet screen displayed on the user interface of a first application to obtain a first bullet screen file. A second bullet screen is then displayed on the user interface of a second application based on this first bullet screen file, thereby testing the performance of the second application during the display of the second bullet screen. By controlling the display of the second bullet screen using the first bullet screen file, the scenario for performance testing of the second application is the same as that of the first application. This results in performance testing results that better illustrate the performance differences between the second and first applications, leading to better optimization of the second application based on these results.

[0207] Please refer to Figure 21 This illustration shows a schematic diagram of a terminal device provided in one embodiment of this application. The terminal device can be any electronic device with data computing, processing, and storage functions. This terminal device can be used to implement the performance testing methods provided in the above embodiments. Specifically:

[0208] The terminal device 2100 includes a central processing unit (such as a CPU, GPU, or FPGA) 2101, a system memory 2104 including RAM (Random-Access Memory) 2102 and ROM (Read-Only Memory) 2103, and a system bus 2105 connecting the system memory 2104 and the central processing unit 2101. The terminal device 2100 also includes a basic input / output system 2106 to facilitate information transfer between various devices within the server, and a large-capacity storage device 2107 for storing the operating system 2113, application programs 2114, and other program modules 2115.

[0209] In some embodiments, the basic input / output system 2106 includes a display 2108 for displaying information and an input device 2116 for user input, such as a mouse or keyboard. Both the display 2108 and the input device 2116 are connected to the central processing unit 2101 via an input / output controller 2110 connected to the system bus 2105. The basic input / output system 2106 may also include the input / output controller 2110 for receiving and processing input from multiple other devices such as a keyboard, mouse, or electronic stylus. Similarly, the input / output controller 2110 also provides output to a display screen, printer, or other types of output devices.

[0210] The mass storage device 2107 is connected to the central processing unit 2101 via a mass storage controller (not shown) connected to the system bus 2105. The mass storage device 2107 and its associated computer-readable media provide non-volatile storage for the terminal device 2100. That is, the mass storage device 2107 may include computer-readable media (not shown) such as a hard disk or a CD-ROM (Compact Disc Read-Only Memory) drive.

[0211] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented using any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. Computer storage media include RAM, ROM, EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage, or other magnetic storage devices. Of course, those skilled in the art will recognize that the computer storage medium is not limited to the above-mentioned types. The system memory 2104 and mass storage device 2107 described above can be collectively referred to as memory.

[0212] According to an embodiment of this application, the terminal device 2100 can also be connected to a remote computer on a network, such as the Internet. That is, the terminal device 2100 can be connected to the network 2112 through the network interface unit 2111 connected to the system bus 2105, or the network interface unit 2111 can be used to connect to other types of networks or remote computer systems (not shown).

[0213] The memory also includes a computer program stored in the memory and configured to be executed by one or more processors to implement the above-described performance testing method.

[0214] In an exemplary embodiment, a computer-readable storage medium is also provided, wherein a computer program is stored therein, and the computer program implements the above-described performance testing method when executed by a processor of a terminal device.

[0215] Optionally, the computer-readable storage medium may include: ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0216] In an exemplary embodiment, a computer program product is also provided, the computer program including computer instructions stored in a computer-readable storage medium. A processor of a terminal device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the terminal device to perform the performance testing method described above.

[0217] It should be noted that this application may display prompt interfaces, pop-ups, or output voice prompts before and during the collection of user data. These prompt interfaces, pop-ups, or voice prompts are used to inform users that their data is being collected. This ensures that the application only begins the steps to collect user data after receiving confirmation from the user regarding the prompt interface or pop-up; otherwise (i.e., without receiving confirmation from the user), the steps to collect user data end, meaning no user data is collected. In other words, all user data collected by this application (including feedback forms, etc.) is processed strictly in accordance with the requirements of relevant national laws and regulations. The informed consent or separate consent of the personal information subject is obtained only with the user's consent and authorization. Subsequent data use and processing are conducted within the scope of laws, regulations, and the personal information subject's authorization, and the collection, use, and processing of relevant user data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0218] It should be understood that "multiple" as used in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0219] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A performance testing method, characterized in that, The method includes: The first user interface is displayed, which is the user interface of the first application, and the first user interface displays at least one first bullet screen. In response to the recording operation for the at least one first bullet comment, a first bullet comment file is obtained, the first bullet comment file being used to record the at least one first bullet comment displayed in the first user interface; At least one second comment is displayed on the second user interface based on the first comment file. The second user interface is the user interface of the second application, and the first application and the second application are different applications. Test the performance of the second application.

2. The method according to claim 1, characterized in that, The display of at least one second bullet comment on the second user interface based on the first bullet comment file includes: Based on the first bullet screen file, a first display frequency is obtained, wherein the first display frequency is the display frequency of the first bullet screen recorded in the first bullet screen file; Based on the first display frequency, the at least one second bullet screen is displayed on the second user interface.

3. The method according to claim 2, characterized in that, The step of displaying the at least one second bullet screen on the second user interface based on the first display frequency includes: Based on the first display frequency, a second bullet screen file is constructed, which is used to record the at least one second bullet screen displayed in the second user interface; Based on the second bullet screen file, the at least one second bullet screen is displayed on the second user interface; The at least one second bullet screen is displayed in the second user interface at a second display frequency, which is the same as the first display frequency.

4. The method according to claim 2, characterized in that, The bullet comments include various types, and different types of bullet comments have different display frequencies; The step of obtaining the first display frequency based on the first bullet screen file includes: Based on the first bullet screen file, obtain the first display frequency corresponding to the first bullet screen of each of the multiple bullet screen types; The step of displaying the at least one second bullet screen on the second user interface based on the first display frequency includes: Based on the first display frequency corresponding to the first bullet screen of the various bullet screen types, the second bullet screen of the various bullet screen types is displayed on the second user interface.

5. The method according to claim 1, characterized in that, The detection of the performance of the second application includes: During the first time period, at least one performance metric corresponding to the second application is detected, the performance metric being used to quantify the performance of the application.

6. The method according to claim 5, characterized in that, The method further includes: Obtain at least one performance metric corresponding to the first application during the first time period; By comparing at least one performance metric corresponding to the second application with at least one performance metric corresponding to the first application, a first comparison result is obtained, which is used to describe the performance difference between the second application and the first application. The second application is optimized based on the first comparison result.

7. The method according to claim 5, characterized in that, The method further includes: Obtain at least one performance metric corresponding to a historical version of the second application; A second comparison result is obtained by comparing at least one performance metric corresponding to the second application with at least one performance metric corresponding to the historical version. The second comparison result is used to describe the performance difference between the second application and the historical version of the second application. The second application is optimized based on the second comparison results.

8. The method according to claim 1, characterized in that, The method further includes: Obtain at least one issue feedback form, which describes a performance problem occurring in the second application; Cluster the at least one issue feedback form to obtain at least one performance issue class, each performance issue class corresponds to one performance issue, and each performance issue class includes at least one issue feedback form; If the increase in the number of feedback orders in the first performance problem class of the at least one performance problem class is greater than or equal to the first threshold in the second time period, then the first prompt information is displayed. The first prompt information is used to indicate that the first performance problem needs to be optimized. The first performance problem is the performance problem corresponding to the first performance problem class.

9. The method according to claim 8, characterized in that, The clustering of the at least one issue feedback form to obtain at least one performance issue class includes: Obtain the problem descriptions included in each of the at least one problem feedback forms; Based on the keyword library, the search is performed on the problem descriptions included in the at least one problem feedback form. The keyword library includes at least one keyword, and each keyword corresponds to a performance problem category. In response to the discovery of the target keyword in the problem description, the problem feedback form is classified into the performance problem category corresponding to the target keyword.

10. The method according to claim 9, characterized in that, The process of obtaining the problem descriptions included in each of the at least one problem feedback forms includes: Obtain the original problem descriptions included in each of the at least one problem feedback forms; If the original problem description is in a first language, then the original problem description is determined as the problem description; If the original problem description is in a second language, then the original problem description is translated into the first language and determined as the problem description.

11. The method according to claim 8, characterized in that, The problem feedback interface of the second application displays at least one keyword tag, which is used to describe performance issues; The clustering of the at least one issue feedback form to obtain at least one performance issue class includes: Determine the keyword tags corresponding to each of the at least one issue feedback form; The issue feedback forms are categorized into the performance issue category corresponding to the keyword tags.

12. A performance testing device, characterized in that, The device includes: A first display module is used to display a first user interface, which is the user interface of a first application, and the first user interface displays at least one first bullet screen. The module is configured to obtain a first bullet screen file in response to a recording operation for the at least one first bullet screen, wherein the first bullet screen file is used to record the at least one first bullet screen displayed in the first user interface; The second display module is used to display at least one second bullet comment based on the first bullet comment file in the second user interface, wherein the second user interface is the user interface of the second application, and the first application and the second application are different applications; The detection module is used to detect the performance of the second application.

13. A terminal device, characterized in that, The terminal device includes a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the method as described in any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which is loaded and executed by a processor to implement the method as described in any one of claims 1 to 11.

15. A computer program product, characterized in that, The computer program product includes a computer program that is loaded and executed by a processor to implement the method as described in any one of claims 1 to 11.

Images