Installation

TestPulse installs like any Azure DevOps extension. Choose your platform below.

Cloud (Marketplace)
On-premises (.vsix)

Open the Marketplace listing

Go to the TestPulse page on the Visual Studio Marketplace.

Get it free

Select Get it free, choose your organisation, and confirm. You need to be a Project Collection Administrator (or request the extension from one).

Open a project

Once installed, open any project — TestPulse appears in the Test Plans area and on work items.

Download the .vsix

Ask your administrator for the TestPulse package (.vsix) approved for your Server version. This documentation does not provide a public Server package download link; obtain the package before continuing.

Upload to your collection

In Azure DevOps Server 2022.1, open the Manage extensions area of your collection and upload the .vsix.

Install into the collection

Install it into the target collection. This requires the Edit collection-level information permission.

Azure DevOps Server 2022.1 is the version targeted by this documentation. Before rollout, validate the workflows you need with your administrator; this is not a qualification of every feature on every Server installation. No TestPulse server-side service is installed.

Prerequisites

An Azure DevOps project with at least one Test Plan and some test cases.
Permission to install extensions (cloud) or upload to the collection (on-premises).
A modern browser (Edge, Chrome, Firefox).

Permissions requested

TestPulse requests four read scopes and two write scopes. Your Azure DevOps account still needs the rights for each action:

Scope	Why
`vso.work`	Read work items (requirements, bugs).
`vso.test`	Read Test Plans, suites, cases and results.
`vso.test_write`	Coverage Builder and Repository: create plans/suites or add cases to a target; reassignment: change testers/configurations.
`vso.work_write`	Explore: create bugs, cases, tracking Task and attachments; set the Task’s state at closure if requested; report a promotion decision on the host work item if enabled.
`vso.build`, `vso.identity`	Associated build and assignee details.

A report does not modify test results, but its history is saved automatically in Extension Data. Creation, addition and modification features have their own effects. See permissions and the action matrix.

Getting started

Guided workshops

Concepts

Generate a report

Exports

Quality & decision

Cockpit

Dashboard

Coverage Builder

Test Repository

Reports history

Configuration

On the work item

Exploratory testing

Security

Reference

Changelog

Prerequisites

Permissions requested

​Prerequisites

​Permissions requested

Prerequisites

Permissions requested