CN113760734A - A data preparation method and device, device, and storage medium - Google Patents

Abstract

The embodiment of the present application discloses a data preparation method, the method includes: acquiring log data of an object to be tested processing a service request; extracting a service execution statement in the log data; performing reverse conversion on the service execution statement, The target execution statement is obtained; the target execution statement is used to update the data in the target database to test the object to be tested. In addition, the embodiments of the present application also disclose a data preparation apparatus, equipment, and storage medium.

Description

A data preparation method, device, device, and storage medium

technical field

The embodiments of the present application relate to the field of computer technologies, and relate to, but are not limited to, a data preparation method, apparatus, device, and storage medium.

Background technique

With the increasing scale of software systems, interface automation testing is valued by more and more companies. Mainly because interface automation can liberate manpower, improve test efficiency, and reduce test costs.

At present, the interface automation test is mainly used in the regression phase of the test, and is triggered by the tester of the module. However, most of the work of interface automation testing is spent on the preliminary preparation work, especially the time spent on data preparation, which requires manual preparation of data preparation, resulting in long test cycles and low work efficiency.

SUMMARY OF THE INVENTION

In view of this, the embodiments of the present application provide a data preparation method, apparatus, device, and storage medium to solve at least one problem in the related art, which can reduce the user's participation in the automatic test process and improve work efficiency.

The technical solutions of the embodiments of the present application are implemented as follows:

In a first aspect, an embodiment of the present application provides a data preparation method, the method includes:

Obtain the log data of the object under test processing business requests;

extracting business execution statements in the log data;

The business execution statement is reversely converted to obtain the target execution statement; the target execution statement is used to update the data in the target database to test the object to be tested. .

In a second aspect, an embodiment of the present application provides a data preparation device, and the device includes:

The acquisition unit is used to acquire the log data of the object to be tested processing the business request;

an extraction unit for extracting business execution statements in the log data;

The conversion unit is used to reversely convert the service execution statement to obtain a target execution statement; the target execution statement is used to update the data in the target database to test the object to be tested.

In a third aspect, an embodiment of the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the above data preparation method when executing the computer program steps in .

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps in the above data preparation method.

In the embodiments of the present application, a data preparation method, device, device, and storage medium are provided, which are used to obtain log data for processing a service request by an object under test; extract service execution statements in the log data; Reverse conversion to obtain the target execution statement; the target execution statement is used to update the data in the target database to test the object to be tested, thereby obtaining the business execution statement related to the object to be tested through test recording, And automatically convert business execution statements into data preparation statements that automatically generate data preparation, reduce the learning cost and writing cost of writing use cases, save manpower, and improve data preparation efficiency.

Description of drawings

FIG. 1 is a schematic diagram of an optional architecture of a test system according to an embodiment of the present application;

FIG. 2 is an optional schematic structural diagram of a test system according to an embodiment of the present application;

3 is an optional schematic flowchart of a data preparation method provided by an embodiment of the present application;

FIG. 4 is an optional schematic structural diagram of a test server provided by an embodiment of the present application;

FIG. 5 is an optional schematic structural diagram of a test server provided by an embodiment of the present application;

FIG. 6 is an optional schematic structural diagram of a test server provided by an embodiment of the present application;

FIG. 7 is an optional schematic flowchart of a data preparation method provided by an embodiment of the present application;

FIG. 8 is an optional schematic flowchart of a data preparation method provided by an embodiment of the present application;

FIG. 9 is an optional schematic structural diagram of a data preparation apparatus provided by an embodiment of the present application;

FIG. 10 is an optional schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application more clear, the specific technical solutions of the application will be described in further detail below with reference to the accompanying drawings in the embodiments of the present application. The following examples are used to illustrate the present application, but are not intended to limit the scope of the present application.

The embodiments of the present application may provide a data preparation method, apparatus, device, and storage medium. In practical applications, the data preparation method can be implemented by a data preparation device, and each functional entity in the data preparation device can be implemented by hardware resources of computer equipment (such as terminal equipment or servers), such as computing resources such as processors, and communication resources (such as for supporting Realize communication in various ways such as optical cable, cellular, etc.) collaborative realization.

The data preparation method of the embodiment of the present application can be applied to the test system shown in FIG. 1 . The data preparation device in the test system can obtain log data of the object to be tested, process the log data, and obtain a target execution statement; the target The execution statement is used to update the data in the target database to test the object to be tested.

In an example, as shown in FIG. 1, the test system includes a test terminal 10 and a server terminal 20; wherein, the test terminal 10 is deployed with the object to be tested, and the test terminal is deployed with a log collection plug-in, which can collect the data of the device to be tested. log data, and send the collected log data to the server 20 . The server 20 acts as a data preparation end of the test end, and generates preparation data for testing the test end. The object to be tested may be a device, a system, an application program or an interface, etc. in the test terminal.

In an example, as shown in FIG. 1 , the test terminal 10 and the server terminal 20 interact through the network 30 . In an example, the testing terminal 10 and the server 20 are integrated in the same physical entity.

The server 20 may be implemented as a data preparation device implementing the data preparation method. The server 20 obtains the log data of the object to be tested processing the business request; extracts the business execution statement in the log data; reversely converts the business execution statement to obtain the target execution statement; the target execution statement is used for the target execution statement. The data in the database is updated to test the object to be tested.

In an example, the server 20 automatically triggers the service request, and sends the service request to the tester 10 . After receiving the service request, the test terminal 10 instructs the object to be tested to execute the service request, so as to execute the service function corresponding to the service request.

In an example, as shown in FIG. 2 , a client 40 is also included in the test, and the client 40 triggers a service request based on the user's operation, and sends the service request to the testing terminal 20 . When the test terminal 20 receives the service request, it instructs the object to be tested to execute the service request, so as to execute the service function corresponding to the service request.

In an example, the client 40 may capture feature information of the service request, and send the feature information to the server 20, where the feature information is used to generate a test case for testing the object to be tested.

In practical applications, the client 40 , the testing terminal 10 and the server 20 may be implemented on the same physical entity, or may be distributed on different physical entities.

Combined with the above-mentioned test system, this embodiment provides a data preparation method, which can save manpower and improve data preparation efficiency.

Below, with reference to the test system shown in FIG. 1 or FIG. 2 , various embodiments of the data preparation method, apparatus, device, and storage medium provided by the embodiments of the present application will be described.

This embodiment provides a data preparation method, which is applied to a data preparation device, and the data preparation device may be a server, where the server may be a computer device or a distributed network composed of computer devices. The functions implemented by the method can be implemented by a processor in a computer device calling program codes, and of course the program codes can be stored in a computer storage medium. It can be seen that the computer device includes at least a processor and a storage medium.

FIG. 3 is a schematic flowchart of the implementation of a data preparation method according to an embodiment of the present application. As shown in FIG. 3 , the method may include the following steps:

S301. Obtain log data of the object to be tested processing the business request;

The test terminal receives the service request from the server or client, and processes the service request through the object to be tested, so as to execute the service function corresponding to the service request. The object to be tested may be an application program, a hardware element, a software interface, etc. in the test terminal. Service requests include query requests, search requests, function start requests, access requests, and the like.

Here, a log collection plug-in is deployed on the test side. The log collection plug-in reads log files from a specified location and reads the log data of the object to be tested in the test side to process business requests. The log collection plugin sends the read log data to the server.

In practical applications, when the log data is sent to the server, the test end is set to the debug mode, and in the debug mode, the log data read by the log collection plug-in is printed out.

In some embodiments, when the test end and the server end are located in the same physical entity, the test end sends log data to the message queue in the form of log messages, and the server end reads the log messages from the message queue, thereby receiving the log data . The message queue may be a distributed message queue for receiving, storing and forwarding log data.

S302, extracting business execution statements in the log data;

After receiving the log data, the server parses the log data to determine the business execution statement used by the object to be tested when processing the business request. Here, the target execution statement may be a Structured Query Language (SQL) statement.

In an example, when the business request is a query request, the SQL statement may be: select student.sname,course.cname from student,course where student.id=course.student_id limit100, the statement indicates the student from the table student (student table) And table course (course schedule) to query student.sname, course.cname (student elective course data).

In this embodiment of the present application, an extraction method for extracting SQL statements from log data may include one of the following:

Extraction method 1. Regularly match log data by setting regular expressions;

Extraction method 2: Process the log data through the called extraction program.

When the extraction method is the extraction method 2, the language used in the extraction program may be the object-oriented programming language Java.

In this embodiment of the present application, the extraction method for extracting SQL statements from log data is not limited in any way.

S303, performing reverse conversion on the business execution statement to obtain a target execution statement;

After the server determines the business execution statement, it reversely converts the business execution statement based on the conversion strategy. The reverse strategy includes reverse transformation rules, such as: converting an insert statement into a delete statement; converting a query statement into an insert statement.

In this embodiment of the present application, one service execution statement may be converted into one or more target execution statements.

In an example, a business execution statement is directly converted into a corresponding target execution statement.

In an example, the business execution statement is split into multiple sub-query statements, and each sub-query statement is converted into a corresponding target business statement, so that one business execution statement is reversely converted into multiple target execution statements.

Taking the business execution statement as: select a.a,b.b from a,b where a.id=b.id limit 100 as an example, the target execution statement after reverse conversion includes:

Target execution statement 1: insert into a values(x,x,x);

The target executes statement 2: insert into b values(x,x,x).

The data in the target execution statement can be called target data, and the target data can be obtained from the database of the test system through the target sentence structure in the target execution statement, or obtained through the user's input operation.

The target statement structure is the statement in the target execution statement that indicates the execution mode. Taking the above target execution statement 1 as an example, the target statement structure is insert. Taking the above target execution statement 2 as an example, the target statement structure is insert.

Here, the target execution statement is used to update the data in the target database to test the object to be tested.

After the server determines the target execution statement, the test case for the object to be tested can be generated directly through the target execution statement.

In practical applications, the server can be connected to a test platform that executes the test function, the server sends the determined target execution statement to the test platform, and the test platform generates a test case for the object to be tested through the target execution statement.

Here, the target execution statement is used as the data preparation part for the test case of the object to be tested, so that when the test case is executed, the data in the database is updated, and the updated data is used as the test data for testing the object to be tested.

In some embodiments, the test terminal, the server terminal, and the test platform are integrated into a test server, and the structure of the test server may be as shown in FIG. 4, including: a test terminal 401, a server terminal 402 and a test platform 403, wherein

The test terminal 401 receives and executes the service request, the log collection plug-in deployed in the test platform collects log data, and sends the collected log data to the server 402 . The server 402 receives log data, parses the log data, and extracts business execution statements in the log data; reversely converts the business execution statements to obtain target execution statements, and sends the obtained target execution statements to Test platform 403 . The test platform generates a test case for testing the object to be tested through the target execution statement. Here, the test platform 403 generates the data preparation in the test case through the target execution statement, so as to update the data in the target database through the data preparation, and obtain the above-mentioned data preparation. The test data used when the object to be tested is tested.

In some embodiments, a message queue is set between the test end 401 and the server end 402, the test end 401 sends log data to the message queue, and the server end 402 reads the log data from the message queue.

The data preparation method provided in the embodiment of the present application can be used in test scenarios such as automated interface testing. The embodiments of the present application do not impose any limitations on the applied test scenarios.

In the embodiment of the present application, log data for processing a service request by an object to be tested is obtained; business execution statements in the log data are extracted; the business execution statements are reversely converted to obtain target execution statements; the target execution statements are For updating the data in the target database, to test the object to be tested, thereby obtaining business execution statements related to the object to be tested through test recording, and automatically converting the business execution statements into data preparation for automatically generating data preparation Statements, reduce the learning cost and writing cost of writing use cases, save manpower, and improve the efficiency of data preparation.

In some embodiments, the implementation of S302 includes:

S3021. Obtain the set regular expression;

S3022. Perform regular matching on the log data by using the regular expression, and extract business execution statements in the log data.

A regular expression is a regular string composed of characters to express the filtering logic of log data

In one example, regular expressions include: select.*from.*$, update.*set.*$, insertinto.*$, and delete from.*$. Among them, "." is used to match any single character except newline "\n" and carriage return "\r"; "*" is used to match the preceding subexpression any number of times. For example, zo* matches "z" as well as "zo" and "zoo"; "$" is used to match the end of the input line.

In some embodiments, the implementation of S303 includes:

S3031. Extract the sub-query statement and table identifier in the service execution statement.

S3032. Determine the target execution statement according to the sub-query statement and the table identifier.

Taking the business execution statement as select a.a,b.b from a,b where a.id=b.id limit 100 as an example, the sub-queries in the business execution statement include:

Subquery 1: Select a.*from a,b where a.id=b.id limit 0,100;

Subquery 2: Select b.*from a,b where a.id=b.id limit 0,100;

The identifier of the table corresponding to the sub-query statement 1 is a, and the identifier of the table corresponding to the sub-query statement 2 is b.

The target execution statement obtained based on the subquery statement 1 and the corresponding table identifier is the target execution statement 1: insertinto a values(x,x,x), and the target execution statement obtained based on the subquery statement 2 and the corresponding table identifier is the target execution statement Statement 2: insert into b values(x,x,x).

The sub-query statement in the embodiment of the present application may include: query statement: select statement, insert statement: insert statement, delete statement: delete statement, edit statement: update statement, and the like. The embodiment of the present application does not impose any limitation on the statement type of the sub-query statement.

In some embodiments, the implementation of S3031 includes:

Parse the business execution statement into an abstract syntax tree including at least one node; the nodes of the abstract syntax tree can be accessed; traverse each node of the abstract syntax tree, and determine the subquery statement and table corresponding to the node logo.

Taking the business execution statement as an SQL statement as an example, when the server splits the business execution statement, the SQL parser abstracts the SQL statement into a syntax tree (AST), and all AST nodes support access (Visitor) Mode, the server can traverse the nodes in the syntax tree according to the user-defined traversal logic. When the server encounters different nodes, it can perform corresponding processing. When the server traverses the complete syntax tree, it can parse out all the subqueries in the SQL statement.

In some embodiments, the implementation of S3032 includes: converting the sub-query statement to obtain a target statement structure; reconstructing the sub-query statement and the corresponding table identifier to obtain target data; converting the target statement structure Assemble with the target data to obtain the target execution statement.

The server converts the sub-query statement through the set conversion rules to obtain the target statement structure. In one example, the transformation rules include:

Rule 1. Convert the select statement into an insert statement;

Rule 2: Convert the insert statement into a delete statement;

Rule 3: Convert the update statement into an insert statement;

Rule 4: Convert the delete statement into an insert statement.

Here, the server reconstructs the sub-query statement and the table identifier corresponding to each sub-query statement, obtains the statement for acquiring the target data, and acquires the target data from the connected target database through the statement for acquiring the target data.

In this embodiment of the present application, the data construction process is reversed. In an example, the purpose of the test is: to query the information of user a on the page, there should be information of a in the database, then call the interface for obtaining the information of user a in the test environment, and the corresponding select statement will be printed in the log data, such as select*from user where name=a; the test environment has the information of a. Then you can convert the statement in the log into an insert statement as the SQL required for data preparation, insert data in the automated environment, and prepare the data for query a. In an example, the purpose of the test is to edit student data, and there should be student data in the database, then the interface for editing student data is called in the test environment, and the corresponding update statement will be printed in the log data, then the update in the log data can be changed. The statement is converted into an insert statement, which is used as the SQL required for data preparation, performs data query in an automated environment, and prepares the required student data.

In some embodiments, after S3031, the method further includes: generating a data clearing command; assembling the data clearing command and the table identifier to obtain a data clearing statement; the data clearing statement is used to complete the data clearing statement. After the test of the object to be tested, the data in the table corresponding to the table identifier is cleared.

Here, the flush command may be a truncate statement.

In some embodiments, characteristic information of the object to be tested processing the service request is acquired; the characteristic information is used to generate a test case for testing the object to be tested.

Wherein, the feature information includes at least one of the following information: request header, parameter transfer, return value and other information.

In the embodiment of the present application, the server sends the feature information to the test platform that generates the test case, as a parameter of the use case entity of the test case.

In practical applications, the client generates a service request based on the user's operation on the browser. At this time, the client fetches feature information from the browser and sends the feature information to the server.

In the following, the data preparation method provided by the embodiment of the present application is further described by taking an interface test scenario as an example.

Interface testing is to test the interface between systems or components, and is mainly used to detect the interaction points between external systems and systems and between internal subsystems. Check the data exchange, transfer and control management process of the interface, as well as the mutual logical dependencies. The interface protocols are divided into HTTP, WebService, Dubbo, Thrift, Socket and other types, and the test types are mainly divided into functional test, performance test, stability test, security test, etc.

The process of interface testing includes: requirement analysis, use case design, script development, test execution and result analysis. Among them, the use case device includes three parts: data preparation (setup), use case entity and data destruction (teardown). : request path, request parameters, expected results, etc.; data destruction includes the logic of cleaning up test traces, which is to restore the modification of data during the test process. The writing of data preparation and data destruction accounts for more than 60% of the entire use case writing workload. Because the function of the program is to process data, an interface often starts processing from a certain stage of the data. Before testing this interface, the data to be processed must be prepared, and the data may depend on other data, which improves the preparation. Data complexity and difficulty.

In the related art, in the data preparation stage, the data preparation scheme includes:

Solution 1: Generate data based on a Graphical User Interface (Graphical User Interface, GUI) operation.

In Scheme 1, the API to be tested has a GUI, and through the GUI operation, the data is generated by manually executing the business process in the system.

The second solution is to generate data based on the invocation of the Application Programming Interface (API).

In the second solution, the API is directly called for data preparation. If there are multiple entities required by the interface to be tested, the new APIs of multiple entities need to be called.

Option 3: Generate data based on database operations.

In the third solution, the data to be created by the interface to be tested is directly inserted into the system database by executing the corresponding SQL statement.

Option 4: Self-built test data based on a third-party library.

In scheme 4, the code is directly written and encapsulated into a function to generate test data through the encapsulated function.

However, the above test data generation schemes all have technical defects:

For scheme 1, it is necessary to manually create test data in the business system, which is inefficient. Moreover, if the interface to be tested is to delete or edit the interface, the constructed test data is not suitable for repeated use. The test data prepared in this scheme is only It is suitable for use when testing the query interface.

For solution 2, firstly, not all entities have APIs, so it is not suitable for testing all interfaces; secondly, when the business is complex, multiple APIs need to be called, and the complexity is high, and when a large amount of test data is required, Calling the API is inefficient, making data preparation inefficient.

For scheme three, when generating test data by operating on the database, the testers are required to have a high understanding of the relationship between business functions and database tables, so that they can directly write SQL statements. And when a business involves multiple database tables, it is easy to miss SQL, resulting in missing test data.

For scheme 4, it is necessary to manually write code, which is labor-intensive, labor-intensive, and prolongs the test cycle.

Therefore, the data preparation scheme in the related art has a high degree of user participation, and requires users to have a high prior knowledge of system business and to know the relationship between the automated test interface and database tables, which makes the writing of automated test cases face efficiency. Low cost, high experience cost.

The embodiment of the present application provides a data preparation method, which captures SQL statements related to the interface to be tested and automatically converts them into data preparation statements, so as to automatically generate SQL statements required for data preparation, and reduce the learning cost and the writing cost of writing use cases. cost, to improve the efficiency of data preparation, save manpower, and solve the problems of low data preparation efficiency and high user participation in related technologies.

In the embodiment of the present application, the service execution process is recorded in the test environment, and during the service execution process, the request header, parameters, return value and other information of the test case are extracted from the browser as the use case entity part of the test case. Extract the log information from the log information, generate data preparation information and data destruction information through the analysis and conversion of the log information, and transmit the generated data preparation information and data destruction information to the automation interface platform, and then prepare the data required for the test to Prepare for automated testing.

It can be applied to the test server shown in FIG. 5 . As shown in FIG. 5 , the test server 500 includes: an interaction module 501 , a business system to be tested 502 , a message queue 503 , a log extraction module 504 , an SQL parsing module 505 , and an interface automation platform 506 . in,

The interaction module 501 is used for interaction with the business system to be tested 502 and the interface automation platform 506 .

When the business system receives the business request, the interaction module sends the business request to the business system to be tested 502, and captures feature information such as request headers, request parameters, and return value information from the browser, and obtains information from the SQL parsing module 505, including The target SQL statement and the data preparation information of the target data are assembled with the feature information and the data preparation information to obtain the fields required by a test case, and transmit them to the interface automation platform 506 .

The service system to be tested 502: a log collection plug-in is deployed to collect service logs.

Here, the business system 502 to be tested can be set to a debug mode, so that the log can print business SQL statements.

The message queue 503 is a distributed message queue used to complete the transfer of log messages of the business system under test to the log extraction module 504 .

Log extraction module 504 : for processing log messages received from the message queue 503 .

Here, the log extraction module 504 can use regular expressions to filter out useless information in the log, only extract business SQL statements printed in the log, and send the extracted business SQL statements to the SQL parsing module 505 .

SQL parsing module 505 : the input is a set of business SQL statements, and the target SQL required for data preparation is obtained through algorithms such as reverse parsing and reconstruction of the business SQL statements, and the target SQL is sent to the interaction module 501 .

As shown in FIG. 6 , the SQL parsing module 505 includes: a structuring sub-module 5051 , an SQL parsing sub-module 5052 , a statement conversion sub-module 5053 , and a data query sub-module 5054 .

Interface automation platform 506: The input is the automated test case information transmitted from the interactive module, and the newly added test case interface is invoked to generate an automated test case.

The data preparation method provided by the embodiment of the present application is shown in FIG. 7 , including:

S701. Collect logs, and extract business SQL statements in the logs.

A log collection plug-in is deployed on the test server of the business system to be tested. When a business request is sent to the test server, the log collection plug-in will read the log file from the specified location and transmit the read log file in the form of log messages to the message queue. The log extraction module consumes the corresponding log messages from the message queue, and extracts the business SQL statements in the log through regular matching.

S702. Perform reverse analysis on the business SQL statement to obtain target SQL and business data.

A business SQL statement may involve multiple tables and a series of calculation logic, and data preparation needs to insert the required data into these tables or clear the existing data. The SQL parsing module is to realize this conversion function.

The log extraction module transmits the extracted business SQL statement to the SQL parsing module.

The structuring submodule 5051 parses the business SQL statement lexically and grammatically, and parses the business SQL statement into a structure of an abstract syntax tree. Here, the structuring submodule may be an SQL parser. In one example, the SQL parser is the open source druid's SQL Parser module.

The SQL parsing sub-module 5052 extracts the sub-query statement in the business SQL statement and the table name of the used table from the structure of the abstract syntax tree, so as to concatenate the SQL required for data preparation, that is, the target SQL.

The target SQL consists of two parts: the SQL statement structure and the business data to be inserted.

(1) The statement conversion sub-module 5053 converts the sub-query statement into an SQL statement structure, that is, a target sub-query statement according to a set rule. The structure of the SQL statement is different according to different interface generation rules. The rules are as follows:

Query interface: The corresponding select statement will be printed in the background, and the generation rule is to convert the select statement into an insert statement;

New interface: the insert statement will be printed in the background, and the generation rule is to convert the insert statement into a delete statement;

Edit interface or delete interface: The update statement or delete statement will be printed in the background. The generation rule is to convert the update statement into an insert statement, or convert the delete statement into an insert statement.

In practical applications, when the object to be tested is an edit interface or a delete interface, the data required for the edit interface or delete interface needs to be constructed before the edit or delete operation is performed. Here, the statement required for data construction can be obtained by calling the query interface .

The data query sub-module 5054 further assembles the sub-query statement and the table name to obtain the sub-query SQL statement that can obtain the table data corresponding to the interface. The test server connects to the test database, and executes the SQL subquery statement to obtain business data, that is, the obtained business data is the relevant test data from the test database.

S703: Assemble the target SQL and business data to obtain a data structure statement.

The interactive module in the test server assembles the target SQL and business data to obtain the target SQL statement required for data preparation.

In the embodiment of the present application, the test server also generates SQL statements required for the data destruction process, here, a truncate statement is generated, and the truncate statement and all the tables obtained by the SQL parsing module are assembled to obtain the SQL statements required for the destruction process.

In the embodiment of the present application, when the object to be tested is an interface, one or more statements will be printed in the log. For example, when the object to be tested is a query interface, one or more select statements may be printed in the log. Another example: when the object to be tested is an editing interface, select statements, update statements, etc. may be printed in the log.

Here, taking the preparation of a test case for automated testing of a user query interface as an example, the data preparation method provided by the embodiment of the present application, as shown in FIG. 8 , includes:

S801. Print a business log;

Here, the user clicks the query button on the page of the test server, the test server generates a query request based on the click operation received by the test button, and executes the query request. At this time, the background of the test server will print the business log of executing the query request;

S802. Extract the SQL in the business log;

The test server grabs the corresponding business log from the log, and performs regular matching on the business log according to the regular expression, and extracts the SQL statement: select a.a,b.b from a,b where a.id=b.id limit100, And pass it to the SQL parsing module.

S803: Structure and split the SQL statement to obtain test data and target SQL statement.

The SQL parsing module will structure the SQL statement to split the sub-query statement; the data query module will assemble the corresponding data query statement, connect the test database to execute the database data corresponding to the interface query, and the query statement is as follows:

Select a.*from a,b where a.id=b.id limit 0,100;

Select b.*from a,b where a.id=b.id limit 0,100;

Then assemble the table information obtained by the SQL parsing module with the data information obtained from the test library, and finally convert the business SQL statement into insert into a values(x,x,x); insert into b values(x,x,x) The data preparation statement, at this time, the data construction method of the user query interface is completed.

A truncate statement is also generated:

truncate table a;

truncate table b.

FIG. 9 is a schematic diagram of the implementation structure of a data preparation apparatus according to an embodiment of the present application. As shown in FIG. 9 , the apparatus 900 includes an acquisition unit 901 , an extraction unit 902 , and a conversion unit 903 .

An obtaining unit 901 is used to obtain the log data of the processing service request of the object to be tested; the processing unit

an extraction unit 902, configured to extract business execution statements in the log data;

The conversion unit 903 is configured to reversely convert the service execution statement to obtain a target execution statement; the target execution statement is used to update the data in the target database to test the object to be tested.

In some embodiments, the extraction unit 902 is further configured to:

Get the set regular expression;

Perform regular matching on the log data through the regular expression, and extract business execution statements in the log data.

In some embodiments, the conversion unit 903 is further configured to:

Extract the subquery statement and table identifier in the service execution statement.

The target execution statement is determined according to the subquery statement and the table identifier.

In some embodiments, the conversion unit 903 is further configured to:

Parse the business execution statement into an abstract syntax tree including at least one node; the nodes of the abstract syntax tree can be accessed;

Traverse each node of the abstract syntax tree, and determine the subquery statement and table identifier corresponding to the node.

In some embodiments, the conversion unit 903 is further configured to:

Converting the sub-query statement to obtain the target statement structure;

Reconstructing the subquery statement and the corresponding table identifier to obtain target data;

The target statement structure and the target data are assembled to obtain the target execution statement.

In some embodiments, the apparatus 900 further includes: a destruction unit for:

Generate data clear command;

Assembling the data clearing command and the table identification to obtain a data clearing statement; the data clearing statement is used to clear the data in the table corresponding to the table identification after completing the test of the object to be tested .

In some embodiments, the apparatus 900 further includes: a feature unit for:

Obtain feature information of the object to be tested processing the service request; the feature information is used to generate a test case for testing the object to be tested. .

It should be noted that the data preparation device provided in the embodiment of the present application includes the included units, which can be implemented by a processor in an electronic device; of course, it can also be implemented by a specific logic circuit; in the process of implementation, the processor It can be a central processing unit (CPU, Central Processing Unit), a microprocessor (MPU, Micro Processor Unit), a digital signal processor (DSP, Digital Signal Processor) or a field programmable gate array (FPGA, Field-Programmable Gate Array), etc. .

The descriptions of the above apparatus embodiments are similar to the descriptions of the above method embodiments, and have similar beneficial effects to the method embodiments. For technical details not disclosed in the device embodiments of the present application, please refer to the descriptions of the method embodiments of the present application for understanding.

It should be noted that, in the embodiments of the present application, if the above data preparation method is implemented in the form of a software function module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of software products in essence or the parts that contribute to related technologies. The computer software products are stored in a storage medium and include several instructions to make A computer device (which may be a personal computer, a server, or a network device, etc.) executes all or part of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a removable hard disk, a read only memory (Read Only Memory, ROM), a magnetic disk or an optical disk and other mediums that can store program codes. As such, the embodiments of the present application are not limited to any specific combination of hardware and software.

Correspondingly, an embodiment of the present application provides an electronic device, including a memory and a processor, where the memory stores a computer program that can be run on the processor, and when the processor executes the program, the computer program provided in the foregoing embodiments is implemented. Steps in a data preparation method. Wherein, the electronic device may be a server.

Correspondingly, the embodiments of the present application provide a storage medium, that is, a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, implements the data preparation method provided in the foregoing embodiments.

It should be pointed out here that the descriptions of the above storage medium and device embodiments are similar to the descriptions of the above method embodiments, and have similar beneficial effects to the method embodiments. For technical details not disclosed in the embodiments of the storage medium and device of the present application, please refer to the description of the method embodiments of the present application to understand.

It should be noted that FIG. 10 is a schematic diagram of a hardware entity of an electronic device according to an embodiment of the present application. As shown in FIG. 10 , the electronic device 1000 includes: a processor 1001 , at least one communication bus 1002 , and at least one external communication interface 1004 and memory 1005. Among them, the communication bus 1002 is configured to realize the connection communication between these components. In an example, the electronic device 1000 further includes a user interface 1003, wherein the user interface 1003 may include a display screen, and the external communication interface 1004 may include a standard wired interface and a wireless interface.

The memory 1005 is configured to store instructions and applications executable by the processor 1001, and can also cache data to be processed or processed by the processor 1001 and various modules in the electronic device (for example, image data, audio data, voice communication data and video data). communication data), which can be implemented by flash memory (FLASH) or random access memory (Random Access Memory, RAM).

It is to be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic associated with the embodiment is included in at least one embodiment of the present application. Thus, appearances of "in one embodiment" or "in some embodiments" in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, and should not be dealt with in the embodiments of the present application. implementation constitutes any limitation. The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages or disadvantages of the embodiments.

It should be noted that, herein, the terms "comprising", "comprising" or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined, or Can be integrated into another system, or some features can be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms. of.

The unit described above as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit; it may be located in one place or distributed to multiple network units; Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in each embodiment of the present application may all be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above integration The unit can be implemented either in the form of hardware or in the form of hardware plus software functional units.

Those of ordinary skill in the art can understand that all or part of the steps of implementing the above method embodiments can be completed by program instructions related to hardware, the aforementioned program can be stored in a computer-readable storage medium, and when the program is executed, the execution includes: The steps of the above method embodiments; and the aforementioned storage medium includes: a removable storage device, a read only memory (Read Only Memory, ROM), a magnetic disk or an optical disk and other media that can store program codes.

Alternatively, if the above-mentioned integrated units of the present application are implemented in the form of software function modules and sold or used as independent products, they may also be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied in the form of software products in essence or the parts that contribute to related technologies. The computer software products are stored in a storage medium and include several instructions to make A computer device (which may be a personal computer, a server, or a network device, etc.) executes all or part of the methods described in the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

The above is only the embodiment of the present application, but the protection scope of the present application is not limited to this. Covered within the scope of protection of this application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims (10)

1. a data preparation method, is characterized in that, described method comprises: Obtain the log data of the object under test processing business requests; extracting business execution statements in the log data; The business execution statement is reversely converted to obtain the target execution statement; the target execution statement is used to update the data in the target database to test the object to be tested. 2. The method according to claim 1, wherein the extracting the business execution statement in the log data comprises: Get the set regular expression; Perform regular matching on the log data through the regular expression, and extract business execution statements in the log data. 3. The method according to claim 1, wherein the reverse conversion is performed on the service execution statement to obtain the target execution statement, comprising: extracting the subquery statement and the table identifier in the business execution statement; The target execution statement is determined according to the subquery statement and the table identifier. 4. The method according to claim 3, wherein the extracting the sub-query statement and the table identifier in the business execution statement comprises: Parse the business execution statement into an abstract syntax tree including at least one node; the nodes of the abstract syntax tree can be accessed; Traverse each node of the abstract syntax tree, and determine the subquery statement and table identifier corresponding to the node. 5. The method according to claim 3, wherein determining the target execution statement according to the subquery statement and the table identifier comprises: Converting the sub-query statement to obtain the target statement structure; Reconstructing the subquery statement and the corresponding table identifier to obtain target data; The target statement structure and the target data are assembled to obtain the target execution statement. 6. The method according to claim 3, wherein the method further comprises: Generate data clear command; Assembling the data clearing command and the table identification to obtain a data clearing statement; the data clearing statement is used to clear the data in the table corresponding to the table identification after completing the test of the object to be tested . 7. The method of claim 1, wherein the method further comprises: Obtain feature information of the object to be tested processing the service request; the feature information is used to generate a test case for testing the object to be tested. 8. A data preparation device, wherein the device comprises: The acquisition unit is used to acquire the log data of the object to be tested processing the business request; an extraction unit for extracting business execution statements in the log data; The processing unit is configured to reversely convert the service execution statement to obtain the target execution statement; the target execution statement is used to update the data in the target database to test the object to be tested. 9. A computer device comprising a memory, a processor and a computer program stored on the memory and running on the processor, wherein the processor implements any of claims 1 to 7 when the processor executes the computer program Steps in the data preparation method described in item . 10. A computer-readable storage medium on which a computer program is stored, characterized in that, when the computer program is executed by a processor, the data preparation method according to any one of claims 1 to 7 is implemented.

Images