Automatic interface testing method and system

Abstract

The invention discloses an automatic interface test method and system, and the method comprises the steps: starting an interface test scene, and obtaining test data related to the interface test scene; wherein the test data comprises test point data, associated data, environment configuration data and interface test data; whether a front interface exists or not is judged, and when the front interface exists, the priority of the associated data is configured in the automatic test scene; whether scene data configuration exists or not is judged, and when the scene data configuration exists, the priority of the scene data is configured in the automatic test scene; processing the test data based on the priority of the data in the test data to generate interface request data; and sending the interface request data, processing corresponding interface data based on the interface request data to obtain an actual test result, and generating a test report based on the actual test result and an expected result in the interface test data.

Description

Technical Field

[0001] The present invention relates to the field of automatic testing technology, and more specifically, to an interface automatic testing method and system. Background Art

[0002] In the process of software development, interface automation testing is one of the important methods to improve testing efficiency and quality. Traditional interface testing methods rely on testers to manually write test cases and prepare test data. In the process of interface function testing with large parameters and complex logic, this work is not only time-consuming and labor-intensive, but also prone to errors and omissions.

[0003] The data-driven framework is a test framework commonly used in the interface testing process. Testers can use different data sets to drive the coverage of functional logic points.

[0004] Therefore, an interface automation testing method based on a data-driven framework is needed. Summary of the invention

[0005] The present invention provides an interface automation testing method and system to solve the problem of how to efficiently perform interface automation testing.

[0006] In order to solve the above problem, according to one aspect of the present invention, a method for automatic interface testing is provided, the method comprising:

[0007] Start an interface test scenario and obtain test data related to the interface test scenario; wherein the test data includes: test point data, associated data, environment configuration data and interface test data;

[0008] Determine whether there is a front-end interface, and if so, configure the priority of the associated data in the automated test scenario;

[0009] Determine whether there is scenario data configuration, and if so, configure the priority of the scenario data in the automated test scenario;

[0010] Processing the test data based on the priority of the data in the test data to generate interface request data;

[0011] The interface request data is sent, the interface corresponding data is processed based on the interface request data to obtain actual test results, and a test report is generated based on the actual test results and expected results in the interface test data.

[0012] Preferably, the method further comprises:

[0013] Test point data is generated according to the test points added by the tester according to the test requirements, so as to generate interface test data based on the test point data.

[0014] Preferably, the step of generating interface test data based on the test point data comprises:

[0015] Generate first interface request data based on the interface template of the interface scenario test and in combination with the test point data;

[0016] Generate second interface test data according to the environment configuration data and the first interface request data;

[0017] Generate third interface test data according to the associated data and the second interface request data;

[0018] Generate fourth interface test data according to the scenario data and the third interface request data;

[0019] The fourth interface test data is used as the interface request data, and the interface test data is stored when the interface request is sent, so as to form an association relationship with the test point and the test point data for data storage.

[0020] Preferably, the method further comprises:

[0021] In the next round of automated testing, if it is found that the type of a certain data is empty or does not exist, the data generation step is skipped and the data of the previous step is retained in the result of the current step; and

[0022] Record data generation logs and abnormal conditions; wherein the abnormal conditions are recorded in the test report.

[0023] Preferably, the method further comprises:

[0024] The tester manually checks the error information based on the test report, supplements the test data based on the error information to manually comb the test point data, and maintains the expected data based on the error information;

[0025] Based on the test point data, the environment variables and data processing logic are manually configured and the expected data is maintained to obtain environment configuration data, priority data and interface test data.

[0026] According to another aspect of the present invention, there is provided an interface automation testing system, the system comprising:

[0027] A test start unit, used to start an interface test scenario and obtain test data related to the interface test scenario; wherein the test data includes: test point data, associated data, environment configuration data and interface test data;

[0028] A front-end interface determination unit, used to determine whether a front-end interface exists, and when a front-end interface exists, configure the priority of associated data in the automated test scenario;

[0029] A scenario data configuration judgment unit, used to judge whether there is scenario data configuration, and when there is scenario data configuration, configure the priority of the scenario data in the automated test scenario;

[0030] An interface request data generating unit, used for processing the test data based on the priority of the data in the test data to generate interface request data;

[0031] The test unit is used to send the interface request data, process the interface corresponding data based on the interface request data to obtain actual test results, and generate a test report based on the actual test results and expected results in the interface test data.

[0032] Preferably, the system further comprises:

[0033] The interface test data generating unit is used to generate test point data according to the test points added by the tester according to the test requirements, so as to generate interface test data based on the test point data.

[0034] Preferably, the interface test data generating unit generates the interface test data based on the test point data, including:

[0035] Generate first interface request data based on the interface template of the interface scenario test and in combination with the test point data;

[0036] Generate second interface test data according to the environment configuration data and the first interface request data;

[0037] Generate third interface test data according to the associated data and the second interface request data;

[0038] Generate fourth interface test data according to the scenario data and the third interface request data;

[0039] The fourth interface test data is used as the interface request data, and the interface test data is stored when the interface request is sent, so as to form an association relationship with the test point and the test point data for data storage.

[0040] Preferably, the interface test data generating unit further comprises:

[0041] A data updating unit is used to skip the data generation step and retain the data of the previous step in the result of the current step if it is found that the type of a certain data is empty or does not exist during the next round of automated testing; and

[0042] A recording unit is used to record data generation logs and abnormal conditions; wherein the abnormal conditions are recorded in the test report.

[0043] Preferably, the system further comprises: a data updating unit, configured to:

[0044] The tester manually checks the error information based on the test report, supplements the test data based on the error information to manually comb the test point data, and maintains the expected data based on the error information;

[0045] Based on the test point data, the environment variables and data processing logic are manually configured and the expected data is maintained to obtain environment configuration data, priority data and interface test data.

[0046] The present invention provides an interface automation test method and system, comprising: starting an interface test scenario, and obtaining test data related to the interface test scenario; wherein the test data comprises: test point data, associated data, environment configuration data and interface test data; judging whether there is a front-end interface, and configuring the priority of associated data in the automation test scenario when there is a front-end interface; judging whether there is a scenario data configuration, and configuring the priority of scenario data in the automation test scenario when there is a scenario data configuration; processing the test data based on the priority of data in the test data to generate interface request data; sending the interface request data, processing interface corresponding data based on the interface request data to obtain actual test results, and generating a test report based on the actual test results and expected results in the interface test data. In the process of testing the complex logic of a fixed interface, the present invention can cover the test points of the test cases by supplementing the test points with simple basic data without modifying the test scripts, thereby reducing the time cost and difficulty of writing interface automation test cases. The data in the test data layer can be dynamically adjusted according to actual conditions to support interface testing requirements in different scenarios. The data in the test process can be accumulated and deposited in the corresponding data layer to form continuous optimization and improvement of the interface automation test process. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] A more complete understanding of exemplary embodiments of the present invention may be obtained by referring to the following drawings:

[0048] Figure 1 is a flowchart of an interface automation testing method 100 according to an embodiment of the present invention;

[0049] Figure 2 A schematic diagram of data interaction in an automated testing process according to an embodiment of the present invention;

[0050] Figure 3 FIG. 3 is a schematic diagram of the structure of an interface automation testing system 300 according to an embodiment of the present invention. DETAILED DESCRIPTION

[0051] Now, exemplary embodiments of the present invention are described with reference to the accompanying drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. These embodiments are provided to disclose the present invention in detail and completely and to fully convey the scope of the present invention to those skilled in the art. The terms used in the exemplary embodiments shown in the accompanying drawings are not intended to limit the present invention. In the accompanying drawings, the same units / elements are marked with the same reference numerals.

[0052] Unless otherwise specified, the terms (including technical terms) used herein have the commonly understood meanings to those skilled in the art. In addition, it is understood that the terms defined in commonly used dictionaries should be understood to have the same meanings as those in the context of the relevant fields, and should not be understood as idealized or overly formal meanings.

[0053] Figure 1 FIG. 1 is a flow chart of an interface automation testing method 100 according to an embodiment of the present invention. Figure 1 As shown, the interface automation testing method provided by the embodiment of the present invention, in the process of testing the complex logic of the fixed interface, the changes of the test points can be completed by supplementing the test points of the use case through simple basic data, without the need to modify the test script, thereby reducing the time cost of writing interface automation test cases and the difficulty of writing interface automation cases; the data in the test data layer can be dynamically adjusted according to the actual situation to support interface testing requirements in different scenarios; the data in the test process can be accumulated and precipitated in the corresponding data layer, forming continuous optimization and improvement of the interface automation testing process. The interface automation testing method 100 provided by the embodiment of the present invention starts from step 101. In step 101, the interface test scenario is started, and test data related to the interface test scenario is obtained; wherein the test data includes: test point data, associated data, environment configuration data and interface test data.

[0054] In step 102, it is determined whether there is a front-end interface, and when there is a front-end interface, the priority of the associated data is configured in the automated test scenario;.

[0055] In step 103, it is determined whether there is scenario data configuration, and if there is scenario data configuration, the priority of the scenario data is configured in the automated test scenario.

[0056] In step 104, the test data is processed based on the priority of the data in the test data to generate interface request data.

[0057] In step 105, the interface request data is sent, the interface corresponding data is processed based on the interface request data to obtain actual test results, and a test report is generated based on the actual test results and expected results in the interface test data.

[0058] Preferably, the method further comprises:

[0059] Test point data is generated according to the test points added by the tester according to the test requirements, so as to generate interface test data based on the test point data.

[0060] Preferably, the step of generating interface test data based on the test point data comprises:

[0061] Generate first interface request data based on the interface template of the interface scenario test and in combination with the test point data;

[0062] Generate second interface test data according to the environment configuration data and the first interface request data;

[0063] Generate third interface test data according to the associated data and the second interface request data;

[0064] Generate fourth interface test data according to the scenario data and the third interface request data;

[0065] The fourth interface test data is used as the interface request data, and the interface test data is stored when the interface request is sent, so as to form an association relationship with the test point and the test point data for data storage.

[0066] Preferably, the method further comprises:

[0067] In the next round of automated testing, if it is found that the type of a certain data is empty or does not exist, the data generation step is skipped and the data of the previous step is retained in the result of the current step; and

[0068] Record data generation logs and abnormal conditions; wherein the abnormal conditions are recorded in the test report.

[0069] Preferably, the method further comprises:

[0070] The tester manually checks the error information based on the test report, supplements the test data based on the error information to manually comb the test point data, and maintains the expected data based on the error information;

[0071] Based on the test point data, the environment variables and data processing logic are manually configured and the expected data is maintained to obtain environment configuration data, priority data and interface test data.

[0072] The method of the present invention applies a data stratification strategy and adopts a database management system to divide the data into test point data, template data, associated logic data, environment configuration data, manual debugging data, test base data, and expected template data for management; in combination with a test data processing logic framework, the test data is processed to generate interface test data; then the test script is executed to complete the dynamic generation of test data, and the interface test case generation and testing are completed. The usage scenario is an interface function test scenario where a fixed interface process needs to be interface tested, but the number of interface request parameters is huge and the interface function process is complex.

[0073] In the present invention, a data stratification strategy is applied to divide the test data into several types, namely, test points, test point data, associated data, environment configuration data, data priority, and interface test data.

[0074] (1) Test point: The test point required by the user storage interface.

[0075] (2) Test point data: Test data generated based on the test points, after being sorted and supplemented, corresponds to the test points to form complete data coverage, which serves as one of the basic parameters for the automatic generation process of interface request data.

[0076] (3) Associated data: generated by the previous and subsequent associated steps of the interface. It can be dynamically generated in the interface scenario, or existing data can be used as one of the basic parameters for automatic data generation and associated with the test point.

[0077] (4) Environmental configuration data: This data is configured by the tester based on the actual situation of the interface scenario test environment and serves as one of the basic parameters for automatic data generation.

[0078] (5) Data priority: Testers configure data based on test scenarios and test case sets as logical parameters for automatic data generation.

[0079] (6) Interface test data: Interface test data automatically generated by the data-driven framework during scenario testing. Testers organize and maintain expected scripts. Test data is associated with test points and test scenarios and serves as one of the basic parameters for automatic data generation.

[0080] Combination Figure 2 As shown, in the present invention, the data processing logic framework is:

[0081] 1. Test point generation of test point data: Apply the general data generation framework to generate basic test data based on the test points. The generated data is checked by testers to reduce data redundancy and supplement test point data coverage.

[0082] 2. Process data based on data priority: Due to the priority, the data generation logic varies. The following steps take scene data > associated data > environment configuration data > interface test data as an example.

[0083] Step 1: Generate "Interface Request Data 1" based on the "Interface Template" of the interface scenario test and the "Test Point Data";

[0084] Step 2: Generate "Interface test data 2" based on "environment configuration data" and "interface request data 1";

[0085] Step 3: Generate "Interface test data 3" based on "related data" and "interface request data 2";

[0086] Step 4: Generate "interface test data 4" based on "scenario data" and "interface request data 3";

[0087] Step 5: Store "interface test data 4" as interface request data when sending an interface request, and form an association relationship with the test point and test point data for data storage.

[0088] If a certain type of data is found to be empty or does not exist during the replacement process in steps 1-4, the data generation step is skipped and the data of the previous step is retained in the result of the current step.

[0089] After the data is finally completed, the data generation log and abnormal conditions are recorded. The abnormal conditions can be viewed in the test report.

[0090] Specifically, combined Figure 2 As shown, during the execution of the interface use case, the preconditions and interface test scenarios have been sorted out, and the test scenario writing of the fixed interface process has been completed. The request template of the interface related to the test scenario has been configured or automatically obtained by associating with the interface management module. Specifically, the test process includes:

[0091] Step 1: After starting the interface test scenario, obtain the scenario-related test data. The data source includes test point data, associated data, environment configuration data, and interface test data.

[0092] Step 2: When there is a front-end interface in the automation scenario, you can configure the data priority in the scenario. The priority of the scene-configured associated data is higher than the data priority setting in the stored data.

[0093] Step 3: When scenario data exists in the automation scenario, it is considered as the debugging data configuration set by the tester, and the scenario data priority is higher than the priority settings of all other data.

[0094] Step 4: Process the interface test data according to the priority finally generated in the scenario process and generate interface request data.

[0095] Step 5: When sending an interface request, record the actual interface request data. Record the interface data and split the data according to the logic of data hierarchical management. When new data exists, pre-supplement the data (pre-supplement the data after the test report is generated and the tester completes the analysis).

[0096] Step 6: Process the corresponding data of the interface and compare it with the expected results in the interface test data to finally generate a test report.

[0097] The key points of the present invention are:

[0098] 1. Data hierarchical management: split data into test point test data, test points, test template data, expected template data, associated logic data, environment configuration data, manual debugging data and test base data to improve data quality, promote data integration and sharing, improve use case execution efficiency, and reduce duplication and redundancy.

[0099] 2. Test point test data is automatically generated through test points and test point data. The generated data can accurately cover the test points, reduce the duplication and redundancy of test cases and data, and ensure the final execution efficiency of the test cases.

[0100] 3. The data processing logic can be configured according to the actual test requirements, and data generation is completed by arranging the data priority in the processing logic.

[0101] 4. By adjusting the environment configuration, the data can be accurately matched to the environment, reducing data invalidation caused by environmental problems encountered during the test process.

[0102] 5. The test case supplement process only requires supplementing the test points and then supplementing the test point data to complete the coverage of the new test points and establish a standardized and optimized data processing process.

[0103] 6. During the use of the use case, temporary use case test points can be supplemented by making minor adjustments to the test case in the manual debugging data module. There is no need to modify other data templates or adjust the use case script, ensuring the security and stability of the use case data.

[0104] 7. The executed test cases will be stored in layers according to the configuration rules, while retaining the relationship between the test data and the test points, forming data accumulation and promoting data integration and sharing.

[0105] The interface automation testing method of the present invention is based on a data-driven framework, dynamically generates interface test data for automated testing, applies a data layering strategy, divides data into test point data, template data, associated logic data, environment configuration data, manual debugging data, test base data, and expected template data for management, combines a data processing logic framework, generates automated use case test data, and can dynamically generate interface test data, thereby improving the flexibility and efficiency of the test. The method of the present invention can realize the dynamic generation and efficient use of test data, reduce the time cost of test data preparation and test case writing; no modification of the test script is required, reducing the time cost of interface automation test case writing and the difficulty of writing interface automation cases; the test data repository formed can be used for functional testing of other test modules to form a test data set; the data in the test process can be accumulated and deposited in the corresponding data layer, forming continuous optimization and improvement of the interface automation test process.

[0106] Figure 3 FIG. 3 is a schematic diagram of the structure of an interface automation test system 300 according to an embodiment of the present invention. Figure 3 As shown, the interface automation test system 300 provided by the embodiment of the present invention includes: a test starting unit 301, a front interface judgment unit 302, a scene data configuration judgment unit 303, an interface request data generation unit 304 and a test unit 305.

[0107] Preferably, the test starting unit 301 is used to start an interface test scenario and obtain test data related to the interface test scenario; wherein the test data includes: test point data, association data, environment configuration data and interface test data.

[0108] Preferably, the front-end interface determination unit 302 is used to determine whether a front-end interface exists, and to configure the priority of the associated data in the automated test scenario when a front-end interface exists.

[0109] Preferably, the scenario data configuration determination unit 303 is used to determine whether scenario data configuration exists, and to configure the priority of the scenario data in the automated test scenario when scenario data configuration exists.

[0110] Preferably, the interface request data generating unit 304 is used to process the test data based on the priority of the data in the test data to generate the interface request data.

[0111] Preferably, the testing unit 305 is used to send the interface request data, process the interface corresponding data based on the interface request data to obtain actual test results, and generate a test report based on the actual test results and expected results in the interface test data.

[0112] Preferably, the system further comprises:

[0113] The interface test data generating unit is used to generate test point data according to the test points added by the tester according to the test requirements, so as to generate interface test data based on the test point data.

[0114] Preferably, the interface test data generating unit generates the interface test data based on the test point data, including:

[0115] Generate first interface request data based on the interface template of the interface scenario test and in combination with the test point data;

[0116] Generate second interface test data according to the environment configuration data and the first interface request data;

[0117] Generate third interface test data according to the associated data and the second interface request data;

[0118] Generate fourth interface test data according to the scenario data and the third interface request data;

[0119] The fourth interface test data is used as the interface request data, and the interface test data is stored when the interface request is sent, so as to form an association relationship with the test point and the test point data for data storage.

[0120] Preferably, the interface test data generating unit further comprises:

[0121] A data updating unit is used to skip the data generation step and retain the data of the previous step in the result of the current step if it is found that the type of a certain data is empty or does not exist during the next round of automated testing; and

[0122] A recording unit is used to record data generation logs and abnormal conditions; wherein the abnormal conditions are recorded in the test report.

[0123] Preferably, the system further comprises: a data updating unit, configured to:

[0124] The tester manually checks the error information based on the test report, supplements the test data based on the error information to manually comb the test point data, and maintains the expected data based on the error information;

[0125] Based on the test point data, the environment variables and data processing logic are manually configured and the expected data is maintained to obtain environment configuration data, priority data and interface test data.

[0126] The interface automation testing system 300 of the embodiment of the present invention corresponds to the interface automation testing method 100 of another embodiment of the present invention, and will not be described in detail herein.

[0127] The invention has been described above with reference to a few embodiments. However, it is readily apparent to a person skilled in the art that other embodiments than the ones disclosed above are equally within the scope of the invention, as defined by the appended patent claims.

[0128] Generally, all terms used in the claims are to be interpreted according to their ordinary meaning in the technical field, unless explicitly defined otherwise therein. All references to "a / said / the [means, components, etc.]" are to be openly interpreted as at least one instance of said means, components, etc., unless explicitly stated otherwise. The steps of any method disclosed herein do not necessarily have to be performed in the exact order disclosed, unless explicitly stated otherwise.

[0129] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0130] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0131] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0132] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0133] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention rather than to limit it. Although the present invention has been described in detail with reference to the above embodiments, ordinary technicians in the relevant field should understand that the specific implementation methods of the present invention can still be modified or replaced by equivalents. Any modification or equivalent replacement that does not depart from the spirit and scope of the present invention should be covered within the scope of protection of the claims of the present invention.

Claims

1. An interface automation testing method, characterized in that: The method comprises: Start an interface test scenario and obtain test data related to the interface test scenario; wherein the test data includes: test point data, associated data, environment configuration data and interface test data; Determine whether there is a front-end interface, and if so, configure the priority of the associated data in the automated test scenario; Determine whether there is scenario data configuration, and if so, configure the priority of the scenario data in the automated test scenario; Processing the test data based on the priority of the data in the test data to generate interface request data; The interface request data is sent, the interface corresponding data is processed based on the interface request data to obtain actual test results, and a test report is generated based on the actual test results and expected results in the interface test data.

2. The method according to claim 1, characterized in that The method further comprises: Test point data is generated according to the test points added by the tester according to the test requirements, so as to generate interface test data based on the test point data.

3. The method according to claim 1, characterized in that The generating interface test data based on the test point data comprises: Generate first interface request data based on the interface template of the interface scenario test and in combination with the test point data; Generate second interface test data according to the environment configuration data and the first interface request data; Generate third interface test data according to the associated data and the second interface request data; Generate fourth interface test data according to the scenario data and the third interface request data; The fourth interface test data is used as the interface request data, and the interface test data is stored when the interface request is sent, so as to form an association relationship with the test point and the test point data for data storage.

4. The method according to claim 3, characterized in that The method further comprises: In the next round of automated testing, if it is found that the type of a certain data is empty or does not exist, the data generation step is skipped and the data of the previous step is retained in the result of the current step; and Record data generation logs and abnormal conditions; wherein the abnormal conditions are recorded in the test report.

5. The method according to claim 1, characterized in that The method further comprises: The tester manually checks the error information based on the test report, supplements the test data based on the error information to manually comb the test point data, and maintains the expected data based on the error information; Based on the test point data, the environment variables and data processing logic are manually configured and the expected data is maintained to obtain environment configuration data, priority data and interface test data.

6. An interface automation test system, characterized in that: The system comprises: A test start unit, used to start an interface test scenario and obtain test data related to the interface test scenario; wherein the test data includes: test point data, associated data, environment configuration data and interface test data; A front-end interface determination unit, used to determine whether a front-end interface exists, and when a front-end interface exists, configure the priority of associated data in the automated test scenario; A scenario data configuration judgment unit, used to judge whether there is scenario data configuration, and when there is scenario data configuration, configure the priority of the scenario data in the automated test scenario; An interface request data generating unit, used for processing the test data based on the priority of the data in the test data to generate interface request data; The test unit is used to send the interface request data, process the interface corresponding data based on the interface request data to obtain actual test results, and generate a test report based on the actual test results and expected results in the interface test data.

7. The system according to claim 6, characterized in that The system further comprises: The interface test data generating unit is used to generate test point data according to the test points added by the tester according to the test requirements, so as to generate interface test data based on the test point data.

8. The system according to claim 6, characterized in that The interface test data generating unit generates interface test data based on the test point data, including: Generate first interface request data based on the interface template of the interface scenario test and in combination with the test point data; Generate second interface test data according to the environment configuration data and the first interface request data; Generate third interface test data according to the associated data and the second interface request data; Generate fourth interface test data according to the scenario data and the third interface request data; The fourth interface test data is used as the interface request data, and the interface test data is stored when the interface request is sent, so as to form an association relationship with the test point and the test point data for data storage.

9. The system according to claim 8, characterized in that The interface test data generating unit further includes: A data updating unit is used to skip the data generation step and retain the data of the previous step in the result of the current step if it is found that the type of a certain data is empty or does not exist during the next round of automated testing; and A recording unit is used to record data generation logs and abnormal conditions; wherein the abnormal conditions are recorded in the test report.

10. The system according to claim 6, characterized in that The system further comprises: a data updating unit, configured to: The tester manually checks the error information based on the test report, supplements the test data based on the error information to manually comb the test point data, and maintains the expected data based on the error information; Based on the test point data, the environment variables and data processing logic are manually configured and the expected data is maintained to obtain environment configuration data, priority data and interface test data.

Images