CN112799943A

CN112799943A - Automatic testing method and device for business system

Info

Publication number: CN112799943A
Application number: CN202110124828.8A
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: 2021-01-29
Filing date: 2021-01-29
Publication date: 2021-05-14
Anticipated expiration: 2041-01-29
Also published as: CN112799943B

Abstract

The application provides a method and a device for automatically testing a business system, which can be used in the financial field or other fields, and the method comprises the following steps: receiving production message data of target transaction; generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule; and if the multi-level scene identification strings respectively meet the executable conditions of the corresponding identification strings, sending the production message data to a test environment of a target service system so as to complete the automatic test of the target service system. The method and the device can avoid repeated scene testing, improve the efficiency of the automatic testing of the service system and further improve the safety of system operation.

Description

Automatic testing method and device for business system

Technical Field

The present application relates to the field of software testing technologies, and in particular, to an automated testing method and an automated testing device for a business system.

Background

With the rapid development of the internet technology, well-jet outbreak occurs in the use and development of rapid payment services, which not only relates to a plurality of mechanisms, but also is applied to different service scenes. Under the condition of ultrahigh daily average transaction and account change amount, higher requirements are put forward on the safe and stable operation of a bank system at a card issuing side, and particularly, higher standards are put forward on how to carry out effective scene coverage and risk control under the condition of system upgrading and transformation in the aspect of bank system testing.

Due to the particularity of the quick payment service, the interactive message comprises dozens of threshold values, the problems that the test scene is out of line with the production scene due to the fact that the parameter combination is rich and the specific scene cannot be obtained through the production service experience exist in the design aspect of the test scene, and the like exist in the aspects of scene design and actual use. In addition, the same scene only needs to be tested, and the production message contains a large amount of message data of the same type of repeated scene, so that after the production message is introduced for testing, a large amount of resources are used for testing the invalid repeated scene, resource waste is caused, efficient scene coverage cannot be performed on the quick payment service, and potential safety hazards are left for system operation.

Disclosure of Invention

Aiming at the problems in the prior art, the application provides a method and a device for automatically testing a service system, which can avoid repeated scene testing, improve the efficiency of automatically testing the service system and further improve the safety of system operation.

In order to solve the technical problem, the present application provides the following technical solutions:

in a first aspect, the present application provides a method for automatically testing a service system, including:

receiving production message data of target transaction;

generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule;

and if the multi-level scene identification strings respectively meet the executable conditions of the corresponding identification strings, sending the production message data to a test environment of a target service system so as to complete the automatic test of the target service system.

Further, the generating a multi-level scene identifier string according to the production packet data and a preset scene identifier generation rule includes:

and if the transaction type data in the production message data meets a preset executable transaction condition, generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule.

Further, if the transaction type data in the production message data conforms to a preset executable transaction condition, generating a multi-level scene identifier string according to the production message data and a preset scene identifier generation rule, including:

and if the transaction type data in the production message data is in a preset executable transaction type group, and the executed times of the transaction type corresponding to the transaction type data are less than the executable times of the transaction type corresponding to the transaction type data, generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule.

Further, if the multi-level scene identifier strings respectively satisfy the executable conditions of the corresponding identifier strings, the method sends the production packet data to a test environment of a target service system to complete an automated test of the target service system, including:

and if the multi-level scene identification strings are respectively in the corresponding scene current-limiting identification string groups, and the executed times of the corresponding current-limiting scenes are respectively less than the executable times of the corresponding current-limiting scenes, transmitting the production message data to a test environment of a target service system to complete the automatic test of the target service system.

Further, the method for automatically testing the service system further includes:

if the multi-level scene identification strings meet the executable conditions of the corresponding identification strings, carrying out data replacement on the production message data according to a preset message replacement rule;

and sending the replaced production message data to a test environment of the target service system to complete the automatic test of the target service system.

Further, after the data replacement is performed on the production message data, the method further includes:

carrying out data encryption and signature calculation on the replaced production message data;

and sending the calculation result to a test environment of the target service system to complete the automatic test of the target service system.

Further, after the sending the production packet data to a test environment of a target service system to complete an automated test of the target service system if the multi-level scene identifier strings respectively satisfy the respective corresponding identifier string executable conditions, the method further includes:

receiving an automatic test result of the target service system;

obtaining the ratio of the times of normal results, the ratio of the times of abnormal results and the ratio of the times of failure results of each of a plurality of dimensions according to the automatic test result and a plurality of pre-stored historical automatic test results;

the plurality of dimensions includes: the transaction type data and scene identification strings at different levels.

In a second aspect, the present application provides an automatic testing apparatus for a business system, including:

the receiving module is used for receiving the production message data of the target transaction;

the generating module is used for generating a multi-level scene identification string according to the production message data and a preset scene identification generating rule;

and the test module is used for sending the production message data to a test environment of a target service system to complete the automatic test of the target service system if the multi-level scene identification strings respectively meet the executable conditions of the corresponding identification strings.

Further, the generating module includes:

and the generating unit is used for generating a multi-level scene identification string according to the production message data and a preset scene identification generating rule if the transaction type data in the production message data accords with a preset executable transaction condition.

In a third aspect, the present application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the business system automation testing method.

In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon computer instructions, which when executed, implement the business system automation test method.

According to the technical scheme, the application provides an automatic testing method and device for the business system. Wherein, the method comprises the following steps: receiving production message data of target transaction; generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule; if the multi-level scene identification strings respectively meet the executable conditions of the corresponding identification strings, the production message data is sent to the test environment of the target service system so as to complete the automatic test of the target service system, so that repeated scene tests can be avoided, the automatic test efficiency of the service system can be improved, and the running safety of the system can be further improved; in particular, the transaction message can automatically replace test data and generate a test signature, the multiplexing of a production scene in a test environment can be realized, particularly, the problem that a third-party rapid payment transaction tester cannot know the actual message production condition through experience service can be solved, furthermore, the difficulty of separation of the test scene from the actual production use scene exists during the design of the test scene and the case, the effectiveness of the test scene can be effectively ensured, and simultaneously, by setting the target transaction type, the target test scene and the number of strokes, the transaction type and the test scene of the test message are effectively limited, the invalid repeated execution of the similar transaction is rejected, the resource investment can be greatly saved, the bank side system of the card issuing institution is fully and effectively covered in the scene, and the safety and the stability of the bank side system of the card issuing institution under the condition of ultrahigh transaction amount can be powerfully guaranteed; in addition, the test scenes extracted through production and transaction can be automatically supplemented and preserved in the test scenes and the test case library, the loopholes of the test scenes and cases are filled, the test assets are enriched, and important decision bases are provided for setting test plans and implementing tests.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 is a schematic flow chart of an automated testing method for a business system in an embodiment of the present application;

FIG. 2 is a schematic flow chart of an automated testing method for a business system according to another embodiment of the present application;

FIG. 3 is a schematic structural diagram of an automated testing apparatus for a business system in an embodiment of the present application;

FIG. 4 is a schematic structural diagram of an automated testing apparatus for a business system in an application example of the present application;

FIG. 5 is a schematic structural diagram of a load module in an application example of the present application;

FIG. 6 is a schematic diagram of a processing module in an example of application of the present application;

FIG. 7 is a schematic structural diagram of a signature module in an application example of the present application;

FIG. 8 is a block diagram of an execution module according to an embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of a statistical analysis module in an application example of the present application;

FIG. 10 is a schematic structural diagram of a parameter maintenance module in an application example of the present application;

FIG. 11 is a schematic structural diagram of an information storage module in an application example of the present application;

FIG. 12 is a flow chart illustrating an automated testing method according to an exemplary embodiment of the present application;

fig. 13 is a block diagram schematically illustrating a system configuration of an electronic device 9600 according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In order to solve the problems in the prior art, the method and the device consider that a test message is generated according to a third-party fast payment transaction production message, the transaction type and the test scene of the test message are effectively limited by setting the target transaction type, the target test scene and the number of strokes, the invalid repeated execution of the similar transaction is rejected, then test encryption and signatures which are necessary to be used during interactive message testing are generated, and finally, automatic test execution is performed. After the transaction is executed, the transaction result is subjected to statistical analysis and is compared with the test case library, the state of the existing case is updated, the existing case is registered and supplemented, the loopholes of the test scene and the case are filled, and a decision basis is provided for the arrangement of a test strategy and the development of test work of testers. The efficiency of the production message in the test process can be greatly improved, the defect that a rapid payment service test scene is separated from production and use can be effectively prevented by means of the production message, the test scene is kept fresh, the actual quality of the test scene is powerfully improved by combining automatic execution, the manpower input in the aspects of scene design, test execution and the like is saved, the efficiency is improved, the test risk is controlled, and the stable operation of a bank side system of a card issuing mechanism is ensured.

Based on this, in order to avoid repeated scene testing, the efficiency of the automatic testing of the service system is improved, and further the safety of the system operation is improved, an embodiment of the present application provides an automatic testing apparatus of the service system, which may be a server or a client device, where the client device may include a smart phone, a tablet electronic device, a network set-top box, a portable computer, a desktop computer, a Personal Digital Assistant (PDA), a vehicle-mounted device, an intelligent wearable device, and the like. Wherein, intelligence wearing equipment can include intelligent glasses, intelligent wrist-watch and intelligent bracelet etc..

In practical applications, the part for performing the service system automation test may be executed on the server side as described in the above, or all the operations may be completed in the client device. The selection may be specifically performed according to the processing capability of the client device, the limitation of the user usage scenario, and the like. This is not a limitation of the present application. The client device may further include a processor if all operations are performed in the client device.

The client device may have a communication module (i.e., a communication unit), and may be communicatively connected to a remote server to implement data transmission with the server. The server may include a server on the task scheduling center side, and in other implementation scenarios, the server may also include a server on an intermediate platform, for example, a server on a third-party server platform that is communicatively linked to the task scheduling center server. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed apparatus.

The server and the client device may communicate using any suitable network protocol, including network protocols not yet developed at the filing date of this application. The network protocol may include, for example, a TCP/IP protocol, a UDP/IP protocol, an HTTP protocol, an HTTPS protocol, or the like. Of course, the network Protocol may also include, for example, an RPC Protocol (Remote Procedure Call Protocol), a REST Protocol (Representational State Transfer Protocol), and the like used above the above Protocol.

It should be noted that the method and the device for automatically testing the business system disclosed in the present application can be used in the field of financial technology, and can also be used in any field except the field of financial technology.

The following examples are intended to illustrate the details.

In order to avoid repeated scenario testing, improve the efficiency of the automatic testing of the service system, and further improve the safety of the system operation, this embodiment provides an automatic testing method of the service system, in which the execution subject is an automatic testing apparatus of the service system, the automatic testing apparatus of the service system includes, but is not limited to, a server, as shown in fig. 1, and the method specifically includes the following contents:

step 100: and receiving the production message data of the target transaction.

Specifically, the method may receive production message data sent by the target service system, where the production message data may be a transaction message corresponding to a current third-party fast payment related transaction, and the production message data may include: transaction type, date, card number, user information, transaction serial number, etc.

Step 200: and generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule.

Specifically, the multi-level scene identification string may include a first-level scene identification string and a second-level scene identification string, and the first-level scene identification string and the second-level scene identification string of the current transaction may be correspondingly identified according to the production packet data and a preset scene identification generation rule.

The first-level scene identification string is composed of a string of characters consisting of 0 and 1, the number of digits of the string is determined by the number of message fields of the transaction type, and the digits of the string correspond to the sequence of the message fields one by one; when a field value is empty, the corresponding number of the scene character string corresponding to the field is 0, and if the field value is not empty, the corresponding number of the scene character string corresponding to the field is 1, so as to form a scene character string, the first-level scene correspondence table is shown in table 1, and the scene in table 1 can represent the message field.

TABLE 1

The second-level scene identification string is composed of a string of numeric and alphabetic character strings, the number of digits of the character strings is determined by the number of message fields of the transaction type, and the digits of the character strings correspond to the sequence of the message fields one by one; the value of each character of the character string is obtained by selecting a corresponding letter for a number with a partial identifier of 1 on the basis of a primary scene current-limiting identifier string by referring to a secondary scene corresponding table, wherein the secondary scene corresponding table is shown in table 2, the scene in table 2 can represent a message field, and in one example, the transaction message is: < BisTp 01</BisTp > < IDTP >01</IDTP > < IDNO >11111111111111111X </IDNO > < TraId > < clone 13388888888 </clone > < TraTi 2020-12-02</TraTi > < TraCard >6888888888888888888</TraCard > Payment transaction </TraNa >, then the corresponding primary scene identification string is: 11101111, the corresponding secondary scene identification string can be: AAF0AOAB, 111011 AB.

TABLE 2

Step 300: and if the multi-level scene identification strings respectively meet the executable conditions of the corresponding identification strings, sending the production message data to a test environment of a target service system so as to complete the automatic test of the target service system.

Specifically, the target business system may be a card-issuing bank system; after the automatic test is completed, the test result, namely the transaction response result information can be output, so that the successful, failed and abnormal transaction number and proportion conditions can be determined in time.

As can be seen from the above description, the method for automatically testing a business system provided by this embodiment receives production message data of a target transaction; generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule; if the multi-level scene identification strings respectively meet the executable conditions of the corresponding identification strings, the production message data is sent to the test environment of the target service system so as to complete the automatic test of the target service system, repeated scene tests can be avoided by applying the multi-level scene identification strings, the automatic test efficiency of the service system can be improved, and the running safety of the system can be further improved.

In order to avoid the invalid repeated execution of the similar transactions and further improve the efficiency of the automation test of the business system, in an embodiment of the present application, step 200 includes:

step 201: and if the transaction type data in the production message data meets a preset executable transaction condition, generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule.

Specifically, the transaction type data may include: transaction type data such as all passing, quick payment signing transaction, quick payment transaction, third-party quick payment return transaction, third-party quick payment cash withdrawal transaction and the like.

Further improving the efficiency of the automatic testing of the service system, referring to fig. 2, in an embodiment of the present application, step 201 includes:

step 2011: and if the transaction type data in the production message data is in a preset executable transaction type group, and the executed times of the transaction type corresponding to the transaction type data are less than the executable times of the transaction type corresponding to the transaction type data, generating a multi-level scene identification string according to the production message data and a preset scene identification generation rule.

Specifically, the preset executable transaction type group comprises a plurality of executable transaction type data, and the preset executable transaction type group can be set according to actual needs and can be stored in the local service system automation test device in advance; the executed times of the transaction type corresponding to the transaction type data can represent the executed times corresponding to the transaction type data before the current test, and the executed times corresponding to the transaction type data can be updated after the current automatic test is completed; the number of times that the transaction type corresponding to the transaction type data can be executed may represent the total number of times that the test can be executed corresponding to the transaction type data, and may be set according to actual needs.

To avoid the scenario repeat test and implement the efficient test of the service system, referring to fig. 2, in an embodiment of the present application, step 300 includes:

step 301: and if the multi-level scene identification strings are respectively in the corresponding scene current-limiting identification string groups, and the executed times of the corresponding current-limiting scenes are respectively less than the executable times of the corresponding current-limiting scenes, transmitting the production message data to a test environment of a target service system to complete the automatic test of the target service system.

Specifically, if a primary scene identifier string is in a pre-stored primary scene current-limiting identifier string group, the executed times corresponding to the primary scene identifier string are less than the executed times corresponding to the primary scene identifier string, a secondary scene identifier string is in a pre-stored secondary scene current-limiting identifier string group, and the executed times corresponding to the secondary scene identifier string are less than the executed times corresponding to the secondary scene identifier string, the production packet data is sent to a test environment of a target service system; the pre-stored primary scene current-limiting identification string group comprises a plurality of primary scene current-limiting identification strings, the secondary scene current-limiting identification string group comprises a plurality of secondary scene current-limiting identification strings, and the primary scene current-limiting identification string group and the secondary scene current-limiting identification string group can be set according to actual needs and can be pre-stored locally in the service system automatic testing device. The number of times that the current limiting scenario has been executed may represent the number of times that tests have been executed corresponding to the current limiting scenario identification string, and the number of times that the current limiting scenario can be executed may represent the total number of times that tests can be executed corresponding to the scenario identification string. The corresponding relationship among the executable transaction type group, the scene current limit identifier string group, the transaction type executable times, the current limit scene executable times, the transaction type executed times and the current limit scene executed times can be shown in table 3, wherein please set a transaction type column to represent the executable transaction type group, please maintain an execution times column to represent the transaction type executable times, please maintain a scene current limit identifier string corresponding to a current limit level of 1 to form a primary scene current limit identifier string group, please maintain a scene current limit identifier string corresponding to a current limit level of 2 to form a secondary scene current limit identifier string group, the primary current limit scene times can represent the current limit scene executable times of the primary current limit scene identifier string, and the secondary current limit scene times can represent the current limit scene executable times of the secondary current limit scene identifier string.

TABLE 3

In order to avoid the difference between the service system and the test environment, which results in that the production message data is not suitable for the test environment, and improve the accuracy of the automated test on the basis of ensuring the efficiency of the automated test, in an embodiment of the present application, after step 200, the method further includes:

step 021: and if the multi-level scene identification strings meet the executable conditions of the corresponding identification strings, performing data replacement on the production message data according to a preset message replacement rule.

Specifically, the preset message replacement rule may be applied to replace a message field value in the production message data with a value that can be successfully executed in the test environment; the scope of the replacement content includes, but is not limited to, the transaction serial number (TraD), the transaction date (TraT), the transaction card number (TraCard), the transaction amount (TraM), etc. in the message. Which is divided into the necessary replacement content and the optional replacement content. Having to replace the content refers to some test data required for the transaction to perform successfully in the test environment, which part of the data cannot be replaced by production data on the premise that the transaction is successful. The optional replacement content refers to a portion of data that does not replace the production data in the message and does not cause the transaction to fail execution in the test environment. The preset message replacement rules depend on the replacement content and are different from each other, including but not limited to, for example, the replacement content is a transaction card number (TraCard), and the dependent replacement rules are replacement by card type (TraCard-1), replacement by card brand (TraCard-2), replacement by card number (TraCard-3), and the like. And if the replacing content is a transaction serial number (TraId), the attached replacing rule is to replace by a pure number (TraId-1), replace by a pure letter (TraId-2), replace by a number and a letter (TraId-3) and the like.

Step 022: and sending the replaced production message data to a test environment of the target service system to complete the automatic test of the target service system.

Specifically, the replaced production message data may be used as the test message data.

In order to further improve the reliability of the automated test, in an embodiment of the present application, after step 021, the method further includes:

step 001: and carrying out data encryption and signature calculation on the replaced production message data.

Specifically, the encryption and signature methods and rules are encryption and signature calculation methods and rules agreed among the acquirer, the payment channel and the card issuer.

Step 002: and sending the calculation result to a test environment of the target service system to complete the automatic test of the target service system.

Specifically, the calculation result may include encrypted production message data and a result obtained by signature calculation.

In order to facilitate the following fault analysis and maintenance of the service system, in an embodiment of the present application, after step 300, the method further includes:

step 400: and receiving an automatic test result of the target service system.

Specifically, the automated test results may include: one of a normal result, an abnormal result, and a failed result.

Step 500: obtaining the ratio of the times of normal results, the ratio of the times of abnormal results and the ratio of the times of failure results of each of a plurality of dimensions according to the automatic test result and a plurality of pre-stored historical automatic test results; the plurality of dimensions includes: the transaction type data and scene identification strings at different levels.

Specifically, the pre-stored historical automatic test result may be a result obtained by historical automatic testing of the service system; the automatic test result can be used as an automatic test result of each dimension, and a historical automatic test result of each dimension can be obtained from a pre-stored historical automatic test result; for any dimension, such as a first-level scene identification string, the normal result frequency ratio, the abnormal result frequency ratio and the failure result frequency ratio corresponding to the dimension can be obtained according to the automatic test result and the multiple historical automatic test results of the dimension. After step 500, the automated test results may be stored locally at the business system automated test equipment as historical automated test results.

In terms of software, in order to avoid repeated scene testing, improve efficiency of automated testing of a service system, and further improve security of system operation, the present application provides an embodiment of an automated testing apparatus for a service system, which is used for implementing all or part of contents in the automated testing method for a service system, and referring to fig. 3, the automated testing apparatus for a service system specifically includes the following contents:

the receiving module 10 is configured to receive production message data of a target transaction.

And a generating module 20, configured to generate a multi-level scene identifier string according to the production packet data and a preset scene identifier generating rule.

And the test module 30 is configured to send the production packet data to a test environment of the target service system if the multi-level scene identifier strings respectively satisfy the executable conditions of the corresponding identifier strings, so as to complete an automated test of the target service system.

In an embodiment of the present application, the generating module includes:

The embodiment of the service system automation test apparatus provided in this specification may be specifically configured to execute the processing flow of the embodiment of the service system automation test method, and the functions of the embodiment are not described herein again, and reference may be made to the detailed description of the embodiment of the service system automation test method.

To further illustrate the present solution, the present application provides an application example of a service system automation test apparatus, referring to fig. 4, the service system automation test apparatus includes: the system comprises a loading module 1, a processing module 2, a signature module 3, an execution module 4, a statistical analysis module 5, a parameter maintenance module 6 and an information storage module 7, wherein the function realized by the loading module 1 can be equivalent to the function realized by the receiving module, the function realized by the processing module 2 can be equivalent to the function realized by the generating module, and the function realized by the execution module 4 can be equivalent to the function realized by the testing module.

Loading the production message data of the third-party fast payment transaction into the system through the loading module 1, performing transaction and scene current-limiting processing on the production message data of each third-party fast payment transaction through the processing module 2 in combination with the parameter maintenance module 6, and then replacing the data in combination with the replacement rule stored in the information storage module 7; after the replacement is finished, the data is encrypted through the signature module 3, and signature data used for testing is calculated; the execution module 4 carries out automatic execution on the current data and writes an execution result into the information storage module 7; the statistical analysis module 5 analyzes and processes the execution result and displays the result to the tester, and updates the case base and the scene base by applying the execution information, which is used as an important basis for the tester to control the test scene and arrange the test plan. The specific description is as follows:

the loading module 1 is used for reading the production message data of the third-party fast payment transaction, backing up the production message data to the information storage module 7, and sending the production message data to the processing module 2 for production message processing.

The processing module 2 is configured to receive the production message data sent by the loading module 1, perform transaction and scene current-limiting processing on the current production message data in combination with the parameter maintenance module 6, then replace the data in combination with a replacement rule stored in the information storage module 7, name each transaction synchronously, write a transaction naming result into a configuration file, and after the transaction processing is finished, write the processed data into the information storage module 7 by the processing module 2.

The signature module 3 reads the processed production message data stored in the information storage module 7 by reading the transaction naming result in the configuration file, encrypts and signs the production message data, and writes the calculation information into the information storage module 7 after the calculation is finished.

The execution module 4 reads the encrypted and signed transaction information stored in the information storage module 7, namely the processed production message data, by reading the transaction naming result in the configuration file, automatically sends a test transaction to test a card issuing institution tested system, namely a test environment, receives response information of the card issuing institution tested system, and writes the response information into the information storage module 7.

And the statistical analysis module 5 is used for reading the transaction response result information stored in the information storage module 7, processing the information and displaying the transaction response result information to a tester.

And the parameter maintenance module 6 is used for maintaining the current limiting rules such as the transaction type execution range and the scene category parameters, the replacement data range, the rules of the replacement data, the replacement data content database and other parameters, and the maintained parameter content is stored in the information storage module 7.

And the information storage module 7 is used for storing the parameter content and the replacement rule maintained by the parameter maintenance module 6 and simultaneously recording the contents of the transaction information, the response information and the like of the processing module 2, the signature module 3 and the execution module 4.

As shown in fig. 5, the loading module 1 is composed of a loading information reading unit 11, a loading information storing unit 12, and a loading information transmitting unit 13. Wherein:

load information reading unit 11: the loading information reading unit is used for reading the production message data of the third-party fast payment transaction and pushing the production message data to the loading information storage unit 12.

Load information storage unit 12: the transaction backup storage unit 77 is used for receiving the production message data read by the loading information reading unit 11, writing the production message data into the information storage module 7, and sending the production message data to the loading information sending unit 13.

The loading information transmitting unit 13: for receiving the production message data pushed by the loading information storage unit 12 and sending the production message data to the processing information receiving unit 21.

As shown in fig. 6, the processing module 2 is composed of six parts, namely a processing information receiving unit 21, a transaction identifying unit 22, a scene identifying unit 23, a data replacing unit 24, a processing information pushing unit 25 and a configuration file generating unit 26, wherein:

the processing information receiving unit 21: for receiving the production message data sent by the loading information sending unit 13.

The transaction identification unit 22: the transaction type identification module is used for identifying the transaction type of the current production message data, judging whether the current transaction conforms to the transaction type current-limiting rule set by the transaction type execution storage unit 73, if not, rejecting the current transaction, if so, judging whether the current transaction type reaches the upper limit of the execution times, and if so, rejecting the current transaction.

The scene recognition unit 23: the system is used for identifying the scene of the current transaction, the identification rules are divided into multi-stage rules, the first-stage scene identification string and the second-stage scene identification string of the current transaction are correspondingly identified according to the rules of the scene library maintenance unit 62, the scene current-limiting identification string and the execution times set by the test scene library storage unit 71 stored in the information storage module are read, whether the current scene accords with the scene current-limiting identification string is judged, if the current scene does not accord with the scene current-limiting identification string, the current transaction is rejected, if the current scene does not accord with the scene current-limiting identification string, whether the transaction reaches the upper limit of the execution times is further judged. And if the current transaction meets the condition, adding 1 to the accumulated execution times of the corresponding current-limiting scene.

The data replacement unit 24: according to the replacement scope and the replacement content scope and the replacement implementation rule set by the replacement scope and rule storage unit 74, the data replacement unit 24 performs data replacement on the current transaction according to the rule. The replacement data includes, but is not limited to, transaction date, transaction time, transaction serial number, transaction card number, and transaction identity information, among others.

The processing information pushing unit 25: and the transaction backup storage unit 77 is used for pushing the production message data after the replacement is completed to the information storage module 7.

The profile generation unit 26: the system is used for naming the trades corresponding to the replaced production message data in sequence and generating a trading naming result into a configuration file.

As shown in fig. 7, the signature module 3 is composed of a signature information reading unit 31, a signature generating unit 32, and a signature information pushing unit 33. Wherein:

the signature information reading unit 31 is configured to select the production message data stored in the information storage module according to the transaction naming result in the configuration file generated by the processing module, and push the production message data to the signature generating unit 32.

Signature generation unit 32: for encrypting data and calculating signature for the production message data by receiving the production message data pushed by the signature information reading unit 31.

Signature information pushing unit 33: and the transaction backup storage unit 77 is used for sending the production message data and the encrypted signature information to the information storage module.

As shown in fig. 8, the execution module 4 is composed of three parts, namely, an execution information reading unit 41, an execution unit 42, and an execution information pushing unit 43. Wherein:

and the execution information reading unit 41 is configured to read the transaction naming result in the configuration file, read the encrypted and signed production message data from the information storage module according to the read transaction naming result, and push the production message data to the execution unit 42.

And the execution unit 42 is configured to receive the encrypted and signed production message data sent by the execution information reading unit 41, send the production message data to the tested system on the bank side of the card issuing organization, and synchronously receive response information of the tested system of the bank of the card issuing organization. After receiving the response result information, the response result information is sent to the execution information pushing unit 43, where the response result information includes, but is not limited to, success or failure in normal situations, and abnormal situations.

And the execution information pushing unit 43 is configured to receive the response result information pushed by the execution unit 42, send the response result information to the executed transaction result storage unit 76 of the information storage module 7, and send information such as the type of the transaction and the scene identification string to the test scene library storage unit 71 and the executed transaction type storage unit 73.

As shown in fig. 9, the statistical analysis module 5 is composed of a statistical information reading unit 51, a statistical information presentation unit 52 and a statistical information updating unit 53. Wherein:

the statistical information reading unit 51: and is configured to read the transaction response result information stored in the information storage module in the current batch, and push the transaction response result information to the statistical information display unit 52.

The statistical information presentation unit 52: by receiving the transaction response result information pushed by the statistical information reading unit 51, statistics is performed according to dimensions such as transaction types, transaction scenes, transaction cases and the like, the number of successful, failed and abnormal transaction strokes and proportion conditions are calculated, the transaction execution information is displayed to the tester, and meanwhile, the transaction execution information is pushed to the statistical information updating unit 53.

The statistical information updating unit 53: after receiving the transaction execution information pushed by the statistical information display unit 52, the transaction execution information is matched with the case library in the information storage module 7. If the matching is successful, updating the existing scene state, case state, execution time and the like, and if the matching is not successful, supplementing the transaction execution information into the case base and simultaneously supplementing the test case state. The transaction execution information includes, but is not limited to, transaction category, transaction scenario, transaction case, execution result of the transaction.

As shown in fig. 10, the parameter maintenance module 6 is composed of five parts, namely, an execution transaction parameter unit 61, a scene library maintenance unit 62, a data replacement range and rule unit 63, a replacement data information maintenance unit 64 and a configuration file maintenance unit 65. Wherein:

execution transaction parameters unit 61: the transaction type setting and maintaining range comprises but is not limited to all execution, third-party fast payment signing transaction, third-party fast payment transaction, third-party fast payment return transaction, third-party fast payment cash withdrawal transaction and the like, and meanwhile, the total execution times of each transaction type can be set.

Scene library maintenance unit 62: the method is used for maintaining the scene current limiting identification strings to be executed according to the scene current limiting rule, the scene current limiting identification strings can be in multiple stages according to the setting, the first-stage scene current limiting identification strings are formed by a string of character strings consisting of 0 and 1, the number of bits of the character strings is determined by the number of message fields of the transaction type, and the character strings are in one-to-one correspondence with the sequence of the message fields. And when the numerical value of a certain field is empty, the corresponding number of the scene character string corresponding to the field is 0, and if the numerical value of the certain field is not empty, the corresponding number of the scene character string corresponding to the field is 1, so that a scene character string is formed, and the total execution times of the scene character string is supported.

The secondary scene current-limiting identification string is composed of a string of numbers and letters, and the number of the character string is determined by the number of the message fields of the transaction type and is in one-to-one correspondence with the sequence of the message fields. The value of each character of the character string is that on the basis of the primary scene current limiting identification string, corresponding letters are selected for the numbers with partial identifications being 1 by referring to the secondary scene corresponding table. And supports the total number of executions of the scene string.

Message example:

< BisTp 01</BisTp > < IDTP 01</IDTP > < IDNO 11111111111111111X </IDNO > < TraD > < TraId > < PHONE 13388888888</PHONE > < TraTi 2020-12-02</TraTi > < TraCard >6888888888888888888</TraCard > Payment transaction </TraNa >

Corresponding to a first-level scene current-limiting identification string: 11101111

The current-limiting identification string corresponding to the secondary scene may be: AAF0AOAB, 111011AB

The scene library maintenance unit sends the scene current limiting identification string maintained by the tester to the test scene library storage unit 71 for storage.

Data replacement range and rule unit 63: the method is used for setting the content range to be replaced in the production transaction message and the rules to be followed during replacement. The range of the replacement content includes, but is not limited to, information such as date, card number, user information, transaction serial number and the like which must be replaced when the test transaction is executed, and information such as commodity category, merchant remark and the like which can be replaced according to the test requirement. Particularly after setting the range of the replacement content, the replacement rule is required to be set, including but not limited to card data type, card brand, card region, card length, etc. The data replacement range and rule unit transmits the replacement content range set by the tester and the rule to be followed at the time of replacement to the replacement range and rule storage unit 74 to store.

Replacement data information maintenance unit 64: for setting specific data information for replacement. The data information includes, but is not limited to, card data, date data, merchandise information data, serial number information, and the like. The replacement data information maintenance unit sends the specific data for replacement maintained by the tester to the replacement data information storage unit 75 for storage.

The profile maintenance unit 65: for manual maintenance of the profile content as required. The content of the configuration file is the range of transaction executed by the signature module and the execution module.

As shown in fig. 11, the information storage module 7 is composed of seven parts, i.e., a test scenario base storage unit 71, a test scenario base storage unit 72, an execution transaction type storage unit 73, a replacement range and rule storage unit 74, a replacement data information storage unit 75, an execution transaction result storage unit 76, and a transaction backup storage unit 77. Wherein:

test scenario library storage unit 71: the system is used for receiving and storing the scene current-limiting identification string and the corresponding current-limiting frequency information maintained by the scene library maintenance unit 62, receiving the transaction type and the scene identification string and other information sent by the execution information pushing unit 43, and accumulating the corresponding scene identification string frequency information.

Test case library storage unit 72: for storing inventory test case information and receiving update information sent by the statistical information update unit 53.

Execution transaction category storage unit 73: the transaction parameter unit 61 is configured to receive and store relevant information of the range of the transaction types to be executed, which is maintained by the transaction parameter unit 61, including but not limited to the transaction types and the enabling states of the transaction types, and receive information of the transaction types and the scene identification strings sent by the transaction information pushing unit 43, and accumulate corresponding transaction type frequency information.

Replacement range and rule storage unit 74: for receiving the replacement content range and the rules to be followed in replacing the data, which are maintained by the stored data replacement range and rules unit 63.

Replacement data information storage unit 75: for receiving and storing the replacement-required data information maintained by the replacement-data-information maintaining unit 64.

Execution transaction result storage unit 76: for receiving and storing the response result information sent by the execution information pushing unit 43.

Transaction backup storage unit 77: the transaction information pushed by the loading information storage unit 12, the processing information pushing unit 25, and the signature information pushing unit 33 is the production message data, and the storage format of the production message data in the transaction backup storage unit may be as shown in table 4.

TABLE 4

In order to further implement efficient automated testing of a service system, in combination with the above automated testing apparatus for a service system, the present application provides an application example of an automated testing method for a service system, which is described in detail below with reference to fig. 12:

step S101: setting current limiting parameters and loading production message data.

Specifically, the acquired production message data needs to be prepared before the test scene design and the test execution of the third-party fast payment related transaction are carried out. Meanwhile, the basic parameters of the transaction are maintained through the parameter maintenance module 6. The basic parameters include, but are not limited to, the current limiting transaction type, the scene current limiting identification string, the replacement content range, the replacement rule and the related replacement data of the current execution. After the parameters are set, the production message data is read by the loading information reading unit 11, and the production message data is backed up to the transaction backup storage unit 77 by the loading information storage unit 12, and the production message data is sent to the processing information receiving unit 21 of the processing module 2 while the backup is completed.

Step S102: message processing, transaction flow limiting and data replacement.

When the transaction passes to the transaction identification unit 22 in the processing module 2, the transaction type (BisTp) of the transaction is identified. If the transaction type of the current transaction meets the executable transaction type range maintained by the tester through the transaction execution parameter unit 61, the current transaction is released, and if the transaction type of the current transaction does not meet the executable transaction type range, the execution is rejected in the current transaction. The transaction type range includes, but is not limited to (0-full clearance, 1-short payment sign-up transaction, 2-short payment transaction, 3-third party short payment return transaction, 4-third party short payment cash withdrawal transaction, etc.).

For the transaction released by the transaction identification unit 22 in the processing module 2, the scene identification unit 23 performs scene identification on the scene identification string (ComBi) of the current transaction according to the scene correspondence rule to generate a primary scene identification string and a secondary scene identification string. If the scene identification string of the current transaction meets the scene current-limiting identification string and the execution times limit maintained by the tester through the scene library maintenance unit 62, the current transaction is released, meanwhile, the execution times of the current scene identification string is added by 1 in an accumulated manner, and if the scene identification string does not meet the execution times limit, the current transaction is rejected.

For the transaction released by the scene recognition unit 23 in the processing module 2, the data replacement unit 24 replaces the production message data of the current transaction. The range of the replacement content and the replacement rule are set and maintained by the data replacement range and rule unit 63. The range of the replacement content includes, but is not limited to, the transaction serial number (TraId), the transaction date (TraTi), the transaction card number (TraCard), the transaction amount (TraAm), etc. in the message. Which is divided into the necessary replacement content and the optional replacement content. Having to replace the content refers to some test data required for the transaction to perform successfully in the test environment, which part of the data cannot be replaced by production data on the premise that the transaction is successful. The optional replacement content refers to a portion of data that does not replace the production data in the message and does not cause the transaction to fail execution in the test environment. The replacement rules depend on the replacement content to be different from each other, including but not limited to, for example, the replacement content being a transaction card number (TraCard), the dependent replacement rules being replacement by card category (TraCard-1), replacement by card brand (TraCard-2), replacement by card digit number (TraCard-3), and the like. And if the replacing content is a transaction serial number (TraId), the attached replacing rule is to replace by a pure number (TraId-1), replace by a pure letter (TraId-2), replace by a number and a letter (TraId-3) and the like.

The production message data that has been replaced by the data replacement unit 24 in the processing module 2 is pushed to the transaction backup storage unit 77 by the processing information pushing unit 25. The configuration file is synchronously generated by the configuration file generating unit 26. The profile content is the system name for each transaction. The system can automatically select the transaction to be executed according to the configuration file, and the tester can manually configure the file to select the transaction execution range according to the requirement.

Step S103: message encryption and signature calculation.

The signature information reading unit 31 in the signature module 3 reads the corresponding production message data according to the content sequence of the configuration file, and the signature generating unit 32 performs data encryption and signature calculation on the production message data. The calculation result is sent to the transaction backup storage unit 77 by the signature information push unit 33. The encryption and signature method and rule are encryption and signature calculation methods and rules agreed among the acquirer, the payment channel and the card issuer.

Step S104: and (4) carrying out automation.

The execution information reading unit 41 in the execution module 4 reads the corresponding transaction information according to the content sequence of the configuration file, the execution unit 42 automatically sends the tested system of the card issuing organization to test, and receives the response result information of the tested system. The system response result information under test is sent to the transaction backup storage unit 77 through the execution information pushing unit 43. The system response result information includes, but is not limited to, a transaction serial number (TraId), a transaction card number (TraCard), a response result information code (ReCode), a response result information code description (ReCodeIn), and the like.

Step S105: and (6) carrying out data statistical analysis.

The statistical information reading unit 51 in the statistical analysis module 5 performs statistical processing on the data information of the transaction executed this time according to the content of the configuration file. The data information includes, but is not limited to, transaction type (BisTp), scene identification string (ComBi), transaction serial number (TraId), transaction date (TraTi), transaction card number (TraCard), response result information code (ReCode), response result information code description (ReCodeIn), and the like. The statistical processing includes, but is not limited to, performing statistical calculation of transaction execution states in terms of a time dimension, a transaction type dimension, a scene dimension, and the like. The transaction information is displayed to the tester through the statistical information display unit 52 to provide test decision information for the tester, and the transaction information is matched with the stock scene library and the case library through the statistical information updating unit 53.

Step S106: and updating the case base.

As for the matching result of the statistical information updating unit 53, if the matching is successful, the transaction execution result, the transaction time, and the like are updated to the scene library and the case library in the information storage module 7; if the matching is not successful, the case base and the scene base are updated in a supplementing way, and the updated content comprises the execution result and the execution time of the transaction except the information of the scene, the case content and the like of the transaction.

According to the description, the method and the device for automatically testing the service system can avoid repeated scene testing, improve the efficiency of automatically testing the service system and further improve the safety of system operation; in particular, the transaction message can automatically replace test data and generate a test signature, the multiplexing of a production scene in a test environment can be realized, particularly, the problem that a third-party rapid payment transaction tester cannot know the actual message production condition through experience service can be solved, furthermore, the difficulty of separation of the test scene from the actual production use scene exists during the design of the test scene and the case, the effectiveness of the test scene can be effectively ensured, and simultaneously, by setting the target transaction type, the target test scene and the number of strokes, the transaction type and the test scene of the test message are effectively limited, the invalid repeated execution of the similar transaction is rejected, the resource investment can be greatly saved, the bank side system of the card issuing institution is fully and effectively covered in the scene, and the safety and the stability of the bank side system of the card issuing institution under the condition of ultrahigh transaction amount can be powerfully guaranteed; in addition, the test scenes extracted through production and transaction can be automatically supplemented and preserved in the test scenes and the test case library, the loopholes of the test scenes and cases are filled, the test assets are enriched, and important decision bases are provided for setting test plans and implementing tests.

In terms of hardware, in order to avoid repeated scenario testing, efficiency of automated testing of a service system is improved, and further safety of system operation is improved, the present application provides an embodiment of an electronic device for implementing all or part of contents in the automated testing method of a service system, where the electronic device specifically includes the following contents:

a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the communication interface is used for realizing information transmission between the service system automatic testing device, the user terminal and other related equipment; the electronic device may be a desktop computer, a tablet computer, a mobile terminal, and the like, but the embodiment is not limited thereto. In this embodiment, the electronic device may be implemented with reference to the embodiment for implementing the method for automatically testing the service system and the embodiment for implementing the apparatus for automatically testing the service system in the embodiments, and the contents thereof are incorporated herein, and repeated details are not repeated here.

Fig. 13 is a schematic block diagram of a system configuration of an electronic device 9600 according to an embodiment of the present application. As shown in fig. 13, the electronic device 9600 can include a central processor 9100 and a memory 9140; the memory 9140 is coupled to the central processor 9100. Notably, this fig. 13 is exemplary; other types of structures may also be used in addition to or in place of the structure to implement telecommunications or other functions.

In one or more embodiments of the present application, the business system automation test function can be integrated into the central processor 9100. The central processor 9100 may be configured to control as follows:

step 100: and receiving the production message data of the target transaction.

As can be seen from the above description, the electronic device provided in the embodiment of the present application can avoid repeated scene tests, improve the efficiency of the automatic test of the service system, and further improve the safety of system operation.

In another embodiment, the service system automation test apparatus may be configured separately from the central processor 9100, for example, the service system automation test apparatus may be configured as a chip connected to the central processor 9100, and the service system automation test function is realized by the control of the central processor.

As shown in fig. 13, the electronic device 9600 may further include: a communication module 9110, an input unit 9120, an audio processor 9130, a display 9160, and a power supply 9170. It is noted that the electronic device 9600 also does not necessarily include all of the components shown in fig. 13; in addition, the electronic device 9600 may further include components not shown in fig. 13, which can be referred to in the prior art.

As shown in fig. 13, a central processor 9100, sometimes referred to as a controller or operational control, can include a microprocessor or other processor device and/or logic device, which central processor 9100 receives input and controls the operation of the various components of the electronic device 9600.

The memory 9140 can be, for example, one or more of a buffer, a flash memory, a hard drive, a removable media, a volatile memory, a non-volatile memory, or other suitable device. The information relating to the failure may be stored, and a program for executing the information may be stored. And the central processing unit 9100 can execute the program stored in the memory 9140 to realize information storage or processing, or the like.

The input unit 9120 provides input to the central processor 9100. The input unit 9120 is, for example, a key or a touch input device. Power supply 9170 is used to provide power to electronic device 9600. The display 9160 is used for displaying display objects such as images and characters. The display may be, for example, an LCD display, but is not limited thereto.

The memory 9140 can be a solid state memory, e.g., Read Only Memory (ROM), Random Access Memory (RAM), a SIM card, or the like. There may also be a memory that holds information even when power is off, can be selectively erased, and is provided with more data, an example of which is sometimes called an EPROM or the like. The memory 9140 could also be some other type of device. Memory 9140 includes a buffer memory 9141 (sometimes referred to as a buffer). The memory 9140 may include an application/function storage portion 9142, the application/function storage portion 9142 being used for storing application programs and function programs or for executing a flow of operations of the electronic device 9600 by the central processor 9100.

The memory 9140 can also include a data store 9143, the data store 9143 being used to store data, such as contacts, digital data, pictures, sounds, and/or any other data used by an electronic device. The driver storage portion 9144 of the memory 9140 may include various drivers for the electronic device for communication functions and/or for performing other functions of the electronic device (e.g., messaging applications, contact book applications, etc.).

The communication module 9110 is a transmitter/receiver 9110 that transmits and receives signals via an antenna 9111. The communication module (transmitter/receiver) 9110 is coupled to the central processor 9100 to provide input signals and receive output signals, which may be the same as in the case of a conventional mobile communication terminal.

Based on different communication technologies, a plurality of communication modules 9110, such as a cellular network module, a bluetooth module, and/or a wireless local area network module, may be provided in the same electronic device. The communication module (transmitter/receiver) 9110 is also coupled to a speaker 9131 and a microphone 9132 via an audio processor 9130 to provide audio output via the speaker 9131 and receive audio input from the microphone 9132, thereby implementing ordinary telecommunications functions. The audio processor 9130 may include any suitable buffers, decoders, amplifiers and so forth. In addition, the audio processor 9130 is also coupled to the central processor 9100, thereby enabling recording locally through the microphone 9132 and enabling locally stored sounds to be played through the speaker 9131.

An embodiment of the present application further provides a computer-readable storage medium capable of implementing all the steps in the service system automation test method in the foregoing embodiment, where the computer-readable storage medium stores a computer program, and the computer program, when executed by a processor, implements all the steps in the service system automation test method in the foregoing embodiment, for example, when the processor executes the computer program, the processor implements the following steps:

step 100: and receiving the production message data of the target transaction.

As can be seen from the above description, the computer-readable storage medium provided in the embodiment of the present application can avoid repeated scene tests, improve the efficiency of the automatic test of the service system, and further improve the security of system operation.

In the present application, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Reference is made to the description of the method embodiments.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The principle and the implementation mode of the present application are explained by applying specific embodiments in the present application, and the description of the above embodiments is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. An automated testing method for a business system, comprising:

receiving production message data of target transaction;

2. The method for automatically testing a business system according to claim 1, wherein the generating a multi-level scene identifier string according to the production message data and a preset scene identifier generation rule comprises:

3. The method according to claim 2, wherein if the transaction type data in the production packet data meets a preset executable transaction condition, generating a multi-level scene identifier string according to the production packet data and a preset scene identifier generation rule, comprises:

4. The method according to claim 1, wherein if the multi-level scene identifier strings respectively satisfy respective corresponding identifier string executable conditions, sending the production packet data to a test environment of a target service system to complete an automated test of the target service system, comprising:

5. The business system automation test method of claim 1, further comprising:

6. The business system automation test method of claim 5, further comprising, after the data replacement of the production message data:

7. The method according to claim 2, wherein after the step of sending the production packet data to a test environment of a target service system to complete the automated testing of the target service system if the multi-level scene identifier strings respectively satisfy the respective corresponding identifier string executable conditions, the method further comprises:

receiving an automatic test result of the target service system;

8. An automated testing device for a business system, comprising:

9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method for automated testing of a business system of any one of claims 1 to 7 when executing the program.

10. A computer-readable storage medium having stored thereon computer instructions, wherein the instructions, when executed, implement the business system automation testing method of any one of claims 1 to 7.