WO2020259516A1

WO2020259516A1 - Unit testing system and unit testing method

Info

Publication number: WO2020259516A1
Application number: PCT/CN2020/097820
Authority: WO
Inventors: 韦晨曦; 李懿; 陈世阳; 江旻; 李斌
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2019-06-28
Filing date: 2020-06-23
Publication date: 2020-12-30
Also published as: CN110287120B; CN110287120A

Abstract

Disclosed are a unit testing system and a unit testing method. The system comprises a monitor, a scenario construction layer, a data source adaptation layer, a unit testing module, a service database and a scenario library, wherein the scenario construction layer can realize standardized management of a unit testing scenario, and a data source adapter of different data source formats in the data source adaptation layer can enable a system to adapt to multiple data source formats and convert same into a unified data format. Therefore, the problem in the prior art that a single testing scenario cannot be standardized and cannot adapt to multiple data source formats is solved. The unit testing module tests a unit to be tested according to scenario data corresponding to a scenario name stored in the service database, thereby ensuring that an independent and lightweight software development kit will not intrude on original single testing logic.

Description

Unit testing system and testing method

Cross references to related applications

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on June 28, 2019, the application number is 201910580506.7, and the application name is "a unit test system and test method", the entire content of which is incorporated into this application by reference in.

Technical field

The invention relates to the technical field of unit testing, in particular to a unit testing system and a testing method.

Background technique

With the development of computer technology, more and more technologies (such as big data, distributed, Blockchain, artificial intelligence, etc.) are applied in the financial field. The traditional financial industry is gradually changing to Fintech. Unit testing technology is no exception, but due to the security and real-time requirements of the financial and payment industries, it also places higher requirements on technology.

A typical unit testing process can be divided into the following steps:

Data loading and single test scenario initialization: This step is used to load business data from the data source and construct the required business scenario.

Execute business logic to be tested: the actual code logic to be tested.

Assertion test: verify whether the returned result of the business logic is correct.

Transaction rollback: restore to the data environment before the start of this single test for use in the next single test case.

The existing technology single test process mainly has the following shortcomings:

1. Insufficient support for data loading. Data sources may include Excel files, csv files, JPA objects, etc. The differences between these different data sources require developers to adapt in the business code. The consequence is not only that business logic and file processing logic are mixed together, but also The code redundancy is high, and the file processing logic written by different developers may be inconsistent, which in turn reduces the standardization of the code.

2. Management of single test scenarios. The single test process lacks standardized management of single test scenarios, and the standardization of single test scenarios depends on the developer's consciousness.

Summary of the invention

The embodiment of the present invention provides a unit test system and a test method to solve the problem that the single test scenario in the prior art cannot be standardized and cannot be adapted to multiple data source formats.

In the first aspect, an embodiment of the present invention provides a unit test system, including a listener, a scene construction layer, a data source adaptation layer, a unit test module, a business database, and a scene library;

The listener is used to obtain the scene name and send the scene name to the scene construction layer;

The scene construction layer is used to determine the data source adapter corresponding to the scene name from the data source adaptation layer according to the scene name, and read the scene data corresponding to the scene name from the scene library according to the data source adapter corresponding to the scene name; corresponding to the scene name Process the scene data of the processed scene; send the scene data corresponding to the processed scene name to the business database for storage;

The unit test module is used to test the unit to be tested according to the scene data corresponding to the scene name stored in the business database.

The above scheme provides a standardized single test scenario management and application system. The scenario construction layer can realize standardized management of unit test scenarios, and the data source adapters of different data source formats in the data source adaptation layer can enable the system to adapt to multiple data source formats and convert them into a unified data format. This solves the problem that the single test scenario in the prior art cannot be standardized and cannot adapt to multiple data source formats. The unit test module tests the unit to be tested according to the scenario data corresponding to the scenario name stored in the business database to ensure that the independent and lightweight software development kit has no intrusion into the original single test logic.

Optionally, the scene construction layer includes a scene builder, a scene parser, and a data processing link;

The scene builder is used to send the scene name sent by the listener to the scene parser;

The scene parser is used to determine the data source adapter corresponding to the scene name from the data source adaptation layer according to the scene name, and read from the scene library according to the data source adapter corresponding to the scene name Fetching the scene data corresponding to the scene name, and sending the read scene data corresponding to the scene name to the data processing link;

The data processing link is used to process the scene data corresponding to the scene name; and send the processed scene data corresponding to the scene name to the service database for storage.

In the above scheme, the scene construction layer can make numbers according to different scene names, which makes it easy for single test developers to perform the single test process. Single test developers only need to pay attention to the single test start-run-complete this step, as for the complexity The scenario construction process and scenario rollback process are all automatically completed by the present invention to ensure that single test developers can focus on the correctness of the business logic without being distracted by how to create the required scenario. The system provides a default parser. It also supports developers to customize the parser according to business needs. Improved the flexibility and adaptive ability of the system.

Optionally, the listener is further configured to send a data rollback instruction to the scene construction layer after monitoring that the unit test module has completed the test of the unit under test.

In the above scheme, rolling back the database after the single test is completed enables the system to support non-transactional rollback operations, thereby not affecting the transactions in the business logic.

Optionally, the data processing link further includes a data cleaning node;

The scene construction layer is further configured to perform data rollback on the scene data corresponding to the scene name in the service database through the data cleaning node in the data processing link after receiving the data rollback instruction .

In the above scheme, the data processing link is composed of a data processing node and a link manager. The system provides multiple default processing nodes. It also supports developers to add custom nodes. At the same time, new processing nodes can be added to realize custom processing. The processing logic is flexible.

Optionally, the data cleaning node performs data rollback on the scene data corresponding to the scene name in the service database through a reverse database operation.

The above solution does not use spring transaction annotations to achieve similar transaction functions, and the cleanup node uses reverse operations to restore the database state, so that the system supports non-transactional rollback operations, which does not affect the transactions in the business logic.

Optionally, the data processing link cleans, filters, fills, converts, and saves the scene data corresponding to the scene name.

It should be noted that the save node in the data processing link can save the constructed scene data as an sql file, or directly store the constructed scene data in a designated database.

In the second aspect, an embodiment of the present invention provides a test method, including:

Get the scene name;

According to the scene name, read the scene data corresponding to the scene name from the scene library, and process the scene data corresponding to the scene name;

The unit to be tested is tested according to the scene data corresponding to the scene name after processing.

The above solution provides a standardized single-test scenario management and application system. Testing the unit to be tested based on the scenario data corresponding to the processed scenario name can make the system adapt to multiple data source formats and convert them into unified data format.

Optionally, the reading scene data corresponding to the scene name from the scene library according to the scene name includes:

Determine the data source adapter corresponding to the scene name from the data source adaptation layer according to the scene name;

Read the scene data corresponding to the scene name from the scene library according to the data source adapter corresponding to the scene name.

In the above solution, the name of the scene that needs to be loaded is obtained through the developer's annotations, and the developer can focus on the correctness of the business logic, so that the process of how to create the required scene is unnecessary, which simplifies the development process and improves development efficiency.

Optionally, the processing the scene data corresponding to the scene name includes:

The scene data corresponding to the scene name is cleaned, filtered, filled, converted and saved.

In the above solution, different scene parsers are selected for different scene names, and data in different formats are unified into the same format through the data source adapter, so that the system can expand new data source formats and has high flexibility. The system can adapt to a variety of scenarios, so that developers do not need to spend more energy in the process of how to create the desired scenario.

Optionally, after the process of testing the unit to be tested according to the scene data corresponding to the scene name after processing, the method further includes:

When it is determined that the test of the unit to be tested is completed, data rollback is performed on the scene data corresponding to the scene name in the service database.

Optionally, the data rollback of the scene data corresponding to the scene name in the service database includes:

Data rollback is performed on the scene data corresponding to the scene name in the service database through a reverse database operation.

The above scheme is different from Spring's transaction-based rollback method. The cleanup node uses reverse operations to restore the database state so that the system supports non-transactional rollback operations so as not to affect the transactions in the business logic.

In a third aspect, an embodiment of the present invention provides a testing device, including:

Get the unit, get the scene name;

The processing unit reads the scene data corresponding to the scene name from the scene library according to the scene name, and processes the scene data corresponding to the scene name; according to the processed scene name corresponding to the scene name The scenario data is tested for the unit to be tested.

Optionally, the processing unit is specifically configured to:

Optionally, the processing unit is further specifically configured to:

The saving node may directly save the scene data in a designated database, or save the scene data as an sql file and save it in the database.

In a fourth aspect, an embodiment of the present invention provides a computer device, including:

Memory, used to store program instructions;

The processor is configured to call the program instructions stored in the memory, and execute the method described in the second aspect and any optional method according to the obtained program.

In a fifth aspect, an embodiment of the present invention provides a computer-readable non-volatile storage medium, including computer-readable instructions, when the computer reads and executes the computer-readable instructions, the computer is caused to execute the above-mentioned second aspect The method and any optional method.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present invention, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings may be obtained from these drawings without creative labor.

Figure 1 is a schematic diagram of a unit testing system in an embodiment of the present invention;

Figure 2 is a schematic diagram of a unit testing system in an embodiment of the present invention;

FIG. 3 is a schematic flowchart of a test method in an embodiment of the present invention;

FIG. 4 is a schematic flowchart of a test method in an embodiment of the present invention;

Fig. 5 is a schematic diagram of a structure of a unit test device in an embodiment of the present invention.

Detailed ways

In order to better understand the above technical solutions, the above technical solutions will be described in detail below in conjunction with the drawings and specific implementations of the specification. It should be understood that the embodiments of the present invention and the specific features in the embodiments are detailed in the technical solutions of the present invention. Note, rather than limiting the technical solution of the present invention, the embodiments of the present invention and the technical features in the embodiments can be combined with each other if there is no conflict.

1 is a schematic diagram of a unit test system provided by an embodiment of the present invention. The system includes a listener 100, a scene construction layer 200, a data source adaptation layer 300, a unit test module 400, a business database 500, and a scene library 600.

The listener 100 is used to obtain the scene name and send the scene name to the scene construction layer 200.

The scene construction layer 200 is used to determine the data source adapter corresponding to the scene name from the data source adaptation layer 300 according to the scene name, and read the scene data corresponding to the scene name from the scene library 600 according to the data source adapter corresponding to the scene name. The scene data corresponding to the scene name is processed, and the scene data corresponding to the processed scene name is sent to the business database for storage.

The unit testing module 400 is configured to test the unit to be tested according to the scenario data corresponding to the scenario name stored in the service database 500.

The data source adaptation layer 300 is used to provide different data source adapters for the scene construction layer 200, and these different data source adapters can adapt to different data source formats.

The scene library 600 is used to provide scene data corresponding to different scene names for the scene construction layer 200.

Specifically, the scene construction layer 200 may include a scene builder, a scene parser, and a data processing link. Among them, the scene builder is used to send the scene name sent by the listener to the scene parser. The scene parser is used to determine the data source adapter corresponding to the scene name from the data source adaptation layer 300 according to the scene name, and read the scene data corresponding to the scene name from the scene library 600 according to the data source adapter corresponding to the scene name, and read The scene data corresponding to the acquired scene name is sent to the data processing link. The data processing link is used to process the scene data corresponding to the scene name, and send the scene data corresponding to the processed scene name to the service database 500 for storage.

After the unit test module 400 has completed the unit test under test, the listener can also send a data rollback instruction to the scene construction layer 200 after the unit test module 400 has finished testing the unit under test, so that the scene construction layer 200 can respond to the business database. 500 performs a rollback operation. Specifically, the data processing link also includes a data cleaning node. After the scene construction layer 200 receives the data rollback instruction, it can perform data rollback on the scene data corresponding to the scene name in the service database 500 through the data cleaning node in the data processing link.

Further, the data processing link cleans, filters, fills, converts and saves the scene data corresponding to the scene name.

To this end, a unit test system provided by an embodiment of the present invention may have a structure as shown in FIG. 2, where the listener 100 shown in FIG. 1 may be located at the single test monitoring layer, and the scene library shown in FIG. 600 can be located at the scene library layer.

As shown in Figure 2, the single test monitoring layer contains a listener, which is responsible for monitoring the execution and termination of the single test case of the business developer. The implementation of the listener is based on the listening interface of the Spring framework, supports the native listening service of the Spring framework, and also supports the developer's custom listening service to achieve personalized functions. When the single test case is detected to start execution, the listener will entrust the scene construction layer to construct the scene data needed to run the single test; after detecting the completion of the single test execution, the listener will again entrust the scene construction layer to roll back the scene data to The state before the start of the single test.

The scene construction layer is responsible for accepting the delegate of the listener to construct the scene required by the developer or roll back the scene data. After the scene builder receives the commission to construct the scene from the listener, it sends the scene name to the scene parser, and the scene parser determines from which data source to obtain the data needed to construct the scene and entrusts the corresponding data source adapter to read the data . The framework provides a default parser, and also supports developers to customize the parser according to business needs. The data processing link consists of a series of data processing nodes and a link manager, responsible for performing necessary processing on the acquired scene data, including data cleaning, filtering, filling, conversion, and saving. Similarly, the framework provides multiple default processing nodes, and also supports developers to add custom nodes. Among them, after the single test is completed, the cleaning node is responsible for restoring the database to the state before the single test started. Unlike the transaction-based rollback method of the Spring framework, the cleanup node uses a "reverse operation" method to restore the database state. There are two saving strategies for saving nodes. One is to save the constructed scene data as sql files. This strategy is suitable for importing the data into the test environment in the cluster after the local development environment; the other is to directly construct The scene is saved in the specified database, and the framework uses the JFinal framework to realize database interaction. At the same time, the framework provides support for a variety of databases, including H2 memory database, mysql (relational database management system) and so on.

The data source adaptation layer is responsible for adapting various data source formats, and provides a consistent data format for the scene construction layer. For example, Excel Adapter (Adapter) is suitable for handling scenes when the scene library is maintained in excel, Bean Adapter is suitable for handling scenes when the scene library is maintained in the developer's source code, and CSV Adapter is suitable for handling when the scene library is maintained as csv Format file scene. If developers have special needs, such as processing data sources in xml or json format, the framework also allows developers to add customized data source adapters.

The role of the scene library layer is to impose a strong constraint on the business developer's scene library, requiring the business developer to maintain the single test scene data in a unified place to achieve the purpose of standardized management. For example, the framework maintains single test scenarios in excel files by default. The advantage is that excel has better visualization and editability, and non-technical developers can also maintain it.

Based on the above unit test system, FIG. 3 exemplarily shows the flow of a test method provided by an embodiment of the present invention. This process can be executed by the aforementioned unit test system.

As shown in Figure 3, the process specifically includes:

Step 301: Obtain the scene name.

Specifically, when the execution of the single test is detected, the name of the scene that needs to be loaded is obtained through the comments of the developer; and the obtained scene name is sent to the scene builder.

It should be noted that the scene builder constructs different scenes for different scene names. For example, taking the loan core system as an example, suppose the business developer wants to test whether the data in the personal center is correct when the borrower has an overdue loan. The scene name obtained at this time is "single-user bill overdue", and the scene builder selects different data source adapters according to this name to construct a suitable scene, thereby improving the adaptability of the system.

Step 302: According to the scene name, read the scene data corresponding to the scene name from the scene library, and process the scene data corresponding to the scene name.

Specifically, the data processing link cleans, filters, fills, converts, and saves the scene data corresponding to the scene name.

Specifically, the data processing link is divided into multiple processing nodes, and the scene data is cleaned, filtered, filled, converted, saved, and so on.

It should be noted that the listener is based on the spring monitoring interface, supports spring's native monitoring service, and also supports the monitoring service set by the developer. The scene parser can be the default and also supports developer settings. The data processing link includes a string of data processing nodes and a link manager. The data processing node can be the default or it can be added by the developer. For example, taking the loan core system as an example, the scene parser maintains the excel based on the scene data detected, so the scene meta information is passed to the excel data source adapter, and the excel data source adapter is responsible for loading the "overdue" from the excel file For the scene data, the next step is to forward the scene data to the data processing link. After the data is filled by the link, the scene data is converted into SQL statements and inserted into the business database. This completes the scene construction process.

Step 303: Test the unit to be tested according to the scene data corresponding to the scene name after processing, and roll back the database after the execution of the single test is completed.

Specifically, the listener is further configured to send a data rollback instruction to the scene construction layer after monitoring that the unit test module has completed the test of the unit under test;

After receiving the data rollback instruction, the scene construction layer performs data rollback on the scene data corresponding to the scene name in the business database through the data cleaning node in the data processing link.

Specifically, the data cleaning node performs data rollback on the scene data corresponding to the scene name in the business database through a reverse database operation.

The save node can directly save the scene data to the specified database, or save the scene data as an sql file and save it in the database.

It should be noted that the database can use JFinal to achieve interaction; the database includes H2 memory database, mysql, etc.

In order to better explain the embodiments of the present invention, the above-mentioned test procedure will be described below in a specific implementation scenario, as shown in Fig. 4:

Suppose a business developer wants to test whether the data in the Motodai personal center is correct when a borrower has an overdue loan note for Motodai. When the single test developer starts the single test, the single test execution monitor of the present invention detects the start of the single test, and first extracts the scene name from the comment of the single test method. For example, in this example, the scene name is "single user bill overdue ", after the listener passes the scene name to the scene builder, the scene builder recognizes the name and informs the default scene parser to resolve the scene name according to the default configuration. Similarly, the scene parser root detects that the scene data is maintained in the data source excel, so the scene meta information is passed to the excel data source adapter, and the excel data source adapter is responsible for loading the "overdue" scene data from the excel file. In one step, the scene data is forwarded to the data processing link. After the link fills in the data as necessary, the scene data is converted into SQL statements and inserted into the business database. This completes the scene construction process.

After the single test runs, when the listener detects that the single test method exits, it will issue an instruction to notify the scene builder to roll back the data. The scene builder entrusts the task to the data cleaning node in the data processing link, and the cleaning node completes the database recovery by executing a reverse SQL operation.

From the perspective of the single test developer, the single test developer needs to pay attention to the single test start-run-complete this step. As for the complex scene construction process and the scene rollback process, it is guaranteed by the present invention to complete automatically Single test developers can focus on the correctness of the business logic, without being distracted by how to create the required scenarios and how to roll back the single test site.

Based on the same technical concept, FIG. 5 exemplarily shows that an embodiment of the present invention provides a testing device, which can execute the foregoing testing process.

As shown in Figure 5, the device may include:

The obtaining unit 501 obtains the scene name;

The processing unit 502 is configured to read the scene data corresponding to the scene name from the scene library according to the scene name, and process the scene data corresponding to the scene name; according to the processed scene The scene data corresponding to the name is tested for the unit to be tested.

Optionally, the processing unit 502 is specifically configured to:

Optionally, the processing unit 502 is further specifically configured to:

Wherein, the database can use JFinal to realize interaction; the database includes H2 memory database, mysql, etc.

Based on the same technical concept, an embodiment of the present invention provides a computer device, including:

Memory, used to store program instructions;

The processor is configured to call the program instructions stored in the memory and execute the above-mentioned test method according to the obtained program.

Based on the same technical concept, the embodiments of the present invention provide a computer-readable non-volatile storage medium, including computer-readable instructions, and when the computer reads and executes the computer-readable instructions, the computer executes the above-mentioned test method.

Finally, it should be noted that those skilled in the art should understand that the embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention can be in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) containing computer-usable program codes. The present invention is described with reference to flowcharts and/or block diagrams of the method, equipment (system), and computer program product according to the present invention. It should be understood that each process and/or block in the flowchart and/or block diagram, and the combination of processes and/or blocks in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing equipment to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing equipment can be generated It is a device that realizes the functions specified in one process or multiple blocks in the flowchart and/or one block or multiple blocks in the block diagram.

These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device. The device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the scope of the present invention. In this way, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalent technologies, the present invention is also intended to include these modifications and variations.

Claims

A unit test system, which is characterized by comprising a listener, a scene construction layer, a data source adaptation layer, a unit test module, a business database, and a scene library;

The listener is used to obtain the scene name, and send the scene name to the scene construction layer;

The scene construction layer is used to determine the data source adapter corresponding to the scene name from the data source adaptation layer according to the scene name, and read from the scene library according to the data source adapter corresponding to the scene name Fetching the scene data corresponding to the scene name; processing the scene data corresponding to the scene name; sending the processed scene data corresponding to the scene name to the business database for storage;

The unit test module is configured to test the unit to be tested according to the scene data corresponding to the scene name stored in the service database.
The system according to claim 1, wherein the scene construction layer includes a scene builder, a scene parser, and a data processing link;

The scene builder is used to send the scene name sent by the listener to the scene parser;

The scene parser is used to determine the data source adapter corresponding to the scene name from the data source adaptation layer according to the scene name, and read from the scene library according to the data source adapter corresponding to the scene name Fetching the scene data corresponding to the scene name, and sending the read scene data corresponding to the scene name to the data processing link;

The data processing link is used to process the scene data corresponding to the scene name; and send the processed scene data corresponding to the scene name to the service database for storage.
The system according to claim 2, wherein the listener is further configured to send a data rollback instruction to the scene construction layer after monitoring that the unit test module has completed the test of the unit under test.
The system according to claim 2, wherein the data processing link further comprises a data cleaning node;

After receiving the data rollback instruction, the scene construction layer performs data rollback on the scene data corresponding to the scene name in the service database through the data cleaning node in the data processing link.
The system according to claim 4, wherein the data cleaning node performs data rollback on the scene data corresponding to the scene name in the service database through a reverse database operation.
The system according to any one of claims 1 to 5, wherein the data processing link cleans, filters, fills, converts and saves the scene data corresponding to the scene name.
A test method, characterized in that it comprises:

Get the scene name;

According to the scene name, read the scene data corresponding to the scene name from the scene library, and process the scene data corresponding to the scene name;

The unit to be tested is tested according to the scene data corresponding to the scene name after processing.
The method according to claim 7, wherein the reading the scene data corresponding to the scene name from the scene library according to the scene name comprises:

Determine the data source adapter corresponding to the scene name from the data source adaptation layer according to the scene name;

Read the scene data corresponding to the scene name from the scene library according to the data source adapter corresponding to the scene name.
The method according to claim 7, wherein the processing the scene data corresponding to the scene name comprises:

The scene data corresponding to the scene name is cleaned, filtered, filled, converted and saved.
The method according to any one of claims 7 to 9, characterized in that, after the process of testing the unit to be tested according to the scene data corresponding to the scene name after processing, the method further comprises:

When it is determined that the test of the unit to be tested is completed, data rollback is performed on the scene data corresponding to the scene name in the service database.
The method according to claim 10, wherein the data rollback of the scene data corresponding to the scene name in the service database comprises:

Data rollback is performed on the scene data corresponding to the scene name in the service database through a reverse database operation.
A computing device, characterized by comprising:

Memory, used to store program instructions;

The processor is configured to call the program instructions stored in the memory, and execute the method according to any one of claims 7 to 11 according to the obtained program.
A computer-readable non-volatile storage medium, characterized by comprising computer-readable instructions, when the computer reads and executes the computer-readable instructions, the computer is caused to execute any one of claims 7 to 11 Methods.