Skip to main content
Generate a complete test report from an Azure DevOps Test Plan. TestPulse reads your data live — nothing is ever written back.

​
Select a Test Plan

Use the autocomplete dropdown to search plans by name or iteration path. Suites load as a tree — child suites are indented under their parent.
  • Expand all / Collapse all to navigate the tree.
  • Uncheck any suite to exclude it from the report.
  • Plans marked INACTIVE are hidden by default — a toggle reveals them.
  • Exclude empty unchecks every suite with zero test cases in one click (suites that failed to load are never touched). A (N hidden) badge appears next to the suite count, and the preference is remembered.

​
Form fields

All visible fields are required unless configured otherwise in Settings → Field configuration. IT Contact, Business Contact, Tester and Approver use Azure DevOps user autocomplete (type at least 2 characters).
FieldDescription
Report titleName displayed on the cover page.
EnvironmentDEV / QA / UAT / PREPROD / PROD (configurable).
Project referenceProject code or identifier.
Change numberOptional — change reference.
Incident / RequestOptional reference fields next to Change number.
ApplicationName of the tested application.
Functional domainRelevant domain or module.
Tested featuresDescription of the covered features.
Test scopeTesting scope and boundaries.
ObjectivesMulti-line — line breaks are preserved in exports.
Entry criteriaMulti-line — conditions for starting the campaign.
Exit criteriaMulti-line — conditions for stopping the campaign.
TesterPerson who performed the tests (ADO autocomplete).
ApproverPerson approving the report (ADO autocomplete).
Approver roleThe approver’s function.
Report datePre-filled with today’s date.
Associated buildLink an ADO build — autocomplete from recent builds (branch and status shown); a clickable link in PDF, HTML and Word.

​
Validation

Each field can carry a regex pattern (Settings → Field configuration):
  • Blocking — generation is prevented if the field fails validation.
  • Warning — generation continues, with an orange alert.
Validation runs in real time in the form (a red / orange indicator per field) and again at generation time. Soft length — an optional threshold per field. Beyond it, an orange, non-blocking hint appears (“n / threshold — may overflow on the cover page”). It never blocks generation and never truncates the value — it only nudges you toward a readable cover page.
Contacts (IT, Business, Tester, Approver) are Azure DevOps identities, so they carry no regex and no soft length — any stored pattern is ignored. They are grouped under “Contacts & validation”.

​
Next

Cover page

Header label vs report title, and choosing what appears.

Generation & templates

The generate flow, cancel, templates and saved views.