CN114490319A - A distributed continuous integration automated testing method and system - Google Patents

Abstract

The invention provides a distributed continuous integration automatic test method and a system, wherein the method comprises the following steps: the development environment node server acquires codes according to the code paths submitted by the code management tool, packages and compiles the codes, and hooks a code automatic scanning task to perform code normative verification after the compilation is finished; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse; the testing environment node server pulls the mirror image from the Docker mirror image warehouse through the integrated service arrangement tool, and automatically constructs a product testing environment; calling a distributed cloud node server to perform an automation script for smoking test, and then respectively executing a UI automation test and an interface automation test; and after the test is finished, the message notification server automatically generates an automatic test report and sends the automatic test report to the relevant personnel of the project. According to the invention, the compiling construction link and the automatic testing link are respectively operated on different servers, so that the continuous integration efficiency is greatly improved.

Description

A distributed continuous integration automated testing method and system

technical field

The invention relates to the field of computer technology, in particular to a distributed continuous integration automated testing method and system based on a micro-service architecture.

Background technique

Code continuous integration is a software engineering process that is an effort to continuously integrate all software engineers' working copies of software into the code backbone. Developers will frequently integrate code into the trunk throughout the day, and each integration will trigger a series of automated processes, as shown in Figure 1, which includes compilation, automated testing, deployment and release. In the process of code continuous integration, the efficiency of integration needs special attention. The faster the code is integrated into the backbone, the shorter the time for relevant staff to get feedback, and the smoother the practice process.

The current code is continuously integrated in practice, and all links in the process, such as compilation and construction, and automated testing, all run on the same server. In the case of software developed with a microservice architecture, the number of microservices is large and the number of automated tests is relatively large, and the running time of the automated test link will become longer, resulting in slower feedback of continuous integration results, thus affecting software development. In addition, in the process of running the automation link, the server will be occupied all the time, unable to respond to other tasks, resulting in the inability to make full use of resources.

SUMMARY OF THE INVENTION

The purpose of the present invention is to provide a distributed continuous integration automated testing method and system, so as to solve the problems of long running time of automated testing and low continuous integration efficiency in the process of continuous integration of existing codes.

In a first aspect, the present invention provides a distributed continuous integration automated testing method, comprising the following steps:

S1. The development environment node server obtains the code and packages and compiles it according to the code path submitted by the code management tool. After the compilation is completed, the automatic code scanning task is attached to perform code normative verification; and it is created after the code normative verification is passed. Docker image file and push to Docker image repository;

S2, the test environment node server pulls the image from the Docker image warehouse through the integrated service orchestration tool, and automatically builds a product test environment;

S3. Invoke the distributed cloud node server to perform an automated script for smoke test first, and after the smoke test is completed, perform UI automation test and interface automation test respectively;

S4. After the test is completed, an automated test report is automatically generated by the message notification server and sent to the relevant personnel of the project.

In a second aspect, the present invention provides a distributed continuous integration automated testing system, including:

The development environment node server is used to obtain the code and package and compile it according to the code path submitted by the code management tool. After the compilation is completed, the automatic code scanning task is attached to perform code normative verification; and after the code normative verification is passed Create a Docker image file and push it to the Docker image repository;

The test environment node server is used to pull the image from the Docker image warehouse through the integration service orchestration tool, and automatically build the product test environment;

Distributed cloud node server, which is used to perform smoke test with automated script first, and after the smoke test is completed, execute UI automation test and interface automation test respectively;

The message notification server is used to automatically generate an automated test report and send it to project stakeholders after the test is completed.

One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages: the compilation and construction links and the automated testing links are respectively run on different servers, the product testing environment is automatically constructed through the testing environment node server, and the Distributed cloud node server for smoke test, UI automation test and interface automation test. Since the development environment node server is only used for code compilation and normative verification, and has nothing to do with testing, under the microservice architecture, even if there are a large number of microservices and a large number of automated tests, it can still ensure rapid feedback of continuous integration results. In the prior art, it takes a long time to run automated tests in the continuous integration process, which leads to the technical problem of low continuous integration efficiency.

The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

The present invention will be further described below with reference to the accompanying drawings and embodiments.

Figure 1 is a schematic diagram of the process flow of existing software from compilation to deployment and release;

Fig. 2 is the flow chart in the method in Embodiment 1 of the present invention;

3 is a schematic diagram of a distributed structure of automated testing according to an embodiment of the present invention;

4 is a schematic diagram of an automated test report generation state according to an embodiment of the present invention;

5 is a schematic diagram of an interface of a Sonar tool according to an embodiment of the present invention;

FIG. 6 is a schematic flowchart of a specific embodiment of the present invention in the research and development stage and the testing stage;

FIG. 7 is a schematic structural diagram of a system in Embodiment 2 of the present invention.

Detailed ways

The embodiments of the present application provide a distributed continuous integration automated testing method and system to solve the problems of long time for running automated tests and low continuous integration efficiency in the existing code continuous integration process.

The general idea of the technical solutions in the embodiments of the present application is as follows: the compilation and construction links and the automated testing links are respectively run on different servers, the product testing environment is automatically constructed through the test environment node server, and the distributed cloud node server is used for smoke testing. , UI automation testing and interface automation testing. Because the development environment node server is only used for code compilation and normative verification, and has nothing to do with testing, it is sufficient to deal with automated testing under the microservice architecture with a large number of microservices, thus solving the problem of running automation in the continuous integration process in the existing technology. The testing time is longer, which leads to technical problems with lower continuous integration efficiency.

Example 1

As shown in FIG. 2, this embodiment provides a distributed continuous integration automated testing method, including the following steps:

S1. The development environment node server obtains the code and packages and compiles it according to the code path submitted by the code management tool. After the compilation is completed, the automatic code scanning task is attached to perform code normative verification; and it is created after the code normative verification is passed. Docker image file and push to Docker image repository;

S2, the test environment node server pulls the image from the Docker image warehouse through the integrated service orchestration tool, and automatically builds a product test environment;

S3. As shown in Figure 3, the distributed cloud node server is called to perform an automated script for smoke test first, and after the smoke test is completed, UI automation test and interface automation test are performed respectively;

S4. As shown in Fig. 4, after the test is completed, an automated test report is automatically generated by the message notification server and sent to the relevant project personnel.

Wherein, as a better or more specific implementation manner of this embodiment, the method further includes:

S5. The node server of the production-like environment uses the service orchestration tool to pull the image from the mirror warehouse, automatically builds the production-like environment, connects the security testing tools and performance testing tools, verifies the project quality and performance, and automatically sends the production-like environment release after the verification is completed. Completed prompt.

The automatic construction of the product test environment is specifically:

S21. Invoke the cloud interface to deploy the service;

S22. Determine whether the service is successfully started through the health check interface. If yes, complete the preparation of the test environment and trigger the distributed cloud node server. If not, feed back a message of unsuccessful startup to the developers and testers.

As shown in Figure 5, in the S1, the code normative verification content includes: front-end code normative verification, back-end code normative verification, and unit test JUNIT, and the code normative verification uses the Sonar tool To proceed, the Sonar tool provides interfaces for Projects, Issues, Code Rules, Quality Configurations, and Quality Thresholds; where:

The "item" is used to view the item information that has been scanned for security;

The "issue" is used to view issue information for the item being scanned;

The "code rules" are used to set rules for code detection;

The "quality configuration" is used to configure the set of rules used during analysis, and each language has a default configuration;

The "quality threshold" is equivalent to a code detection threshold, and a prompt will appear if the code problem exceeds the threshold, or an email notification will be sent;

In the S4, after the feedback result of the automated test report is sent to the relevant personnel of the project, if there are new functions and related bugs, after the testers manually verify that the new functions and related bugs pass, the automated test scripts are sorted and added to the test case. The library automatically sends a message to the relevant personnel of the project to prompt the completion of the product test release.

The integration service orchestration tool is Docker Compose or k8s; the UI automation test uses the Selenium-based test platform Automate, and the interface automation test uses the Jmeter script and the Requests+ receiving piling test tool Mock to complete the main line process verification.

To sum up, as shown in Figure 6, the tasks in different stages of the continuous integration pipeline are clearly described:

1. R&D stage

Before developers submit code, use Sonar related plug-ins to scan the code, and submit the code management tool git after modification;

2. Test phase

The development environment node server uses the Jenkins task orchestration tool to obtain the submitted code path from git, package and compile it through Maven, and enable Junit unit testing during the compilation process. After the Sonar code specification check is passed, a Docker image file is created and pushed to the Docker image repository;

The test environment node server integrates the service orchestration tool Docker Compose or k8s, pulls the image from the mirror warehouse, automatically builds the product test environment, triggers the automated test node server, and performs the smoke test through the automated script. After the test is completed, the test work is divided into Two parts:

(1) Execute UI automation test and interface automation test respectively through two cloud node servers. The UI automation test uses the Selenium-based test platform Automate, while the interface automation test uses Jmeter script and Requests+ receiving piling test tool Mock to complete the main line process verification. After the code is compiled and packaged, the test server will be triggered and called, which is responsible for managing and calling two distributed cloud servers. One of the Windows Servers uses Automate, a UI automation testing platform based on Selenium’s self-developed. , IE and phantomJS and other browsers provide support to perform UI testing; another Linux server is responsible for running the jmeter interface test script and the interface test code based on the requests library written in python language. After the test execution is completed, the test results will be fed back to the relevant personnel via email for follow-up work.

(2) The testers manually verify the new functions and related bugs. After the test is passed, the automated test scripts are sorted and added to the test case library. After the verification is completed, a reminder email is automatically sent, and the product test release is completed;

3. Deployment stage:

When a large version of a product is released, it is necessary to perform security testing and performance testing in a production-like environment. The production-like environment should be built according to the production environment as much as possible, including network, data volume, service deployment topology, etc., and the production-like environment node server will use the service orchestration The tool pulls images from the mirror warehouse, automatically builds a production-like environment, integrates DockerCompose or K8s through Jenkins, pulls images from the mirror warehouse, and automatically builds an integrated test environment. Jenkins connects security testing tools and performance testing tools to verify project quality and After the verification is completed, a reminder email is automatically sent, and the production-like environment is released.

Based on the same inventive concept, the present application also provides a device corresponding to the method in the first embodiment, and the details are in the second embodiment.

Embodiment 2

As shown in FIG. 7, a distributed continuous integration automated testing system is provided in this embodiment, including:

The development environment node server is used to obtain the code and package and compile it according to the code path submitted by the code management tool. After the compilation is completed, the automatic code scanning task is attached to perform code normative verification; and after the code normative verification is passed Create a Docker image file and push it to the Docker image repository;

The test environment node server is used to pull the image from the Docker image warehouse through the integration service orchestration tool, and automatically build the product test environment;

Distributed cloud node server, which is used to perform smoke test with automated script first, and after the smoke test is completed, execute UI automation test and interface automation test respectively;

The message notification server is used to automatically generate an automated test report and send it to project stakeholders after the test is completed.

Wherein, as a better or more specific implementation manner of this embodiment, the device further includes:

The production-like environment node server is used to pull images from the mirror warehouse through the service orchestration tool to automatically build a production-like environment; hook up the security testing tools and performance testing tools to verify the quality and performance of the project, and automatically send the production-like environment after the verification is completed. Post completion prompt.

The specific process of automatically constructing the product test environment is as follows: calling the cloud interface to deploy the service; judging whether the service is successfully started through the health check interface; if so, complete the preparation of the test environment and trigger the distributed cloud node server; Success messages are fed back to developers and testers.

The code normative verification content includes: front-end code normative verification, back-end code normative verification, and unit test JUNIT, and the code normative verification is performed using the Sonar tool, which provides "projects", Interface for Issues, Code Rules, Quality Configuration, and Quality Thresholds; where:

The "item" is used to view the item information that has been scanned for security;

The "issue" is used to view issue information for the item being scanned;

The "code rules" are used to set rules for code detection;

The "quality configuration" is used to configure the set of rules used during analysis, and each language has a default configuration;

The "quality threshold" is equivalent to a code detection threshold, and a prompt will appear if the code problem exceeds the threshold, or an email notification will be sent;

The message notification server, after sending the automated test report feedback results to the relevant project personnel, if there are new functions and related bugs, after the testers manually verify that the new functions and related bugs pass, the automated test scripts are sorted and added to the test. The use case library automatically sends a message to the relevant project personnel to prompt the completion of the product test release.

The integration service orchestration tool is Docker Compose or k8s; the UI automation test uses the Selenium-based test platform Automate, and the interface automation test uses the Jmeter script and the Requests+ receiving piling test tool Mock to complete the main line process verification.

Since the system introduced in the second embodiment of the present invention is the system used to implement the method in the first embodiment of the present invention, based on the method introduced in the first embodiment of the present invention, those skilled in the art can understand the specific structure and deformation of the device , so it is not repeated here. All devices used in the method of Embodiment 1 of the present invention belong to the scope of protection of the present invention.

The technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages: the compilation and construction links and the automated testing links are respectively run on different servers, the product testing environment is automatically constructed through the testing environment node server, and distributed cloud nodes are used. The server performs smoke testing, UI automation testing and interface automation testing. Since the development environment node server is only used for code compilation and normative verification, and has nothing to do with testing, under the microservice architecture, even if there are a large number of microservices and a large number of automated tests, it can still ensure rapid feedback of continuous integration results. In the prior art, it takes a long time to run automated tests in the continuous integration process, which leads to the technical problem of low continuous integration efficiency.

Although the specific embodiments of the present invention have been described above, those skilled in the art should understand that the specific embodiments we describe are only illustrative, rather than used to limit the scope of the present invention. Equivalent modifications and changes made by a skilled person in accordance with the spirit of the present invention should be included within the scope of protection of the claims of the present invention.

Claims (10)

1. a distributed continuous integration automated testing method, is characterized in that: comprise the following steps: S1. The development environment node server obtains the code and packages and compiles it according to the code path submitted by the code management tool. After the compilation is completed, the automatic code scanning task is attached to perform code normative verification; and it is created after the code normative verification is passed. Docker image file and push to Docker image repository; S2, the test environment node server pulls the image from the Docker image warehouse through the integrated service orchestration tool, and automatically builds a product test environment; S3. Invoke the distributed cloud node server to perform an automated script for smoke test first, and after the smoke test is completed, perform UI automation test and interface automation test respectively; S4. After the test is completed, an automated test report is automatically generated by the message notification server and sent to the relevant personnel of the project. 2. a kind of distributed continuous integration automated testing method according to claim 1, is characterized in that: also comprises: S5. The node server of the production-like environment uses the service orchestration tool to pull the image from the mirror warehouse, automatically builds the production-like environment, connects the security testing tools and performance testing tools, verifies the project quality and performance, and automatically sends the production-like environment release after the verification is completed. Completed prompt. 3. a kind of distributed continuous integration automated testing method according to claim 1, is characterized in that: described automatic construction product test environment is specifically: S21. Invoke the cloud interface to deploy the service; S22. Determine whether the service is successfully started through the health check interface. If yes, complete the preparation of the test environment and trigger the distributed cloud node server. If not, feed back a message of unsuccessful startup to the developers and testers. 4. A distributed continuous integration automated testing method according to claim 1, characterized in that: in the S1, the code normative verification content comprises: front-end code normative verification, back-end code normative verification Verification and unit testing JUNIT and the code normative verification is performed using the Sonar tool, which provides interfaces for "Project", "Issue", "Code Rules", "Quality Configuration" and "Quality Thresholds"; wherein : The "item" is used to view the item information that has been scanned for security; The "issue" is used to view issue information for the item being scanned; The "code rules" are used to set rules for code detection; The "quality configuration" is used to configure the set of rules used during analysis, and each language has a default configuration; The "quality threshold" is equivalent to a code detection threshold, and a prompt will appear if the code problem exceeds the threshold, or an email notification will be sent; In the S4, after the feedback result of the automated test report is sent to the relevant personnel of the project, if there are new functions and related bugs, after the testers manually verify that the new functions and related bugs pass, the automated test scripts are sorted and added to the test case. The library automatically sends a message to the relevant personnel of the project, indicating that the product test release is completed. 5. a kind of distributed continuous integration automation testing method according to claim 1 and 2, is characterized in that: described integration service orchestration tool is Docker Compose or k8s; Described UI automation test uses the test platform Automate based on Selenium, The interface automation test uses the Jmeter script and the Requests+ receiving piling test tool Mock to complete the main line process verification. 6. A distributed continuous integration automated testing system, characterized in that: comprising: The development environment node server is used to obtain the code and package and compile it according to the code path submitted by the code management tool. After the compilation is completed, the automatic code scanning task is attached to perform code normative verification; and after the code normative verification is passed Create a Docker image file and push it to the Docker image repository; The test environment node server is used to pull the image from the Docker image warehouse through the integration service orchestration tool, and automatically build the product test environment; Distributed cloud node server, which is used to perform smoke test with automated script first, and after the smoke test is completed, execute UI automation test and interface automation test respectively; The message notification server is used to automatically generate an automated test report and send it to project stakeholders after the test is completed. 7. a kind of distributed continuous integration automated testing system according to claim 6, is characterized in that: also comprises: The production-like environment node server is used to pull images from the mirror warehouse through the service orchestration tool to automatically build a production-like environment; hook up security testing tools and performance testing tools to verify the quality and performance of the project, and automatically send the production-like environment after the verification is completed Publish complete prompt. 8. A distributed continuous integration automated testing system according to claim 6, characterized in that: the specific process of automatically constructing a product testing environment is: calling a cloud interface to deploy a service; judging whether the service is started successfully through a health check interface, If so, complete the preparation of the test environment and trigger the distributed cloud node server; if not, feed back a message that the startup was unsuccessful to developers and testers. 9. A distributed continuous integration automated testing system according to claim 6, characterized in that: the code normative verification content comprises: front-end code normative verification, back-end code normative verification and unit testing JUNIT and the code normative verification is performed using the Sonar tool, which provides interfaces for "Project", "Issue", "Code Rules", "Quality Configuration" and "Quality Thresholds"; where: The "item" is used to view the item information that has been scanned for security; The "issue" is used to view issue information for the item being scanned; The "code rules" are used to set rules for code detection; The "quality configuration" is used to configure the set of rules used during analysis, and each language has a default configuration; The "quality threshold" is equivalent to a code detection threshold, and a prompt will appear if the code problem exceeds the threshold, or an email notification will be sent; The message notification server, after sending the automated test report feedback results to the relevant project personnel, if there are new functions and related bugs, after the testers manually verify that the new functions and related bugs pass, the automated test scripts are sorted and added to the test. The use case library automatically sends a message to the relevant project personnel to prompt the completion of the product test release. 10. a kind of distributed continuous integration automated testing system according to claim 6 or 7, is characterized in that: described integration service orchestration tool is Docker Compose or k8s; Described UI automation test uses the test platform Automate based on Selenium, The interface automation test uses the Jmeter script and the Requests+ receiving piling test tool Mock to complete the main line process verification.

Images