Skip to content

Jenkins Integration with qTest and VersionOne

Jenkins Integration

The integration of Jenkins with qTest Manager and VersionOne will help automate the testing process, which in turn will accelerate the delivery process.

Download Datasheet Contact Us

Jenkins – qTest and VersionOne Integration Overview

In an Application Lifecycle Management (ALM) ecosystem, the choice of systems and the collaboration between the cross-functional teams play a great role. While the choice of systems impacts the productivity of a team, the cross-functional collaboration helps the teams get complete context of the business requirements.

Best-of-breed systems such as Jenkins, qTest Manager, and VersionOne help enterprises keep the business and product development team focused on customer priorities, quality of delivery, and also, help automate some steps in the delivery process to accelerate the delivery cycle.

How Jenkins – qTest – VersionOne integration is beneficial for an enterprise

  • Accelerate delivery cycle by automating some test process
  • Access to QA plans and defects in real time
  • Real-time updates on the status of a story, its estimated time of delivery, and any risks that might delay the impending release
  • Complete context of the customer requirement and visibility into codes written by the development team & test cases
    written by QA team
  • Coordinate on the delivery timelines seamlessly with concurrent updates on changes

With Jenkins + qTest Manager + VersionOne integration, enterprises can:

Jenkins qTest VersionOne Integration

How OpsHub Integration Manager integrates Jenkins, qTest Manager and VersionOne

OpsHub Integration Manager integrates Jenkins, qTest Manager and VersionOne – all the three systems with each other bi-directionally. It ensures that all historical and current data is available to each user, in that user’s preferred system, with full context, in real-time. All ‘stories’ from VersionOne automatically synchronize to qTest Manager and all defects associated with the ‘requirement’ synchronize back to VersionOne. Jenkins helps in triggering certain automated quality checks in the ecosystem before the a user story/feature is committed.

Entities that can be synchronized between Jenkins, qTest and VersionOne

Jenkins qTest VersionOne Entities Mapping

Use Case: Jenkins integration with VersionOne and qTest

Problem statement: The QA team wants to automate some of the testing process before source code commit.

Solution: With VersionOne getting integrated with Jenkins and qTest Manager, the QA team will be able to run specific test/regression suits after completion of a user story/feature and before it is committed.

  1. An automation script for quality testing is written in Jenkins which is supposed to run when any ‘defect’ in qTest Manager is marked ‘resolved’.
  2. The quality control team runs test case on a ‘defect’ and marks it ‘resolved’.
  3. Jenkins, automatically, runs the scheduled test on the ‘defect’.
  4. The test results are synchronized to qTest Manager irrespective of whether the test is successful or not.
  5. Based on the test result, the developer would know whether to the trigger the build or not.
Jenkins Integration with qTest VersionOne

Benefits of integration for Jenkins, VersionOne and qTest Manager users

Jenkins & VersionOne users

  • Visibility into QA schedule and test cases in advance
  • Complete context of the defects and their severity
  • No dependency on manual communication for making business decisions
  • Automation introduced through Jenkins saves time

qTest Manager users

  • Access to the business requirements, development status, and associated updates from within qTest Manager
  • Complete context of the customer requirements and priorities
  • No manual efforts needed to keep back-end teams updated on the QA cycle and reports
  • Automation introduced through Jenkins saves time