CN111078536A

CN111078536A - Test data generation method, device and system

Info

Publication number: CN111078536A
Application number: CN201911196002.1A
Authority: CN
Inventors: 钱峰
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2019-11-29
Filing date: 2019-11-29
Publication date: 2020-04-28

Abstract

The embodiment of the specification discloses a test data generation method, a test data generation device and a test data generation system, wherein the method obtains signing configuration data which comprises a client type and first sub-configuration data of a data item corresponding to client signing; acquiring signing flow data according to the client type; and generating customer subscription data for testing according to the subscription flow data, a first data generation rule corresponding to a data item in the subscription flow data and first sub-configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

Description

Test data generation method, device and system

Technical Field

The present invention relates to the field of computer data processing technologies, and in particular, to a method, an apparatus, and a system for generating test data.

Background

The testing process of the bank software comprises monomer testing, function testing, automation testing, pressure testing and the like, and all testing processes need corresponding testing data. In the internet bank test, data in the functional test stage is generally generated by testers through the subscription function of the internet bank, and different subscription processes need to be executed for different customer groups. And the monomer test is completed by the developer himself. However, developers often do not want to generate test data through the contract module, and need to face interaction with an external system, communication debugging and the like, which is too long in time cost. Automated testing and stress testing, in turn, often requires large amounts of test data, which becomes extremely inefficient or even impossible if the data generation method of functional testing is followed.

Disclosure of Invention

An object of the embodiments of the present specification is to provide a method, an apparatus, and a system for generating test data, which can implement automatic generation of test data and greatly improve test efficiency.

The specification provides a test data generation method, a test data generation device and a test data generation system, which are realized in the following modes:

a test data generation method, comprising:

acquiring signing configuration data, wherein the signing configuration data comprises a client type and first sub-configuration data of a data item corresponding to a client signing;

acquiring signing flow data according to the client type;

and generating customer subscription data for testing according to the subscription flow data, a first data generation rule corresponding to a data item in the subscription flow data and first sub-configuration data.

In another embodiment provided by the method described herein, the method further comprises:

acquiring transaction configuration data, wherein the transaction configuration data comprises payee information and second sub-configuration data of data items in a client-payee relationship;

and generating customer transaction data for testing according to the customer subscription data, the payee information and a second data generation rule and second sub-configuration data of the data items in the customer-payee relationship.

In another embodiment provided by the method described in this specification, the subscription configuration data is configured according to a first data generation rule corresponding to each data item in the subscription process data.

In another embodiment provided by the method described herein, the first data generation rule or the second data generation rule is determined according to a storage rule of the data item in a database.

In another aspect, an embodiment of the present specification further provides a test data generation apparatus, where the apparatus includes:

the system comprises a first data acquisition module, a second data acquisition module and a third data acquisition module, wherein the first data acquisition module is used for acquiring signing configuration data which comprises a client type and first sub-configuration data of a data item corresponding to a client signing;

the second data acquisition module is used for acquiring the signing flow data according to the client type;

and the first test data generation module is used for generating customer subscription data for testing according to the subscription flow data, a first data generation rule corresponding to a data item in the subscription flow data and the first sub-configuration data.

In another embodiment provided by the apparatus described herein, the apparatus further comprises:

the third data acquisition module is used for acquiring transaction configuration data, wherein the transaction configuration data comprises payee information and second sub-configuration data of data items in the relationship between the payee information and the client and the payee;

and the second test data generation module is used for generating customer transaction data for testing according to the customer subscription data, the payee information, and a second data generation rule and second sub-configuration data of the data items in the customer-payee relationship.

In another embodiment provided by the apparatus described in this specification, the subscription configuration data is configured according to a first data generation rule corresponding to each data item in the subscription process data.

In another embodiment provided by the apparatus described in this specification, the first data generation rule or the second data generation rule is determined according to a storage rule of the data item in a database.

In another aspect, an embodiment of the present specification further provides a test data generating apparatus, where the apparatus includes a processor and a memory for storing processor-executable instructions, and the instructions, when executed by the processor, implement the following steps:

acquiring signing flow data according to the client type;

In another aspect, an embodiment of the present specification further provides a test data generation system, where the system includes at least one processor and a memory storing computer-executable instructions, and the processor executes the instructions to implement the steps of the method according to any one of the above embodiments.

The test data generation method, device and system provided in one or more embodiments of the present specification may be configured to automatically generate rules by combing signing process data corresponding to different client types in advance and presetting data corresponding to multiple data items involved in the signing process. Then, test data can be automatically generated based on the pre-carded signing process data, the data automatic generation rules of each data item and the configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

Drawings

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

FIG. 1 is a schematic flow chart diagram illustrating an embodiment of a test data generation method provided herein;

fig. 2 is a schematic flow chart of a personal client subscription process in one embodiment provided herein;

fig. 3 is a schematic diagram of an enterprise customer subscription flow in another embodiment provided herein;

FIG. 4 is a schematic flow chart diagram illustrating another exemplary method of generating test data provided herein;

FIG. 5 is a schematic illustration of a personal customer sign-up and payee information in another embodiment provided by the present description;

FIG. 6 is a schematic illustration of an enterprise customer subscription and payee information in another embodiment provided by the present description;

fig. 7 is a schematic block diagram of an embodiment of a test data generating apparatus provided in this specification.

Detailed Description

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

The testing process of the bank software comprises monomer testing, function testing, automation testing, pressure testing and the like, and all testing processes need corresponding testing data. In the internet bank test, data in the functional test stage is generally generated by testers through the subscription function of the internet bank, and different subscription processes need to be executed for different customer groups. And the monomer test is completed by the developer himself. However, developers often do not want to generate test data through the contract module, and need to face interaction with an external system, communication debugging and the like, which is too long in time cost. Automated testing and stress testing, in turn, often requires large amounts of test data, which becomes extremely inefficient or even impossible if the data generation method of functional testing is followed. Correspondingly, the embodiments of the present specification provide a test data generation method, which may be implemented by combing signing process data corresponding to different client types in advance, and presetting and configuring a data automatic generation rule corresponding to multiple data items involved in the signing process. Then, test data can be automatically generated based on the pre-carded signing process data, the data automatic generation rules of each data item and the configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

Fig. 1 is a schematic flowchart of an embodiment of a test data generation method provided in this specification. Although the present specification provides the method steps or apparatus structures as shown in the following examples or figures, more or less steps or modules may be included in the method or apparatus structures based on conventional or non-inventive efforts. In the case of steps or structures which do not logically have the necessary cause and effect relationship, the execution order of the steps or the block structure of the apparatus is not limited to the execution order or the block structure shown in the embodiments or the drawings of the present specification. When the described method or module structure is applied to a device, a server or an end product in practice, the method or module structure according to the embodiment or the figures may be executed sequentially or in parallel (for example, in a parallel processor or multi-thread processing environment, or even in an implementation environment including distributed processing and server clustering).

Fig. 1 shows a specific embodiment, and in an embodiment of the test data generation method provided in this specification, the method may include:

s0: and acquiring signing configuration data, wherein the signing configuration data comprises a client type and first sub-configuration data of a data item corresponding to the client signing.

The subscription profile may include customer-specific data for some or all of the data items involved in the customer account opening process. The signed configuration data can be pre-configured by a tester according to the test requirement.

The data items may include data types involved in the customer account opening process, such as customer number, customer name, customer type, line of account opening, certificate type, certificate number, and the like.

The first sub-configuration data may be specific customer data configured to correspond to a single data item. For example, the client number is 01000, the client name is A, the client type is an individual client, the bank Beijing division of the China's bank acts as an account opening action, the certificate type is an identity card, and the like.

The customer type may be divided according to actual business of the financial institution. For example, in some embodiments, the customer types may include personal customers, business customers. In other embodiments, the client type may be further subdivided into domestic personal clients, domestic enterprise clients, overseas personal clients, overseas enterprise clients.

S2: and acquiring the signing flow data according to the client type.

The signing flow data can be obtained by combing the existing customer account opening flow of the financial institution. The client subscription process data corresponding to different client types generally have a certain difference. In some embodiments, the signing process data corresponding to each client type may be combed in advance according to the client type, and if the client is divided into four client types, i.e., domestic personal, domestic enterprise, overseas personal, and overseas enterprise, the signing process data corresponding to each client type may be combed respectively. Generally, the difference between the domestic signing process and the overseas signing process is not large, and the signing process data corresponding to the individual client and the enterprise client can be obtained by combing according to two dimensions of the individual and the enterprise.

When the subscription configuration data of the test data to be generated is configured, the client type corresponding to the test data to be generated may be configured, and then, the subscription flow data corresponding to the test data to be generated may be obtained according to the client type in the subscription configuration data.

In an implementation scenario provided in this specification, the data of the subscription process corresponding to the personal client and the enterprise client are sorted as follows:

(1) an individual customer:

the subscription of an online bank individual to open an account generally requires the following steps:

establishing a client;

establishing a user;

opening token/short message authentication for the client;

establishing a user channel (online banking);

opening services such as investment and financing, online payment and direct payment for financing;

establishing a customer user relationship;

establishing an account;

binding a service account;

setting a limit for an account;

a customer account relationship is established.

The subscription process corresponding to the combed individual client is shown in fig. 2, and fig. 2 shows a schematic diagram of the subscription process of the individual client in some embodiments of the present specification.

(2) Enterprise customers:

the subscription of an account opening by an online bank client generally requires the following steps:

establishing a client;

establishing an authorization flow;

establishing an authorization level;

establishing a user;

establishing a customer user relationship;

establishing a user channel;

maintaining the basic authority of the client user;

maintaining an authorized user;

establishing an account;

establishing a customer account relationship;

maintaining client user account permissions;

and maintaining the approval process.

The subscription process corresponding to the combed enterprise client is shown in fig. 3, and fig. 3 is a schematic diagram of the subscription process of the enterprise client in some embodiments of the present disclosure.

S4: and generating customer subscription data for testing according to the subscription flow data, a first data generation rule corresponding to a data item in the subscription flow data and first sub-configuration data.

The first data generation rule corresponding to the data item may include an automatic generation rule of specific customer data corresponding to each data item in a process of generating the data to be tested. In some embodiments, the data generation rules may be determined by analyzing existing customer account opening data of the financial institution; meanwhile, the data generation rule may be determined in further consideration of the need for testing, the simplicity, efficiency, and the like of data generation.

In some implementation scenarios of the present specification, the generation rules of the data items corresponding to each link in the client subscription flow may be as shown in tables 1 to 15 below.

TABLE 1 customer data sheet

TABLE 2 user data sheet

Table 3 customer subscriber relationship data table

TABLE 4 user channel data sheet

Table 5 user service provisioning data table

TABLE 6 Account data sheet

TABLE 7 customer Account relationship data sheet

Table 8 data sheet for opening payment service by account

TABLE 9 Account fulfillment investment service data sheet

Table 10 customer service data (p.o.; official) table

Table 11 authorized work flow data (to public) table

Table 12 authorization level data (public) table

Table 13 authorized user data (public) table

TABLE 14 client user Account Authority data (for public) Table

Table 15 examination and approval process data (for public)

The generation of the signing data can be carried out in sequence according to the execution sequence of each link and the series relation among the links in the client signing flow; meanwhile, for the data items corresponding to each link, specific client data corresponding to each data item is generated according to the generation rule of each data item and the first sub-configuration data of part of the data items. The generated specific customer data may then be stored in each data table in the database, forming customer subscription data for testing. For example, the generated client number may be recorded in a log table, and the client, the account, the authority, and the like are also identified by the client number and then stored in a corresponding data table, so as to form client subscription data corresponding to one or more clients, so as to be used for subsequent software function tests. The client subscription data is automatically generated based on the automatic generation rule of each data item in the subscription flow, so that the automatic generation of the client subscription data can be simply and efficiently realized, and the efficiency of generating test data is improved; meanwhile, the data is generated based on the customer subscription flow which is combed in advance, and the accuracy of automatic generation of the customer subscription data can be further ensured, so that the generated test data is more in line with the actual business, and the test result is more in line with the actual production requirement.

In some embodiments of the present specification, the first data generation rule may be determined according to a storage rule of the data item in a database. Customer subscription data of a financial institution is usually stored in a database in a data table form, different data items correspond to fixed storage rules in the database, and if a certificate number usually has a fixed length and specific data has no requirement, the number length can be set, and the certificate number is randomly generated; the service is usually corresponding to a service code, and needs to be determined by configuration, and the corresponding generation rule is directly set to be determined according to the configuration, and the like. The automatic generation rule of each data item is determined based on the data storage rules of different data items, so that the accuracy and the simplicity of test data generation can be further improved.

In some embodiments of the present specification, a data item to be configured and sub-configuration data of the data item in the subscription configuration data may also be determined according to the first data generation rule. As can be seen from the generation rules of the data items in tables 1 to 15, not all data items need to be configured specifically. If the generation rule corresponding to some data items is fixed, and if the review flag in table 15 is fixed to 0 and the status is fixed to V, the specific data of the two data items can be set in advance according to the generation rule without additional configuration by the tester. Specific data of data items such as the client type, the approval model and the like need to be additionally configured by a tester according to test requirements. The generation rules of some data items are set as default values or randomly generated according to certain requirements, so that the quantity of data to be configured can be further reduced, the configuration workload of testers is reduced, and the generation efficiency of test data is improved.

In some embodiments, a batch of test data may be generated according to test requirements, and accordingly, the number of test data to be generated may be further configured in the contract configuration data, where the number may include the number of each customer type, the number of each user type, the number of each account type, and the like.

In some implementation scenarios of this specification, the relevant configuration table may be defined according to an automated generation rule of each data item of the subscription process:

1. customer configuration table: the configuration of the number, market segmentation, type, service opening and the like of the online bank customers can be defined;

2. user configuration table: the configuration of the number of online banking users, the opening of services and the like can be defined;

3. user channel configuration table: configurations such as an online banking user opening channel, a default safety tool and the like can be defined;

4. account configuration table: the configuration of the number, the type, the account length, the currency and the like of the online bank account can be defined;

5. permission configuration table: the configuration of the network bank client, the user, the authority to be opened of the account and the like can be defined;

6. authorization procedure configuration table: the authorization level, the order, the number of passing persons and the like of the online bank client can be defined;

7. approval process configuration table: the configuration of the online bank customer for opening the approval process under which accounts can be defined.

The tester can configure specific data in the form of configuration files, then can call each configuration file to write specific values of each configuration table into the configuration table, and the customer signing parameter data is stored and displayed in the form of the configuration table for subsequent flow calling. A configuration table may be configured for each link, and specific data of a part of data items of the corresponding link may be configured according to the configuration table.

For example, for customer data, since most data items may be generated by random rules or default values, there are not many data items that need to be configured, and the configuration table may be defined as in table 16 below. In the test data generation process, for data of a data item needing to be determined according to configuration, the data in the configuration table can be called; and generating the data of the data item with the default value or the default random generation rule directly according to the generation rule of the data item. Meanwhile, each generated specific data can be written into a data table corresponding to the database.

Table 16 customer data configuration table

FIG. 4 is a schematic diagram of test data generation flow in further embodiments of the present description. In other embodiments of the present description, as shown in fig. 4, the method may further include:

s6: acquiring transaction configuration data, wherein the transaction configuration data comprises payee information and second sub-configuration data of data items in a client-payee relationship;

s8: and generating customer transaction data for testing according to the customer subscription data, the payee information and a second data generation rule and second sub-configuration data of the data items in the customer-payee relationship.

In some embodiments of the present description, payee information and customer payee relationship may be further teased out based on the teased subscription flow data, as shown in fig. 5 and 6. Fig. 5 shows a contract flow chart of the increased payee information and the client-payee relationship corresponding to the individual client, and fig. 6 shows a contract flow chart of the increased payee information and the client-payee relationship corresponding to the enterprise client. Then, data items of the payee information and customer payee relationship and second data generation rules for the data items may be set. The data items and the second data generation rules may be set according to existing transaction data and test requirements, etc. Table 17 and table 18 show the rules for creating data items relating to the payee and the customer payee, which are set in advance.

Table 17 payee data sheet

Table 18 customer payee relationship data

The transaction configuration data may include payee information configured by the tester as required by the test and second sub-configuration data for data items in the customer payee relationship. The second sub-configuration data may be specific data corresponding to a single data item. When generating the test data, the customer transaction data for the test may be generated according to the second data generation rule, the transaction configuration data, and the customer subscription data of each data item in the payee information and customer payee relationship.

In some embodiments, payee information may be configured, such as with a payee configuration table. The configuration table of the payee can define the configuration of the number of the payee, the identification inside and outside the line, the type, the account length, the currency and the like. Then, specific data corresponding to the payee, which is related to the specific data corresponding to each data item by the customer, may be generated based on the second data item generation rule. And further combining the customer subscription data for testing generated by the embodiment to generate transaction data. In the process, the generated data such as the payee data, the client payee relation data, the transaction amount and the like can be stored in a corresponding data table in the database to form transaction data. After the transaction data is generated, the client number in the log table can be sent to the testing terminal for testing.

In one implementation scenario of the present specification, a method for performing monomer testing using the scheme of the above embodiment is also provided. The JUnit can be used for testing the single body, and the JUnit testing comprises a setup process and a Teardown process, wherein the setup process mainly realizes initialization work before testing, and the teardown process mainly realizes garbage recycling and other work after testing. The signed data for testing can be generated in the setup stage, and after the testing is finished, the signed data is destroyed in the Teardown stage.

According to the signing process and the automatic generation rule of each data item, test data can be configured and generated, and the following configuration written for individual signing clients in practical application is as follows:

by utilizing the configuration, an individual customer can be created, and the customer can create 2 accounts, wherein one account is a credit card and the other account is a debit card, and simultaneously, a mobile phone channel is correspondingly opened, electronic payment, direct financial payment and investment service are opened, 5 collection account numbers are created, wherein 3 in-line accounts (1 debit card and 2 credit cards) and 2 out-of-line accounts are created.

The following is the configuration written for the enterprise contracted customer in the practical application:

an enterprise customer can be created by utilizing the configuration, 10 accounts and 5 collection accounts can be created under the customer, 1 user is created by default, the customer correspondingly opens account inquiry (ES010), bank-enterprise account checking (ES210), transfer remittance (ES020) and private transfer (ES270) services, meanwhile, each account is provided with the authority of balance inquiry of today (EF0101), transaction inquiry of today (EF0109), transfer remittance delegation (EF0201), transfer remittance inquiry (020EF 4) and private account inquiry (EF2704), and finally, the approval process of transfer remittance (EB020) and private transfer (EB270) is established for all accounts under the customer.

Through the flexible configuration, the data requirements of developers in the JUnit single body test can be met, and a good foundation is laid for the development of the test.

Meanwhile, millions of test data can be provided aiming at the scenes of automatic test and pressure test. When the data is configured, various customers, accounts and correspondingly generated test data under different services can be configured. The batch data generation can be realized by adopting a storage process of Oracle.

By adopting the configured development, the automatic generation of the single test data and the batch automatic generation of the data required by the automatic test and the pressure test can be realized, so that the complex operations of interaction, communication and debugging between the tester and an external system, and the like are reduced, and the test efficiency is greatly improved.

For the data of the monomer test, after the test is finished, the test data can be destroyed through a Teardown process; for batch data of automation and pressure test, customer data can be cancelled in a batch mode, and the space occupied by test data is reduced.

The embodiments in the present specification are 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. For details, reference may be made to the description of the related embodiments of the related processing, and details are not repeated herein.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

The test data generation method provided in one or more embodiments of the present specification may be configured to automatically generate rules by combing signing process data corresponding to different client types in advance and presetting data corresponding to multiple data items involved in the signing process. Then, test data can be automatically generated based on the pre-carded signing process data, the data automatic generation rules of each data item and the configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

Based on the test data generation method, one or more embodiments of the present specification further provide a test data generation apparatus. The apparatus may include systems, software (applications), modules, components, servers, etc. that utilize the methods described in the embodiments of the present specification in conjunction with hardware implementations as necessary. Based on the same innovative conception, embodiments of the present specification provide an apparatus as described in the following embodiments. Since the implementation scheme of the apparatus for solving the problem is similar to that of the method, the specific implementation of the apparatus in the embodiment of the present specification may refer to the implementation of the foregoing method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated. Specifically, fig. 7 shows a schematic block structure diagram of an embodiment of a test data generation apparatus provided in the specification, and as shown in fig. 7, the apparatus may include:

the first data obtaining module 102 may be configured to obtain subscription configuration data, where the subscription configuration data includes a client type and first sub-configuration data of a data item corresponding to a client subscription;

a second data obtaining module 104, configured to obtain subscription process data according to the client type;

the first test data generating module 106 may be configured to generate customer subscription data for testing according to the subscription flow data, a first data generating rule corresponding to a data item in the subscription flow data, and the first sub-configuration data.

In another embodiment of the present specification, the apparatus may further include:

a third data obtaining module 108, configured to obtain transaction configuration data, where the transaction configuration data includes payee information and second sub-configuration data of data items in the customer-payee relationship;

the second test data generating module 110 may be configured to generate customer transaction data for testing according to the customer subscription data, the payee information, and the second data generating rule and the second sub-configuration data of the data item in the customer-payee relationship.

In another embodiment of this specification, the subscription configuration data may be configured according to a first data generation rule corresponding to each data item in the subscription process data.

In another embodiment of the present specification, the first data generation rule or the second data generation rule may be determined according to a storage rule of the data item in a database.

It should be noted that the above-described apparatus may also include other embodiments according to the description of the method embodiment. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.

The test data generation device provided in one or more embodiments of the present specification may automatically generate rules by combing signing process data corresponding to different client types in advance, and presetting data corresponding to multiple data items involved in the signing process. Then, test data can be automatically generated based on the pre-carded signing process data, the data automatic generation rules of each data item and the configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

The method or apparatus provided by the present specification and described in the foregoing embodiments may implement service logic through a computer program and record the service logic on a storage medium, where the storage medium may be read and executed by a computer, so as to implement the effect of the solution described in the embodiments of the present specification. Accordingly, the present specification also provides a test data generating device comprising a processor and a memory storing processor-executable instructions which, when executed by the processor, implement steps comprising the method of any one of the embodiments described above.

The storage medium may include a physical device for storing information, and typically, the information is digitized and then stored using an electrical, magnetic, or optical media. The storage medium may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy, such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth.

acquiring signing flow data according to the client type;

It should be noted that the above description of the apparatus according to the method embodiment may also include other embodiments. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.

The test data generation device in the above embodiment may automatically generate rules by combing the subscription process data corresponding to different client types in advance, and presetting and configuring data corresponding to multiple data items involved in the subscription process. Then, test data can be automatically generated based on the pre-carded signing process data, the data automatic generation rules of each data item and the configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

The present specification also provides a test data generation system, which may be a single test data generation system, or may be applied to a variety of computer data processing systems. The system may be a single server, or may include a server cluster, a system (including a distributed system), software (applications), an actual operating device, a logic gate device, a quantum computer, etc. using one or more of the methods or one or more of the example devices of the present specification, in combination with a terminal device implementing hardware as necessary. The test data generation system may comprise at least one processor and a memory storing computer executable instructions which, when executed by the processor, implement the steps of the method described in any one or more of the embodiments above.

It should be noted that the above-mentioned system may also include other implementation manners according to the description of the method or apparatus embodiment, and specific implementation manners may refer to the description of the related method embodiment, which is not described in detail herein.

The test data generation system according to the embodiment may automatically generate rules by combing the subscription process data corresponding to different client types in advance and presetting data corresponding to a plurality of data items related to the configuration subscription process. Then, test data can be automatically generated based on the pre-carded signing process data, the data automatic generation rules of each data item and the configuration data. By utilizing the embodiments of the specification, the automatic generation of the test data can be realized, and the test efficiency is greatly improved.

It should be noted that, the above-mentioned apparatus or system in this specification may also include other implementation manners according to the description of the related method embodiment, and a specific implementation manner may refer to the description of the method embodiment, which is not described herein in detail. The embodiments in the present specification are 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. In particular, for the hardware + program class, storage medium + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for the relevant points, refer to the partial description of the method embodiment.

The embodiments of the present description are not limited to what must be consistent with a standard data model/template or described in the embodiments of the present description. Certain industry standards, or implementations modified slightly from those described using custom modes or examples, may also achieve the same, equivalent, or similar, or other, contemplated implementations of the above-described examples. The embodiments using these modified or transformed data acquisition, storage, judgment, processing, etc. may still fall within the scope of the alternative embodiments of the present description.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, etc. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may therefore be considered as a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method or apparatus that comprises the element.

As will be appreciated by one skilled in the art, one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, one or more embodiments of the present description 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.

One or more embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the present specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

The embodiments in the present specification are 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. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment. In the description of the specification, reference to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.

Claims

1. A method for generating test data, comprising:

acquiring signing flow data according to the client type;

2. The method of claim 1, further comprising:

3. The method according to claim 1, wherein the subscription configuration data is configured according to a first data generation rule corresponding to each data item in the subscription process data.

4. The method of claim 2, wherein the first data generation rule or the second data generation rule is determined according to a storage rule of the data item in a database.

5. A test data generation apparatus, characterized in that the apparatus comprises:

6. The apparatus of claim 5, further comprising:

7. The apparatus according to claim 5, wherein the subscription configuration data is configured according to a first data generation rule corresponding to each data item in the subscription process data.

8. The apparatus of claim 6, wherein the first data generation rule or the second data generation rule is determined according to a storage rule of the data item in a database.

9. A test data generation apparatus, the apparatus comprising a processor and a memory for storing processor-executable instructions, which when executed by the processor implement steps comprising:

acquiring signing flow data according to the client type;

10. A test data generation system comprising at least one processor and a memory storing computer-executable instructions which, when executed by the processor, implement the steps of the method of any one of claims 1 to 4.