Embedded help still shows an older version
The Documentation page displays the extension version loaded in your tab. After an update, reload the Azure DevOps tab, then reopen TestPulse → Documentation. If the version remains old, ask your administrator to check the version installed in the organisation or collection. On Server, updating requires the approved extension package. Embedded help in 2.74.2 includes eleven practical guides; the online documentation and the extension are updated separately. See the installation guide and release notes.I want to import CSV cases with their suites
From 2.74.0, open Import → CSV test cases. The separate XML choice is for automated results and AUTO reports. CSV can create cases or reuse their IDs, then attach them to existing or new static suites. It does not overwrite existing case steps. See the complete CSV tutorial. After an interruption, keep the local journal and use Verify and resume. Do not clear browser data to bypass an uncertain outcome. Resolving an operation as absent requires your own Azure DevOps check, then an automatic verification before a separate resume action. The CSV journal is distinct from the Extension Data history quota.CSV preview reports TF237111 on an area path
Update to 2.74.2 or later, reload Azure DevOps and review Area path for new test cases in Test plan. The plan’s area is proposed as a starting point, but any populated CSV Area Path takes priority. Your selected suite’s path is not that field. The error identifies the case and area; correct the value or have Edit work items in this node checked on the intended area. Preparing the preview creates nothing and the fix does not grant permissions. See CSV area troubleshooting. You can also search plans by name or ID and static suites by name, full path or ID. Choose the matching result; typing alone does not select a destination.CSV preview preparation returns a 403 in 2.74.0
Version 2.74.1 fixes a service-address defect that could block this step before any creation. After updating, reload the Azure DevOps tab, check the version in Documentation, then review the file and mappings before Prepare preview. Granting more permissions does not fix this routing defect. For an import that already performed writes, preserve its journal and use Verify and resume. See CSV troubleshooting.My report is empty or Generate does not download a file
Generate first displays the report on screen; downloading is a separate export action.- Check the project, plan and included suites.
- Complete missing or invalid fields named by the validation message.
- If the report has cases but no executed tests, check the results in the selected scope. An unexecuted campaign is not a generation failure.
- Once the report is displayed, select PDF. If the button is missing, check export button visibility.
A known bug is missing from my report
First read the Bug source banner. With Bugs from the plan runs, the bug must be attached to a run result in the selected plans and suites; a simple case or requirement link is not enough. Check that association in Azure DevOps, the scope and any warning about the number of runs read, then regenerate the report. Loading an old report keeps its old snapshot. See Bugs of a report.The session Task opens a start form
Check for version 2.73.1 or later, then reload the tracking Task’s Explore tab. This release fixes restoration from the Task. If the message names Explore AI, the session belongs to TestPulse Studio: open that tab. See Session report.The “Test coverage” tab doesn’t appear on a work item
A brand-new contribution can take a short while for Azure DevOps to ingest. Do a cold refresh (Ctrl+Shift+R) on the work item. The tab is auto-placed and mounts on click — see The Test coverage tab.On Server, tests show as “Not Run” even though they passed
Update to the latest version — the plan/suite resolution reads outcomes correctly on Azure DevOps Server.Creating a plan returns a 403
If the message mentions managing plans under an area path, check Manage test plans on that area path. The 403 code alone is not enough to conclude: also have your administrator check extension approval and your rights. See Create the plan.Notifications are blocked on-premises
A browser CORS limit. TestPulse shows the JSON payload so you can copy-paste it into Teams / Slack — see Notifications.The dashboard widget shows old numbers
The widget reads the latest published snapshot, not live data. Publish a fresh report with Share to project — see Quality overview widget.Storage is nearly full
History is bounded by an Extension Data quota. Delete old reports (the storage indicator warns at 80%) — see Report history.A write is refused, with a banner instead of an error
Exploratory sessions write to Azure DevOps — attachments, work items, the archived Task. That capability introduced the work-items write permission, and adding a permission requires a one-time administrator re-approval of the extension. Until an administrator approves it, every write is refused and TestPulse shows an explanatory banner rather than a raw error. Reading is unaffected. See Permissions.I can’t resume a colleague’s active session
TestPulse offers active-session resumption only to its author. The hub offers resume for your session; a colleague’s session only opens the work item. This is a TestPulse resumption rule, not a confidentiality guarantee: session documents live in project-level Extension Data. A closed session can be viewed from its tracking Task. See Privacy.I can’t delete a capture from a session timeline
Three reasons, and the interface names the one that applies. The capture was already sent to a bug, task or test case — removing it would make the timeline disagree with what was actually transmitted. The session is closed: a closed session is a record, and nothing in it is editable. Or the session was started before this capability shipped, so TestPulse can’t establish whether the capture was ever transmitted — it refuses rather than guessing it safe. Note that deleting an entry only removes it from your session. The attachment itself stays in Azure DevOps — TestPulse never deletes anything there.A capture or file is greyed out when I close the session
Its upload couldn’t be resolved, and the reason is shown next to it. TestPulse leaves it visible and greyed rather than dropping it from the list, so you know something didn’t make it rather than discovering the gap later in the report.A session’s verdict doesn’t appear in my report or quality gate
By design. A verdict — Passed, Failed or Blocked — is a tester’s judgement on a session, not a test result. It is counted nowhere: no report indicator, no quality gate, no coverage. It shows in the Explore hub, is filterable there, and is written as a tag on the archived Task for Azure DevOps queries. See Sessions hub.Related
Permissions & scopes
Access and the 403.
Glossary
Key terms.