Skip to main content
TestPulse builds reports and analyses in your browser, using Azure DevOps reads. Calculating a score does not modify your test results. Some features do create or change objects, and the extension automatically saves working data. Distinguish Azure DevOps business data — plans, suites, points, work items and attachments — from TestPulse data stored in Azure DevOps Extension Data. “Read-only” for the former does not mean “no saves” for the latter.

Action matrix

Writes to existing objects

CSV test-case import, available from 2.74.0, adds cases to static suites. It publishes no execution result and does not replace the steps of reused IDs. Its JSON report is not an undo mechanism: after an interruption, keep the journal and verify before resuming. Generation from Repository can add cases to an existing shared structure. Bulk reassignment changes testers or configurations. A promotion decision can add a tag and comment to the host work item. These actions have different effects: check the target and preview of the action you use.
Bulk reassignment has no undo command. Changing a configuration can cause Azure DevOps to recreate a point and lose its associated result. The preview lets you exclude points that were already run. Export the previous state as CSV before applying if you need a record.

Automatic saving and sharing

History, Cockpit snapshots and Explore sessions explain why TestPulse can write to Extension Data without asking you to confirm every save. This storage belongs to Azure DevOps; it does not create a TestPulse backend. Its scope varies: personal history per user, shared reports and several settings at project level. See Privacy and data. There is no TestPulse service generating reports while your browser is closed: scheduled reports are reminders displayed when you open the extension.

Data leaving Azure DevOps

No TestPulse backend receives your reports. That does not mean data cannot leave Azure DevOps: exports become local files, and Test or Notify sends a message to your chosen webhook. Any subsequent sharing of those files and the channel’s recipients depend on your choices.

Permissions and scopes

The six scopes and the rights to check.

Privacy and data

Storage, visibility and outbound data.