CN111737140A - Interface automated testing method, apparatus, device, and computer-readable storage medium - Google Patents

Abstract

The invention relates to the technical field of financial technology (Fintech), and discloses an interface automatic testing method, device, device and computer-readable storage medium. The method includes: when an interface protocol test request is received, obtaining the interface protocol The test request corresponds to the target version protocol to be tested; if there is a baseline version protocol associated with the target version protocol, compare the target version protocol with the baseline version protocol to obtain protocol update information; obtain the baseline version protocol Corresponding baseline test engine, update the baseline test engine according to the protocol update information to obtain a target test engine; generate a target test case according to the target test engine, run the target test case to obtain the target test of the target version protocol result. The present invention passes the protocol version comparison test, does not require testers to review the test results, and improves the efficiency of the regression test.

Description

Interface automated testing method, apparatus, device, and computer-readable storage medium

technical field

The present invention relates to the technical field of financial technology (Fintech), and in particular, to a method, apparatus, device and computer-readable storage medium for automatic interface testing.

Background technique

With the rapid development of Internet technology, especially Internet financial technology (Fintech), more and more technologies (big data, distributed, blockchain, artificial intelligence, etc.) are applied in the financial field, and the functions of financial business platforms are becoming more and more more and more.

The financial business platform usually sets up a large number of data interfaces to realize the interaction of financial business data. When the interface development of the financial business platform is completed, interface testing is required. Since there are many data interfaces, there are many test cases for interface testing. The current test case Mainly through manual writing is more troublesome, the test case generation time is long, and the interface testing efficiency is low. Based on this, some developers have proposed an automatic test case generation scheme. The automatic generation of test cases shortens the writing time of test cases and improves the test case to a certain extent. The efficiency of interface testing is improved. However, for frequent regression testing, since the test cases generated by automation are different each time, and the test results obtained each time are different, test result analysis needs to be performed each time, and errors in the test results are found. Low efficiency and long regression testing time.

SUMMARY OF THE INVENTION

The main purpose of the present invention is to provide an interface automatic testing method, device, equipment and computer-readable storage medium, aiming at solving the current interface regression testing method, using different test cases to obtain different test results each time, each time All need to analyze the test results separately, the errors in the test results are found to be inefficient, and the regression test time is long.

In order to achieve the above object, the present invention provides a method for automatic testing of interfaces, and the automatic testing method for interfaces comprises the following steps:

When receiving the interface protocol test request, obtain the target version protocol to be tested corresponding to the interface protocol test request;

If there is a baseline version protocol associated with the target version protocol, comparing the target version protocol with the baseline version protocol to obtain protocol update information;

Obtain the baseline test engine corresponding to the baseline version protocol, update the baseline test engine according to the protocol update information, and obtain the target test engine;

Generate a target test case according to the target test engine, and run the target test case to obtain the target test result of the target version protocol.

Optionally, after the step of acquiring the target version protocol to be tested corresponding to the interface protocol test request when an interface protocol test request is received, the method includes:

Judging whether there is a baseline version protocol associated with the target version protocol;

If the baseline version protocol associated with the target version protocol does not exist, analyze the target version protocol to generate a target test engine, wherein the target test engine includes a business rule engine, a basic field engine and a MOCK test engine;

Generate a target test case according to the target test engine, and run the target test case to obtain the target test result of the target version protocol.

Optionally, if the baseline version protocol associated with the target version protocol does not exist, the step of analyzing the target version protocol to generate a target test engine includes:

If the baseline version protocol associated with the target version protocol does not exist, analyze the target version protocol, and obtain the service scenario identifier of the target version protocol;

Querying the preset data platform, obtaining the business test rules corresponding to the business scenario identifiers, and summarizing the business test rules to generate a business rule engine;

Traverse the protocol attribute of the target version protocol, and generate a basic field engine according to the preconfigured divergence rule and the field type, field length and field enumeration in the protocol attribute;

Pull the protocol content information and the protocol upstream and downstream relationship of the target version protocol from the preset protocol management platform, and generate a MOCK test engine according to the protocol content information and the protocol upstream and downstream relationship;

A target test engine is generated by combining the business rule engine, the basic field engine and the MOCK test engine.

Optionally, the step of pulling the protocol content information and the protocol upstream and downstream relationships of the target version protocol from the preset protocol management platform, and generating a MOCK test engine according to the protocol content information and the protocol upstream and downstream relationships, including :

Pull the protocol content information of the target version protocol and the protocol upstream and downstream relationship from the preset protocol management platform, and obtain each target downstream protocol to be MOCK downstream of the target version protocol according to the protocol upstream and downstream relationship;

Acquiring the preset target field for Cartesian divergence in the target downstream protocol, performing a Cartesian product on the target downstream protocol according to the target field, and generating a successful MOCK set and a failed MOCK set;

Do Cartesian product between the described successful MOCK sets, obtain the successful class MOCK rule, do Cartesian product with an element in the described failure MOCK set and the described successful MOCK set, obtain the failure class MOCK rule;

The MOCK test engine is generated by summarizing the success class MOCK rules and the failure class MOCK rules.

Optionally, the step of obtaining the baseline test engine corresponding to the baseline version protocol, updating the baseline test engine according to the protocol update information, and obtaining the target test engine, includes:

Obtain the baseline test engine corresponding to the baseline version protocol, wherein the baseline test engine includes: a business rule engine, a basic field engine and/or a MOCK test engine;

Query the preset support platform, obtain the update scene identifier in the protocol update information from the preset support platform, and the update test rule corresponding to the update scene identifier, and add the update test rule to the Business rules engine, get updated business rules engine;

Traversing the newly added attributes of the protocol update information, and updating the basic field engine according to the change type, change length and newly added enumeration in the newly added attributes, to obtain an updated basic field engine;

Do Cartesian product with the MOCK rule in described protocol update information and described MOCK test engine, described MOCK test engine is updated, obtain the MOCK test engine of update;

A target test engine is obtained by combining the updated business rule engine, the updated basic field engine and the updated MOCK test engine.

Optionally, the steps of generating a target test case according to the target test engine and running the target test case to obtain the target test result of the target version protocol include:

Obtain the business rule engine, basic field engine and MOCK test engine in the target test engine;

Extract business engine rules from the business rules engine, extract field engine rules from the basic field engine, and extract MOCK engine rules from the MOCK test engine;

A target test case is generated according to the business engine rule, the field engine rule and the MOCK engine rule, and the target test case is run to obtain the target test result of the target version protocol.

Optionally, the step of generating a target test case according to the business engine rule, the field engine rule and the MOCK engine rule, and running the target test case to obtain the target test result of the target version protocol, includes:

Obtaining the basic case of the business engine rule, calling a preset automated test platform to process the basic case to generate a business message, and intercepting the business message to generate a business type test case;

Obtain the field engine rules, call the preset automated test platform to process the required business engine rules to generate basic packets, intercept the basic packets, modify the basic packets according to the field engine rules, and generate field type test cases ;

Obtain the MOCK engine rules, call the preset automated test platform to process the necessary business engine rules to generate basic messages, intercept the basic messages, process the basic messages according to the MOCK engine rules, and generate MOCK type test cases ;

The service type test case, the field type test case, and the MOCK type test case are performed a Cartesian product to generate a target test case, and the target test case is run to obtain the target test result of the target version protocol.

Optionally, after generating a target test case according to the target test engine and running the target test case to obtain the target test result of the target version protocol, the method includes:

obtaining the preset service serial number corresponding to the target test case, and storing the target test result of the target version protocol in association with the preset service serial number;

When receiving the test result comparison request, use the preset service serial number as the primary key to obtain the target test result corresponding to the target version protocol and the baseline test result corresponding to the baseline version protocol;

Comparing the target test result and the baseline test result to remove redundant data, and output comparison abnormality information.

In addition, in order to achieve the above purpose, the present invention also provides an interface automatic testing device, the interface automatic testing device includes:

a request receiving module, configured to obtain the target version protocol to be tested corresponding to the interface protocol test request when receiving the interface protocol test request;

a protocol comparison module, configured to compare the target version protocol and the baseline version protocol to obtain protocol update information if there is a baseline version protocol associated with the target version protocol;

an engine update module, configured to obtain a baseline test engine corresponding to the baseline version protocol, update the baseline test engine according to the protocol update information, and obtain a target test engine;

A running test module is configured to generate a target test case according to the target test engine, and run the target test case to obtain a target test result of the target version protocol.

In addition, in order to achieve the above object, the present invention also provides an automatic interface test device, the interface automatic test device includes: a memory, a processor, and an automatic interface test stored on the memory and can be run on the processor. A program, when the interface automatic testing program is executed by the processor, implements the steps of the above-mentioned interface automatic testing method.

In addition, in order to achieve the above object, the present invention also provides a computer-readable storage medium, on which an automated interface test program is stored, and the automated interface test program is executed by a processor to achieve the above-mentioned The steps of the interface automation test method.

The present invention provides an interface automated testing method, apparatus, device and computer-readable storage medium. In the embodiment of the present invention, when an interface protocol test request is received, the target version protocol to be tested corresponding to the interface protocol test request is obtained; it is judged whether there is a baseline version protocol associated with the target version protocol, if there is a target version protocol associated with the target version protocol The baseline version protocol associated with the version protocol is determined as a regression test, and the target version protocol and the baseline version protocol are compared to obtain protocol update information; the baseline test engine corresponding to the baseline version protocol is obtained, and updated according to the protocol information to update the baseline test engine to obtain a target test engine; generate a target test case according to the target test engine, run the target test case to obtain the target test result of the target version protocol, that is, in this embodiment, pass the update test engine, and use the updated test engine to update test cases. Compared with the current interface regression test, the current interface regression test creates a test case every time. Since each test case is a new one, then based on the test case The obtained test result is also a new test result, which needs to be analyzed every time, and the efficiency of error detection in the test result is low; while the test case of this application is updated according to the target protocol version, and the test result obtained by the target protocol version, The test results obtained by the baseline version of the protocol are similar, and the test results of the same test case before and after the update can be compared, which can quickly locate the problem, improve the efficiency of error detection in the test results, and reduce the need for manual review. Manual review by testers The workload is improved, and the efficiency of interface automation testing is improved.

Description of drawings

1 is a schematic diagram of a device structure of a hardware operating environment involved in an embodiment of the present invention;

2 is a schematic flowchart of the first embodiment of the interface automated testing method of the present invention;

3 is a schematic diagram of a specific scene created by a MOCK test engine in the first embodiment of the interface automated testing method of the present invention;

4 is a schematic flowchart of the second embodiment of the interface automated testing method of the present invention;

5 is a schematic diagram of a scenario for updating a business rule engine in the second embodiment of the interface automated testing method of the present invention;

6 is a schematic diagram of a scenario in which a basic field engine is updated in the second embodiment of the interface automated testing method of the present invention;

Fig. 7 is the schematic flow chart of MOCK test engine update in the second embodiment of the interface automated testing method of the present invention;

8 is a schematic diagram of a scenario of result comparison in the fourth embodiment of the interface automated testing method of the present invention;

FIG. 9 is a schematic diagram of functional modules of an embodiment of an interface automated testing apparatus according to the present invention.

The realization, functional characteristics and advantages of the present invention will be further described with reference to the accompanying drawings in conjunction with the embodiments.

Detailed ways

It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention.

Existing interface testing solutions Continuous Integration Testing Platform (Continuous Integration TestingPlatform: also known as automated testing platform, formulate test case input and expected checkpoints, test cases that can be manually or automatically triggered for execution) The platform's test solutions provide The generation of automated use cases and automated plans requires manual construction of automated use cases in the form of a tree, providing an assertion mechanism, supporting built-in functions and expressions to calculate assertion results, and supporting database query expectations and actual comparisons.

The CI test platform is associated with the protocol message sending tool. The protocol sending tool needs to manually assemble the interface message for execution, and manually check whether the interaction between the running result and the background is normal, and output the test report by itself as the follow-up test record. The CI test platform is associated with the baffle platform. This platform is used to simulate the return messages of the upstream and downstream systems. It is also called the baffle system. The first time the baffle system is used, it needs to be manually deployed to the upstream system and set on the page where the upstream system is located. MOCK shutter rules, trigger the simulation shutter to take effect by enabling or disabling the rules.

The cost of writing test cases for such an interface test solution is high: the coverage of existing CI test scenarios is insufficient, and it is difficult to supplement a large number of existing test cases. Now there are baffle platforms, each scenario needs to be configured separately, and it is time-consuming and labor-intensive to construct baffles in a large number of abnormal scenarios in the test. Test test case assertions are complicated to write and easy to miss; frequent regression testing of test test cases requires manual intervention and review of test comparison results, and a large number of test cases make people in a state of fatigue analysis, which is not conducive to efficient regression testing. Due to the deficiencies of the technical interface testing solutions, the method, device, equipment and computer-readable storage medium for automatic interface testing of the present invention are proposed.

As shown in FIG. 1 , FIG. 1 is a schematic diagram of a device structure of a hardware operating environment involved in an embodiment of the present invention.

The interface automatic testing device in the embodiment of the present invention may be a PC or a server.

As shown in FIG. 1 , the interface automated testing equipment may include: a processor 1001 , such as a CPU, a network interface 1004 , a user interface 1003 , a memory 1005 , and a communication bus 1002 . Among them, the communication bus 1002 is used to realize the connection and communication between these components. The user interface 1003 may include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (eg, a WI-FI interface). The memory 1005 may be high-speed RAM memory, or may be non-volatile memory, such as disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the device structure shown in FIG. 1 does not constitute a limitation on the device, and may include more or less components than the one shown, or combine some components, or arrange different components.

As shown in FIG. 1, the memory 1005, which is a computer storage medium, may include an operating system, a network communication module, a user interface module, and an automatic interface testing program.

In the device shown in FIG. 1 , the network interface 1004 is mainly used to connect to the background server and perform data communication with the background server; the user interface 1003 is mainly used to connect to the client (client) and perform data communication with the client; and the processor 1001 can be used to call the interface automatic testing program stored in the memory 1005, and perform the operations in the following interface automatic testing method.

Based on the above hardware structure, an embodiment of the interface automatic testing method of the present invention is proposed.

Referring to FIG. 2, FIG. 2 is a schematic flowchart of the first embodiment of the interface automated testing method of the present invention, and the method includes:

Step S10, when receiving the interface protocol test request, obtain the target version protocol to be tested corresponding to the interface protocol test request;

The interface automated testing method in this embodiment is applied to an interface automated testing device, which is a hardware carrier of an interface automated testing computer program, and the automated testing device in this embodiment can be set in different financial institutions.

The interface automated test device receives the interface test request, wherein the triggering method of the interface test request is not specifically limited, that is, the interface test request may be actively triggered by the user. The virtual button manually triggers the interface test request; in addition, the interface test request can also be automatically triggered by the interface automated test equipment. The interface automated testing device monitors the state of the interface in real time, and when the interface automated testing device detects that a new interface protocol version is released, the interface automated testing device automatically triggers an interface test request.

When the interface automated test device receives the interface protocol test request, the interface automated test device obtains the target version protocol to be tested corresponding to the interface protocol test request, wherein the content of the target version protocol is not specifically limited, that is, the target version protocol may be the first one. The interface protocol of the first version can also be the interface protocol of the second version and the interface protocol of the later updated version.

Step S20, judging whether there is a baseline version protocol associated with the target version protocol;

After the interface automated test equipment obtains the target version protocol to be tested, the interface automated test equipment obtains the version identifier of the target version protocol, and the interface automated test equipment determines whether the target version protocol is the first protocol version according to the version identifier. When it is the first protocol version, the interface automated test equipment determines that there is no baseline version protocol associated with the target version protocol, and the interface automated test equipment needs to directly create test cases according to the target version protocol; when the target version protocol is not the first protocol version , the interface automated test equipment determines that there is a baseline version protocol associated with the target version protocol, the interface automated test equipment can update the test cases of the baseline version protocol, and generate test cases corresponding to the target version protocol, wherein the baseline version protocol is the project repository A "snapshot" of each artifact version in a specific period, it provides a formal standard on which subsequent work is based and only authorized to change this standard Changes will be recorded as a delta until the next baseline version of the agreement is built.

The technical solution in this embodiment is to reduce the operation of the tester to review the test results. Therefore, the interface automated testing equipment determines whether there is a baseline version protocol associated with the target version protocol. If there is a baseline version protocol associated with the target version protocol, according to The baseline version protocol is used to update test cases, and use the updated test cases to test to obtain test results, so that the test results can be directly compared without manual review.

In order to facilitate understanding, this embodiment first describes the interface test that does not have a baseline version protocol associated with the target version protocol, that is, this embodiment first describes that when the target version protocol is the initial version The steps for automatic interface testing of the version protocol, specifically:

Step S30, if there is no the baseline version protocol associated with the target version protocol, then analyze the target version protocol to generate a target test engine, wherein the target test engine includes a business rule engine, a basic field engine and a MOCK test engine;

If there is no baseline version protocol associated with the target version protocol, the interface automated test equipment analyzes the target version protocol to generate a target test engine, where the target test engine includes a business rule engine, a basic field engine, and a MOCK test engine. Rule Engine): Provide a configuration mechanism according to the business requirements of some special cases, and generate a test case pool according to the preset configuration. Basic field engine (Interface Field Rule Engine): Automatically generate basic field validation test case pools based on attributes such as attribute length, mandatory, and enumeration of all fields of the interface. MOCK Engine (Mock Rule Engine): MOCK service is a baffle tool proposed for network, code, and RMB services. MOCK engine is a set of solutions for automatic generation of abnormal scenario test cases based on MOCK service; specifically, including :

Step a1, if the baseline version protocol associated with the target version protocol does not exist, analyze the target version protocol, and obtain the service scenario identifier of the target version protocol;

Step a2, query the preset data support platform, obtain the business test rules corresponding to the business scenario identifiers, and summarize the business test rules to generate a business rule engine;

Step a3, traverse the protocol attribute of the target version protocol, and generate a basic field engine according to the pre-configured divergence rule and the field type, field length and field enumeration in the protocol attribute;

Step a4, pulling the protocol content information and the protocol upstream and downstream relationship of the target version protocol from the preset protocol management platform, and generating a MOCK test engine according to the protocol content information and the protocol upstream and downstream relationship;

Step a5, combine the business rule engine, the basic field engine and the MOCK test engine to generate a target test engine.

If there is no baseline version protocol associated with the target version protocol, the interface automated testing device analyzes the target version protocol and obtains the business scenario identifier of the target version protocol. In this embodiment, the interface automated testing device in step a2 generates a business rule engine according to the business scenario identifier. , including: interface automated test equipment querying the preset data platform (the preset data platform refers to the preset business data management platform, the preset data platform contains the business scenario identifiers corresponding to each interface, and the business scenario identifiers are related to the Business scenario information, and business test rules corresponding to each business scenario information, the preset support data platform is specifically used to automatically trigger the calling rules when the next batch of daily cuts and daily cuts are synchronized after the batch execution is completed and the test cases are verified. A platform that captures the batch of data that meets the required form in real time and manages the data), obtains the business test rules corresponding to the business scenario identifiers, and summarizes the business test rules to generate a business rules engine.

That is, the interface automated test equipment manually configures an automated test basic case on the automated test platform to maintain the action scheduling and parameter transfer between actions, and the business rule engine generates batches of the basic cases in the automated test platform and the set of scenarios of the support platform. The business rule engine pool (1*n), after the scenario of the platform to be tested is updated, the business engine will be automatically updated synchronously and added to the business engine pool to generate a business rule engine.

For example, the business rules engine automatically generates engine data and stores it in the engine pool according to the scenario of the Yangshu platform; the scene change of the Yangshu platform triggers the automatic update of the engine and supports manual maintenance. The rules are divided into three categories: must-pass, success, and failure. Used to generate field type test cases and MOCK type test cases. The business engine pool includes fields such as the engine rule identifier, the scenario identifier of the Yangshu platform, the basic rule identifier of the automated test platform, the rule summary, and the status. For example, the rule summary is taken from the Yangshu platform scenario, for example, the Yangshu platform scene "931", the summary "settlement by order - single loan, 0T loan, stay on 0T+1 day".

In this embodiment, the interface automated test equipment generates a basic field engine in step a3, which includes: the interface automated test equipment traverses the protocol attributes of the target version protocol, and performs field type, field length and field enumeration according to the preconfigured divergence rules and the protocol attributes. Divergent generation base field engine.

For example, 1. If the field is of type STRING: if there is a default value, it will emit the cases equal to the default value, not equal to the default value, empty string, or NULL; if there is an enumeration value, it will emit a value equal to each enumeration value. , non-enumeration value, empty string, and NULL; if there is no default value and enumeration value, there are several cases of empty string, NULL, equal length, and super long; 2. If the field is of DECIMAL type : Emit empty strings, NULL values; scatter negative numbers and maxLength (maximum precision length) equal length delLength (minimum length) equal length random numbers; 0; 0.0; 0.00; maxLength equal length delLength equal length random numbers; maxLength, etc. Long delLength super long random number; maxLength super long delLength equal length random number; 3. If the field is of the TIME type: YYYYMMddHHmmss and some illegal conditions are diverged according to the system time; 4. If the field is of the NUMBER type: empty; negative and maxLength is the same length Random number; 0; maxLength equal length random number; maxLength super long random number; maxLength equal length letter + random number; 5. If the field is MsgFieldArray type: divergent and empty; one set of data; two sets of data; the rule that will diverge Stored in the field engine pool.

In this embodiment, the step a4 interface automated test equipment generates a MOCK test engine, and the MOCK engine is an engine pool that automatically generates and saves engine rules according to the upstream and downstream relationships and attribute values of the protocol; the MOCK engine pool includes an engine rule ID, a MOCK header, and a MOCK message. Fields such as Style, Rule Summary, Status, etc. The summary is the downstream service id and the service status to be mocked, for example, MOCK header "{"02100040":"response.errCode='0000';response.retStatus='S';response.retList=";"," 02300298":"response.errCode='9999';response.retStatus='F';response.retList=";"",MOCK message body "{"02100040":{"retCode":"30790000","retMsg" :"MOCKSUCC"},"02300298":{"retCode":"30790002","retMsg":"MOCKFAIL"}}",summary{"02100040":"succ","02300298":"fail"}, representing 02100040 Protocol returns success, 02300298 Service returns failure. The steps of MOCK test engine generation, including:

Step a41, pulling the protocol content information of the target version protocol and the protocol upstream and downstream relationships from the preset protocol management platform, and obtaining each target downstream protocol to be MOCKed downstream of the target version protocol according to the protocol upstream and downstream relationships;

Step a42, obtain the target field that carries out the Cartesian divergence of the preset configuration in the target downstream protocol, and perform the Cartesian product of the target downstream protocol according to the target field, and generate a successful MOCK set and a failed MOCK set;

Step a43, do Cartesian product between the described successful MOCK sets, obtain the successful class MOCK rule, make a Cartesian product with an element in the described failure MOCK set and the described successful MOCK set, obtain the failure class MOCK rule;

In step a44, the MOCK test engine is generated by summarizing the success class MOCK rules and the failure class MOCK rules.

For example, 1. The interface automated test equipment pre-configures which fields in the downstream protocol need Cartesian divergence, and each attribute successfully enumerates the set and fails to enumerate the set. As shown in Figure 3, protocol 1 contains attributes A and B, where A:{0}, B:{a} are the set of successful enumeration values, and A:{1}, B:{b,c} are the failed enumeration Value set; 2. The interface automated test equipment obtains the downstream protocol that needs MOCK according to the upstream and downstream relationship (1:n) of the protocol to be tested; 3. The interface automated test equipment generates a Cartesian product for each downstream protocol according to the divergence field configuration The MOCK sets of success and failure respectively, as shown in Figure 3, the Cartesian product {0}*{a}={0,a} between the successful sets of interface 1, and the Cartesian product {1}*{b between the failed sets, c}={1,b},{1,c}; 4. Do Cartesian product of successful type sets between downstream protocols to generate successful MOCK-like rules and write them into the engine pool; as shown in Figure 3, the success of interface 1 and interface 2 The Cartesian product of the MOCK set generates {0,a,d},{0,a,e}; 4. Each downstream protocol failure class set only needs to be combined with the first pass data set of all other protocols and written to the engine pool . As shown in Figure 3, the failed MOCK set of interface 1 and the first successful MOCK set of interface 2 are Cartesian product to generate {1,b,d},{1,c,d}, and the success class MOCK rules and failure class MOCK rules Summarize and generate MOCK test engine; the interface automation test equipment combines business rule engine, basic field engine and MOCK test engine to generate target test engine.

The interface automation test equipment generates test cases for interface automation testing by driving the target test engine, specifically:

Step S40, generating a target test case according to the target test engine, and running the target test case to obtain a target test result of the target version protocol.

In the interface automation test equipment, the business rule engine drives the automatic generation of business type test cases; the basic field engine drives the automatic generation of protocol field type test cases; the MOCK engine drives the automatic generation of MOCK type test cases; the target test engine selects three engine data for Cartesian product Generate target test cases, that is, the interface automated test equipment extracts business type test cases, field type test cases, and MOCK type test cases from the engine pool corresponding to the target test engine, and converts business type test cases, field type test cases, and MOCK type test cases. The test cases are spliced to form a target test case, and the interface automated test equipment runs the target test case to obtain the target test result of the target version protocol. In this embodiment, the interface automated testing device creates a test case when the target protocol version is the initial protocol version, so that the interface automated testing is more efficient.

Further, referring to FIG. 4 , FIG. 4 is a schematic flowchart of the second embodiment of the interface automated testing method of the present invention.

Based on the first embodiment of the automatic interface testing method of the present invention, a second embodiment of the automatic interface testing method of the present invention is proposed; this embodiment is a step after step S20 in the first embodiment, and the difference between this embodiment and the above implementation is:

Step S50, if there is a baseline version protocol associated with the target version protocol, compare the target version protocol with the baseline version protocol to obtain protocol update information.

If there is a baseline version protocol associated with the target version protocol, the interface automated test device compares the target version protocol with the baseline version protocol to obtain protocol update information, and the interface automated test device updates the test engine according to the protocol update information, specifically:

Step S60: Obtain a baseline test engine corresponding to the baseline version protocol, update the baseline test engine according to the protocol update information, and obtain a target test engine.

The interface automated test device obtains the baseline test engine corresponding to the baseline version protocol, and the interface automated test device updates the baseline test engine according to the protocol update information to obtain the target test engine, specifically, including:

Step b1, obtaining the baseline test engine corresponding to the baseline version protocol, wherein the baseline test engine includes: a business rule engine, a basic field engine and/or a MOCK test engine;

Step b2, query the preset support platform, obtain the update scene identifier in the protocol update information from the preset support platform, and the update test rule corresponding to the update scene identifier, and add the update test rule Go to the business rule engine to obtain an updated business rule engine;

Step b3, traverse the newly added attributes of the protocol update information, and update the basic field engine according to the change type, change length and newly added enumeration in the newly added attributes, and obtain an updated basic field engine;

Step b4, the MOCK rule in described protocol update information and described MOCK test engine is done Cartesian product to described MOCK test engine and is updated, obtains the MOCK test engine of update;

Step b5, combining the updated business rule engine, the updated basic field engine and the updated MOCK test engine to obtain a target test engine.

That is, the interface automated test equipment obtains the baseline test engine corresponding to the baseline version protocol, and the baseline test engine includes: a business rule engine, a basic field engine and/or a MOCK test engine, and the interface automated test equipment updates the business rule engine, basic field engine and/or respectively. Or MOCK test engine, referring to FIG. 5, FIG. 5 is a schematic diagram of a scenario of updating the business rule engine in the second embodiment of the interface automated testing method of the present invention; the step b1 of updating the business rule engine in the present embodiment includes: the interface automated testing equipment queries the Set up the data platform, obtain the update scenario ID in the protocol update information from the preset data platform, and the update test rule corresponding to the update scenario ID, and the interface automated test equipment adds the update test rule to the business rule engine to obtain the updated business. Rules engine.

Referring to FIG. 6, FIG. 6 is a schematic diagram of a scenario of updating the basic field engine in the second embodiment of the interface automated testing method of the present invention. The steps of updating the basic field engine by the interface automated testing equipment in this embodiment include: 1. Synchronizing the protocol management platform (protocol The management module uses the timing polling mechanism to pull the latest version of the protocol and the upstream and downstream relationships of the protocol management platform in real time, automatically synchronize it to the protocol interface management module, and provide personalized protocol configuration functions. Subsequent engine generation and update depend on the definition and The relationship between the upstream and downstream of the protocol, the protocol management module includes interface configuration management and upstream and downstream interface management) the new version of the protocol. 2. Compare the old and new versions of the target version protocol and the baseline version protocol, and obtain new attributes, new enumerations of attributes, type changes, and length changes; 3. According to new attributes, new enumerations, and type changes According to the rules defined in the background, the new engine rules are automatically distributed, and the additional information is added to the engine pool to obtain the updated business rules engine.

Referring to Fig. 7, Fig. 7 is the schematic flow chart of MOCK test engine update in the second embodiment of the interface automated test method of the present invention; the step of interface automated test equipment update MOCK test engine in the present embodiment comprises: 1, compare new and old downstream protocols, Identify and store updated changes: new enumerations, new fields, new upstream and downstream result ports, deletions do not need to be processed; for example, a. If new enumerations are added: use the original Cartesian product data set and add new ones The enumeration re-Cartesian product is added to the engine pool. As shown in Figure 3, the A field of interface 1 adds a successful enumeration 2, and the successful MOCK set adds an enumeration 2 and the B field to the successful MOCK set to do a Cartesian product to generate {2,a}. The newly added MOCK collection executes the MOCK engine generation logic and generates the engine rules. b. If a new field is added: Re-Cartesian product with the original Cartesian product data set and each enumeration value of the new field is added to the engine pool. As shown in Figure 3, interface 1 adds a C field, the original success or failure MOCK set and the C field success or failure enumeration carry out a Cartesian product, and the reorganized Cartesian product combination updates the elements in the original MOCK set, for example: {0, a } is {0,a,w}, etc. At the same time, the remaining rules are added to the MOCK set. After the Cartesian product of the updated MOCK set, the rules in the original MOCK engine are updated, and new rules are added to the engine. c. If a new protocol is added: determine whether the upstream and downstream protocols participate in MOCK. If so, re-go the MOCK engine generation logic to obtain an updated MOCK test engine.

The interface automation test equipment obtains the target test engine by combining the updated business rule engine, the updated basic field engine and the updated MOCK test engine, so as to perform the interface automation test through the target test engine, specifically:

Step S70, generating a target test case according to the target test engine, and running the target test case to obtain a target test result of the target version protocol.

In the interface automation test equipment, the business rule engine drives the automatic generation of business type test cases; the basic field engine drives the automatic generation of protocol field type test cases; the MOCK engine drives the automatic generation of MOCK type test cases; the target test engine selects three engine data for Cartesian product Generate target test cases, that is, the interface automated test equipment extracts business type test cases, field type test cases, and MOCK type test cases from the engine pool corresponding to the target test engine, and converts business type test cases, field type test cases, and MOCK type test cases. The test cases are spliced to form target test cases, and the interface automated test equipment runs the target test cases to obtain the target test results of the target version protocol.

In the embodiment of the present invention, when an interface protocol test request is received, the target version protocol to be tested corresponding to the interface protocol test request is obtained; it is judged whether there is a baseline version protocol associated with the target version protocol, if there is a target version protocol associated with the target version protocol The baseline version protocol associated with the version protocol is determined as a regression test, and the target version protocol and the baseline version protocol are compared to obtain protocol update information; the baseline test engine corresponding to the baseline version protocol is obtained, and updated according to the protocol information to update the baseline test engine to obtain a target test engine; generate a target test case according to the target test engine, run the target test case to obtain the target test result of the target version protocol, that is, in this embodiment, pass the update test engine, and use the updated test engine to update test cases. Compared with the current interface regression test, the current interface regression test creates a test case every time. Since each test case is a new one, then based on the test case The obtained test result is also a new test result, and the test case of the embodiment of the present invention is updated according to the target protocol version, the test result obtained by the target protocol version is similar to the test result obtained by the baseline version protocol, and the same before and after the update can be obtained. The test results of the test cases are compared, which can quickly locate the problem and improve the efficiency of error discovery. It does not require manual review, reduces the workload of manual review by testers, and improves the efficiency of automated interface testing.

Further, based on the above embodiments of the automatic interface testing method of the present invention, a third embodiment of the automatic interface testing method of the present invention is proposed.

This embodiment is a refinement of step S40 in the first embodiment and/or step S70 in the second embodiment. In this embodiment, a target test case is generated according to the target test engine, and the target test case is obtained by running the target test case. The specific implementation of the target test result of the target version protocol includes:

Obtain the business rule engine, basic field engine and MOCK test engine in the target test engine;

Extract business engine rules from the business rules engine, extract field engine rules from the basic field engine, and extract MOCK engine rules from the MOCK test engine;

A target test case is generated according to the business engine rule, the field engine rule and the MOCK engine rule, and the target test case is run to obtain the target test result of the target version protocol.

The interface automation device obtains the business rule engine, the basic field engine and the MOCK test engine in the target test engine; the interface automation device extracts the business engine rules from the business rule engine, extracts the field engine rules from the basic field engine, and extracts the field engine rules from the MOCK test engine Extract MOCK engine rules; interface automation equipment generates target test cases according to business engine rules, field engine rules and MOCK engine rules, and runs the target test cases to obtain the target test results of the target version protocol, specifically, including:

Obtaining the basic case of the business engine rule, calling a preset automated test platform to process the basic case to generate a business message, and intercepting the business message to generate a business type test case;

Obtain the field engine rules, call the preset automated test platform to process the required business engine rules to generate basic packets, intercept the basic packets, modify the basic packets according to the field engine rules, and generate field type test cases ;

Obtain the MOCK engine rules, call the preset automated test platform to process the necessary business engine rules to generate basic messages, intercept the basic messages, process the basic messages according to the MOCK engine rules, and generate MOCK type test cases ;

The service type test case, the field type test case, and the MOCK type test case are performed a Cartesian product to generate a target test case, and the target test case is run to obtain the target test result of the target version protocol.

That is, the interface automated testing device generates a basic case for acquiring business engine rules, invokes a preset automated test platform to process the basic case to generate business packets, and intercepts the business packets to generate business type test cases, including: 1. Obtaining the business engine rules The basic case of the automated test platform, the scenario identification of the Yangshu platform, the call to the automated test platform, the interception of the packets generated by the automated test platform into the test case pool, and the generation of business-type test cases.

Interface automation test equipment basic field type test case generation process: 1. Obtain the field engine rules. 2. Obtain the business engine rules that must pass. Call the CI platform to intercept the packets generated by the CI platform; 3. According to the field engine rules, tamper with the packet A, get the use case packet A', fall into the use case pool, and generate the basic field type test case. For example, the test case id and name must pass the business engine and the corresponding field engine id and summary are concatenated respectively. For example, the use case id "B0000000001_F15759718157471", the use case name "single settlement - single, 0T loan, stay in 0T+1 day, within the range of APP_TYPE enumeration value".

Interface automation test equipment MOCK type test case generation process: 1. Obtain MOCK engine rules; 2. Obtain must pass business engine rules. Call the CI platform to intercept the packets generated by the CI platform. fall into the use case pool. 3. After all mock use cases are generated, use the use case "preset business serial number" as the if condition to splice each mock message in the MOCK engine to generate the MOCK configuration. Push the MOCK configuration to the mockserver platform. The interface automation test equipment makes a Cartesian product of the business type test case, the field type test case and the MOCK type test case to generate the target test case, and runs the target test case to obtain the target test result of the target version protocol. In this embodiment, the target test case is generated according to the target test engine, and the tester does not need to manually write the target test case, which improves the efficiency of automatic interface testing.

Further, based on the above-mentioned embodiments of the automatic interface testing method of the present invention, a fourth embodiment of the automatic interface testing method of the present invention is proposed.

This embodiment is a step after step S40 in the first embodiment and step S70 in the second embodiment. The difference between the above embodiments in this embodiment is:

obtaining the preset service serial number corresponding to the target test case, and storing the target test result of the target version protocol in association with the preset service serial number;

When receiving the test result comparison request, use the preset service serial number as the primary key to obtain the target test result corresponding to the target version protocol and the baseline test result corresponding to the baseline version protocol;

Comparing the target test result and the baseline test result to remove redundant data, and output comparison abnormality information.

The interface automated testing device obtains the preset service serial number corresponding to the target test case, and the interface automated testing device associates and saves the target test result of the target version protocol with the preset service serial number; The preset service serial number is the primary key, and the target test result corresponding to the target version protocol is obtained, and the baseline test result corresponding to the baseline version protocol is obtained; the target test result and the baseline test result are compared to remove redundancy Data, output comparison exception information.

Specifically, referring to FIG. 8, FIG. 8 is a schematic diagram of a scenario of result comparison in the fourth embodiment of the interface automated testing method of the present invention; the interface automated testing device obtains the target message and target DB of the target version protocol; the interface automated testing device obtains the baseline The baseline packet of the version protocol and the baseline target DB, the result comparison is divided into packet comparison and DB comparison. The packet and DB comparison is a use case level comparison. The text comparison only needs to perform consistency comparison on the return packets of the use case, and configure the relationship between the use case "preset service serial number" and the primary key of each table. Use the primary key of the full database table as the DB to compare the query conditions in the SQL, and generate the full database table query statement irrespective of the subsystem dimension and scenario. The DB results of each use case use the "preset business serial number" as the input parameter to obtain the full database table results. Use case level Back up, the executed test plan is checked for consistency with the returned messages of the baseline version, and consistent records, inconsistent records, and missing comparison records of the baseline version are obtained. Inconsistent difference records may be noisy, fields such as timestamps. Provides the function of statistical analysis of noise generation, which is convenient for manual maintenance of the noise field list; in this embodiment, the business serial number is preset as the primary key, the test results are compared, and the abnormal information of the test interface results is output. Regression testing efficiency.

Referring to FIG. 9, FIG. 9 is a schematic diagram of functional modules of an embodiment of the interface automatic testing device of the present invention. In the embodiment of the interface automatic testing device of the present invention, the interface automatic testing device includes:

a request receiving module, configured to obtain the target version protocol to be tested corresponding to the interface protocol test request when receiving the interface protocol test request;

a protocol comparison module, configured to compare the target version protocol and the baseline version protocol to obtain protocol update information if there is a baseline version protocol associated with the target version protocol;

an engine update module, configured to obtain a baseline test engine corresponding to the baseline version protocol, update the baseline test engine according to the protocol update information, and obtain a target test engine;

A running test module is configured to generate a target test case according to the target test engine, and run the target test case to obtain a target test result of the target version protocol.

In one embodiment, the interface automated testing device includes:

a protocol judgment module for judging whether there is a baseline version protocol associated with the target version protocol;

An engine generation module, configured to analyze the target version protocol to generate a target test engine if the baseline version protocol associated with the target version protocol does not exist, wherein the target test engine includes a business rule engine, a basic field engine and MOCK test engine;

A running test module is configured to generate a target test case according to the target test engine, and run the target test case to obtain a target test result of the target version protocol.

In one embodiment, the engine generation module includes:

an analysis and acquisition unit, configured to analyze the target version protocol if the baseline version protocol associated with the target version protocol does not exist, and obtain a business scenario identifier of the target version protocol;

a first generating unit, configured to query a preset data raising platform, obtain business test rules corresponding to the business scenario identifiers, and generate a business rule engine by summarizing the business test rules;

a second generating unit, configured to traverse the protocol attributes of the target version protocol, and generate a basic field engine based on divergence according to preconfigured divergence rules and field types, field lengths and field enumeration in the protocol attributes;

The third generating unit is used to pull the protocol content information and the upstream and downstream relationship of the target version protocol from the preset protocol management platform, and generate a MOCK test engine according to the protocol content information and the upstream and downstream relationship of the protocol;

The fourth generating unit is configured to combine the business rule engine, the basic field engine and the MOCK test engine to generate a target test engine.

In an embodiment, the third generating unit is further configured to:

Pull the protocol content information of the target version protocol and the protocol upstream and downstream relationship from the preset protocol management platform, and obtain each target downstream protocol to be MOCK downstream of the target version protocol according to the protocol upstream and downstream relationship;

Acquiring the preset target field for Cartesian divergence in the target downstream protocol, performing a Cartesian product on the target downstream protocol according to the target field, and generating a successful MOCK set and a failed MOCK set;

Do Cartesian product between the described successful MOCK sets, obtain the successful class MOCK rule, do Cartesian product with an element in the described failure MOCK set and the described successful MOCK set, obtain the failure class MOCK rule;

The MOCK test engine is generated by summarizing the success class MOCK rules and the failure class MOCK rules.

In one embodiment, the engine update module includes:

An engine obtaining unit, used for obtaining the baseline test engine corresponding to the baseline version protocol, wherein the baseline test engine includes: a business rule engine, a basic field engine and/or a MOCK test engine;

The first update unit is used to query the preset support platform, obtain the update scene identifier in the protocol update information, and the update test rule corresponding to the update scene identifier from the preset support platform, and use the The update test rule is added to the business rules engine to obtain the updated business rules engine;

The second update unit is configured to traverse the newly added attributes of the protocol update information, update the basic field engine according to the change type, change length and newly added enumeration in the newly added attributes, and obtain the updated basic field engine;

The 3rd update unit is used to make Cartesian product with the MOCK rule in the described protocol update information and the MOCK test engine to update the MOCK test engine to obtain the updated MOCK test engine;

An engine combining unit, configured to combine the updated business rule engine, the updated basic field engine and the updated MOCK test engine to obtain a target test engine.

In one embodiment, the running test module includes:

an engine acquisition unit, used to acquire the business rule engine, the basic field engine and the MOCK test engine in the target test engine;

A rule extraction unit, for extracting business engine rules from the business rules engine, extracting field engine rules from the basic field engine, and extracting MOCK engine rules from the MOCK test engine;

A use case generation unit, configured to generate a target test case according to the business engine rule, the field engine rule and the MOCK engine rule, and run the target test case to obtain the target test result of the target version protocol.

In an embodiment, the use case generation unit is further used for:

Obtaining the basic case of the business engine rule, calling a preset automated test platform to process the basic case to generate a business message, and intercepting the business message to generate a business type test case;

Obtain the field engine rules, call the preset automated test platform to process the required business engine rules to generate basic packets, intercept the basic packets, modify the basic packets according to the field engine rules, and generate field type test cases ;

Obtain the MOCK engine rules, call the preset automated test platform to process the necessary business engine rules to generate basic messages, intercept the basic messages, process the basic messages according to the MOCK engine rules, and generate MOCK type test cases ;

The service type test case, the field type test case, and the MOCK type test case are performed a Cartesian product to generate a target test case, and the target test case is run to obtain the target test result of the target version protocol.

In one embodiment, the interface automated testing device includes:

an obtaining and saving module, configured to obtain a preset service serial number corresponding to the target test case, and store the target test result of the target version protocol in association with the preset service serial number;

The result obtaining module is used to obtain the target test result corresponding to the target version protocol and the baseline test result corresponding to the baseline version protocol with the preset service serial number as the main key when receiving the test result comparison request ;

The result comparison module is used for comparing the target test result and the baseline test result to remove redundant data, and output comparison abnormality information.

In the embodiment of the present invention, when an interface protocol test request is received, the target version protocol to be tested corresponding to the interface protocol test request is obtained; it is judged whether there is a baseline version protocol associated with the target version protocol, if there is a target version protocol associated with the target version protocol The baseline version protocol associated with the version protocol is determined as a regression test, and the target version protocol and the baseline version protocol are compared to obtain protocol update information; the baseline test engine corresponding to the baseline version protocol is obtained, and updated according to the protocol information to update the baseline test engine to obtain a target test engine; generate a target test case according to the target test engine, run the target test case to obtain the target test result of the target version protocol, that is, in this embodiment, pass the update test engine, and use the updated test engine to update test cases. Compared with the current interface regression test, the current interface regression test creates a test case every time. Since each test case is a new one, then based on the test case The obtained test result is also a new test result, and the test case of this application is updated according to the target protocol version. The test result obtained by the target protocol version is similar to the test result obtained by the baseline version protocol, so that the tester can quickly locate the problem. The workload of manual review by testers is reduced, and the efficiency of automatic interface testing is further improved.

For the methods executed by the above program modules, reference may be made to the various embodiments of the automatic interface testing method of the present invention, which will not be repeated here.

The present invention also provides a computer-readable storage medium.

The computer-readable storage medium of the present invention stores an automated interface testing program, and when the automated interface testing program is executed by the processor, implements the steps of the above-described interface automated testing method.

For the method implemented when the automatic interface testing program running on the processor is executed, reference may be made to the various embodiments of the automatic interface testing method of the present invention, which will not be repeated here.

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 system 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 system. Without further limitation, an element qualified by the phrase "comprising a..." does not preclude the presence of additional identical elements in the process, method, article or system that includes the element.

The above-mentioned serial numbers of the embodiments of the present invention are only for description, and do not represent the advantages or disadvantages of the embodiments.

From the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation. Based on such understanding, the technical solutions of the present invention can be embodied in the form of software products in essence or the parts that make contributions to the prior art, and the computer software products are stored in a storage medium (such as ROM/RAM) as described above. , magnetic disk, optical disk), including several instructions to make a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present invention.

The above are only preferred embodiments of the present invention, and are not intended to limit the scope of the present invention. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present invention, or directly or indirectly applied in other related technical fields , are similarly included in the scope of patent protection of the present invention.

Claims (11)

1. an interface automatic testing method, is characterized in that, described interface automatic testing method comprises the steps: When receiving the interface protocol test request, obtain the target version protocol to be tested corresponding to the interface protocol test request; If there is a baseline version protocol associated with the target version protocol, comparing the target version protocol with the baseline version protocol to obtain protocol update information; Obtain the baseline test engine corresponding to the baseline version protocol, update the baseline test engine according to the protocol update information, and obtain the target test engine; Generate a target test case according to the target test engine, and run the target test case to obtain the target test result of the target version protocol. 2. interface automation testing method as claimed in claim 1, is characterized in that, described when receiving interface protocol test request, after obtaining the step of described interface protocol test request corresponding to the target version agreement to be tested, described method include: Judging whether there is a baseline version protocol associated with the target version protocol; If the baseline version protocol associated with the target version protocol does not exist, analyze the target version protocol to generate a target test engine, wherein the target test engine includes a business rule engine, a basic field engine and a MOCK test engine; Generate a target test case according to the target test engine, and run the target test case to obtain the target test result of the target version protocol. 3. interface automation testing method as claimed in claim 2 is characterized in that, described if there is no described baseline version protocol associated with described target version protocol, then analyze the step of described target version protocol and generate target test engine ,include: If the baseline version protocol associated with the target version protocol does not exist, analyze the target version protocol, and obtain the service scenario identifier of the target version protocol; Querying the preset data platform, obtaining the business test rules corresponding to the business scenario identifiers, and summarizing the business test rules to generate a business rule engine; Traverse the protocol attribute of the target version protocol, and generate a basic field engine according to the preconfigured divergence rule and the field type, field length and field enumeration in the protocol attribute; Pull the protocol content information and the protocol upstream and downstream relationship of the target version protocol from the preset protocol management platform, and generate a MOCK test engine according to the protocol content information and the protocol upstream and downstream relationship; A target test engine is generated by combining the business rule engine, the basic field engine and the MOCK test engine. 4. The interface automated testing method according to claim 3, wherein the protocol content information and the protocol upstream and downstream relationship of the target version protocol are pulled from the preset protocol management platform, according to the protocol content information and the protocol upstream and downstream relationships. The steps of generating the MOCK test engine for the upstream and downstream relationships of the protocol include: Pull the protocol content information of the target version protocol and the protocol upstream and downstream relationship from the preset protocol management platform, and obtain each target downstream protocol to be MOCK downstream of the target version protocol according to the protocol upstream and downstream relationship; Acquiring the preset target field for Cartesian divergence in the target downstream protocol, performing a Cartesian product on the target downstream protocol according to the target field, and generating a successful MOCK set and a failed MOCK set; Do Cartesian product between the described successful MOCK sets, obtain the successful class MOCK rule, do Cartesian product with an element in the described failure MOCK set and the described successful MOCK set, obtain the failure class MOCK rule; The MOCK test engine is generated by summarizing the success class MOCK rules and the failure class MOCK rules. 5. The interface automated testing method as claimed in claim 1, is characterized in that, described obtaining the corresponding baseline testing engine of described baseline version protocol, updating described baseline testing engine according to described protocol update information, obtaining target testing engine's steps, including: Obtain the baseline test engine corresponding to the baseline version protocol, wherein the baseline test engine includes: a business rule engine, a basic field engine and/or a MOCK test engine; Query the preset support platform, obtain the update scene identifier in the protocol update information from the preset support platform, and the update test rule corresponding to the update scene identifier, and add the update test rule to the Business rules engine, get updated business rules engine; Traversing the newly added attributes of the protocol update information, and updating the basic field engine according to the change type, change length and newly added enumeration in the newly added attributes, to obtain an updated basic field engine; Do Cartesian product with the MOCK rule in described protocol update information and described MOCK test engine, described MOCK test engine is updated, obtain the MOCK test engine of update; A target test engine is obtained by combining the updated business rule engine, the updated basic field engine and the updated MOCK test engine. 6. The interface automated testing method according to claim 1 or 2, wherein the target test case is generated according to the target test engine, and the target test case is obtained by running the target test case to obtain the target test result of the target version protocol. steps, including: Obtain the business rule engine, basic field engine and MOCK test engine in the target test engine; Extract business engine rules from the business rules engine, extract field engine rules from the basic field engine, and extract MOCK engine rules from the MOCK test engine; A target test case is generated according to the business engine rule, the field engine rule and the MOCK engine rule, and the target test case is run to obtain the target test result of the target version protocol. 7. The method for automated testing of interfaces as claimed in claim 6, wherein the target test case is generated according to the business engine rule, the field engine rule and the MOCK engine rule, and the target test case is run to obtain The steps of the target test result of the target version protocol include: Obtaining the basic case of the business engine rule, calling a preset automated test platform to process the basic case to generate a business message, and intercepting the business message to generate a business type test case; Obtain the field engine rules, call the preset automated test platform to process the required business engine rules to generate basic packets, intercept the basic packets, modify the basic packets according to the field engine rules, and generate field type test cases ; Obtain the MOCK engine rules, call the preset automated test platform to process the necessary business engine rules to generate basic messages, intercept the basic messages, process the basic messages according to the MOCK engine rules, and generate MOCK type test cases ; The service type test case, the field type test case, and the MOCK type test case are performed a Cartesian product to generate a target test case, and the target test case is run to obtain the target test result of the target version protocol. 8. The interface automated testing method according to any one of claims 1-7, wherein the target test case is generated according to the target test engine, and the target test case is run to obtain the target of the target version protocol After the step of testing the results, the method includes: obtaining the preset service serial number corresponding to the target test case, and storing the target test result of the target version protocol in association with the preset service serial number; When receiving the test result comparison request, use the preset service serial number as the primary key to obtain the target test result corresponding to the target version protocol and the baseline test result corresponding to the baseline version protocol; Compare the target test result and the baseline test result to remove redundant data, and output comparison abnormality information. 9. An interface automatic testing device, characterized in that, the interface automatic testing device comprises: a request receiving module, configured to obtain the target version protocol to be tested corresponding to the interface protocol test request when receiving the interface protocol test request; a protocol comparison module, configured to compare the target version protocol and the baseline version protocol to obtain protocol update information if there is a baseline version protocol associated with the target version protocol; an engine update module, configured to obtain a baseline test engine corresponding to the baseline version protocol, update the baseline test engine according to the protocol update information, and obtain a target test engine; A running test module is used to generate a target test case according to the target test engine, and run the target test case to obtain a target test result of the target version protocol. 10. An interface automated testing device, characterized in that the interface automated testing device comprises: a memory, a processor, and an automated interface testing program stored on the memory and running on the processor, the interface When the automated testing program is executed by the processor, the steps of the interface automated testing method according to any one of claims 1 to 8 are implemented. 11. A computer-readable storage medium, characterized in that, an interface automated test program is stored on the computer-readable storage medium, and the interface automated test program is implemented as any one of claims 1 to 8 when the interface automated test program is executed by the processor. The steps of the interface automation testing method described in the item.

Images