CN114637689A

CN114637689A - Application evaluation method, device, equipment and storage medium

Info

Publication number: CN114637689A
Application number: CN202210372892.2A
Authority: CN
Inventors: 梁雄; 张棵; 郑培龙; 余小娟
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2022-04-11
Filing date: 2022-04-11
Publication date: 2022-06-17

Abstract

The disclosure provides an application evaluation method which can be applied to the field of finance. The application evaluation method comprises the following steps: acquiring label information of target service data, wherein the target service data comprise transaction data obtained in response to user transaction operation, and the label information comprises a label for representing a test service scene; determining a plurality of test cases according to the test parameters of the label information, wherein the plurality of test cases comprise test cases of normal service scenes and test cases of abnormal service scenes; determining a test result of a test case in the plurality of test cases according to the target service data to obtain a plurality of test results; and determining an evaluation result of the target application according to the plurality of test results. The present disclosure also provides an application evaluation apparatus, a device, a storage medium, and a program product.

Description

Application evaluation method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of finance, and in particular, to an application evaluation method, apparatus, electronic device, computer-readable storage medium, and computer program product.

Background

In the automatic test, a tester adopts service data under a common application scene to test, and the selected service data is data in a normal state. For a test case containing all abnormal scenes, a tester needs to spend a lot of time for designing and compiling, and the labor cost is high.

In consideration of the manual writing cost, the test cases formed by using the service data in the related technology are simple to combine, only relate to normal service scenes, and cannot relate to a plurality of abnormal scenes. Therefore, in the process of actually using the application program, the judgment of the application program on the abnormal scene has a problem, and the program of the transaction application cannot be completely and effectively verified.

Disclosure of Invention

In view of the foregoing, the present disclosure provides an application evaluation method, an application evaluation apparatus, an electronic device, a computer-readable storage medium, and a computer program product, which expand a service scenario of an application test and ensure that evaluation of an application can cover an abnormal service scenario.

According to a first aspect of the present disclosure, there is provided an application evaluation method including: acquiring label information of target service data, wherein the target service data comprises transaction data obtained in response to user transaction operation, and the label information comprises a label used for representing a test service scene; determining a plurality of test cases according to the test parameters of the label information, wherein the plurality of test cases comprise test cases of normal service scenes and test cases of abnormal service scenes; determining a test result of a test case in the plurality of test cases according to the target service data to obtain a plurality of test results; and determining an evaluation result of the target application according to the plurality of test results.

According to an embodiment of the present disclosure, determining a test result of a test case of a plurality of test cases according to target service data, and obtaining the plurality of test results includes: determining a processing script corresponding to a test case in a plurality of test cases; and inputting the target service data into the processing script, and outputting the test result of the test case to obtain a plurality of test results.

According to the embodiment of the present disclosure, before obtaining the tag information of the target service data, the method includes: determining a plurality of test conditions required by a service scene according to the service scene of the target application; and determining label information according to the test conditions.

According to the embodiment of the disclosure, the label information includes a general label and a preset label, wherein determining the plurality of test cases according to the test parameters of the label information includes: determining a plurality of test scenes according to test parameters corresponding to preset labels; and determining a plurality of test cases according to the universal label and the plurality of test scenes.

According to the embodiment of the disclosure, the preset tag at least comprises one of the following tags: the label corresponding to the test scene used for representing the user account security and the label corresponding to the test scene used for representing the user transaction behavior.

According to an embodiment of the present disclosure, further comprising: before determining the test result of the test case in the plurality of test cases, obtaining backup data according to the target service data; and replacing the target service data with the backup data after determining the evaluation result of the target application.

A second aspect of the present disclosure provides an application evaluation apparatus including: the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for acquiring label information of target service data, the target service data comprises transaction data obtained in response to user transaction operation, and the label information comprises a label used for representing a test service scene; the second determining module is used for determining a plurality of test cases according to the test parameters of the label information, wherein the plurality of test cases comprise test cases in a normal service scene and test cases in an abnormal service scene; the third determining module is used for determining the test result of the test case in the plurality of test cases according to the target service data to obtain a plurality of test results; and the evaluation module is used for determining the evaluation result of the target application according to the plurality of test results.

A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the application evaluation method described above.

The fourth aspect of the present disclosure also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described application evaluation method.

A fifth aspect of the present disclosure also provides a computer program product comprising a computer program which, when executed by a processor, implements the above-described application evaluation method.

Drawings

The foregoing and other objects, features and advantages of the disclosure will be apparent from the following description of embodiments of the disclosure, which proceeds with reference to the accompanying drawings, in which:

fig. 1 schematically shows a system architecture of an application evaluation method according to an embodiment of the present disclosure;

FIG. 2 schematically shows a flow diagram of an application evaluation method according to an embodiment of the present disclosure;

FIG. 3 schematically illustrates a flow chart of a method of determining a plurality of test results according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of a method of determining tag information according to an embodiment of the present disclosure;

fig. 5 schematically illustrates a flow chart of a method of determining a plurality of test cases according to an embodiment of the present disclosure;

FIG. 6 schematically shows a schematic diagram of an application evaluation system architecture according to an embodiment of the present disclosure;

fig. 7 schematically shows a block diagram of the structure of an application evaluation apparatus according to an embodiment of the present disclosure; and

fig. 8 schematically shows a block diagram of an electronic device adapted to apply the evaluation method according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that these descriptions are illustrative only and are not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.

All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure, application and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations, necessary confidentiality measures are taken, and the customs of the public order is not violated.

In the technical scheme of the disclosure, before the personal information of the user is acquired or collected, the authorization or the consent of the user is acquired.

The embodiment of the disclosure provides an application evaluation method, which includes obtaining label information of target service data, wherein the target service data includes transaction data obtained in response to user transaction operation, and the label information includes a label used for representing a test service scene; determining a plurality of test cases according to the test parameters of the label information, wherein the plurality of test cases comprise test cases of normal service scenes and test cases of abnormal service scenes; determining a test result of a test case in the plurality of test cases according to the target service data to obtain a plurality of test results; and determining an evaluation result of the target application according to the plurality of test results.

Fig. 1 schematically shows a system architecture of an application evaluation method according to an embodiment of the present disclosure.

As shown in fig. 1, the application scenario 100 according to this embodiment may include

terminal devices

101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).

The

terminal devices

101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the

terminal devices

101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.

It should be noted that the application evaluation method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the application evaluation apparatus provided by the embodiment of the present disclosure may be generally disposed in the server 105. The application evaluation method provided by the embodiments of the present disclosure may also be performed by a server or a server cluster that is different from the server 105 and is capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105. Accordingly, the application evaluation apparatus provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the

terminal devices

101, 102, 103 and/or the server 105.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

The application evaluation method of the disclosed embodiment will be described in detail below with reference to fig. 2 to 6 based on the scenario described in fig. 1.

Fig. 2 schematically shows a flow chart of an application evaluation method according to an embodiment of the present disclosure.

As shown in fig. 2, the method includes operations S210 to S240.

In operation S210, tag information of target service data is acquired.

According to the embodiment of the disclosure, the target business data comprises transaction data obtained in response to a user transaction operation, and the transaction data comprises information such as a transaction account, a transaction frequency and a transaction time. The label information includes a scene label and a scene identifier, the scene label is used for representing a label of a test service scene, and the scene identifier is used for identifying a corresponding scene label.

For example, a scenario label characterizing a blacklist and non-blacklist service scenario may be $ (blacklist, non-blacklist), and a scenario identifier is < table name.user security >; the scene label representing the business scene of successful and failed transaction operation is $ (0,1), and the scene identifier is < table name. The form of the scene identifier includes the form of < table name, field name >, and the scene label includes the forms of $ (value1, value2, …), $ (scene state 1, scene state 2, …), and the specific application form may be determined according to the service scene. Value1, value2, scene state 1, and scene state 2 may represent test parameters in the service scene. The scene state 1 and the scene state 2 can also correspond to a specific field value according to a set rule to be used as a test parameter.

According to the embodiment of the disclosure, after the target service data is determined, the tag information of the service scene state which needs to be changed by the current target service data is determined. Specifically, after the target service data is obtained, the service scenario to be changed in the test is determined to be a blacklist scenario and a non-blacklist scenario, and then the label information of the service scenario is determined, for example, the scenario identifier < table name >. field name >, the scenario label, the test parameter to be changed, and the like of the service scenario are determined, so that a plurality of test cases are obtained through the change of the label information.

According to the embodiment of the disclosure, before the tag information of the target service data is acquired, the target application may be analyzed, and the type, the category information, and the like of the test data required for testing the target application may be determined. And then determining corresponding target service data according to the type of the test data required by the analyzed target application.

In operation S220, a plurality of test cases including test cases of a normal service scenario and test cases of an abnormal service scenario are determined according to the test parameters of the label information.

According to the embodiment of the disclosure, after the tag information of the target service scene is acquired, the field name of the service scene state which needs to be changed in the tag information and the test parameter corresponding to the field name are acquired. And obtaining a plurality of test cases of all service scenes related to the service data according to a plurality of test parameters corresponding to a plurality of field names. The test cases comprise test cases of normal business scenes and test cases of abnormal business scenes.

It should be noted that the corresponding test parameters for a plurality of field names may be the same, but the meaning of the representation of the test parameters within different field names may differ.

For example, the service scenario status included in the tag information is normal and invalid, the scenario tag is $ (0,1), where the test parameters include 0 and 1, the test parameter corresponding to normal is 0, and the test parameter corresponding to invalid is 1. The label information also comprises a service scene blacklist and a non-blacklist account, the scene label is $ (blacklist, non-blacklist), the testing parameter corresponding to the blacklist account is 1, and the testing parameter corresponding to the non-blacklist account is 2. Another expression of the scenario label may be $ (1, 2).

According to an embodiment of the present disclosure, a plurality of test scenarios are determined according to a test parameter. For example, for target service data "user a transfers to user B", according to the multiple test parameters of the multiple service scenarios, test cases of all service scenarios corresponding to the target service data, that is, 4 test cases, "user a is a blacklist, transfers normally", "user a is a blacklist, makes a transfer operation obsolete", "user a is a non-blacklist, transfers normally", "user a is a non-blacklist, makes a transfer operation obsolete", and all service scenarios corresponding to the target service data are obtained. And the 'A user is a blacklist, transfer is normally carried out' and belongs to a test case of an abnormal service scene, and the 'A user is a blacklist, transfer operation is invalidated' and belongs to a test case of a normal service scene.

In operation S230, a test result of a test case of the plurality of test cases is determined according to the target service data, so as to obtain a plurality of test results.

According to the embodiment of the disclosure, after the target business data and the plurality of test cases are determined, under the test scene of the determined test cases, the target business data is input to the target application, and then the target application program executes the corresponding operation under the business scene. The test results of the test case may be determined according to the operation performed by the target application. And after the target application finishes the operation of the service environments corresponding to the plurality of test cases, obtaining a plurality of test results of the plurality of test cases.

For example, still taking the target service data as "user a transfers to user B" as an example, the service scenarios are blacklist and non-blacklist. And aiming at the normal service scene that the user A is a blacklist and transfer operation is cancelled, when the transfer operation is executed by the target application, the user A is determined to be the blacklist according to the test parameters, target service data are added in a blacklist database, and the transfer is cancelled.

Aiming at the abnormal service scene, the user A is a blacklist and transfers money normally, when the target application executes the transfer operation of the blacklist user, the target application should execute the invalidation operation which is the same as the normal scene, and the obtained execution result is different from the abnormal service scene. And if the normal transfer operation executed by the target application is consistent with the operation logic of the abnormal service scene, determining that the program writing of the target application has a logic error. The target application logic verification under the abnormal service scene is realized.

In operation S240, an evaluation result of the target application is determined according to the plurality of test results.

According to the embodiment of the disclosure, after the test result of the test case in the plurality of test cases is determined, the plurality of test results, that is, the test results of all the test cases of the target application covering the normal service scene and the abnormal service scene, are obtained. From the multiple test results obtained, the entire program evaluation result of the target application can be determined. Specifically, the evaluation result of the target application may be that there is a problem in the program writing logic related to a plurality of similar abnormal service scenarios, depending on whether errors occur in the test results of the target application in the similar abnormal service scenarios.

According to the embodiment of the disclosure, after the evaluation result of the target application is determined, the evaluation result can be returned to the tester, so that the tester can modify the program according to the evaluation result. Specifically, the evaluation result may include an execution log of the test case, an error-reporting keyword, a field name of the related abnormal service scenario, and the like.

In consideration of the related art, in order to cover a normal scene and an abnormal scene, a tester needs to write a large number of test cases, which is very labor-intensive. In addition, for a plurality of written test cases, the corresponding service data needs to be queried in the database and then written into the case data set, that is, the test data volume required by the service scenario is large, and it takes a lot of time to determine the test data from the database. Account status is normal, abnormal, account balance is sufficient, insufficient, account type is credit-lost, etc. to be used in connection with a transfer transaction. The database does not necessarily contain proper service data, and the state and balance of the service data can be changed along with manual transaction of a tester in a testing environment.

The method and the system have the advantages that a plurality of service scenes are represented by label information of target service data, a test case comprising a normal scene and an abnormal scene is obtained by changing the label information, a plurality of service scenes of one service data can be constructed, and the test case of the abnormal scene is covered; and testing the target application by using the obtained plurality of test cases and the target service data to obtain a test result of the target application. According to the method and the device, the application program structure does not need to be analyzed, and the test data corresponding to all service scenes does not need to be manually compiled, so that the test and evaluation of the target application are realized, and the program problems of the target application in normal scenes and abnormal scenes are effectively verified.

According to the method and the device, through the label information of the target business data, the business data matched with the test cases can be searched one by one in the database for a plurality of test cases under one business data, and the branch condition coverage rate of the transaction program is effectively improved. By adding the label information after the normal case, changing the service scene state contained in the label information and constructing the test case covering the normal scene and the abnormal scene, the time for compiling the test case is reduced, and the efficiency of application evaluation is improved.

FIG. 3 schematically illustrates a flow chart of a method of determining a plurality of test results according to an embodiment of the present disclosure.

As shown in fig. 3, the method of determining a plurality of test results of this embodiment includes operations S331 to S332. May be used as a specific embodiment of operation S230.

In operation S331, a processing script corresponding to a test case of the plurality of test cases is determined.

In operation S332, the target service data is input into the processing script, and the test result of the test case is output to obtain a plurality of test results.

According to the embodiment of the disclosure, after a plurality of test cases are determined, a processing script corresponding to a test case in the plurality of test cases is determined, then the processing script corresponding to the test case is automatically called, target service data is used as input of the processing script, and a test result of the test case is output. The processing script is a program or function that implements the test case in the target application.

According to the embodiment of the disclosure, for a plurality of test cases, after the processing script corresponding to the current test case is automatically called to process the target service data and the test result is obtained, the processing script of the next test case is used to process the target service data.

According to the embodiment of the disclosure, after the processing script corresponding to the test case is determined, the processing script can be automatically called through the program interface, the target application is triggered to take the target service data as input, and the test result is output.

Fig. 4 schematically illustrates a flow chart of a method of determining tag information according to an embodiment of the present disclosure.

As shown in fig. 4, the method of determining tag information of this embodiment includes operations S411 to S412.

According to an embodiment of the present disclosure, operation S210 is to acquire tag information of the target service data. As an embodiment, before operation S210, operations S411 to S412 are further included.

In operation S411, a plurality of test conditions required for a service scenario are determined according to the service scenario of a target application.

According to the embodiment of the disclosure, for a target application which needs to be tested, before obtaining tag information of target service data, a service scene of the target application needs to be determined, and a category of the target service data needs to be determined.

According to the embodiment of the disclosure, a plurality of test conditions required by a service scene are determined according to the service scene related to a target application, and then the test conditions are configured according to a preset rule. Specifically, the method includes the state of the service scenario, and the type of the service scenario. For example, the target application is determined to be a transaction application, the service scene is determined to include a transaction state, credit investigation information and safety information, the test condition of the transaction state is determined to include normal or invalid, and the credit investigation information test condition includes a credit loss user, a low credit user, a normal user and the like; the test conditions for the security information include blacklists and non-blacklists.

According to the embodiment of the disclosure, the target business data can be directly obtained from the transaction information database, and can also be obtained from the case database designed by the tester. The target service data further includes a primary key field for determining location information of the target service data. For example, the primary key field includes a transaction account number and a currency type, and the target transaction data is determined in the database by the transaction account number and the currency type. For example, the identification of the transaction account number may be represented as < table name.Account >, and the identification of the currency type may be represented as < table name.currency type >.

In operation S412, tag information is determined according to the test condition.

According to the embodiment of the disclosure, after the corresponding test condition is determined, the corresponding label information is determined according to the service scene in the test condition.

For example, for a certain mobile banking APP, the target application is a transaction-type application, for example, in a blacklist and non-blacklist service scenario, the test condition needs to include a security tag of the transaction user, i.e. a scene tag $ (blacklist, non-blacklist). After the test condition is determined, determining that the tag information corresponds to the structured information according to the test condition, for example, according to a scene tag $ (non-blacklist, blacklist), determining that the abnormal behavior of the user occurs to $ (blacklist), and setting a corresponding test parameter to 1; the determination that no abnormal behavior occurs is $ (non-blacklist), and the test parameter is set to 2.

Fig. 5 schematically illustrates a flow chart of a method of determining a plurality of test cases according to an embodiment of the present disclosure.

As shown in fig. 5, the method for determining multiple test cases according to this embodiment includes operations S521 to S522, which may be a specific embodiment of operation S220.

In operation S521, a plurality of test scenarios are determined according to the test parameters corresponding to the preset tag.

According to the embodiment of the disclosure, the label information comprises the universal label and the preset label, and the universal label can be suitable for various service scenes, so that the time for reconfiguring the universal label is reduced, and the testing efficiency is improved. For example, the general label included in the label information indicates that the service scenario state is normal and invalid, and indicates $ (0,1), the test parameter includes 0 and 1, the test parameter corresponding to normal is 0, and the test parameter corresponding to invalid is 1.

According to the embodiment of the disclosure, the universal tag is a specific tag value, the corresponding function is realized through a transaction commonality scene, and the value cannot be modified and can be directly selected and used by a tester. The $ (value1, value2, value 3 …) may also be set as a general label, where the value1, the value2, and the value 3 may be configured according to a preset rule. The preset tag is suitable for a non-general service scene, for example, a blacklist and a preset tag $ (non-blacklist, blacklist) corresponding to the non-blacklist scene.

According to the embodiment of the disclosure, a plurality of test parameters of the preset label are obtained according to the preset label of the non-universal service scene, and a plurality of test scenes are determined through the combination of the plurality of test parameters. For example, the preset tags include $ (non-blacklist, blacklist) and $ (non-six-month no-transaction account, six-month no-transaction account), each preset tag includes two test parameters, and 4 test scenarios can be determined.

In operation S522, a plurality of test cases are determined according to the common label and the plurality of test scenarios.

According to the embodiment of the disclosure, in the case of determining a plurality of test scenarios, the plurality of test scenarios and the plurality of general labels are combined to determine a plurality of test cases. For example, the general label is $ (0,1), and the general label is combined with the 4 test cases to determine 8 test cases, taking the obtained 4 test scenarios as an example.

According to an embodiment of the present disclosure, the tag information supports a < table name field name (value1, value2) > format for mutation of a certain flag bit of the character type field. For example, < M.N (2, 1) > indicates that field N is 1 bit long in total from bit 2.

According to the embodiment of the disclosure, the preset tag and the general tag may include tags corresponding to a plurality of service scenarios. The preset labels comprise labels corresponding to test scenes for representing user account safety and labels corresponding to test scenes for representing user transaction behaviors. For example, the generic tag includes a transaction status, an indicia of a credit lost account sanction, etc.; the preset labels include $ (non-blacklist, blacklist), $ (non-case account, case account), $ (non-penalty account, penalty account), $ (non-six months no transaction account, six months no transaction account), and the like.

According to the embodiment of the disclosure, before determining the test result of the test case in the plurality of test cases, backup data is obtained according to the target service data. And after determining the evaluation result of the target application, replacing the target business data with the backup data. The test case is obtained by changing the label information of the target business data, and the target business data itself is not changed. There are multiple test cases for the target business data, and the target business data may be changed due to errors hidden by the program in the process of testing.

The target service data is data obtained in a normal service scene, and the change of the service data can cause errors in the subsequent test cases. Before the test result of the test case in the plurality of test cases is determined, backup data is obtained according to the target service data, and then after the evaluation result of the target application is determined, the backup data is used for replacing the target service data, so that the backup and the reduction of the target service data are realized, and the accuracy of the next target service data in the next test is ensured.

Fig. 6 schematically shows a schematic diagram of an application evaluation system structure according to an embodiment of the present disclosure.

As shown in fig. 6, the application evaluation system 600 includes a scenario configuration means 610, a data parsing means 620, a case combination means 630, a script scheduling means 640, an evaluation means 650, and a backup means 660.

According to the embodiment of the present disclosure, the scene configuration device 610 analyzes the target application, determines the service scene of the target application, and determines the type of the target service data, so as to preset the corresponding tag and tag rule. The data parsing device 620 may parse the acquired target service data according to the test condition configured by the scenario configuration device 610, and parse out the tag type, the identification information of the tag < table name, field name >, and the like. The case combining device 630 may obtain the data analyzed by the data analyzing device 620, determine the label information, the test parameters, and the like of the target service data, and combine the data into a plurality of test cases of the target service data. Then, the script scheduling device 640 calls the test script corresponding to the test case to perform testing, and outputs an evaluation result. The evaluation device 650 may obtain an evaluation result of the target application according to the evaluation result obtained by the case combination device, and output the evaluation result in the form of a log.

The backup device 660 backs up the data analyzed by the data analysis device 620 before the case combination device 630 determines the test result of the test case, and restores the backed-up data to restore the target service data after the evaluation device 650 determines the test result of the target application.

Fig. 7 schematically shows a block diagram of the structure of an application evaluation apparatus according to an embodiment of the present disclosure.

As shown in fig. 7, the application evaluation apparatus 700 of this embodiment includes a first determination module 710, a second determination module 720, a third determination module 730, and an evaluation module 740.

The first determining module 710 is configured to obtain tag information of target service data, where the target service data includes transaction data obtained in response to a user transaction operation, and the tag information includes a tag used for characterizing a test service scenario. In an embodiment, the first determining module 710 may be configured to perform the operation S210 described above, which is not described herein again.

The second determining module 720 is configured to determine a plurality of test cases according to the test parameters of the tag information, where the plurality of test cases include a test case in a normal service scenario and a test case in an abnormal service scenario. In an embodiment, the second determining module 720 may be configured to perform the operation S220 described above, which is not described herein again.

The third determining module 730 is configured to determine a test result of a test case in the plurality of test cases according to the target service data, so as to obtain a plurality of test results. In an embodiment, the third determining module 730 may be configured to perform the operation S230 described above, which is not described herein again.

And the evaluation module 740 is configured to determine an evaluation result of the target application according to the plurality of test results.

In an embodiment, the evaluation module 740 may be configured to perform the operation S240 described above, which is not described herein again.

According to an embodiment of the present disclosure, the third determining module 730 includes a first determining unit and a second determining unit.

The first determining unit is used for determining the processing script corresponding to the test case in the plurality of test cases. In an embodiment, the first determining unit may be configured to perform the operation S331 described above, which is not described herein again.

And the second determining unit is used for inputting the target service data into the processing script and outputting the test results of the test cases to obtain a plurality of test results. In an embodiment, the second determining unit may be configured to perform the operation S332 described above, which is not described herein again.

According to an embodiment of the present disclosure, the first determining module 710 includes a third determining unit and a fourth determining unit.

And the third determining unit is used for determining a plurality of test conditions required by the service scene according to the service scene of the target application. In an embodiment, the third determining unit may be configured to perform the operation S411 described above, which is not described herein again.

And the fourth determining unit is used for determining the label information according to the test condition. In an embodiment, the fourth determining unit may be configured to perform the operation S412 described above, which is not described herein again.

According to an embodiment of the present disclosure, the second determination module 720 includes a fifth determination unit and a sixth determination unit.

And the fifth determining unit is used for determining a plurality of test scenes according to the test parameters corresponding to the preset labels. In an embodiment, the fifth determining unit may be configured to perform the operation S521 described above, which is not described herein again.

And the sixth determining unit is used for determining a plurality of test cases according to the universal label and the plurality of test scenes. In an embodiment, the sixth determining unit may be configured to perform the operation S522 described above, and is not described herein again.

According to an embodiment of the present disclosure, the application evaluation apparatus further includes a backup module and a replacement module.

The backup module is used for analyzing the target code and determining the syntax tree structure data of the target code. In an embodiment, the backup module may be configured to perform the operation S610 described above, which is not described herein again.

The replacement module is used for determining the branch position in the target code according to the syntax tree structure data. In an embodiment, the replacing module may be configured to perform the operation S620 described above, which is not described herein again.

As shown in fig. 8, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., Application Specific Integrated Circuit (ASIC)), among others. The processor 801 may also include onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flows according to embodiments of the present disclosure.

In the RAM 803, various programs and data necessary for the operation of the electronic apparatus 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or RAM 803. Note that the programs may also be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.

Electronic device 800 may also include input/output (I/O) interface 805, input/output (I/O) interface 805 also connected to bus 804, according to an embodiment of the present disclosure. Electronic device 800 may also include one or more of the following components connected to I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement a method according to an embodiment of the disclosure.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 802 and/or RAM 803 described above and/or one or more memories other than the ROM 802 and RAM 803.

Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the method illustrated in the flow chart. When the computer program product runs in a computer system, the program code is used for causing the computer system to realize the application evaluation method provided by the embodiment of the disclosure.

The computer program performs the above-described functions defined in the system/apparatus of the embodiments of the present disclosure when executed by the processor 801. The systems, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In one embodiment, the computer program may be hosted on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted in the form of a signal on a network medium, distributed, downloaded and installed via communication section 809, and/or installed from removable media 811. The computer program containing program code may be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.

In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

In accordance with embodiments of the present disclosure, program code for executing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, these computer programs may be implemented using high level procedural and/or object oriented programming languages, and/or assembly/machine languages. The programming language includes, but is not limited to, programming languages such as Java, C + +, python, the "C" language, or the like. The program code may execute entirely on the user computing device, partly on the user device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The above-mentioned embodiments are intended to illustrate the objects, aspects and advantages of the present disclosure in further detail, and it should be understood that the above-mentioned embodiments are only illustrative of the present disclosure and are not intended to limit the present disclosure, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. An application evaluation method comprising:

acquiring label information of target service data, wherein the target service data comprises transaction data obtained in response to user transaction operation, and the label information comprises a label used for representing a test service scene;

determining a plurality of test cases according to the test parameters of the label information, wherein the test cases comprise test cases of normal service scenes and test cases of abnormal service scenes;

determining a test result of a test case in the plurality of test cases according to the target service data to obtain a plurality of test results; and

and determining an evaluation result of the target application according to the plurality of test results.

2. The method of claim 1, wherein the determining the test result of the test case of the plurality of test cases according to the target business data to obtain a plurality of test results comprises:

determining a processing script corresponding to a test case in the plurality of test cases; and

and inputting the target service data into the processing script, and outputting the test result of the test case to obtain a plurality of test results.

3. The method of claim 1, wherein prior to obtaining tag information for the target business data, comprising:

determining a plurality of test conditions required by the service scene according to the service scene of the target application; and

and determining the label information according to the test condition.

4. The method of claim 1, the label information comprising a generic label and a pre-set label, wherein determining a plurality of test cases according to the test parameters of the label information comprises:

determining a plurality of test scenes according to the test parameters corresponding to the preset labels; and

and determining a plurality of test cases according to the universal label and the plurality of test scenes.

5. The method of claim 4, wherein the preset tag comprises at least one of: the label corresponding to the test scene used for representing the user account security and the label corresponding to the test scene used for representing the user transaction behavior.

6. The method of claim 1, further comprising:

before determining the test result of the test case in the plurality of test cases, obtaining backup data according to the target service data; and

and replacing the target service data with the backup data after determining the evaluation result of the target application.

7. An application evaluation apparatus comprising:

the system comprises a first determining module, a second determining module and a third determining module, wherein the first determining module is used for acquiring label information of target service data, the target service data comprises transaction data obtained in response to user transaction operation, and the label information comprises a label used for representing a test service scene;

the second determining module is used for determining a plurality of test cases according to the test parameters of the label information, wherein the test cases comprise test cases in normal service scenes and test cases in abnormal service scenes;

the third determining module is used for determining the test result of the test case in the plurality of test cases according to the target service data to obtain a plurality of test results; and

and the evaluation module is used for determining the evaluation result of the target application according to the plurality of test results.

8. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-6.

9. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program which, when executed by a processor, implements a method according to any one of claims 1 to 6.