CN114780431A - SAI THRIFT automatic test method - Google Patents

Abstract

The invention discloses an SAI THRIFT automatic test method, which has excellent universality, supports the test verification requirements of three scenes in a set of test framework, and forms three test kits, namely an automatic test kit, a new environment test kit and a development test kit based on a set of universal deploy and autotest scripts. The automatic testing and verifying task calls an automatic verification suite, so that the quality of engineering codes can be ensured; when a testing framework is deployed SAI THRIFT in the new environment, a new environment testing suite is called, and the SAI THRIFT testing environment can be rapidly deployed; and carrying out engineering development or problem positioning and modifying scenes, calling a development test suite before preparing to submit codes, and carrying out test verification by using the generated mirror image to confirm that the newly added codes have no influence on the existing functions. The invention can ensure the stability of SAI THRIFT test and effectively improve the efficiency of SAI development and maintenance.

Description

SAI THRIFT automated testing method

technical field

The invention relates to the technical field of service deployment testing, in particular to a SAI THRIFT automated testing method.

Background technique

Thrift is a cross-language and cross-platform service deployment framework. It defines RPC interfaces and data types through the interface definition language, and then generates different language codes (supports C++, Java, Python, PHP, Ruby, Erlang and other languages) through the Thrift compiler. ), and the generated code is responsible for the implementation of the RPC protocol layer and the transport layer. RPC (RemoteProcedure Call) is a remote calling protocol. Simply put, it enables applications to call remote procedures or services as if they were calling local methods. It can be used in many scenarios such as distributed services, distributed computing, and remote service calls.

SAI Thrift is a set of SAI functional testing framework based on Thrift technology. As shown in Figure 1, it consists of a server (Test Machine) and a device under test (DUT, Device Under Test). The network card of the server is connected to the device under test. directly connected to the network port. The DUT acts as the SAI Thrift test server, and the server Test Machine acts as the SAI Thrift test client. Run SAI Server Container, also known as Thrift Test Server, on the device under test Switch; use a server with multiple INTF network cards as Test Machine, also known as SAIThrift Test Client, and the server interface is physically connected to the device under test; Execute the test PTF script on the Thrift TestClient to test the function and performance of the device under test. At present, the test equipment and the test server are interconnected using multiple network ports for functional testing of the equipment. The Test Machine server first remotely calls the SAI external interface on the DUT to configure the Device; the Test Machine server then constructs the assembly message and sends it to the DUT through the network card; then checks whether the network card receives the message from the DUT, if received The document further checks whether the packet format meets the expectations, so as to achieve the purpose of testing the DUT packet forwarding function.

In the practice of engineering program development, usually the version control of the code is integrated with the compilation environment. The code is updated and managed through the code version control tool, and the program version can be compiled from the code directory obtained from the version control tool. To ensure the quality of the development project, automated testing tasks can be deployed. In order to improve the efficiency of development, an automated compilation task is also established, and code compilation is performed on the server on a regular basis.

In the application practice of SAI Thrift, there is a lack of a test framework that can simultaneously adapt to automatic build version automated testing, new test environment SAI THRIFT deployment and test verification, and compile server self-compiled version testing.

SUMMARY OF THE INVENTION

According to an embodiment of the present invention, a SAI THRIFT automated testing method is provided, comprising the following steps:

Create an encoding and compilation server to be responsible for compiling the system images used;

Create an automated test server to trigger scheduled compilation and scheduled automated test execution;

Abstractly analyze the requirements of SAI Thrift automated testing, new test environment deployment to execute SAI THRIFT automated testing, and automated testing of the developer's compiled version, and obtain three execution actions: image construction, test environment deployment, and test case execution;

Mirror construction can be automatically compiled or built by developers;

The deployment of the test environment is abstracted into a deploy script, which adapts to the local deployment execution based on the test server and the remote deployment execution of the code server;

The test case execution is abstracted into an autotest script, and it is also adapted to the local deployment execution based on the test server and the remote deployment execution of the code server;

Based on the deploy script and autotest script, carry out packaging abstraction to obtain automated test suites, new environment test suites, and development test suites, which are respectively used for SAI Thrift automated testing, new test environment deployment to execute SAI THRIFT automated testing, and developer compiled versions of automated tests.

Further, the automatic compilation and construction are executed regularly by the encoding server, and the compilation task is triggered regularly by the Jenkins continuous integration tool.

Further, developers independently compile and build by incremental compilation, only compiling modified files.

Further, using the automated test suite for SAI Thrift automated testing is specifically:

Automatically compile the project, compile the project regularly, obtain the compiled image, and push the compiled image to the specified location for storage;

Automate test tasks and call deploy scripts to complete image deployment;

Call the autotest script for automated testing and generate automated test results;

Analyze automated test results, generate automated test reports, and send them to relevant personnel via email or other tools.

Further, when the storage resources of the test server are sufficient, use the new environment test suite to deploy the new test environment and execute the SAI THRIFT automated test as follows:

Obtain the LoadJenkinsImage script from the compilation server, use the LoadJenkinsImage script to download the automatically compiled image and the saithrift intermediate file generated by the compilation to the code directory of the version control tool, and then copy it to the test server;

On the test server, execute the deploy script to deploy the image;

On the test server, call the autotest script, execute the automated test, and obtain the automated test result;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

Further, when the storage resources of the test server are limited, use the new environment test suite to deploy the new test environment and execute the SAI THRIFT automated test as follows:

Obtain the LoadJenkinsImage script from the compilation server, and use the LoadJenkinsImage script to download the compiled image and the saithrift intermediate file generated by the compilation to the code directory of the version control tool;

On the code server, remotely call and execute the deploy script to deploy the image;

On the code server, remotely call the autotest script, execute automated tests, and obtain automated test results;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

Further, when the storage resources of the test server are limited, the automated testing of the developer-compiled version using the development test suite is as follows:

Use the code management server to modify the specified code, perform incremental compilation for the modified code, and generate an image;

Obtain the LoadJenkinsImage script from the compilation server, call the LoadJenkinsImage script, and organize the generated image and the compiled saithrift intermediate files into a folder;

On the code server, call the deploy script to deploy the generated image to the test server and test equipment;

On the code server, call the autotest script, execute the automated test, and obtain the automated test result;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

Further, when the storage resources of the test server are sufficient, the automated testing of the compiled version of the developer using the development test suite is as follows:

Use the code management server to modify the specified code, perform incremental compilation for the modified code, and generate an image;

Obtain the LoadJenkinsImage script from the compilation server, call the LoadJenkinsImage script, organize the generated image and the compiled saithrift intermediate files into a folder, package and compress the folder and copy it to the test server;

On the test server, execute the deploy script to deploy the image;

On the test server, call the autotest script, execute the automated test, and obtain the automated test structure;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

According to the SAI THRIFT automated testing method of the embodiment of the present invention, the present invention has excellent versatility, and supports the test verification requirements of the three scenarios in a set of test frameworks. Based on a set of general deploy and autotest scripts, the Three test suites were created - automated test suite, new environment test suite, development test suite. The automated test verification task invokes the automated verification suite to ensure the quality of the engineering code; when deploying the SAITHRIFT test framework in the new environment, the new environment test suite is invoked to quickly deploy the SAI THRIFT test environment; for engineering development or problem location, modify the scenario and prepare for Before code submission, you can call the development test suite and use the generated image for test verification to confirm that the new code has no effect on the existing functions. The present invention can ensure the stability of the SAI THRIFT test and effectively improve the efficiency of SAI development and maintenance.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and are intended to provide further explanation of the claimed technology.

Description of drawings

FIG. 1 is a test frame diagram of SAI Thrift in the prior art.

FIG. 2 is a test frame diagram of the SAI THRIFT automated test method according to an embodiment of the present invention.

FIG. 3 is a flowchart of a SAI THRIFT automated testing method according to an embodiment of the present invention.

Detailed ways

The preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings to further illustrate the present invention.

First, the SAI THRIFT automated testing method according to an embodiment of the present invention will be described with reference to FIGS. 2 to 3 , which is used for functional testing of equipment, and has a wide range of application scenarios.

As shown in Figures 2 to 3, the SAI THRIFT automated testing method according to the embodiment of the present invention includes the following steps:

In S1, as shown in Figure 3, an encoding and compiling server is created to be responsible for compiling the system image used. In this embodiment, the system image includes SAI (Thrift) Server Docker Image and PTF Client Docker Image.

In S2, as shown in Figure 3, an automated test server is created for triggering timing compilation and timing automated test execution.

In S3, as shown in Figure 3, abstract analysis of the requirements for SAI Thrift automated testing, new test environment deployment and execution of SAI THRIFT automated testing, and automated testing of developers' compiled versions to obtain image construction, test environment deployment, and test case execution. Three perform actions.

In S4, as shown in Figure 3, the image build can be automatically compiled or built by developers. In this embodiment, further, the automatic compilation and construction are executed by the encoding server periodically, and the compilation task is triggered regularly by means of the Jenkins continuous integration tool. Developers independently compile and build using incremental compilation, only compiling modified files, and quickly building the version image.

In S5, as shown in Figure 3, the deployment of the test environment is abstracted into a deploy script, which is adapted to the local deployment execution based on the test server and the remote deployment execution of the code server.

In S6, as shown in Figure 3, the test case execution is abstracted into an autotest script, which is also adapted to the local deployment execution based on the test server and the remote deployment execution of the code server.

In S7, as shown in Figure 3, based on the deploy script and the autotest script, the packaging abstraction is performed to obtain automated test suites, new environment test suites, and development test suites, which are respectively used for SAI Thrift automated testing and new test environment deployment. Execute SAI THRIFT automated tests as well as automated tests of developer-compiled versions.

Further, in this embodiment, using the automated test suite to perform the SAI Thrift automated test is specifically:

Automatically compile the project, compile the project regularly, obtain the compiled image, and push the compiled image to the specified location for storage;

Automate test tasks and call deploy scripts to complete image deployment;

Call the autotest script for automated testing and generate automated test results;

Analyze automated test results, generate automated test reports, and send them to relevant personnel via email or other tools.

Further, in this embodiment, when the storage resources of the test server are sufficient, using the new environment test suite to deploy the new test environment and execute the SAI THRIFT automated test is specifically:

Obtain the LoadJenkinsImage script from the compilation server, use the LoadJenkinsImage script to download the automatically compiled image and the saithrift intermediate file generated by the compilation to the code directory of the version control tool, and then copy it to the test server;

On the test server, execute the deploy script to deploy the image;

On the test server, call the autotest script, execute the automated test, and obtain the automated test result;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

Further, in this embodiment, when the storage resources of the test server are short, using the new environment test suite to deploy the new test environment and execute the SAI THRIFT automated test is specifically:

Obtain the LoadJenkinsImage script from the compilation server, and use the LoadJenkinsImage script to download the compiled image and the saithrift intermediate file generated by the compilation to the code directory of the version control tool;

On the code server, remotely call and execute the deploy script to deploy the image;

On the code server, remotely call the autotest script, execute automated tests, and obtain automated test results;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

Further, in this embodiment, when the storage resources of the test server are in short supply, using the development test suite to perform the automated test of the compiled version of the developer is specifically:

Use the code management server to modify the specified code, perform incremental compilation for the modified code, and generate an image;

Obtain the LoadJenkinsImage script from the compilation server, call the LoadJenkinsImage script, and organize the generated image and the compiled saithrift intermediate files into a folder;

On the code server, call the deploy script to deploy the generated image to the test server and test equipment;

On the code server, call the autotest script, execute the automated test, and obtain the automated test result;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

Further, in this embodiment, when the storage resources of the test server are sufficient, using the development test suite to perform the automated test of the compiled version of the developer is specifically:

Use the code management server to modify the specified code, perform incremental compilation for the modified code, and generate an image;

Obtain the LoadJenkinsImage script from the compilation server, call the LoadJenkinsImage script, organize the generated image and the compiled saithrift intermediate files into a folder, package and compress the folder and copy it to the test server;

On the test server, execute the deploy script to deploy the image;

On the test server, call the autotest script, execute the automated test, and obtain the automated test structure;

Analyze the automated test results and confirm that the changes made to the code directory have no effect on the basic functions.

The SAI THRIFT automated testing method according to the embodiment of the present invention is described above with reference to FIGS. 2 to 3. The present invention has excellent versatility, and supports the test verification requirements of three scenarios in a set of test frameworks. A set of common deploy and autotest scripts to form three test suites - automated test suites, new environment test suites, and development test suites. The automated test verification task invokes the automated verification suite to ensure the quality of the engineering code; when deploying the SAI THRIFT test framework in the new environment, the new environment test suite is invoked to quickly deploy the SAI THRIFT test environment; for engineering development or problem location, modify the scenario and prepare Before submitting the code, you can call the development test suite and use the generated image for test verification to confirm that the new code has no effect on the existing functions. The present invention can ensure the stability of the SAI THRIFT test and effectively improve the efficiency of SAI development and maintenance.

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

While the content of the present invention has been described in detail by way of the above preferred embodiments, it should be appreciated that the above description should not be construed as limiting the present invention. Various modifications and alternatives to the present invention will be apparent to those skilled in the art upon reading the foregoing. Accordingly, the scope of protection of the present invention should be defined by the appended claims.

Claims (8)

1. An SAI THRIFT automatic test method, comprising the steps of:

creating a coding and compiling server for taking charge of a system mirror image used for compiling;

creating an automatic test server for triggering timing compilation and timing automatic test execution;

carrying out abstract analysis on requirements of SAI thread automated testing, deployment and execution SAI THRIFT automated testing of a new testing environment and automated testing of a developer compiling version to obtain three execution actions of mirror image construction, testing environment deployment and test case execution;

the mirror image construction can be automatically compiled and constructed or independently compiled and constructed by developers;

deploying and abstracting the test environment to form a deployment script, and adapting to local deployment execution based on a test server and remote deployment execution of a code server;

abstracting the test case execution into an autotest script, and adapting to local deployment execution based on the test server and remote deployment execution of the code server;

and packaging and abstracting on the basis of the deployment script and the autotest script to obtain an automatic test suite, a new environment test suite and a development test suite, wherein the automatic test suites are respectively used for carrying out the SAI Thrift automatic test, the new test environment deployment execution SAI THRIFT automatic test and the automatic test of the developer compiling version.

2. The automated SAI THRIFT test method of claim 1, wherein the automated compilation build is executed periodically by the code server, with timed triggering of compilation tasks by Jenkins persistent integration tools.

3. The automated SAI THRIFT test method of claim 1, wherein the developer autonomic compilation constructs compilation only modified files in an incremental compilation.

4. The automated test method SAI THRIFT of claim 1, wherein performing the SAI thread automated test using the automated test kit specifically comprises:

the method comprises the steps of automatically compiling a project, regularly compiling the project, obtaining a compiled mirror image, and pushing the compiled mirror image to a specified position for storage;

the automatic test task calls the deployment script to complete the deployment of the mirror image;

calling the autotest script to perform automatic testing, and generating an automatic testing result;

and analyzing the automatic test result, generating an automatic test report, and pushing the report to related personnel through mails or other tools.

5. The automated testing method SAI THRIFT of claim 1, wherein when the test server storage resources are sufficient, performing the new test environment deployment execution SAI THRIFT automated testing using the new environment test suite specifically comprises:

acquiring a LoadJenkins image script from the compiling server, downloading an automatically compiled mirror image and a saitthrift intermediate file generated by compiling to a code directory of a version control tool by using the LoadJenkins image script, and copying the code directory to the testing server;

executing the deployment script and the deployment of the mirror image on the test server;

calling an autotest script on the test server, executing an automatic test, and obtaining an automatic test result;

and analyzing the automatic test result, and confirming the modification of the code directory without influencing the basic function.

6. The automated test method SAI THRIFT as claimed in claim 1, wherein when the test server is in a short storage resource, performing the new test environment deployment execution SAI THRIFT automated testing using the new environment test suite specifically comprises:

acquiring a LoadJenkins image script from the compiling server, and downloading a compiled mirror image and a saitthrift intermediate file generated by compiling to a code directory of a version control tool by using the LoadJenkins image script;

remotely calling and executing the deployment script on the code server, and executing the deployment of the mirror image;

remotely calling an autotest script on the code server, executing an automatic test, and obtaining an automatic test result;

and analyzing the automatic test result, and confirming the modification of the code directory without influencing the basic function.

7. The automated test method SAI THRIFT of claim 1, wherein when the test server is in a short storage resource state, using the development test suite to perform automated testing of the compiled version of the developer is specifically:

modifying the specified code by using a code management server, and performing incremental compilation aiming at the modified code to generate a mirror image;

acquiring a LoadJenkins image script from the compiling server, calling the LoadJenkins image script, and arranging the generated mirror image and the saitthrift intermediate file generated by compiling into a folder;

calling the deployment script on the code server, and deploying the generated mirror image to the test server and the test equipment;

calling the autotest script on the code server, executing an automatic test, and obtaining an automatic test result;

and analyzing the automatic test result, and confirming the modification of the code catalog without influencing the basic function.

8. The automated test method SAI THRIFT of claim 1, wherein when the test server has sufficient storage resources, the automated testing of the compiled version of the developer using the development test suite is performed by:

modifying the specified code by using a code management server, and performing incremental compilation aiming at the modified code to generate a mirror image;

acquiring a LoadJenkins image script from the compiling server, calling the LoadJenkins image script, arranging the generated mirror image and the saitthrift intermediate file generated by compiling into a folder, packaging and compressing the folder, and copying the folder to the testing server;

executing the deployment script and the deployment of the mirror image on the test server;

calling the autotest script on the test server, executing an automatic test, and obtaining an automatic test structure;

and analyzing the automatic test result, and confirming the modification of the code directory without influencing the basic function.

Images