Skip to main content
TestPulse is 100% client-side. Reports are built in your browser — there is no backend server, and no data ever leaves your Azure DevOps tenant.

​
Where your data lives

  • Reports & history — saved to Azure DevOps Extension Data (user-scoped; project-scoped only when you share to project). Nothing is sent to a third party.
  • Preferences — stored the same way, or in the browser for UI-only choices (for example the work-item tab’s language).
  • Attachments — images are cached in memory and re-fetched from Azure DevOps when needed; they are stripped from saved history to respect the storage quota.
  • Exploratory sessions — stored at project scope, so that a session started on one screen can be found from another and listed in the hub.
Project scope means exactly that: anyone with access to the project can read any session’s notes and captures, whatever Azure DevOps team they belong to. Team-level segregation does not apply to this storage. The hub’s Tester filter reduces noise; it grants no confidentiality. Keep out of session notes anything you would not put in a work item comment.

​
No telemetry by default

TestPulse does not phone home. There is no analytics backend — the only outbound calls are to your Azure DevOps and, if you configure them, your Teams / Slack webhooks.

​
On-premises

On Azure DevOps Server, everything runs the same way against your server. The only browser limitation is CORS on outbound webhooks — TestPulse falls back to a copy-paste payload (see Notifications).

Permissions & scopes

What TestPulse can access.

Read-only by design

Where it writes, and where it never does.