Get updates on Accelerate 2022

We're back in person. Join us in September for Accelerate in Santa Clara, California.

Sign up for updates
Your transformation toolkit

Advance your enterprise testing strategy with our transformation toolkit.

Learn more
Tricentis qTest

Powering Agile and DevOps workflows

Orchestration, automation, and communication are core tenets required for DevOps success. qTest Pulse helps improve these areas with easy-to-configure workflows that trigger updates across Agile and DevOps tools.

Tricentis qTest team

Automating communication and collaboration

In order for DevOps to work in the enterprise, your testing teams need the ability to communicate and collaborate efficiently. qTest Pulse is an advanced rules engine that automates tool communication within a DevOps pipeline.



Flexible rule sets

Drag and drop rules to orchestrate common events across tools like Jira, Jenkins, and GitHub via webhooks.


Extremely extensible

Use pre-set rules or code your own to trigger data and communication updates across a wide range of tools.


Workflow standardization

Enforce best practices by designing workflows to require certain events before progressing to the next delivery stage.

How it works

With qTest Pulse, create and store custom rules to automatically update tools across your delivery pipeline when certain actions occur.

Step 1: Upload existing rules or create custom code
Step 2: Set code to trigger other webhook-based systems
Step 3: qTest executes and updates systems
Step 4: Systems updates through real-time data processing

Automatically orchestrate DevOps events

Sometimes testers communicate a defect description correctly, but it still takes too long to get the defect resolved. While developers might orchestrate an automated build job, they may not have communicated the results to everyone involved with product, dev, and QA, causing unnecessary delays.

Prevent communication breakdowns by automating updates across Agile teams. With qTest Pulse, set custom rules to remove bottlenecks and keep projects on schedule.

Triggers and actions to orchestra DevOps events

How Pulse is being used across the enterprise

While qTest Pulse’s flexibility allows for multiple use cases and workflows, take a look at one common way that qTest Pulse is being used to simplify enterprise DevOps.

Using qTest across the enterprise

Work with your community to perfect DevOps

When using qTest Pulse, you won’t be working alone. Our GitHub repository makes it easy to re-use existing rules or build new rules, and all of this is supported by the Tricentis community.

How to work with the DevOps community

Limitless integration possibilities

qTest Pulse can orchestrate those common, frequently executed events across any tool with a webhook in your software delivery pipeline. Here are just some of the ways to use qTest Pulse.



When a test fails, send a Slack message to notify the owner of the initial requirement.


qTest manager

When all test pass in a sprint, notify the product lead that features are ready for production.



Triggers a Jenkins build job using the webhook API.



Format test execution results from raw .xml (JUnit style) and send them to qTest Manager.


Jira software

When a test fails 7 times in a row, automatically create a Jira bug.



Format test results from raw Cucumber Java .json and send them to qTest Manager.

Get started with unified test management