Where your data lives
What leaves through exports or notifications
CSV import keeps a local progress journal. Clearing it or changing browsers removes the ability to resume from that journal. A downloaded JSON report remains a file to protect according to its contents; it does not replace the journal and cannot be imported to restore it. This workflow is available from 2.74.0. A PDF, Word document, Excel workbook, HTML or PowerPoint presentation becomes a local file. TestPulse no longer controls its distribution once you share it. For Teams or Slack, a report message contains its title, environment, pass rate, execution rate and bug count. The Test button sends a sample message. The destination is the URL saved in your settings; the content is not sent to a TestPulse server. See Notifications.Telemetry and external services
TestPulse does not include an analytics backend collecting your reports. Product data access uses Azure DevOps, and notifications you trigger use your webhooks. This describes TestPulse; it does not replace the policies of Azure DevOps, Teams, Slack or your browser.Azure DevOps Server
Azure DevOps data is read and saved against your server. Notifications remain outbound browser requests: network policy and CORS can prevent them. TestPulse then offers the payload to copy for manual handling. Local exports remain available.Related
Permissions and scopes
What TestPulse can access.
Action matrix
Reads, saves, creations and modifications.