Test method and device of business system, equipment, storage medium and program product

Abstract

The invention provides a test method and device of a business system, equipment, a storage medium and a program product, relates to the technical field of test, and can solve the problem of low test efficiency of the business system. According to the specific technical scheme, after service demand information of a to-be-tested service is obtained, associated transaction data, obtained from an original service system, of the to-be-tested service can be converted, and target transaction data suitable for the to-be-tested service system is obtained. Therefore, the execution process and the execution sequence of the plurality of execution steps required by the to-be-tested business can be constructed according to the business demand information of the to-be-tested business and the target transaction data, and the combined transaction process of the to-be-tested business is obtained. In this way, the combined transaction process can be executed in the to-be-tested business system according to the execution sequence of the multiple execution steps, and account following consistency of the to-be-tested business system and the original business system is verified based on the obtained execution result. The test efficiency of the service system is improved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of testing, and in particular, to a testing method, device, and equipment for a business system, a storage medium, and a program product. BACKGROUND

[0002] Before a new system (such as an Internet Technology (IT) system) goes online, comprehensive function and performance testing, stress testing, and stability testing need to be performed to expose possible transaction defects and system vulnerabilities of the new system in advance, so as to reduce the risk of system switching on business.

[0003] Generally, to ensure the normal function of the new system, the new system needs to be tested in an artificial manner. However, due to high labor costs and incomplete coverage of scenarios, the efficiency is relatively low. SUMMARY

[0004] Embodiments of the present application provide a testing method, device, and equipment for a business system, a storage medium, and a program product, which can improve the testing efficiency of the business system.

[0005] To achieve the above-mentioned purpose, embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a testing method for a business system is provided. The method includes: after obtaining business requirement information of a to-be-tested business, converting associated transaction data of the to-be-tested business obtained from an original business system to obtain target transaction data suitable for a to-be-tested business system. In this way, the execution flow and execution order of a plurality of execution steps required by the to-be-tested business can be constructed according to the business requirement information of the to-be-tested business and the target transaction data, and a combined transaction flow of the to-be-tested business is obtained. In this way, the combined transaction flow can be executed in the to-be-tested business system according to the execution order of the plurality of execution steps, and the accounting consistency between the to-be-tested business system and the original business system is verified based on the obtained execution result.

[0007] Based on the business requirement information of the to-be-tested business acquired, the associated transaction data of the to-be-tested business acquired from the original business system can be converted to obtain target transaction data applicable to the to-be-tested business system. In this way, the test device can construct the execution flow and the execution order of the multiple execution steps required by the to-be-tested business according to the business requirement information of the to-be-tested business and the target transaction data, and obtain the combined transaction flow of the to-be-tested business. In this way, the test device can execute the combined transaction flow in the to-be-tested business system according to the execution order of the multiple steps, obtain the execution result capable of verifying the account consistency between the to-be-tested business system and the original business system, and thus detect whether the to-be-tested business system can realize the function of the original business system or whether there is a vulnerability in the process of realizing the function of the original business system. Thus, the test efficiency is improved.

[0008] In a possible implementation manner of the first aspect, the to-be-tested business includes multiple sub businesses, and the constructing the combined transaction flow according to the business requirement information and the target transaction data can specifically include: determining an execution function corresponding to each sub business from a preset function set, and determining business data required by each sub business from the target transaction data; establishing a calling relationship between the execution function corresponding to each sub business and the required business data to obtain the execution flow of the multiple steps, and determining the execution order of the multiple steps according to the dependency relationship between the multiple sub businesses. In this way, the combined transaction flow of the to-be-tested business can be obtained. The execution function corresponding to one sub business implements the execution flow of the sub business by calling the business data required by the sub business.

[0009] Based on the implementation manner, the execution function corresponding to each sub business is selected from the execution function set, and the data required by the sub business is selected from the target transaction data. In this way, the execution flow of the execution step corresponding to the sub business can be constructed, and the execution order of the multiple steps can be determined according to the dependency relationship between the multiple sub businesses. This is simple and convenient.

[0010] In a possible implementation manner of the first aspect, the method can further include: mapping the transaction results of the follow-up transaction threads obtained by sequentially connecting the plurality of execution steps to the thread shared variable to obtain a data shared domain. The data shared domain includes the second execution result obtained by sequentially connecting the plurality of execution steps in the original business system and an execution precondition of each execution step. The execution precondition can include that an amount of transaction data required for executing the execution step supports the execution step and / or a transaction account corresponding to the execution step is in a normal state. In this way, the execution precondition corresponding to each execution step can be obtained from the data shared domain before the combined transaction process is executed according to the execution order. For each execution step, if the execution environment of the execution step meets the corresponding execution precondition, the execution process of the execution step is executed; if the execution environment of the execution step does not meet the corresponding execution precondition, the execution process of the execution step is stopped.

[0011] Based on the implementation manner, for each execution step, before the execution step is executed, the transaction environment of the execution step can be verified based on the execution precondition corresponding to the execution step. If the transaction environment of the execution step meets the corresponding execution precondition, the execution process of the execution step is executed, which avoids the situation that the execution step is still executed when the data in the to-be-tested business system does not meet the execution precondition, resulting in execution failure, and thus the resources of the test device are wasted.

[0012] In a possible implementation manner of the first aspect, the method can further include: for each execution step, after the execution process of the execution step is executed, the second execution result corresponding to the execution step can be obtained from the data shared domain. In this way, if the first execution result is consistent with the second execution result, it is determined that the account balance of the to-be-tested business system is consistent with that of the original business system. If the first execution result and the second execution result are inconsistent, it is determined that the account balance of the to-be-tested business system is inconsistent with that of the original business system.

[0013] Based on the implementation manner, for each execution step, after the execution step is executed, the execution result of the execution step can be verified based on the execution precondition corresponding to the execution step. If the execution result of the execution step meets the corresponding execution precondition, it indicates that the to-be-tested business system can operate normally, so that the to-be-tested business can be verified, and the situation that the to-be-tested business system continues to operate when an operation exception occurs, thereby affecting the use of the user, is avoided.

[0014] In a possible implementation manner of the first aspect, the method can further include: obtaining special business requirement information of a target object; the target object is one of a plurality of test objects included in the to-be-tested business; obtaining a transaction sequence corresponding to the target object from the configuration information of the original business system, and determining an execution flow of an execution step corresponding to the target object according to the special business requirement information and the transaction sequence; configuring a verification rule for the target object; the verification rule includes a pre-verification rule and a post-verification rule, the pre-verification rule is used to verify execution flows of a plurality of steps included in the special combined transaction flow before the special combined transaction flow is executed, and the post-verification rule is used to verify an execution result of the special combined transaction flow; executing the execution flow of the execution step of the target object in the to-be-tested business system, and verifying the execution step and the execution result of the target object by using the verification rule.

[0015] Based on the implementation manner, for an object with special requirements, a special combined execution flow and a verification rule can be set for the object, and flexibility and scalability of the to-be-tested business system are increased.

[0016] In a possible implementation manner of the first aspect, the method can further include: mapping a plurality of transaction fields in the original business system to transaction fields of the to-be-tested business system to obtain a transaction field mapping relationship between the original business system and the to-be-tested business system; determining a number of a newly-added transaction field in the to-be-tested business system based on a number determination manner and the transaction field mapping relationship; the number determination manner includes: manually setting a field, and determining according to a transaction field similar to a target transaction field, the target transaction field being one in the to-be-tested business system.

[0017] Based on the implementation manner, by mapping the fields in the original business system to the fields in the to-be-tested business system, a conversion relationship between the to-be-tested business system and the original business system can be constructed, and for the newly-added transaction field in the to-be-tested business system, a number of the newly-added transaction field can be obtained by a manual manner or according to other transaction fields, and the number is simple and convenient to determine.

[0018] In a possible implementation manner of the first aspect, the method further can include: constructing a target base class, the target base class including a plurality of basic functions required for transaction execution; selecting, according to a transaction type supported by the to-be-tested system, a plurality of basic functions matched with each transaction type from the target base class, and combining the plurality of basic functions to obtain an execution function corresponding to the transaction type, to obtain the preset execution function set; and the preset execution function set including execution functions corresponding to a plurality of transaction types. In this way, the execution function corresponding to each sub-business can be determined from the preset execution function set according to the transaction type of each sub-business.

[0019] Based on the implementation manner, by constructing a general function set, for each business subsequently, a suitable execution function can be selected from the function set, which is simple and convenient.

[0020] In the second aspect, a testing device of a business system is provided, which includes: an acquisition module configured to acquire business requirement information of a to-be-tested business. A conversion module is configured to convert associated transaction data of the to-be-tested business acquired from an original business system to obtain target transaction data applicable to the to-be-tested business system. A construction module is configured to construct an execution flow and an execution order of a plurality of execution steps required by the to-be-tested business according to the business requirement information and the target transaction data, to obtain a combined transaction flow of the to-be-tested business. An execution module is configured to execute the combined transaction flow in the to-be-tested business system according to the execution order to obtain a first execution result, and verify the account consistency between the to-be-tested business system and the original business system according to the first execution result.

[0021] In the third aspect, a testing device is provided, which includes a memory and at least one processor. The memory is in communication connection with the processor. The memory is configured to store computer program code, the computer program code including computer instructions. When the processor executes the computer instructions, the testing device executes the method as described in the first aspect and any possible implementation manner thereof.

[0022] In the fourth aspect, an embodiment of the present application provides a computer readable storage medium, which stores computer instructions. When the computer instructions are executed by a processor, the method as described in the first aspect and any possible implementation manner thereof is implemented.

[0023] In the fifth aspect, an embodiment of the present application provides a computer program product, which, when running on a computer / being executed by a processor of a computer, implements the method as described in the first aspect and any possible implementation manner thereof. The computer can be the testing device as described in the first aspect and any possible implementation manner thereof.

[0024] It can be understood that the beneficial effects achieved by the test device of the business system according to the second aspect, the test equipment according to the third aspect, the computer readable storage medium according to the fourth aspect, and the computer program product according to the fifth aspect can refer to the beneficial effects in the first aspect and any possible implementation manner thereof, and details are not described herein. BRIEF DESCRIPTION OF DRAWINGS

[0025] Figure 1 A structural schematic diagram of a test system provided by an embodiment of the present application is shown in the figure;

[0026] Figure 2 A flowchart of a test method of a business system provided by an embodiment of the present application is shown in the figure;

[0027] Figure 3 A flowchart of another test method of a business system provided by an embodiment of the present application is shown in the figure;

[0028] Figure 4 A combined transaction flow diagram of a business to be tested provided by an embodiment of the present application is shown in the figure;

[0029] Figure 5 A flowchart of another test method of a business system provided by an embodiment of the present application is shown in the figure;

[0030] Figure 6 A flowchart of another test method of a business system provided by an embodiment of the present application is shown in the figure;

[0031] Figure 7 A flowchart of another test method of a business system provided by an embodiment of the present application is shown in the figure;

[0032] Figure 8 A flowchart of a preset execution function construction method provided by an embodiment of the present application is shown in the figure;

[0033] Figure 9 A diagram of a business to be tested provided by an embodiment of the present application is shown in the figure;

[0034] Figure 10 A diagram of another business to be tested provided by an embodiment of the present application is shown in the figure;

[0035] Figure 11 A flowchart of another test method of a business system provided by an embodiment of the present application is shown in the figure;

[0036] Figure 12 A structural schematic diagram of a service design based on an abstract class and a combination mode provided by an embodiment of the present application is shown in the figure;

[0037] Figure 13 A diagram of a business extension provided by an embodiment of the present application is shown in the figure;

[0038] Figure 14 A structural schematic diagram of a test device provided in an embodiment of the present application is shown in FIG. 1.

[0039] Figure 15 A structural schematic diagram of a test device provided in an embodiment of the present application is shown in FIG. 1. DETAILED DESCRIPTION

[0040] Hereinafter, the terms "first" and "second" are used only for the purpose of description, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first" and "second" can explicitly or implicitly include one or more of the features. In the description of the embodiments, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0041] The exemplary embodiments will be described in detail below with reference to the drawings. In the following description, the same numbers are used to represent the same elements in different drawings, unless otherwise specified. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with the present application. Rather, they are merely examples of devices and methods consistent with some aspects of the present application, as detailed in the appended claims.

[0042] In the technical solutions provided in the embodiments of the present application, the collection, storage, use, processing, transmission, provision and disclosure of information such as financial data or user data comply with relevant laws and regulations and do not violate public order and good customs.

[0043] It should be noted that in the embodiments of the present application, some existing industry solutions such as software, components, models, etc. may be mentioned, which should be considered as exemplary, and the purpose is only to illustrate the feasibility of the implementation of the technical solutions of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0044] As known from the background art, in order to determine that the new system can operate normally, before the new system goes online, the new system needs to be tested in multiple aspects (such as stress testing, performance testing, stability testing, etc.). Even if the function verification of the test environment is normal, it is necessary to verify in advance whether the configurations of the new system in the quasi-production environment are correct, so as to exclude risks in advance.

[0045] Therefore, in the switching stage of the old system and the new system, in order to ensure smooth transition, it is necessary to run the new system and the old system at the same time, and balance the traffic between the new system and the old system.

[0046] In addition, before the new system goes online, a high-load scenario of the formal production environment needs to be simulated to ensure that the new system can withstand real business pressure and detect the stability and recovery capability of the new system.

[0047] In addition, the account consistency between the new system and the old system needs to be verified in advance without interfering with the production environment.

[0048] In view of this, the embodiments of the present application provide a testing method, which can forward the production transactions of the old system to the new system and test the account consistency between the new system and the old system. In this way, whether the function of the new system can meet the demand can be detected.

[0049] In the embodiments of the present application, the old system can also be referred to as an original system or an original business system. That is, the old system is a system that needs to be replaced. The new system can be referred to as a system to be put online, a system to be tested, a system to be tested, and the like. That is, the new system is a system that needs to be put online to replace the old system.

[0050] The method provided by the embodiments of the present application will be described below with reference to the accompanying drawings.

[0051] In an example, as shown in Figure 1 , a testing system provided by the embodiments of the present application can include a testing device, a first server and a second server. The testing device is in communication connection with the first server and the second server respectively.

[0052] The first server runs an original business system, and the second server runs a business system to be tested.

[0053] The business system (including the original business system and the business system to be tested) involved in the embodiments of the present application can be a business system of multiple industries, for example, a business system of the financial industry (such as a business system of a bank, a business system of a securities center, etc.), or a business system of the Internet industry (such as a business system of a communication operator, a business system of a device manufacturer, etc.). Of course, it can also be a business system of other industries, which is not limited by the embodiments of the present application.

[0054] The testing method provided by the embodiments of the present application will be described below with reference to the accompanying drawings. The actions and terms involved in the embodiments of the present application can be mutually referenced and are not limited. The actions involved in the embodiments of the present application are only an example, and other names can also be used in specific implementation, such as: “include” described in the embodiments of the present application can be replaced by “carry” or “carry” and the like.

[0055] Figure 2 The testing method provided by the embodiments of the present application is applied to Figure 1 the testing device, and the method comprises:

[0056] S201, obtain service requirement information of a to-be-tested service.

[0057] The to-be-tested service can be a service supported by a to-be-tested service system, for example, a transaction service such as a transfer service or a withdrawal service, or a batch service. The service requirement information of the to-be-tested service can refer to an operation required to be performed by the service supported by the to-be-tested service system. For example, the service requirement information can include user requirements, system requirements, and scenario requirements (such as a single transaction, a combined transaction, and message conversion).

[0058] In a possible implementation, before the to-be-tested service system is put into operation or during a trial operation of the to-be-tested service (the original service system is also in an online state), in response to a test operation or an operation of performing a service, a test device can obtain the service requirement information of the to-be-tested service.

[0059] The test operation can refer to logging in a test account in the to-be-tested service system and simulating an operation of performing a service. The operation of performing a service can refer to logging in a real account in the to-be-tested service system and performing a corresponding operation (such as a transfer operation or a storage operation) according to user requirements.

[0060] In an application scenario, taking the to-be-tested service system as a bank service system and the to-be-tested service as a transfer service as an example, the user requirements are to transfer a amount of the first account to the second account, and the corresponding system requirements are to perform a transfer of the amount of the first account and the second account and to increase the amount of the second account by the amount. That is, the service requirement information of the to-be-tested service system can refer to a requirement to perform a transfer service according to user requirements. The corresponding operation is to reduce the amount of the first account by the amount of the user requirements and to increase the amount of the second account by the corresponding amount.

[0061] S202, convert the associated transaction data of the to-be-tested service obtained from the original service system to obtain target transaction data applicable to the to-be-tested service system.

[0062] The associated transaction data of the to-be-tested service can include a transaction message corresponding to the to-be-tested service. The transaction message can be used to indicate or carry data related to the to-be-tested service. For example, the transaction message corresponding to the transfer service can include a message indicating that a preset amount is deducted from the transfer account and a message indicating that the amount of the receiving transfer account is increased by the preset amount.

[0063] In the embodiments of the present application, since the functions and background program codes in the original business system and the to-be-tested business can be different, the fields and field values included in the message also change. Therefore, in order to ensure that the to-be-tested system can implement the functions of the original business system, the associated transaction data in the original business system can be converted to obtain target transaction data for the to-be-tested business system.

[0064] In an example, taking the to-be-tested business system as a bank business system and the to-be-tested business as a withdrawal business as an example, the test device can obtain the transaction message related to the withdrawal business from the original business system, and convert the account field, the account name field and the transfer amount field in the transaction message to fields supported or identifiable by the to-be-tested business system, and determine the values of the fields in the to-be-tested business system.

[0065] For example, the fields included in the transaction message corresponding to the withdrawal business in the original business system and the corresponding field values are shown in Table 1. The fields included in the transaction message corresponding to the withdrawal business in the to-be-tested business system are shown in Table 2.

[0066] Table 1

[0067] Field Field Meaning Field Value Op_ID Transaction Business A2020A107 GRZH Personal Account 2011XX2023 Drw_Amt Withdrawal Amount XXX TQFS Withdrawal Method AA

[0068] Table 2

[0069]

[0070]

[0071] In combination with Table 1 and Table 2, the test device can convert Op_ID to tq_ID, convert GRZH to grzh, convert Drw_Amt to tqje, and convert TQFS to tqfs. In this way, the fields in the withdrawal message of the original business system can be converted to the fields in the withdrawal message of the to-be-tested business system. After obtaining the fields in the withdrawal message of the to-be-tested business system, the field values of each field can be determined based on the field value determination mode. For details, reference can be made to the following embodiments, which will not be described here.

[0072] S203, constructing an execution flow and an execution order of a plurality of execution steps required by the to-be-tested business system according to the business requirement information and the target transaction data, to obtain a combined transaction flow of the to-be-tested business.

[0073] The to-be-tested service includes a plurality of sub-services. For example, the to-be-tested service can include services corresponding to a plurality of test accounts, and each test account corresponds to a sub-service. For another example, the to-be-tested service can include a plurality of different services, and the plurality of services are associated with each other. For example, the to-be-tested service can be an account opening service, and the account opening service can include a user registration service, an account allocation service, a permission setting service, and the like.

[0074] The combined transaction process can include an execution process and an execution order of a plurality of execution steps. The execution process of the execution step can refer to running an execution function corresponding to the execution step and calling related service data. The execution order of the plurality of execution steps can refer to a dependency relationship of the plurality of execution steps, for example, input data required by a certain execution step is output data of a previous execution step.

[0075] In a possible implementation, an execution function corresponding to each sub-service is determined from a preset execution function set, and service data required by each sub-service is determined from target transaction data. A calling relationship between the execution function corresponding to each sub-service and the required service data is established to obtain an execution process of a plurality of steps, and an execution order of the plurality of steps is determined according to a dependency relationship between the plurality of sub-services.

[0076] The preset execution function set can include a plurality of execution functions, and one execution function can execute one service, or at least one service function can be implemented through the execution function. For example, the execution function corresponding to a sub-service can implement an execution process of an execution step of the sub-service by calling service data required by the sub-service.

[0077] In an example, the to-be-tested service includes a plurality of services corresponding to a plurality of test accounts, and the service corresponding to the test account is a transfer service. The execution function corresponding to the transfer service can implement a transfer operation. For example, the execution function corresponding to the transfer service can be a function or program code compiled by a maintenance personnel. The test device can run the program code corresponding to the transfer service to implement the transfer function. The service data required by the transfer service can include data such as a transfer account and a transfer account name, a transfer amount, a receiving account and a receiving transfer account, a transfer mode, and the like.

[0078] In an application scenario, one execution function can include multiple sub-functions, or the program code corresponding to one execution function can include multiple sub-code blocks, and the multiple sub-functions or sub-code blocks can collectively implement a transfer function. The test device can obtain at least one execution function required for a transfer service from a preset execution function set, obtain service data required for the transfer service from an original service system, and configure the service data required for the transfer service into the at least one execution function required for the transfer service. In this way, when the test device runs the at least one execution function in the to-be-tested service system, the service data required for the execution service can be called to execute the execution process corresponding to the transfer service.

[0079] In the application scenario, since the services corresponding to the multiple test accounts are in parallel, the execution order of the multiple steps of the to-be-tested service can be simultaneous execution of the multiple steps.

[0080] In another example, in a case where there is an association between the multiple sub-services of the to-be-tested service, the execution function corresponding to each sub-service is used to implement the function corresponding to the sub-service.

[0081] For example, the to-be-tested service is an account opening service, and the multiple sub-services of the account opening service can include a user registration service, an account allocation service, and a permission setting service. The test device can obtain an execution function capable of executing the user registration service, an execution function capable of executing the account allocation service, and an execution function of the permission setting service from a preset execution function set, and obtain service data required for the user registration service (such as registration field information and user information), service data required for the account allocation service (such as a bank of opening, a new account, an account type, and user information associated with the account), and service data required for the permission setting service (such as a transfer limit and account permission) from the target transaction data.

[0082] After obtaining the execution function corresponding to each sub-service and the required service data, the service data required for each sub-service can be written into the execution function corresponding to the sub-service to establish a calling relationship between the execution function corresponding to the sub-service and the required service data. In this way, the execution process of each execution step can be obtained.

[0083] Further, after obtaining the execution process of each execution step, the execution order of the multiple steps can be determined according to the dependency relationship between the multiple sub-services.

[0084] For example, the dependency relationship between the plurality of sub-services of the account opening service can be: after the user registration service is completed, the account allocation service is implemented based on the registration information of the user, and after the account allocation service is completed, the permissions of the account of the user are set, that is, the permission setting service is executed. That is, the output of the user registration service is the input of the account allocation service, and the output of the account allocation service is the input of the permission setting service. The execution order of the plurality of sub-services is: user registration service→account allocation service→permission setting service.

[0085] S204, in the to-be-tested business system, execute the combined transaction process according to the execution order of the plurality of execution steps to obtain a first transaction result.

[0086] Wherein, executing the combined transaction process according to the execution order of the plurality of execution steps can be executing the execution function corresponding to each sub-service according to the execution order or the dependency relationship of the plurality of sub-services of the to-be-tested business.

[0087] Wherein, the first transaction result can be the data change information after the to-be-tested business system executes the execution process of the plurality of steps. For example, the first transaction result corresponding to the transfer service can be that the change of the amount in the transfer account and the change of the amount in the receiving transfer account are matched after the execution process of the plurality of steps of the transfer service. For example, the amount decreased in the transfer account is consistent with the amount increased in the receiving transfer account. For example, the first transaction result corresponding to the account opening service can be that the account opening information is correct (the user name is correct, the allocated account does not coincide with the account of other users, etc.) after the execution process of the plurality of steps of the account opening service.

[0088] S205, verifying the account consistency of the to-be-tested business and the original business system according to the first execution result.

[0089] Wherein, the account consistency can be whether the execution result of the to-be-tested business in the to-be-tested business system is the same as the execution result in the original business system. For example, whether the actual data generated by the to-be-tested business is consistent with the account record in the original business system.

[0090] In a possible implementation, for each execution step, before executing the execution process of the execution step, the execution precondition corresponding to the execution step can be acquired, and in the case that the execution environment of the execution step meets the corresponding execution precondition, the execution process of the execution step is executed; in the case that the execution environment of the execution step does not meet the corresponding execution precondition, the execution process of the execution step is stopped.

[0091] In an example, the execution precondition can include that the transaction data required by the execution step supports the execution step and / or the transaction account corresponding to the execution step is in a normal state.

[0092] In one application scenario, taking the business to be tested, which includes a transfer business, as an example, the preconditions for the execution of the transfer business may include: the transaction amount is less than or equal to the account amount and / or the accounts of the transferring account and the receiving account are in normal status (e.g., not canceled, not restricted from transferring, etc.).

[0093] based on Figure 2 The proposed technical solution allows the testing equipment to transform the associated transaction data of the business under test obtained from the original business system after acquiring the business requirements information. This transformation yields target transaction data that the testing system can support and recognize. Based on the business requirements and target transaction data, the testing equipment can then construct the execution flow and sequence of multiple execution steps required for the business under test, resulting in a combined transaction flow. The testing equipment can then execute this combined transaction flow in the testing system according to the execution sequence of the multiple steps. This provides execution results that verify the consistency between the testing system and the original business system, thereby detecting whether the testing system can implement the functions of the original system or whether there are vulnerabilities in the implementation process. This significantly improves testing efficiency.

[0094] In some embodiments, such as Figure 3 As shown, the method provided in this application embodiment may further include:

[0095] S301. Map the transaction results of the tracking transaction thread to the thread-shared variable to obtain the data shared domain.

[0096] The tracking transaction thread is obtained by chaining multiple execution steps. The data sharing domain includes the second execution result obtained from the chained execution steps in the original business system, as well as the preconditions for each execution step. The preconditions for the execution step may include the transaction data required to execute the execution step, the execution step being supported, and / or the transaction account corresponding to the execution step being in a normal state.

[0097] In one possible implementation, to execute the business logic under test, a condition chain can be formed by concatenating the execution conditions of multiple steps. The transaction results of the tracking transaction thread are then stored in a thread-shared variable, resulting in a data shared domain. Based on this data shared domain, pre-verification and post-verification of the execution steps can be performed. In this way, before any step of the business logic under test, it can be verified whether that step should be executed.

[0098] In one example, such as Figure 4As shown, the combined transaction process can include an action chain, a condition chain, and a combined transaction chain. The action chain can include an execution transaction required to implement the to-be-tested business. The condition chain can include execution preconditions and execution postconditions corresponding to multiple steps of the to-be-tested business. The combined transaction chain can include an execution order of the multiple execution steps. For example, the execution order of the multiple execution steps is: step 1→step 2→…→step n. n is a positive integer.

[0099] In an example, the configuration code of the pre-execution condition can be:

[0100]

[0101] In the embodiments of the present application, the execution conditions (including execution preconditions and execution postconditions) corresponding to the execution steps can be in the format of a json configuration file to achieve flexible configuration of the conditions. The test device can also support resetting or modifying the execution conditions of the execution steps to achieve flexible setting of the execution conditions.

[0102] S302, before executing the combined transaction according to the execution order, obtaining, from the data sharing domain, an execution precondition corresponding to each execution step.

[0103] In an example, in combination with Figure 4 Before the execution process of the execution step 1 needs to be executed, the execution precondition of the execution step 1 can be obtained from the condition chain, and it is verified whether the execution environment of the execution step meets the execution precondition of the execution step 1.

[0104] The above S204 can specifically include:

[0105] S303, for each execution step, if the execution environment of the execution step meets the corresponding execution precondition, executing the execution process of the execution step.

[0106] The execution environment of the execution step includes transaction data required by the execution step in the to-be-tested business system and an account state corresponding to the execution step.

[0107] In combination with the execution precondition in the above S205, if the transaction data required by the execution step supports the execution step and / or the transaction account corresponding to the execution step is in a normal state, it is indicated that the execution environment of the execution step meets the corresponding execution precondition. For example, if the balance in the transfer account is greater than or equal to the preset balance, and / or the transfer account has the right to transfer and the supported transfer balance is greater than or equal to the preset balance, it is indicated that the execution environment of the execution step meets the corresponding execution precondition.

[0108] S304. If the execution environment of this execution step does not meet the corresponding preconditions, stop the execution process of this execution step.

[0109] Referring to the example in S205 above, if the amount in the transfer account is less than the preset amount, and / or the transfer account's permissions do not support transfers and / or the supported transfer amount is less than the preset amount, then the execution process of this execution step will be stopped.

[0110] based on Figure 3 The technical solution allows for the verification of the transaction environment for each execution step before execution, based on the corresponding preconditions. Only when the transaction environment of the execution step meets the corresponding preconditions will the execution process of that step be executed. This avoids the situation where the execution step fails due to the data in the business system under test not meeting the preconditions, thus wasting the resources of the testing equipment.

[0111] In some embodiments, such as Figure 5 As shown in the embodiments of this application, the method may further include:

[0112] S501. For each execution step, after executing the execution flow of that execution step, obtain the second execution result corresponding to that execution step from the data sharing domain.

[0113] The second execution result can be the result of executing this step in the original business system. Typically, the execution result in the original business system is a correct result or a result that meets the requirements.

[0114] In one example, after a certain execution step is completed in the business system under test, the test device can obtain the second execution result of that execution step from the data sharing domain.

[0115] Specifically, S205 mentioned above may include:

[0116] S502. If the first execution result is consistent with the second execution result, determine that the accounting of the business system under test is consistent with that of the original business system.

[0117] The first execution result being consistent with the second execution result can mean that the data change amount after performing a certain execution step in the to-be-tested business system is consistent with the data change amount after performing the execution step in the original business system. For example, for the same transfer business, the data change amount of the transfer account after performing the transfer step in the to-be-tested business system is consistent with the data change amount of the transfer account after performing the same transfer step in the original business system, and the data change amount of the receiving transfer account is also consistent, which indicates that the account balance of the to-be-tested business system is consistent with that of the original business system.

[0118] S503, in the case where the first execution result is inconsistent with the second execution result, determining that the account balance of the to-be-tested business system is inconsistent with that of the original business system.

[0119] For example, for the same transfer business, the data change amount of the transfer account after performing the transfer step in the to-be-tested business system is inconsistent with the data change amount of the transfer account after performing the same transfer step in the original business system, and / or the data change amount of the receiving transfer account is inconsistent, which indicates that the account balance of the to-be-tested business system is inconsistent with that of the original business system.

[0120] Further, in the case where the account balance of the to-be-tested business system is inconsistent with that of the original business system, the test device can output prompt information. The prompt information is used to prompt that the execution result of the to-be-tested business system is abnormal.

[0121] Based on the technical solution of the application, Figure 5 for each execution step, the execution result of the execution step can be verified based on the execution post-condition corresponding to the execution step after the execution step is performed, and in the case where the execution result of the execution step meets the corresponding execution post-condition, it is indicated that the to-be-tested business system can normally run, so that the to-be-tested business can be verified, and it is avoided that the to-be-tested business system continues to run when an abnormality occurs, thereby affecting the use of the user.

[0122] In some embodiments, as shown in Figure 6 the method provided by the application can further include:

[0123] S601, mapping a plurality of transaction fields in the original business system to transaction fields of the to-be-tested business system to obtain a transaction field mapping relationship between the original business system and the to-be-tested business system.

[0124] In an example, the original transaction data (also referred to as original message) in the original business system can be preliminarily processed based on a json configuration file to obtain transaction data in the to-be-tested business system, so as to realize data conversion between the original business system and the to-be-tested business system.

[0125] In one possible implementation, after obtaining multiple transaction fields from the original business system and multiple transaction fields from the business to be tested, the testing device can associate transaction fields with the same meaning to obtain a transaction mapping relationship.

[0126] In one application scenario, taking a banking business system as an example, the mapping relationship between the transaction fields in the original business system and the transaction fields in the business system to be tested can be shown in Table 3.

[0127] Table 3

[0128]

[0129]

[0130] In Table 3, the first and third columns are the field numbers.

[0131] S602. For newly added fields in the business system to be tested, determine the transaction fields used in each of the multiple execution steps based on the field determination method and the transaction field mapping relationship.

[0132] In one possible implementation, the testing equipment can determine the newly added transaction fields in the business system under test based on the mapping relationship between the transaction fields in the original business system and the business system under test. For the newly added transaction fields, the testing equipment can determine the number of the newly added transaction fields according to the numbering determination method.

[0133] The numbering determination method may include at least one of the following:

[0134] 1-1. Manually set the number of the transaction field.

[0135] In one example, for certain transaction fields in the business to be tested, if these fields do not exist in the original business system, then the labels for these transaction fields can be determined manually. For instance, referring to Table 3 above, fields such as center number, card number, and bank account type are newly added transaction fields in the business to be tested, but do not exist in the original business system. These fields can be manually assigned labels or fixed values ​​can be used.

[0136] 1-2. Determine based on transaction fields that are similar to the target transaction field.

[0137] The target field is one of multiple fields in the business system to be tested.

[0138] In one example, for certain fields in the business process under test, if the field does not exist in the original business system, it can be determined based on field values ​​in either the original business system or the business process under test that have a similarity greater than a threshold. For instance, referring to Table 3 above, the center number is a newly added field. The center number field can be determined based on fields related to the number in the business process under test. For example, if a field related to the number in the business process under test is a bank account number, the test device can determine the center number field based on the naming rules for bank account numbers (first letter of the pinyin). The type, card number, and bank account type can all be determined using the same method.

[0139] Of course, other methods can be used to determine this, for example, the result value of the previous execution step can be selected as the field number of the current execution step.

[0140] based on Figure 6 The technical solution maps fields from the original business system to fields in the business system under test, thus establishing a conversion relationship between the two systems. For newly added transaction fields in the business system under test, the number of the new transaction field can be determined manually or based on other transaction fields, which is simple and convenient.

[0141] In some embodiments, such as Figure 7 As shown in the embodiments of this application, the method may further include:

[0142] S701. Obtain the specific business requirements information of the target object.

[0143] The target object is one of several test objects included in the business to be tested. For example, the target object can be a special rule, a special user, etc. The special rule can be an anti-fraud rule, and the special business requirements information of a special user can be called the user's personalized business requirements, exclusive business requirements, etc.

[0144] In one example, for specific business scenarios, the test equipment can employ a factory design pattern for its design process. The test equipment can customize the processing flow corresponding to the specific business requirements based on the target object's needs and a particular transaction sequence.

[0145] S702. Obtain the transaction sequence corresponding to the target object from the configuration information of the original business system, and determine the execution flow of the execution steps corresponding to the target object based on the special business requirement information and the transaction sequence.

[0146] The transaction sequence corresponding to the target object can include a transaction field corresponding to the target object. Based on the transaction field, transaction data meeting the business requirement of the target object can be determined. For example, the target object is a test account, and the transaction data meeting the business requirement of the test account can include personal account information, bank account number, and the like. Details can be referred to S203, which will not be repeated here.

[0147] S703, configuring a verification rule for the target object.

[0148] The verification rule can include a pre-verification rule and a post-verification rule. The pre-verification rule is used to verify the execution flow of the multiple steps included in the special combination transaction process before the special combination transaction is executed, and the post-verification rule is used to verify the execution result of the special combination transaction process.

[0149] S704, executing the execution flow of the execution steps of the target object in the to-be-tested business, and verifying the execution steps and the execution result of the target object using the verification rule.

[0150] S704 can refer to the technical solutions of the above Figure 3 and Figure 4 , which will not be repeated here.

[0151] Based on the technical solutions of the above Figure 7 , for objects with special requirements, a special combination execution process and verification rule can be set for the object, which increases the flexibility and scalability of the to-be-tested business system.

[0152] In some embodiments, as shown in Figure 8 , the above-mentioned preset execution function set can be constructed by the following steps.

[0153] S801, constructing a target base class.

[0154] The target base class (AbstractService) can also be called an abstract class, and can include multiple basic functions required for transaction execution.

[0155] S802, according to the transaction type supported by the to-be-tested business system, selecting multiple basic functions matching the transaction type from the target base class, and combining the multiple basic functions to obtain an execution function corresponding to the transaction type, to obtain a preset execution function set.

[0156] The target base class can include execution functions (or methods) required by multiple businesses (such as message conversion business, single transaction business, and combination transaction business), such as doService(). The functions in the base class can serve as the basis for all businesses.

[0157] For each sub-business, a corresponding execution function can be selected in the target base class, and then the function corresponding to each sub-business is taken as a leaf node of the combined business, to obtain a recursive tree structure, thereby realizing the execution logic of the combined business. Then, the test device can associate the plurality of sub-businesses according to the business rules of the to-be-tested business, to obtain a combined transaction process.

[0158] In the doService() method, the combined node traverses all the child nodes thereunder and recursively calls the doService() method of the child nodes, to realize nested calling. When a new transaction business is subsequently extended, only the target base class needs to be inherited, and the processing method thereof needs to be implemented.

[0159] Based on the technical solution, Figure 8 by constructing a general function set, a suitable execution function can be selected from the function set for each business subsequently, which is simple and convenient.

[0160] In some embodiments, the determination of the execution function corresponding to each sub-business from the preset execution function set in S203 can include: determining the execution function corresponding to each sub-business from the preset execution function set according to the transaction type of each sub-business.

[0161] In some embodiments, as shown in Figure 9 the to-be-tested business can include a message conversion business, a single transaction business, a combined transaction business, etc. The plurality of businesses all inherit the target base class, or build an execution process on the basis of the target base class.

[0162] The combined transaction business can further include a plurality of recursive child nodes. The plurality of recursive child nodes can correspond to the plurality of sub-businesses one by one.

[0163] Further, in combination with Figure 9 as shown in Figure 10 a special business can be added in the existing to-be-tested business, and then an execution process of the special business is built on the basis of the target base class.

[0164] In some embodiments, as shown in Figure 11 the method provided by the embodiments of the present application can include:

[0165] S111, in response to an asynchronous task of an original business system, performing mapping between the original business system and a to-be-tested business system.

[0166] The mapping includes interface mapping and field mapping. By performing the mapping between the original business system and the to-be-tested business system, transaction data of the to-be-tested business system can be obtained.

[0167] S112, based on the transaction configuration and the transaction data of the to-be-tested business, constructing a combined transaction process of the to-be-tested business.

[0168] The transaction configuration includes transaction configuration of single transaction business and transaction configuration of combined transaction business.

[0169] S113, before executing the combined transaction process of the to-be-tested business, pre-verification is performed on multiple steps of the combined transaction process, and after executing the multiple steps of the combined transaction process, post-verification is performed on the execution result.

[0170] S114, storing execution information of the to-be-tested business.

[0171] Based on the technical solution, Figure 11 through the mapping between the original business system and the to-be-tested business system, the transaction data of the to-be-tested business is obtained, and based on the transaction data and the transaction configuration of the to-be-tested business, the combined transaction process of the to-be-tested business is obtained, thus, through executing the combined transaction process and verifying the combined transaction process, the performance of the to-be-tested business system can be detected.

[0172] In an example, as shown in Figure 12 a structural diagram of service design based on abstract class and combination mode is provided for the embodiment of the present application.

[0173] The abstract class (AbstractService) can include attributes and methods. The attributes can include pre-execution conditions (preConditions, nested list structure) and post-execution conditions (postConditions, nested list structure). The methods can include a template method (doServiceTemplate ()), an abstract method (doService ()), a preprocessing method (doPreConditionsService ()), and a post-processing method (doPostConditionsService ()).

[0174] FieldService is used to handle data format conversion logic and implement the doService() method. ActionService is used to handle single transaction processes and implement the doService() method. CombinedService is used to manage multiple sub-services through a combination mode and contains an actions list (which stores sub-services of the AbstractService type) to form a one-to-many correspondence of "combined transaction-action set". Recursive sub-nodes can use the abstract class service (AbstractService: action) and template method (doServiceTemplate()) to implement corresponding functions.

[0175] Based on the scheme of Figure 12 , the doServiceTemplate() service execution process is fixed, and the subclass only needs to focus on the specific implementation of doService(). Combined transaction business only needs to recursively call the doServiceTemplate() of the sub-service (through loop traversal of the actions list), supports infinite nesting of simple services (FieldService / ActionService) and combined services (CombinedService), forms a tree-shaped service structure, and implements the hierarchical processing logic of "recursive sub-nodes".

[0176] During the execution of CombinedService, all sub-services contained therein (regardless of the number of levels) are traversed, and the complete life cycle of each sub-service (precondition→core service→postcondition) is triggered in turn, thereby realizing the modular combination and reuse of complex business processes.

[0177] In another example, as shown in Figure 13 , a schematic diagram of business extension provided by the embodiment of the application is provided.

[0178] As shown in Figure 13 , the implementation class TBBCN9S102Impl can dynamically find the corresponding business logic processing class according to the transaction code and field of the original business system in the doTBBCN9S102 method, thereby enhancing the flexibility and scalability of the to-be-tested business system test. The following describes Figure 13 .

[0179] 1-1, Transaction forwarding factory class (TBCN9S102Factory).

[0180] The function of the transaction forwarding factory class is to manage a set of transaction forwarding instances, and store the processor instances in beansMap (HashMap<String, ITBCN9S102Handler>).

[0181] The method used is to provide getHandler() and setHandler() methods for instance management.

[0182] 1-2, Processor interface (ITBCN9S102Handler).

[0183] The processor interface can use the getHandlerBEAN() method to obtain the processor instance.

[0184] 1-3, Processor abstract class / base class.

[0185] The processor abstract class / base class can implement the ITBCN9S102Handler interface. Its core business methods include #doFeatureService() (feature service processing, protected method), #doService() (general service processing, protected method), and +afterPropertiesSet() (initialization method, public method).

[0186] 1-4, Default forwarding instance (AppCombinedTransactionsImpl).

[0187] The default forwarding instance can inherit TBCN9S102Handler as the default transaction forwarding implementation class, and implement the getHandlerBEAN() method to provide specific processor instances.

[0188] 1-5, Forwarding entry interface (ITBCN9S102).

[0189] The forwarding entry specification includes the doTBCN9S102() method (transaction forwarding entry).

[0190] 1-6, Forwarding entry implementation class (TBCN9S102Impl).

[0191] The forwarding entry implementation class is used to implement the ITBCN9S102 interface, and its doTBCN9S102() method completes the specific forwarding logic by calling the doFeatureService() method of AppCombinedTransactionsImpl.

[0192] It should be noted that, Figure 13The process logic is as follows: Forwarding entry point: TBCN9S102Impl implements the doTBCN9S102() method of the ITBCN9S102 interface, serving as the starting point for transaction forwarding. Business processing: The entry method calls doFeatureService() of AppCombinedTransactionsImpl (the default forwarding instance), ultimately completing the core logic through doService() of TBCN9S102Handler. Instance management: The TBCN9S102Factory factory class manages multiple ITBCN9S102Handler instances through beansMap, supporting flexible switching between different forwarding processors.

[0193] based on Figure 13 The illustrated process logic is defined and standardized through the ITBCN9S102 and ITBCN9S102Handler interfaces, achieving separation of business logic and instance management. By inheriting from TBCN9S102Handler, custom forwarding instances can be defined, and the factory class dynamically manages instances, supporting adaptation to multiple scenarios.

[0194] Figure 14 This is a schematic diagram of a testing device provided in an embodiment of this application. Figure 14 As shown, the testing device includes: an acquisition module 1401, a conversion module 1402, a construction module 1403, and an execution module 1404.

[0195] The acquisition module 1401 is used to acquire business requirement information of the business to be tested. The conversion module 1402 is used to convert the associated transaction data of the business to be tested obtained from the original business system to obtain target transaction data suitable for the business system to be tested. The construction module 1403 is used to construct the execution flow and execution order of multiple execution steps required by the business to be tested based on the business requirement information and the target transaction data, obtaining the combined transaction flow of the business to be tested. The execution module 1404 is used to execute the combined transaction flow in the business system to be tested according to the execution order, obtain the first execution result, and verify the consistency of accounting between the business system to be tested and the original business system based on the first execution result.

[0196] In other embodiments, the service to be tested includes multiple sub-services. The aforementioned construction module 1402 is specifically used for: determining the execution function corresponding to each sub-service from a preset set of execution functions, and determining the business data required by each sub-service from the target transaction data; establishing the calling relationship between the execution function corresponding to each sub-service and the required business data to obtain an execution flow of multiple steps, wherein the execution function corresponding to a sub-service implements the execution flow of the sub-service by calling the business data required by the sub-service; and determining the execution order of multiple steps based on the dependencies between multiple sub-services.

[0197] In other embodiments, such as Figure 14 As shown, the testing device may further include a mapping module 1405, used to: map the transaction results of the tracking transaction thread to thread-shared variables to obtain a data sharing domain. The tracking transaction thread is obtained by concatenating multiple execution steps; the data sharing domain includes the second execution results obtained after executing multiple concatenated execution steps in the original business system and the execution preconditions for each execution step; the execution preconditions include: the amount of transaction data required to execute the execution step supports the execution step and / or the transaction account corresponding to the execution step is in a normal state. The aforementioned execution module 1404 is specifically used to: obtain the execution preconditions corresponding to each execution step from the data sharing domain before executing the combined transaction process in the execution order; for each execution step, if the execution environment of the execution step meets the corresponding execution preconditions, execute the execution process of the execution step; if the execution environment of the execution step does not meet the corresponding execution preconditions, stop executing the execution process of the execution step.

[0198] In other embodiments, the acquisition module 1401 is further configured to: for each execution step, after executing the execution flow of that execution step, acquire the second execution result corresponding to the execution step from the data sharing domain. The execution module 1404 is specifically configured to: determine that the accounting of the business system under test is consistent with the original business system if the first execution result and the second execution result are consistent; and determine that the accounting of the business system under test is inconsistent with the original business system if the first execution result and the second execution result are inconsistent.

[0199] In other embodiments, the acquisition module 1401 is further configured to acquire specific business requirement information of the target object; the target object is one of multiple test objects included in the business to be tested; the transaction sequence corresponding to the target object is acquired from the configuration information of the original business system, and the execution flow of the execution steps corresponding to the target object is determined according to the specific business requirement information and the transaction sequence. The construction module 1403 is further configured to: configure verification rules for the target object; the verification rules include pre-verification rules and post-verification rules, the pre-verification rules are used to verify the execution flow of multiple steps included in the specific combined transaction process before executing the specific combined transaction process, and the post-verification rules are used to verify the execution result of the specific combined transaction process. The execution module 1404 is further configured to: execute the execution flow of the execution steps of the target object in the business system to be tested, and use the verification rules to verify the execution steps and execution result of the target execution.

[0200] In some embodiments, the mapping module 1405 is further configured to map a plurality of transaction fields in the original business system to transaction fields of the to-be-tested business system, to obtain a transaction field mapping relationship between the original business system and the to-be-tested business system; and determine the number of the newly added transaction field in the to-be-tested business system based on a number determination manner and the transaction field mapping relationship. The number determination manner includes: manually setting the field, and determining the number according to a transaction field similar to a target transaction field, the target transaction field being one in the to-be-tested business system.

[0201] In some embodiments, the construction module 1402 is further configured to: construct a target base class, the target base class including a plurality of basic functions required for transaction execution; select a plurality of basic functions matched with each transaction type from the target base class according to the transaction types supported by the to-be-tested system, and combine the plurality of basic functions to obtain an execution function corresponding to the transaction type, to obtain a preset execution function set; and the preset execution function set includes execution functions corresponding to a plurality of transaction types. The construction module 1402 is specifically configured to: determine the respective corresponding execution functions from the preset execution function set according to the transaction types of each sub-business.

[0202] The test device provided by the embodiments of the present application can execute the method shown in the method embodiments, and the implementation principles and beneficial effects can refer to the related description in the method embodiments, which will not be repeated here.

[0203] Figure 15 A structural schematic diagram of a test device provided by the embodiments of the present application is shown in FIG. 1. As shown in the figure, the test device includes a memory 1501, a transceiver 1502, and at least one processor 1503. Figure 15

[0204] The transceiver 1502 is used to interact with other devices to realize the transceiving of data. For example, in the embodiments of the present application, the transceiver 502 can be specifically used to obtain the business requirement information of the to-be-tested business.

[0205] The memory 1501 is used to store computer program code, which includes computer instructions. The computer instructions run in the test device to implement the method shown in the method embodiments. For example, the memory can include a random access memory (RAM), and can also include a non-volatile memory (NVM), such as at least one disk memory, and can also be a U disk, a mobile hard disk, a read-only memory, a magnetic disk or an optical disk, etc.

[0206] ​The processor 503 can be a general processor, including a central processing unit (CPU), a network processor (NP), etc.; can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The processor 503 can also be other general processors. The general processor can be a microprocessor or the processor can also be any conventional processor.

[0207] The memory 1501, the transceiver 1502 and the processor 1503 are communicatively connected. For example, the memory 1501, the transceiver 1502 can be connected with the processor 503 through a system bus and complete communication among each other. The system bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, an industry standard architecture (ISA) bus, etc. The system bus can be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, only one thick line is shown in the figure, but it does not mean that there is only one bus or only one type of bus.

[0208] Optionally, the memory 1501 can be independent or integrated with the processor 1503. When the memory 1501 is independently arranged, the memory 1501 and the processor 1503 are connected through a system bus.

[0209] The embodiment of the present application further provides a chip for running instructions, which is used for executing the technical solutions of the test method of the business system in the above embodiment.

[0210] The embodiment of the present application further provides a computer readable storage medium, which stores computer instructions. When the computer instructions are executed by a processor, the technical solutions of the test method of the business system in the above embodiment are implemented. Specifically, when the computer instructions are executed by the processor, the test device can execute the technical solutions of the test method of the business system in the above embodiment.

[0211] The embodiment of the present application further provides a computer program product, which comprises a computer program stored in a computer readable storage medium, at least one processor can read the computer program from the computer readable storage medium, and the at least one processor can implement the technical solution of the test method of the business system in the above embodiment when executing the computer program.

[0212] The computer readable storage medium can be realized by any type of volatile or nonvolatile storage devices or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The computer readable storage medium can be any available medium that can be accessed by a general or special purpose computer.

[0213] An exemplary computer readable storage medium is coupled to the processor, so that the processor can read information from the storage medium and write information to the computer readable storage medium. Of course, the computer readable storage medium can also be an integral part of the processor. The processor and the computer readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the computer readable storage medium can also exist as discrete components in an electronic control unit or a host device, and the embodiment of the present application does not limit this.

[0214] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the modules is only a logical function division, and actual implementation can have another division manner, for example, a plurality of modules can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed each other can be indirect coupling or communication connection through some interfaces, devices or modules, and can be electrical, mechanical or other forms.

[0215] The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical units, i.e., may be located in one place, or may be distributed to multiple network units. Part or all of the modules can be selected according to actual needs to implement the embodiments of the present application.

[0216] In addition, the functional modules in each embodiment of the present application can be integrated in one processing unit, or each module can be physically present alone, or two or more modules can be integrated in one unit. The unit formed by the above modules can be realized in the form of hardware or in the form of hardware plus software functional units.

[0217] The integrated modules realized in the form of software functional modules can be stored in a computer readable storage medium. The software functional modules stored in a storage medium include a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute part of the steps of the method of each embodiment of the present application.

[0218] It should be understood that the steps of the method disclosed in the embodiments of the present application can be directly embodied as hardware processor execution, or executed by a combination of hardware and software modules in the processor.

[0219] Those of ordinary skill in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction-related hardware. The aforementioned program can be stored in a computer readable storage medium. The program, when executed, executes steps including the above-mentioned method embodiments; and the aforementioned storage medium includes ROM, RAM, magnetic or optical disc, and various media that can store program codes.

[0220] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the above embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the above embodiments, or make equivalent replacements for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A testing method for a business system, characterized in that, include: Obtain the business requirements information of the service to be tested; The associated transaction data of the business to be tested obtained from the original business system is transformed to obtain target transaction data suitable for the business system to be tested; Based on the business requirement information and the target transaction data, construct the execution flow and execution order of multiple execution steps required for the business to be tested, and obtain the combined transaction flow of the business to be tested; In the business system to be tested, the combined transaction process is executed in the order of execution to obtain a first execution result, and the consistency of the tracking between the business system to be tested and the original business system is verified based on the first execution result.

2. The method according to claim 1, characterized in that, The service to be tested includes multiple sub-services; the step of constructing the execution flow and execution order of multiple execution steps required for the service to be tested based on the service requirement information and the target transaction data includes: The execution function corresponding to each sub-business is determined from the preset set of execution functions, and the business data required for each sub-business is determined from the target transaction data; Establish the calling relationship between the execution function corresponding to each sub-business and the required business data to obtain the execution flow of the multiple steps. The execution function corresponding to a sub-business implements the execution flow of the sub-business by calling the business data required by the sub-business. The execution order of the multiple steps is determined based on the dependencies between the multiple sub-businesses.

3. The method according to claim 2, characterized in that, The method further includes: The transaction results of the tracking transaction thread are mapped to thread-shared variables to obtain a data-shared domain; the tracking transaction thread is obtained by concatenating the multiple execution steps; the data-shared domain includes the second execution results obtained by the multiple execution steps after concatenation in the original business system and the execution preconditions for each execution step; the execution preconditions include: the amount of transaction data required to execute the execution step supports the execution step and / or the transaction account corresponding to the execution step is in a normal state; The process of executing the combined transaction in the order described in the business system under test includes: Before executing the combined transaction process in the order described above, the execution preconditions corresponding to each execution step are obtained from the data sharing domain. For each execution step, the execution process of the execution step is executed if the execution environment of the execution step meets the corresponding execution preconditions. If the execution environment of the execution step does not meet the corresponding preconditions, the execution process of the execution step shall be stopped.

4. The method according to claim 3, characterized in that, The method further includes: For each execution step, after executing the execution flow of the execution step, the second execution result corresponding to the execution step is obtained from the data sharing domain; The step of verifying the consistency of the accounting between the business system under test and the original business system based on the first execution result includes: If the first execution result is consistent with the second execution result, it is determined that the accounting of the business system under test is consistent with that of the original business system. If the first execution result and the second execution result are inconsistent, it is determined that the accounting of the business system under test is inconsistent with that of the original business system.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Obtain the specific business requirements information of the target object; the target object is one of multiple test objects included in the business to be tested; Obtain the transaction sequence corresponding to the target object from the configuration information of the original business system, and determine the execution flow of the execution steps corresponding to the target object based on the special business requirement information and the transaction sequence; Configure verification rules for the target object; the verification rules include pre-verification rules and post-verification rules, the pre-verification rules are used to verify the execution flow of multiple steps included in the dedicated combined trading process before executing the dedicated combined trading process, and the post-verification rules are used to verify the execution result of the dedicated combined trading process; The execution flow of the target object's execution steps is executed in the business system to be tested, and the execution steps and results of the target object are verified using the verification rules.

6. The method according to any one of claims 1-4, characterized in that, The method further includes: Multiple transaction fields in the original business system are mapped to transaction fields in the business system under test, thereby obtaining the transaction field mapping relationship between the original business system and the business system under test; Based on the numbering determination method and the transaction field mapping relationship, the number of the newly added transaction field in the business system to be tested is determined; the numbering determination method includes: manually setting the field, or determining it based on a transaction field similar to the target transaction field, wherein the target transaction field is one of the business systems to be tested.

7. The method according to claim 2, characterized in that, The method further includes: Construct a target base class, which includes the basic functions required for multiple transaction executions; Based on the transaction types supported by the business system under test, multiple basic functions matching each transaction type are selected from the target base class, and the multiple basic functions are combined to obtain the execution function corresponding to the transaction type, so as to obtain the preset execution function set; the preset execution function set includes execution functions corresponding to multiple transaction types; The step of determining the execution function corresponding to each sub-service from the preset set of execution functions includes: Based on the transaction type of each sub-business, the corresponding execution function is determined from the preset set of execution functions.

8. A testing apparatus for a business system, characterized in that, include: The acquisition module is used to acquire business requirement information of the service to be tested. The conversion module is used to convert the related transaction data of the business to be tested obtained from the original business system to obtain target transaction data suitable for the business system to be tested. The construction module is used to construct the execution flow and execution order of multiple execution steps required by the business requirement information and the target transaction data, so as to obtain the combined transaction flow of the business to be tested. An execution module is used to execute the combined transaction process in the business system under test according to the execution order, obtain a first execution result, and verify the consistency of the tracking between the business system under test and the original business system based on the first execution result.

9. A testing device, characterized in that, include: A memory and at least one processor; the memory is communicatively connected to the processor; the memory is used to store computer program code, the computer program code including computer instructions; when the processor executes the computer instructions, the test device performs the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, are used to implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, When the computer program product is run on a computer / executed by the computer's processor, it implements the method as described in any one of claims 1-7.

Images