Software application performance test method and device, electronic equipment and product

Abstract

The invention discloses a software application performance test method and device, electronic equipment and a product, and the method and device can display corresponding operation performance data of a software application during the operation of a performance test script at a Web front end, so that a tester can visually see the change of the performance data; meanwhile, during testing, the software versions of the software applications are updated, and the software applications of different software versions are controlled to run the performance testing script, so that running performance data corresponding to the software applications of different software versions can be obtained; and finally, reading the operation performance data corresponding to different versions by means of a Web front end, and carrying out comparison visual display, so that a function of comparing and displaying the performance data among iterations of a plurality of app versions can be realized. Therefore, the invention provides the performance test method supporting visual display and comparison of the performance data, and the test convenience is improved, so that the method is very suitable for large-scale application and popularization.

Description

Technical Field

[0001] The present invention belongs to the technical field of software testing, and particularly relates to a performance testing method, device, electronic device and product for software applications. Background Art

[0002] In order to ensure that an application can provide a smooth, stable and efficient user experience under various device and network conditions, performance testing not only needs to focus on the response speed, resource utilization and stability of the application, but also involves the optimization of the user interface (UI) and user experience. Among them, through testing, developers can discover and solve potential performance problems, thereby improving the market competitiveness of the application.

[0003] Currently, traditional performance testing script tools do not provide a unified visualization page. Although operators can obtain data such as cpu, gpu, and memory, they cannot intuitively see the changes in these data. At the same time, they cannot view and compare the changes in performance data between multiple app version iterations. In this way, the convenience of software testing will be reduced. Therefore, based on the foregoing deficiencies, how to provide a performance testing method for software applications that can visually display the performance data of software applications and at the same time can compare and display the performance data between multiple app version iterations has become an urgent problem to be solved. Summary of the Invention

[0004] The purpose of the present invention is to provide a performance testing method, device, electronic device and product for software applications, so as to solve the problem that the existing technology does not provide a unified visualization page during software testing, resulting in testers being unable to intuitively see the changes in performance data and unable to view and compare the changes in performance data between multiple app version iterations.

[0005] To achieve the above purpose, the present invention adopts the following technical solutions:

[0006] In the first aspect, a performance testing method for software applications is provided, including:

[0007] Obtain a performance testing script of a software application on a target device, where the performance testing script is constructed according to the performance testing requirements of the software application;

[0008] Control the software application to run the performance testing script, so as to obtain the running performance data of the software application of the current software version after running the performance testing script;

[0009] Write the running performance data of the software application of the current software version into a database;

[0010] Update the software version of the software application on the target device, and control the software application to re-run the performance test script until all the software versions to be tested this time have been polled, so that after all the software versions have been polled, the database stores the running performance data corresponding to the software applications of different software versions, so that the Web front-end can read the running performance data corresponding to the software applications of different software versions in the database and visually display the comparison of each running performance data.

[0011] Based on the above disclosed content, the present invention first constructs a performance test script for the software application on the target device according to the performance test requirements of the software application, and then controls the software application to run the performance test script to obtain the running performance data of the software application of the current software version. Then, the running performance data is written into the database to achieve data storage; then, the software version of the software application on the target device is updated, and the software application is controlled to re-run the foregoing performance test script until all the software versions to be tested this time have been polled; in this way, the running performance data corresponding to the software applications of different software versions can be obtained; finally, the running performance data corresponding to the software applications of different software versions is sent to the Web front-end, so that the Web front-end reads the foregoing running performance data and visually displays the comparison of different running performance data. Based on this, the function of comparing and displaying performance data between multiple app version iterations can be achieved.

[0012] Through the above design, the present invention can display the running performance data corresponding to the software application during the running of the performance test script on the Web front-end. In this way, testers can intuitively see the changes in the performance data; at the same time, during the test, by updating the software version of the software application and controlling the software applications of different software versions to run the performance test script, based on this, the running performance data corresponding to the software applications of different software versions can be obtained; finally, by means of the Web front-end to read the running performance data corresponding to different versions and visually display the comparison, thus, the function of comparing and displaying performance data between multiple app version iterations can be realized; in this way, the present invention provides a performance test method that supports visual display and comparison of performance data, improves the convenience of testing, and therefore is very suitable for large-scale application and promotion.

[0013] In a possible design, writing the running performance data of the software application of the current software version into the database includes:

[0014] Determine whether the target device is an IOS device;

[0015] If so, parse the software application to obtain the current software version number and software name of the software application;

[0016] Generate a performance data field based on the running performance data of the software application for the current software version, the current software version number of the software application, and the software name, where the performance data field is used to characterize the performance test path of the software application for the current software version, the type of the target device, the current software version number of the software application, the software name, and the performance data type;

[0017] Associate the performance data field with the running performance data of the software application for the current software version, and store the associated running performance data of the software application for the current software version into the database.

[0018] In a possible design, if the target device is an Android device, the method further includes:

[0019] Write the running performance data of the software application for the current software version into a CSV file, and save the CSV file to the target device;

[0020] Parse the software application to obtain the current software version number and the software name of the software application;

[0021] Generate a performance data field based on the running performance data of the software application for the current software version, the current software version number of the software application, and the software name;

[0022] Export the CSV file to a software test terminal connected to the target device, and when exporting, associate the CSV file with the performance data field, so that the software test terminal can read the running performance data of the software application for the current software version from the CSV file associated with the performance data field and write it into the database.

[0023] In a possible design, the performance test path is stored in a path table, and is associated with the running performance data of the software application for the current software version through the performance data field corresponding to the performance test path. The software name is stored in an app table, and is associated with the running performance data of the software application for the current software version through the performance data field corresponding to the software name.

[0024] In a possible design, the running performance data corresponding to software applications of different software versions is associated with corresponding performance data fields, where the performance data fields are used to characterize the performance test path of the software application, the type of the target device, the current software version number of the software application, the software name, and the performance data type;

[0025] Among them, the Web front end reads multiple performance data fields in the database through the app information interface, and based on each performance data field and the performance data reading interface, reads the running performance data associated with each performance data field in the database.

[0026] In a possible design, after obtaining the running performance data of the software application of the current software version, the method further includes:

[0027] Removing invalid data from the running performance data of the software application of the current software version to obtain processed running performance data;

[0028] Performing correction processing on deviation data and abnormal data in the processed running performance data to obtain corrected running performance data, where the deviation data is data with a deviation from a preset value greater than a preset range, and the abnormal data is empty data or non-numeric data;

[0029] Performing timestamp conversion processing on the corrected running performance data to obtain the acquisition time of the corrected running performance data;

[0030] Storing the acquisition time into the corrected running performance data to obtain actual running performance data, and storing the actual running performance data into the database.

[0031] In a possible design, after obtaining the corrected running performance data, the method further includes:

[0032] Using a support vector machine decision function to determine whether the corrected running performance data is correct data;

[0033] If not, re-performing correction processing on the deviation data and abnormal data in the processed running performance data until the corrected running performance data is correct data.

[0034] In a second aspect, a performance testing device for a software application is provided, including:

[0035] An acquisition unit, configured to acquire a performance test script of a software application on a target device, where the performance test script is constructed according to the performance test requirements of the software application;

[0036] A performance testing unit, configured to control the software application to run the performance test script, so as to obtain the running performance data of the software application of the current software version after running the performance test script;

[0037] A data storage unit, configured to write the running performance data of the software application of the current software version into the database;

[0038] The performance testing unit is also used to update the software version of the software application on the target device, and control the software application to re-run the performance testing script until all the software versions to be tested this time are polled. After all the software versions are polled, the running performance data corresponding to the software applications with different software versions is stored in the database, so that the Web front-end can read the running performance data corresponding to the software applications with different software versions in the database, and visually display the comparison of each running performance data.

[0039] In a third aspect, another performance testing device for software applications is provided. Taking the device as an electronic device as an example, it includes a memory, a processor, and a transceiver that are communicatively connected in sequence. Among them, the memory is used to store computer programs, the transceiver is used to send and receive messages, and the processor is used to read the computer programs and execute the performance testing method for the software application as described in the first aspect or any possible design in the first aspect.

[0040] In a fourth aspect, a storage medium is provided. Instructions are stored on the storage medium. When the instructions run on a computer, they execute the performance testing method for the software application as described in the first aspect or any possible design in the first aspect.

[0041] In a fifth aspect, a computer program product containing instructions is provided. When the instructions run on a computer, the computer is made to execute the performance testing method for the software application as described in the first aspect or any possible design in the first aspect.

[0042] Beneficial effects:

[0043] (1) The present invention can display the corresponding running performance data of the software application during the running performance testing script on the Web front-end. In this way, testers can intuitively see the changes in the performance data. At the same time, during testing, by updating the software version of the software application and controlling the software applications with different software versions to run the performance testing script, based on this, the running performance data corresponding to the software applications with different software versions can be obtained. Finally, by using the Web front-end to read the running performance data corresponding to different versions and visually display the comparison, thus, the function of comparing the performance data between multiple app version iterations can be realized. In this way, the present invention provides a performance testing method that supports visual display and comparison of performance data, improves the convenience of testing, and is therefore very suitable for large-scale application and promotion. Description of the drawings

[0044] Figure 1 It is a schematic flowchart of the steps of the performance testing method for the software application provided by the embodiment of the present invention;

[0045] Figure 2Schematic diagram of the performance table provided by the embodiments of the present invention;

[0046] Figure 3 Schematic diagram for displaying the performance data of the Web front-end provided by the embodiments of the present invention;

[0047] Figure 4 Schematic diagram of the structure of the performance test analysis device for software applications provided by the embodiments of the present invention;

[0048] Figure 5 Schematic diagram of the structure of the electronic device provided by the embodiments of the present invention. Detailed implementation manners

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the present invention in combination with the accompanying drawings and the description of the embodiments or the prior art. Obviously, the following description of the structures of the drawings is only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings. It should be noted here that the description of these embodiments is used to help understand the present invention, but does not constitute a limitation to the present invention.

[0050] It should be understood that although terms such as first and second may be used herein to describe various units, these units should not be limited by these terms. These terms are only used to distinguish one unit from another. For example, the first unit may be called the second unit, and similarly, the second unit may be called the first unit, without departing from the scope of the exemplary embodiments of the present invention.

[0051] It should be understood that for the term "and / or" that may appear in this article, it is only a description of the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, B exists alone, and both A and B exist simultaneously; for the term " / and" that may appear in this article, it is a description of another association object relationship, indicating that two relationships may exist. For example, A / and B may represent: A exists alone, and both A and B exist; in addition, for the character " / " that may appear in this article, generally it means that the front and rear associated objects are an "or" relationship.

[0052] Embodiment:

[0053] See Figure 1As shown, the performance testing method for software applications provided in this embodiment can display the corresponding performance data of a software application during the execution of a performance testing script on the Web front-end. In this way, testers can intuitively observe the changes in performance data. At the same time, during testing, by updating the software version of the software application and controlling software applications with different software versions to execute the performance testing script, based on this, the running performance data corresponding to software applications with different software versions can be obtained. Finally, the running performance data corresponding to different versions can be read through the Web front-end and compared and visually displayed. Based on this, the function of comparing performance data during the iteration of multiple app versions can be achieved. In this way, this method improves the convenience of testing. Therefore, it is very suitable for large-scale application and promotion. Among them, for example, this method can be run on a target device, a software testing terminal, and the Web front-end side. Optionally, the software testing terminal can be, but is not limited to, a personal computer (PC), and the target device can be, but is not limited to, a mobile phone or a tablet. It can be understood that the foregoing execution entities do not constitute a limitation on the embodiments of the present application. Correspondingly, the running steps of this method can be, but are not limited to, as shown in the following steps S1 to S4.

[0054] S1. Obtain a performance testing script of a software application on a target device, where the performance testing script is constructed according to the performance testing requirements of the software application. In this embodiment, the performance testing requirements of the software application are performance testing scenarios, such as usage scenarios like playing videos, news live broadcasts, and article viewing. In this way, testers can pre-construct corresponding performance testing scripts based on the foregoing different usage scenarios and store them in the software testing terminal. Then, the software testing terminal sends the performance testing script to the target device, so that the target device executes the received performance testing script to obtain running performance data.

[0055] Among them, the process of obtaining running performance data can be, but is not limited to, as shown in the following step S2.

[0056] S2. Control the software application to execute the performance testing script to obtain the running performance data of the software application of the current software version after executing the performance testing script. In this embodiment, it is equivalent to the software application executing the foregoing performance testing script, so that during the execution process, corresponding running performance data is generated, such as CPU occupancy rate, memory occupancy rate, etc. For example, if the performance testing scenario is the metaverse, then the execution of the performance testing script can be: open the app and enter the metaverse details page, record for 3 minutes, stay for 10 seconds after opening the app, enter the metaverse details, and end the recording after 3 minutes. Of course, the foregoing example is only an example, and when the scenario is different, the execution process also changes accordingly, and no specific limitation is made here.

[0057] After running the performance test script and obtaining the running performance data of the software application of the current software version, the running performance data can be written into the database so that the subsequent Web front-end can read and display the running performance data based on the database. Among them, the data writing process can be but is not limited to the steps shown in the following step S3.

[0058] S3. Write the running performance data of the software application of the current software version into the database. In specific applications, due to different operating systems of the target devices, there will be different testing methods. Therefore, in this embodiment, different data writing methods are deployed for android devices and IOS devices, and the process can be but is not limited to the steps shown in the following steps S31 to S34.

[0059] S31. Determine whether the target device is an IOS device. In this embodiment, the system version number in the mobile phone information is obtained to determine whether the target device is an IOS device. Among them, if the target device is an IOS device, the performance data field of the running performance data can be constructed and the two can be associated. Then, the associated running performance data is written into the database. Specifically, the construction process of the performance data field can be but is not limited to the steps shown in the following step S32 and step S33.

[0060] S32. If so, parse the software application to obtain the current software version number and software name of the software application. In this embodiment, the software application is parsed through a script to obtain the relevant information of the app, that is, the current software version number and software name of the software application. Then, the performance data field can be constructed in combination with the foregoing running performance data, and the process can be but is not limited to the steps shown in the following step S33.

[0061] S33. Generate a performance data field based on the running performance data of the software application of the current software version, the current software version number and software name of the software application, where the performance data field is used to characterize the performance test path of the software application of the current software version, the type of the target device, the current software version number of the software application, the software name, and the performance data type.

[0062] In this embodiment, fields of relevant data to be obtained are preset. For example, the performance data type is defined as the type field, the type value occupied by the app during runtime is defined as the type_value field, the type value occupied by the mobile phone is defined as the type_value_all field, the time when the data is obtained is defined as the time field, and the path for obtaining data (performance test path) is defined as the path_type field. At the same time, in addition to performance data, it is also necessary to compare different versions of different apps on different mobile phones. Therefore, a mobile phone type field is set as phone_type, a mobile phone model field is set as phone, an app code is set as the app_code field, and the app version is set as the app_vno field.

[0063] Based on this, the performance data fields corresponding to the running performance data of the software application of the current software version can be constructed through the fields set above. Among them, the performance data fields include: the performance test path field of the software application of the current software version, the type field of the target device, the current software version number field of the software application, the software name field, and the performance data type field (such as CPU, memory, or GPU, etc.).

[0064] Optionally, if the performance test scenario is playing a video, the type of the corresponding target device is IOS, and the performance data type is CPU (that is, the obtained running performance data is the running data of the CPU), then the foregoing performance data fields can be: phone_type is set to 1 (1 represents an IOS device), the type field is cpu (that is, the performance data type is CPU), and path_type is set to 3 (the performance test path is 3, indicating that the test scenario is playing a video). Of course, the foregoing example is only illustrative. When the performance test scenario, device type, and performance data type are different, the performance data fields are also different, and it is not limited to the foregoing example here.

[0065] In addition, in this embodiment, the performance test path is stored in a path table (that is, a separate path table is set up to store the performance test path), and through the performance data field corresponding to the performance test path (that is, path_type), it is associated with the running performance data of the software application of the current software version. The software name is stored in an app table (similarly, a separate app table is set up to store the foregoing software name), and through the performance data field corresponding to the software name (that is, app_code), it is associated with the running performance data of the software application of the current software version.

[0066] After the performance data fields are constructed, they can be associated with the currently obtained running performance data to obtain the associated running performance data. The data association process is as shown in step S34 below.

[0067] S34. Associate the performance data field with the running performance data of the software application of the current software version, and store the running performance data of the software application of the associated current software version in the database; in specific implementation, the performance data field can be written into the running performance data to obtain a performance table; then, store this performance table in the database; among them, a specific example of the data table can be seen in Figure 2 as shown.

[0068] Thus, through the foregoing steps S31 to S34, the writing of the running performance data of the software application on the IOS device can be achieved.

[0069] Similarly, when it is determined that the target device is an android device, the writing process of its corresponding running performance data can be but is not limited to the following steps S35 to S38 as shown.

[0070] S35. Write the running performance data of the software application of the current software version into a CSV file, and save the CSV file to the target device; in this embodiment, after the android device running performance test script obtains the performance data, write the performance data into a csv file, among which, different performance parameters are different csv files, the first column of the csv file is the data generation time, the second column is the data value, and finally multiple csv files will be generated and stored in the target device (such as a mobile phone); then, the CSV file needs to be exported to the software test terminal connected to the target device; of course, when exporting, corresponding performance data fields will also be generated; among them, the generation process of the performance data field and the export process of the CSV file can be but is not limited to the following steps S36 to S38 as shown.

[0071] S36. Analyze the software application to obtain the current software version number and software name of the software application.

[0072] S37. Generate a performance data field according to the running performance data of the software application of the current software version, the current software version number and software name of the software application; in this embodiment, the generation process of the performance data field can be seen in the foregoing step S33, and will not be elaborated here.

[0073] After generating the performance data field, the association and export of the CSV file can be carried out, and the process is as shown in the following step S38.

[0074] S38. Export the CSV file to the software test terminal connected to the target device. When exporting, associate the CSV file with the performance data fields, so that the software test terminal can read the running performance data of the software application of the current software version from the CSV file associated with the performance data fields and write it into the database. In this embodiment, the data of the android device is exported to a folder on the target device using the adb command, and a script is written to read the csv file data. At the same time, the corresponding performance data fields will also be associated. For example, the performance test path is the cpu data csv file when playing a video, the type field is set to cpu, the phone_type is set to 2 (2 represents an android device), and the path_type is set to 3.

[0075] In this way, through the foregoing steps S35 to S38, the writing of the running performance data of the software application on the android device can be completed. Among them, for example, the foregoing database is a MySQL database. At the same time, in order to ensure the accuracy of the obtained running performance data, this embodiment also sets a data preprocessing operation, and its process is as follows:

[0076] The first step: Remove the invalid data in the running performance data of the software application of the current software version to obtain the processed running performance data. In this embodiment, the invalid data is duplicate, incorrect, and incomplete data. In this way, after removing the invalid data, the correction of the deviation data and abnormal data can be performed, and its process is shown in the following second step.

[0077] The second step: Perform correction processing on the deviation data and abnormal data in the processed running performance data to obtain the corrected running performance data. Among them, the deviation data is data whose deviation from the preset value is greater than the preset range, and the abnormal data is empty data or non-numeric data. In this embodiment, for example, but not limited to, the mean, median, or mode can be used to fill the numerical deviation data and abnormal data. At the same time, for example, the foregoing preset value is the median or average value of the running performance data, and the preset range is 5%. That is, if a data deviates from the median or average by 5%, it is determined as deviation data.

[0078] In addition, after obtaining the corrected running performance data, this embodiment can also use the vector machine decision function to determine whether the corrected running performance data is correct data. Among them, if not, the deviation data and abnormal data in the processed running performance data are corrected again until the corrected running performance data is correct data. If it is determined as correct data, the following third step can be performed.

[0079] In this embodiment, it is equivalent to performing classification using the above decision function after calibration and other processing. For example, for a dataset with default values, the default feature values are filled with the mean value, and then the filled samples are substituted into the decision function to obtain data classification. Among them, if the data classification result is correct data, the following third step can be executed; otherwise, data correction needs to be performed again. In this way, the accuracy of data correction can be ensured.

[0080] After obtaining the calibrated operation performance data, timestamp conversion can be performed, and the process is as shown in the following third step.

[0081] Third step: Perform timestamp conversion processing on the calibrated operation performance data to obtain the acquisition time of the calibrated operation performance data. In this embodiment, the timestamp is a way for a computer to store time. This representation is convenient for computer storage and processing, but it cannot be directly represented as time. For example, the timestamp is: 1609459200, and the corresponding acquisition time after conversion is; 2021-01-01 00:00:00. In this way, by converting the timestamp, it is convenient for testers to intuitively understand the acquisition time of the data.

[0082] After completing the timestamp conversion, the actual operation performance data can be obtained, and then the writing of the actual operation performance data can be performed, and the process is as shown in the following fourth step.

[0083] Fourth step: Store the acquisition time into the calibrated operation performance data to obtain the actual operation performance data, and store the actual operation performance data into the database. In this embodiment, the writing process of the actual operation performance data can refer to the foregoing steps S31 to S38, which will not be elaborated here.

[0084] Meanwhile, for example, but not limited to, a write command can be used to write the foregoing operation performance data. For example, when storing the CPU performance data of the performance test paths of android and ios devices, the command is "INSERT INTO pro_perf_monitor(app_code,app_vno,path_type,`type`,type_value,`time`,phone,phone_type)""values(%s,%s,%s,%s,%s,%s,%s,%s)"; of course, the foregoing command is only illustrative and is not limited thereto here.

[0085] Thus, after completing the performance test of the software application of the current version on the target device, the software application can be updated to implement its performance test under different software versions. The performance test process of the software application of different software versions is as shown in the following step S4.

[0086] S4. Update the software version of the software application on the target device, and control the software application to re-run the performance test script until all the software versions to be tested this time are polled. After all the software versions are polled, the database stores the running performance data corresponding to the software applications with different software versions, so that the Web front-end can read the running performance data corresponding to the software applications with different software versions in the database and visually display the comparison of each running performance data; in this embodiment, every time the software application is updated, the foregoing steps S2 and S3 need to be re-executed until all the software versions are polled, and then the running performance data corresponding to the software applications of each software version can be written into the database; then, the foregoing different running performance data can be transmitted to the Web front-end, so that the Web front-end can visually display the comparison of each running performance data.

[0087] Optionally, as described above, the running performance data corresponding to the software applications with different software versions is associated with corresponding performance data fields. Therefore, for example, when the Web front-end reads data, it will construct corresponding interfaces. Specifically, the Web front-end reads multiple performance data fields in the database through the app information interface, and based on each performance data field and the performance data reading interface, reads the running performance data associated with each performance data field in the database.

[0088] In this way, it is equivalent to configuring an interface for obtaining app information to obtain all app project names, versions, and performance test paths, so as to read the app names and versions in the app table of the database, the performance test paths in the path table, and the performance data fields (i.e., fields such as app_code, app_vno, path_type, etc.) based on this interface; then, configure an interface for reading performance data, such as reading the performance data of the app performance test path A on a certain Android device, so as to obtain the associated running performance data based on the foregoing performance data fields; finally, the different running performance data obtained can be visually displayed by comparison.

[0089] Among them, for example, the entire web page is displayed in partitions according to performance scenarios, apps, devices, and performance test paths; for example, the display of the CPU performance data of a certain path of a certain app on a certain Android device is a region, and the specific display style can be seen Figure 3 as shown; further, clicking on the icon with the version number on the graph can hide and display the data related to this version, and the display page supports the function of filtering data according to the project app, app version number, and performance path.

[0090] Of course, in this embodiment, the software test terminal can also read different running performance data from the database, then perform comparative analysis to obtain the comparative analysis results, and transmit them to the Web front end, which can directly visualize the foregoing comparative analysis results.

[0091] Through the performance testing method of the software application described in detail in the foregoing steps S1 to S4, the present invention can display the corresponding performance data of the software application during the running performance test script on the Web front end. In this way, testers can intuitively see the changes in the performance data. At the same time, during the test, by updating the software version of the software application and controlling the software application of different software versions to run the performance test script, based on this, the running performance data corresponding to the software application of different software versions can be obtained. Finally, the Web front end can be used to read the running performance data corresponding to different versions and perform comparative visualization display. Based on this, the function of comparing and displaying the performance data between multiple app version iterations can be realized. In this way, the present invention improves the convenience of testing, and therefore is very suitable for large-scale application and promotion.

[0092] As Figure 4 shown, in the second aspect of this embodiment, a hardware device for implementing the performance testing method of the software application described in the first aspect of the embodiment is provided, including:

[0093] An acquisition unit, configured to acquire a performance test script of a software application on a target device, where the performance test script is constructed according to the performance test requirements of the software application.

[0094] A performance testing unit, configured to control the software application to run the performance test script, so as to obtain the running performance data of the software application of the current software version after running the performance test script.

[0095] A data storage unit, configured to write the running performance data of the software application of the current software version into a database.

[0096] The performance testing unit is further configured to update the software version of the software application on the target device and control the software application to re-run the performance test script until all the software versions to be tested this time are polled, so that after all the software versions are polled, the database stores the running performance data corresponding to the software application of different software versions, so that the Web front end can read the running performance data corresponding to the software application of different software versions in the database and perform comparative visualization display of each running performance data.

[0097] For the working process, working details and technical effects of the device provided in this embodiment, reference can be made to the first aspect of the embodiment, which will not be elaborated here.

[0098] As Figure 5 shown, in the third aspect of this embodiment, another performance testing device for software applications is provided. Taking the device as an electronic device as an example, it includes: a memory, a processor, and a transceiver that are communicatively connected in sequence. Among them, the memory is used to store computer programs, the transceiver is used to send and receive messages, and the processor is used to read the computer programs and execute the performance testing method for software applications as described in the first aspect of the embodiment.

[0099] Specifically, the memory may include, but is not limited to, random access memory (RAM), read only memory (ROM), flash memory, first input first output (FIFO), and / or first in last out (FILO), etc.; specifically, the processor may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor may be implemented in at least one hardware form of DSP (Digital Signal Processing), FPGA (Field-Programmable Gate Array), and PLA (Programmable Logic Array). At the same time, the processor may also include a main processor and a coprocessor. The main processor is a processor used to process data in the wake state, also known as the CPU (Central Processing Unit); the coprocessor is a low-power processor used to process data in the standby state.

[0100] In some embodiments, the processor may integrate a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content to be displayed on the display screen. For example, the processor may be, but is not limited to, a microprocessor of the STM32F105 series, a reduced instruction set computer (RISC) microprocessor, an X86 architecture processor, or a processor integrated with an embedded neural-network processing unit (NPU); the transceiver may be, but is not limited to, a Wi-Fi wireless transceiver, a Bluetooth wireless transceiver, a General Packet Radio Service (GPRS) wireless transceiver, a ZigBee (low-power local area network protocol based on the IEEE 802.15.4 standard) wireless transceiver, a 3G transceiver, a 4G transceiver, and / or a 5G transceiver, etc. In addition, the device may also include, but is not limited to, a power module, a display screen, and other necessary components.

[0101] For the working process, working details, and technical effects of the electronic device provided in this embodiment, reference may be made to the first aspect of the embodiment, which will not be elaborated here.

[0102] The fourth aspect of this embodiment provides a storage medium storing instructions for the performance testing method of the software application described in the first aspect of the embodiment, that is, the storage medium stores instructions that, when run on a computer, execute the performance testing method of the software application described in the first aspect of the embodiment.

[0103] Among them, the storage medium refers to a carrier for storing data, which may be, but is not limited to, including floppy disks, optical discs, hard disks, flash memories, USB flash drives, and / or Memory Sticks, etc. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.

[0104] For the working process, working details, and technical effects of the storage medium provided in this embodiment, reference may be made to the first aspect of the embodiment, which will not be elaborated here.

[0105] The fifth aspect of this embodiment provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the performance testing method of the software application described in the first aspect of the embodiment. Among them, the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.

[0106] Finally, it should be noted that the above are only preferred embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A performance testing method for a software application, characterized in that: include: Obtaining a performance test script of a software application on a target device, wherein the performance test script is constructed according to a performance test requirement of the software application; Controlling the software application to run the performance test script, so as to obtain the running performance data of the software application of the current software version after running the performance test script; Writing the running performance data of the software application of the current software version into a database; Update the software version of the software application on the target device, and control the software application to re-run the performance test script until all the software versions to be tested this time are polled, so that after all the software versions are polled, the database stores the running performance data corresponding to the software applications with different software versions, so that the Web front end can read the running performance data corresponding to the software applications with different software versions in the database, and compare and visualize the various running performance data.

2. The method according to claim 1, characterized in that Writing the running performance data of the software application of the current software version into a database includes: Determine whether the target device is an IOS device; If yes, then parse the software application to obtain the current software version number and software name of the software application; Generate a performance data field based on the running performance data of the software application of the current software version, the current software version number and the software name of the software application, wherein the performance data field is used to characterize the performance test path of the software application of the current software version, the type of the target device, the current software version number, the software name and the performance data type of the software application; The performance data field is associated with the running performance data of the software application of the current software version, and the associated running performance data of the software application of the current software version is stored in the database.

3. The method according to claim 2, characterized in that If the target device is an Android device, the method further includes: Writing the running performance data of the software application of the current software version into a CSV file, and saving the CSV file to the target device; Parsing the software application to obtain the current software version number and software name of the software application; Generate a performance data field according to the running performance data of the software application of the current software version, the current software version number and the software name of the software application; The CSV file is exported to a software testing terminal connected to the target device, and when exporting, the CSV file is associated with the performance data field, so that the software testing terminal can read the running performance data of the software application of the current software version from the CSV file associated with the performance data field, and write it into the database.

4. The method according to claim 2, characterized in that: The performance test path is stored in the path table, and is associated with the running performance data of the software application of the current software version through the performance data field corresponding to the performance test path. The software name is stored in the app table, and is associated with the running performance data of the software application of the current software version through the performance data field corresponding to the software name.

5. The method according to claim 1, characterized in that The running performance data corresponding to the software applications of different software versions are associated with corresponding performance data fields, wherein the performance data fields are used to characterize the performance test path of the software application, the type of the target device, the current software version number of the software application, the software name and the performance data type; Among them, the Web front end reads multiple performance data fields in the database through the app information interface, and reads the operating performance data associated with each performance data field in the database based on each performance data field and the performance data reading interface.

6. The method according to claim 1, characterized in that After obtaining the running performance data of the software application of the current software version, the method further includes: Removing invalid data from the running performance data of the software application of the current software version to obtain processed running performance data; Correcting the deviation data and abnormal data in the processed running performance data to obtain corrected running performance data, wherein the deviation data is data whose deviation from a preset value is greater than a preset range, and the abnormal data is empty data or non-digital data; Performing timestamp conversion processing on the corrected running performance data to obtain the collection time of the corrected running performance data; The acquisition time is stored in the corrected operation performance data to obtain actual operation performance data, and the actual operation performance data is stored in the database.

7. The method according to claim 6, characterized in that After obtaining the corrected operating performance data, the method further includes: Using a vector machine decision function, determining whether the corrected operating performance data is correct data; If not, the deviation data and abnormal data in the processed operating performance data are corrected again until the corrected operating performance data is correct.

8. A performance testing device for a software application, characterized in that: include: An acquisition unit, configured to acquire a performance test script of a software application on a target device, wherein the performance test script is constructed according to a performance test requirement of the software application; A performance testing unit, used to control the software application to run the performance testing script, so as to obtain the running performance data of the software application of the current software version after running the performance testing script; A data storage unit, used to write the running performance data of the software application of the current software version into a database; The performance testing unit is also used to update the software version of the software application on the target device and control the software application to re-run the performance testing script until all the software versions to be tested are polled. After all the software versions are polled, the database stores the running performance data corresponding to the software applications with different software versions, so that the Web front end can read the running performance data corresponding to the software applications with different software versions in the database and compare and visualize the various running performance data.

9. An electronic device, characterized in that: include: A memory, a processor and a transceiver which are sequentially communicatively connected, wherein the memory is used to store computer programs, the transceiver is used to send and receive messages, and the processor is used to read the computer program, and execute the performance testing method for the software application as described in any one of claims 1 to 7.

10. A computer program product comprising instructions, characterized in that When the instructions are executed on a computer, the computer is caused to execute the performance testing method for a software application as claimed in any one of claims 1 to 7.

Images