It’s already been a busy year at Tricentis, from our enhanced integration with Jira Software to our release of qTest 9, which includes new solutions for scaling test automation and enterprise BDD. We’re releasing another major enhancement to the most popular CI tool in the industry — Jenkins.
We have built a Jenkins Pipeline integration for the qTest Platform to facilitate continuous integration and continuous delivery. This new integration builds on our integration with Jenkins Freestyle by offering customers another way to collect executed test results triggered off CI builds from their Jenkins servers. Take a look at how it works in the list below.
Features of the qTest Jenkins Pipeline integration include:
- Jenkins Pipeline Support: Configure the Tricentis qTest Plugin to automatically send test results to qTest Manager projects
- Executive Dashboards with qTest Insights: Leverage qTest Insights to build executive-level dashboards based on Jenkins results.
- Flexible Results Options: We’ve added an option to override existing test case steps with new steps when submitting test results.
- Customize CI Results Locations: The new ability to specify the destination for test execution results, whether it’s a Release, Test Cycle or Test Suite.
- Organize Test Results: JUnit test results are now submitted to qTest Manager in the same order they are laid out in the junit.xml.
What Is Jenkins Pipeline?
When using Jenkins, teams practicing continuous integration usually decide to use the Freestyle or Pipeline projects. While Freestyle might be a flexible option for small teams and simple jobs, Freestyle does not scale well for the enterprise due to the comprehensive nature of large continuous delivery pipelines. For enterprise teams, the Jenkins Pipeline is the suggested option to handle modeling simple-to-complex delivery pipelines “as code” via the Pipeline domain-specific language (DSL) syntax and is now supported through the qTest Jenkins Plugin.
Why Is It Important?
DevOps breaks down traditional barriers between development teams and operations to make releases more seamless while continuously checking quality at each stage. However, testing teams can be left out of unit level automation and lack visibility into the latest test and build results. With our integration to Jenkins Pipeline, Tricentis qTest users can now better unify tests that run through continuous integration with other automated functional, performance, exploratory and manual tests, all in one platform.
To learn more and get started with the Jenkins Pipeline integration, visit our support article.