Shulou(Shulou.com)06/01 Report--

DevOps is a practical approach designed to integrate R & D and operations with high quality, thereby significantly reducing the time from system change submission to deployment in production environments. Continuous integration is a very important part of DevOps, which involves integrating code from multiple developers and continuously compiling and testing to identify defects as early as possible. Automation is the core of continuous integration, and tool chain integration is the means and method to realize automation. This article focuses on how to integrate unit testing tools in DevOps tool chain integration. A Method of Unit Test Tool Integration Unit Testing Overview Unit testing refers to checking and testing the smallest testable unit in the software. Generally speaking, the specific meaning of the unit in unit testing can be determined according to the actual situation, such as a function in C language, a class in Java and C#, etc. Unit testing is the lowest level of testing activity performed during software development and can be performed in isolation from the rest of the program. integration condition Continuous integration pipeline includes unit test. First, R & D personnel are required to write corresponding functional test methods or function test methods (unit test methods) after completing function development. For large-scale projects, unit test methods can be written step by step along with function development progress or selected according to priority and importance of functions. For Java development projects, it is recommended to use the Junit tool for unit test writing, and for C#development projects to use the Nunit tool for unit test writing. At present, these two unit test tools TFS platform have good support, so they can be easily incorporated into the TFS continuous integration pipeline. core value By including unit testing activities in the continuous integration pipeline, bugs can be found faster in the development phase and fixed at a lower cost. Bug discovery and repair becomes more difficult and costs increase exponentially in the later stages of software development; therefore, writing unit test methods and integrating applications as early as possible is of great significance to improve software quality. Unit Test Tool Integration Practice Tool Chain Integration Framework In order to do a good job in digital transformation and focus on building an integrated R & D and O & M process, enterprises are building an efficient and complete DevOps tool chain, running through development, testing and O & M, building a tool chain that supports continuous integration, automated testing and continuous delivery, and realizing automation of the whole process of R & D-O & M lifecycle: two scenarios of unit test integration cloud integration Continuous integration of unit test tools (Nunit, Junit) of two mainstream development languages (C#, Java) is realized based on TFS platform. As long as the project team completes the preparation of the first unit test method and runs it locally, the unit test process can be added to the continuous integration process: Create a continuous integration pipeline (generation definition) in the TFS tool, and automate the code pulling, downloading, compiling, and executing unit testing methods by adding compilation, unit testing, and other steps: At present, pipelines containing unit test processes support automatic execution in a variety of ways: automatic triggering on code submission, timed triggering, automatic triggering on pull requests (code merge): Unit test results and code coverage (Cobertura, Jacoco support) can be quickly and intuitively fed back to developers via email and page display: integration on the cloud Cloud computing is gradually widely used in enterprises, using cloud for construction, testing and deployment integration, with advantages such as efficiency, speed and consistency. DevOps continuous integration pipeline can adopt TFS as the entry platform, and TFS triggers Jenkins to compile and unit test on the cloud, and transmit the unit test results and code coverage results back to TFS release: Note: For cloud unit test integration, you need to add a statement that calls the unit test tool to the pipeline script on the cloud, for example: stage ('Unit Test'){ steps { sh "${mvnCmd} clean test cobertura:cobertura" //Please modify the path of pom file according to actual situation step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml']) //Please add maven-suicide-plugin to the pom file of the code in advance } concluding remarks Experience shows that R & D projects with a complete unit test methodology have higher software quality, unit regression testing can be performed whenever code is modified, and unit test integration automation greatly saves valuable time for developers, thus focusing on the interaction between unit tests and global functionality.

Add me VX: 17324089390 Reply keyword "test" Get limited software test learning materials Oh ~~

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.