TestPulseExecutive quality reporting for Azure DevOpsAzure DevOps helps you execute tests. TestPulse helps you decide whether you are ready to release. Turn Azure Test Plans into executive-ready reports, defensible release decisions, and audit evidence — in minutes. No server. No external database. No synchronisation. No account. 100% Azure DevOps native. Works with Azure DevOps Services and Azure DevOps Server 2022.1. Available in English and French. Documentation · Free, with no paid tier or trial From test execution to release confidenceAzure Test Plans is excellent for running tests. But before a CAB, steering committee, client handover, or audit, QA teams still need to assemble evidence: results, defects, coverage, screenshots, and a clear release recommendation. TestPulse turns the data already in Azure DevOps into a professional quality narrative — without exporting spreadsheets, formatting slides, or moving test data outside your tenant. In one click, deliver:
Executive-ready reports, without manual formattingSelect your plans and suites, choose an export, and produce a polished report with a cover page, KPIs, charts, per-case detail, attachments, and a signature page. Use PDF, HTML, Word, Excel, or PowerPoint according to the audience. Attachments are part of the report by default: images are embedded, and every other file is listed with a clickable name that opens the evidence in Azure DevOps and a readable type rather than a raw MIME type. A file type we do not recognise still keeps its link. Charts render locally, so nothing leaves your tenant and reporting also works offline. Configure the header label, theme colour, cover logo, signature page, visible export buttons, and section order so every report looks like your organisation — not like a tool.
Make release decisions you can defendPass rate alone is not a release decision. TestPulse gives QA and release leaders a deterministic Quality Score from 0 to 100, an A–E grade, and a clear GO / NO-GO verdict. There is no AI, black box, or hidden weighting: the full calculation is visible on demand, and the same data always produces the same verdict. That makes the decision explainable today and defensible months later. Scoring profiles — Strict, Standard, and Ramp-up — let you adapt the evaluation to your context while keeping sprints comparable. Each carries a pass-rate floor and an execution-rate floor that cannot be compensated by a good score elsewhere, so neither a collapsed campaign nor an unfinished one can come out GO, and a failed test with no defect raised blocks the verdict rather than flattering it. The scale in force and the threshold applied are named on the report itself, so a verdict can be defended months later. Watch points highlight the issues that matter: open blocking bugs, uncovered requirements, and failed tests without a defect raised.
Prove coverage during auditsWhen an auditor, customer, or stakeholder asks what was tested, TestPulse gives you a clear, exportable chain of evidence: Epic → User Story → Test Case → Bug The traceability matrix shows the complete relationship in one table. Requirement coverage distinguishes what is genuinely tested from what merely has a plan. Coverage depth shows whether linked tests actually exercise the substance of a requirement, while requirement drift flags stories changed since their last test run.
Find gaps before they reach productionStart from requirements rather than a plan. Select requirements by ID, area path, iteration, or query, then see which are covered, where the gaps are, and whether linked tests provide meaningful depth. The analysis is read-only and deterministic — no AI. If needed, creating a regression plan is a separate, explicit action.
Put quality signals where teams workEvery user story gets a Test coverage tab directly in Azure DevOps. Teams can see the coverage state, depth analysis, execution verdict, linked tests, and related defects without opening a report or changing tools.
Exploratory testing, properly recordedRun a timeboxed exploratory session from any work item. Capture a charter, notes, screen captures pasted directly into the session, annotations, and new work items — without leaving the session. While a session is still active, correct a note or a capture's caption, or remove an entry you didn't mean to keep — attachments always remain in Azure DevOps, nothing is ever deleted there. Attaching evidence is a gesture you cannot get wrong. The drop zone on the timeline is large and explicit, the whole panel becomes a target while you drag, and a file released beside it is swallowed rather than opened in the tab — your session never leaves the screen. A Browse button is there for anyone who would rather not drag, with no type filter applied. Several files can be attached in one gesture: they upload one after another with a progress line, a note typed meanwhile is kept, and if one file is refused the others stay attached while the message names the one that failed, in Azure DevOps's own words. When you close a session you can also record whether the delivery may move to the next environment stage. Every project starts with a suggested TEST → QUAL → PROD ladder that an administrator renames, reorders or empties under Settings — emptying it disables the feature for the whole project, and choosing a stage when you start a session is optional. The decision is one of OK, Reserved or Blocked, with a comment required for the last two, and it is final once the session is closed. It is written as a queryable tag on the session task, as a coloured band on the session PDF, and — the one place TestPulse writes on a work item it did not create — as a tag and one discussion comment on the work item the session was run from. That write is triggered only by your explicit close with a decision selected, is shown to you in full before you act, touches nothing but tags and the discussion, is disableable project-wide, and is never blocking: an unsaved form or a refused permission skips it, names why, and the session still closes with the decision recorded and exported. Like the verdict, it never counts toward any indicator. When the session closes, TestPulse archives it to a Task linked to the story — with an optional Passed/Failed/Blocked verdict, final once set and never counted in your report's indicators. The Explore hub lists every project session, grouped by work item and filterable by area path, iteration path, campaign, tester, verdict, and period — each session dated to the minute, the most recent first inside a story and any still-open one at the top, with a period filter that includes both of the days you pick, read as calendar days in your own time zone. Sessions can be exported as signed PDFs, carrying your organisation's colour and logo just like your test reports — on Azure DevOps Services and on-premises alike — while an aggregated report covers a complete scope. A session whose tracking task has been deleted stays listed, its dead link replaced by an explicit mention rather than silently dropped. Each session report ends with an Evidence section listing the attachments produced — a register without links in Azure DevOps, clickable in the PDF, where anything no longer attached is flagged rather than left as a dead link. Sessions are never deleted; after a threshold, they are retained as display-only archives.
Reassign a whole campaign without walking the treeAzure DevOps can assign testers on a single suite, but the action does not cascade into child suites — and neither CSV import nor the bulk-edit grid can reach the tester or the configuration at all, because both belong to the test point rather than to the Test Case work item. On a real plan of 172 suites, rotating a tester meant opening up to 172 of them. Bulk reassignment inventories what is actually there — testers and configurations side by side, sorted by volume, with unassigned points as a category of their own — then applies the change in one pass, across a single plan or up to ten at once. Replace one or more values, apply to a whole scope, or apply to a suite and every child suite beneath it. What you reassign towards is not limited to what the scope already carries: any configuration defined in the project can be the destination, including one no point uses yet, and any tester can, resolved against the identities of the organisation rather than kept as typed text. Testers already in the scope are offered without typing. Where a project catalogue or identity search is restricted — it can be, on an on-premises server — the screen says so and falls back to what the scope carries, never to an empty field. Starting another pass takes you back to the first step on a freshly read plan list: the operation just applied made the previous inventory wrong. Nothing is written before a review screen states the points affected, the suites touched, how many already carry an execution result, the cases deliberately skipped, and the exact endpoint that will be called. Changing a tester keeps the point and its result attached; changing a configuration rewrites the test case's assignments and may cost the execution history — the two are never presented as the same mechanism. The operation cannot be undone, says so plainly, and lets you export the prior state first. A partial failure lists every failed point with its cause and replays only those. Built for the QA work beyond the reportTestPulse also gives quality teams the operational capabilities needed to keep their test estate useful over time:
Enterprise-ready by designTestPulse is 100% client-side. Your test data stays in your Azure DevOps tenant:
Requested permissions are deliberately limited to read access for test plans, work items, identities, and builds. Two write permissions are used only after an explicit user action: creating a plan from the Coverage builder, reassigning testers or configurations from the Bulk reassignment tab, or creating or attaching a work item from an exploratory session. Getting started
No account to create. No key to enter. No backend to deploy. Why teams choose TestPulseProfessional management-ready reporting. Deterministic release confidence. Audit-ready traceability. Meaningful requirement coverage. Native Azure DevOps integration. Complete data control. Built by QA engineers for QA, test, and release teams who need to answer one critical question with evidence: Can we release with confidence? Support
Built by AT Conseil. Free, and staying free. |
