System of one-stop interface automatic test platform

Abstract

The invention discloses a system of a one-stop interface automatic test platform. The system comprises an application layer and an infrastructure layer, the application layer comprises a use case writing page, a use case list, a test suite page and a report list; the infrastructure layer comprises a platform background service and a Mysql database; the platform interface is in bidirectional interaction connection with the platform background service, and the platform background service is connected with the database; the platform background service comprises single case storage / editing / debugging, report query, suite query / editing / debugging, service parameter query / editing and case trigger execution interfaces; the Mysql database comprises a case table, a suite configuration table and an execution report table. According to the method disclosed by the invention, the case is compiled with low codes, namely an automatic case does not need to be compiled manually just like a pytest framework, and other parts only need to be clicked, selected or pasted except that an assertion part needs a small amount of codes.

Description

Technical Field

[0001] The present invention relates to the technical field of automated testing, and in particular to a system of a one-stop interface automated testing platform. Background Art

[0002] The commonly used interface automation testing frameworks in the industry can be roughly divided into two categories. One is the combination of handwritten code case + visual report represented by Pytest+Request+Allure+Jenkins, and the other is the combination of case writing tool + visual report represented by Postman+Newman+Allure+Jenkins. However, no matter which form, multiple tools need to cooperate with each other to complete the entire automated testing process of writing, debugging, triggering execution, and viewing reports. Even for interface automation testing frameworks with relatively low entry barriers such as Postman+Newman+Allure+Jenkins, users also need to be familiar with the use of multiple tools at the same time. If you want to further expand, complex development linkage is also required. If you want to assemble a single case into a complex suite for flexible execution through sequential execution, parameter flow, etc., more complex professional skills are required, which also means a higher learning cost.

[0003] In this case, there is an urgent need for a low-code, one-stop testing platform that can solve the entire automation process of writing, debugging, triggering execution, and viewing reports. It does not require manual writing of code cases like pytest, nor does it require high expansion costs like postman. It only requires the deployment of one platform, and the entire automation process only needs to run on one platform. Summary of the invention

[0004] The purpose of the present invention is to provide a one-stop interface automation test platform system to solve the problems in the prior art.

[0005] To achieve the above-mentioned object, the present invention provides the following technical solutions: a system of a one-stop interface automation test platform, comprising an application layer and an infrastructure layer; The application layer includes a use case writing page, a use case list, a test suite page and a report list; The test case writing page is used to write test cases, including test steps and expected results; The use case list: lists all test cases for users to view and manage; The test suite page is used to organize and manage multiple test cases to form a test suite; The report list: displays the results of each test execution, including pass and fail information.

[0006] The infrastructure layer includes platform backend services and MySQL database; The platform interface is bidirectionally interactively connected to the platform backend service, and the platform backend service is interconnected with the database; The platform backend services include single case saving / editing / debugging, report query, package query / editing / debugging, service parameter query / editing, and case trigger execution interface; The Mysql database includes a case table, a suite configuration table, and an execution report table.

[0007] The single case save / edit / debug: allows users to save, edit and debug a single test case; users can modify the parameters of the test case, the information of the expected results, and perform simulation execution to check its correctness; The report query: provides the function of querying the test report, which is used to view the historical test results, understand the test status and error details; The suite query / edit / debug is used to create, edit and debug test suites, combining multiple test cases to form a complete test process; The service parameter query / edit: used to query and edit the parameters of the test service; The case triggers the execution interface: when the user prepares the test case and suite, the execution interface is triggered to start the test.

[0008] The case table stores the specific information of the test case; The suite configuration table stores configuration information of the test suite; The execution report form records the execution results of each test.

[0009] The method comprises the following steps: S1. Use react+Feibing to develop a simple-to-use interface, then fill in the request body and assertion, and click Save to generate a case with one click; S2, ase data storage: split the interface automation case into various fields and store them in the MySQL database; S3, assembly and running of test suites: Use python+django to develop backend services, based on the case data of S2, and flexibly combine and execute multiple automated cases in sequence in a data-driven way, and transfer parameters between cases; and use caching technology to store the debugging results in the local cache to support suite debugging; S4, case running: the backend service provides an interface to the caller, triggering the execution of the case at the pipeline and scheduled task; S5. Report viewing: The platform analyzes the execution results, obtains the total number of cases, number of successes, number of failures, and execution process logs, and stores them in the database. It also supports viewing and re-triggering execution on the platform interface.

[0010] Compared with the prior art, the present invention has the following beneficial effects: Low-code case writing: There is no need to manually write automated cases like the pytest framework. Except for the assertion part which requires a small amount of code, the rest only requires clicking, selecting or pasting.

[0011] One-stop automation platform: It integrates the interfaces and interfaces of report viewing, pipeline triggering, and assembly kits. There is no need to build multiple environments, and the entire automation process can be completed on one platform.

[0012] Flexible arrangement and assembly of automation suites: The writing of a single case using tools such as Postman and JMeter can also be achieved with low code, but scenario-based suite cases require the writing of complex execution codes to schedule the case execution sequence and flow parameters. This platform encapsulates and integrates these tools, and you only need to arrange the sequence and fill in the parameters on the interface. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings: Figure 1 is a schematic diagram of the present invention; Figure 2 It is the test suite page of the present invention - the design prototype diagram; Figure 3 It is the use case writing page of the present invention - page screenshot. DETAILED DESCRIPTION

[0014] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention.

[0015] See also Figure 1-3,In an embodiment of the present invention, a system of a one-stop interface automation testing platform includes an ,application layer and an infrastructure layer; The application layer includes a use case writing page, a use case list, a test suite page and a report list; The test case writing page is used to write test cases, including test steps and expected results; The use case list: lists all test cases for users to view and manage; The test suite page is used to organize and manage multiple test cases to form a test suite; The report list: displays the results of each test execution, including pass and fail information.

[0016] The infrastructure layer includes platform backend services and MySQL database; The platform interface is bidirectionally interactively connected to the platform backend service, and the platform backend service is interconnected with the database; The platform backend services include single case saving / editing / debugging, report query, package query / editing / debugging, service parameter query / editing, and case trigger execution interface; The single case save / edit / debug: allows users to save, edit and debug a single test case; users can modify the parameters of the test case, the information of the expected results, and perform simulation execution to check its correctness; The report query: provides the function of querying the test report, which is used to view the historical test results, understand the test status and error details; The suite query / edit / debug is used to create, edit and debug test suites, combining multiple test cases to form a complete test process; The service parameter query / edit: used to query and edit the parameters of the test service; The case triggers the execution interface: when the user prepares the test case and suite, the execution interface is triggered to start the test.

[0017] The Mysql database includes a case table, a suite configuration table, and an execution report table.

[0018] The case table stores the specific information of the test case; The suite configuration table stores configuration information of the test suite; The execution report form records the execution results of each test.

[0019] The method comprises the following steps: S1. Use react+Feibing to develop a simple-to-use interface, then fill in the request body and assertion, and click Save to generate a case with one click; S2, ase data storage: split the interface automation case into various fields and store them in the MySQL database; S3, assembly and running of test suites: Use python+django to develop backend services, based on the case data of S2, and flexibly combine and execute multiple automated cases in sequence in a data-driven way, and transfer parameters between cases; and use caching technology to store the debugging results in the local cache to support suite debugging; S4, case running: the backend service provides an interface to the caller, triggering the execution of the case at the pipeline and scheduled task; S5. Report viewing: The platform analyzes the execution results, obtains the total number of cases, number of successes, number of failures, and execution process logs, and stores them in the database. It also supports viewing and re-triggering execution on the platform interface.

[0020] The working principle of the present invention is: React+Feibing is used to develop an easy-to-use interface, which allows you to easily select the environment, service, and interface path, and then fill in the request body and assertion. Click Save to generate a case with one click.

[0021] Case data storage: Split the interface automation case into individual fields and store them in the MySQL database. This facilitates case query management and allows for flexible assembly and execution.

[0022] Assembling and running the test suite: Use python+django to develop the backend service. Based on the case data in the second step, multiple automated cases are flexibly combined and executed in sequence in a data-driven way, and parameters are transferred between cases. And through caching technology, the debugging results are stored in the local cache to support the debugging of the suite.

[0023] Case running: The backend service provides an interface to the caller, which can trigger the execution of cases in multiple places such as pipelines and scheduled tasks, and can be used flexibly.

[0024] Report viewing: The platform can analyze the execution results, obtain the total number of cases, number of successes, number of failures, and execution process logs, and store them in the database. It also supports viewing and re-triggering execution on the platform interface.

[0025] Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein by equivalents. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A one-stop interface automation test platform system, characterized by: Includes application layer and infrastructure layer; The application layer includes a use case writing page, a use case list, a test suite page and a report list; The infrastructure layer includes platform backend services and MySQL database; The platform interface is bidirectionally interactively connected to the platform backend service, and the platform backend service is interconnected with the database; The platform backend services include single case saving / editing / debugging, report query, package query / editing / debugging, service parameter query / editing, and case trigger execution interface; The Mysql database includes a case table, a suite configuration table, and an execution report table.

2. The one-stop interface automation test platform system according to claim 1, characterized in that: The test case writing page is used to write test cases, including test steps and expected results; The use case list: lists all test cases for users to view and manage; The test suite page is used to organize and manage multiple test cases to form a test suite; The report list: displays the results of each test execution, including pass and fail information.

3. The one-stop interface automation test platform system according to claim 1, characterized in that: The single case save / edit / debug: allows users to save, edit and debug a single test case; users can modify the parameters of the test case, the information of the expected results, and perform simulation execution to check its correctness; The report query: provides the function of querying the test report, which is used to view the historical test results, understand the test status and error details; The suite query / edit / debug is used to create, edit and debug test suites, combining multiple test cases to form a complete test process; The service parameter query / edit: used to query and edit the parameters of the test service; The case triggers the execution interface: when the user prepares the test case and suite, the execution interface is triggered to start the test.

4. The one-stop interface automation test platform system according to claim 1, characterized in that: The case table stores the specific information of the test case; The suite configuration table stores configuration information of the test suite; The execution report form records the execution results of each test.

5. The one-stop interface automation test platform system according to claim 1, characterized in that: The method comprises the following steps: S1. Use react+Feibing to develop a simple-to-use interface, then fill in the request body and assertion, and click Save to generate a case with one click; S2, ase data storage: split the interface automation case into various fields and store them in the MySQL database; S3, assembly and running of test suites: Use python+django to develop backend services, based on the case data of S2, and flexibly combine and execute multiple automated cases in sequence in a data-driven way, and transfer parameters between cases; and use caching technology to store the debugging results in the local cache to support suite debugging; S4, case running: the backend service provides an interface to the caller, triggering the execution of the case at the pipeline and scheduled task; S5. Report viewing: The platform analyzes the execution results, obtains the total number of cases, number of successes, number of failures, and execution process logs, and stores them in the database. It also supports viewing and re-triggering execution on the platform interface.

Images