Video Briefing

Sync Azure DevOps and qTest with qTest Pulse

This video demonstrates a two-way integration between Azure DevOps and Tricentis qTest built on qTest Pulse. Azure DevOps service hooks send work item created, updated and deleted events to Pulse, which keeps the matching qTest requirement current. A defect submitted from a failed test run in qTest is created in Azure DevOps as a bug with a qTest tag and a link back, and changes made to that bug in Azure DevOps update the qTest defect. The demo also shows Slack notifications sent by Pulse and test case generation with qTest Copilot.

qTestTricentis qTestTricentisAzure DevOpsTest ManagementDevOpsQATestingAutomationSDLC

Key Takeaways

  1. 01

    qTest Pulse rules, triggers and actions, paired with Azure DevOps service hooks, keep qTest requirements in step with work items as they are created, updated and deleted.

  2. 02

    A defect submitted from a failed test run in qTest is created in Azure DevOps as a bug, tagged as coming from qTest and linked back to its source.

  3. 03

    Changes a developer makes to that bug in Azure DevOps, such as state and added detail, update the defect in qTest.

  4. 04

    Linking a test case to its requirement in qTest gives the tester traceability, so later changes to the requirement reach them.

  5. 05

    The same Pulse setup can post Slack notifications when work items change, and qTest Copilot can generate test cases from a requirement description.

Sync Azure DevOps and qTest with qTest Pulse: transcript and chapter notes

Watch a working two-way integration between Azure DevOps and Tricentis qTest, built on qTest Pulse. When a work item is created, updated or deleted in Azure DevOps, the matching requirement in qTest follows. A defect logged from a failed test in qTest becomes a bug in Azure DevOps and stays in sync as developers work it.

In this demo Hari Kiran Yalavarthi follows the work the way a team does it. A developer creates a feature in Azure DevOps and it shows up in qTest as a requirement with its state, area path, description and acceptance criteria. The feature is edited, then deleted, and qTest follows each change. A tester links a test case to the requirement for traceability, runs it, fails it and submits a defect. That defect is created in Azure DevOps with a qTest tag and a link back to the source, and when the developer changes its state and adds detail, the qTest defect updates to match.

qTest Pulse ships with a qTest license. The JavaScript, webhook design and field mapping that make it work in a specific environment still have to be built, and that is the work we do. Read qTest Pulse integration and automation, built and run by Merito for the service, or see Tricentis qTest for the product. Merito is an authorized Tricentis reseller and services partner, listed as a Certified Solution Partner in the Tricentis partner directory. Book a conversation.

Consultation request

Book a consultation with Merito

Use this form to talk through the workflow, platform fit, and delivery priorities behind this video with a Merito specialist.

Discovery

Turn the video into a working plan

Use the conversation to translate what you saw here into a practical next step for your team.

Alignment

Get the right specialist involved

We route the request to the team best suited for platform strategy, implementation, quality, or AppSec delivery work.

Get Started

Secure intake workflow

The request is protected by reCAPTCHA Enterprise and processed through Merito's standard consultation flow.

This site is protected by reCAPTCHA Enterprise and the Google Privacy Policy and Terms of Service apply.

Back to videos