Skip to main content
TestPulse exports the same report to five formats, each optimised for a different use.
All five formats follow the language selected in the extension — sheet names, column headers and labels included.
Every format shows a suite by its path — CH › SALES › Pre-Payment rather than Pre-Payment. In PDF, Word, HTML and PowerPoint a long path is cut in the middle and keeps its first level and its last two; Excel keeps the full path in its own Suite path column.

​
At a glance

​
PDF — the full report

Settings → PDF section order contains 12 reorderable sections. The suite × configuration grid is an additional option: it is inserted at the results position and has no separate position in that panel. PDF charts accompany the metrics when enabled. The report can contain:
  • Cover page — project info grid, logo (PNG/JPEG/SVG), environment badge
  • Executive summary — the automated verdict, or a per-report custom summary
  • KPI cards — pass rate, execution rate, passed/failed/blocked, bugs of the report (where they come from)
  • Results table — latest outcome per test case; a multi-config matrix when 2–3 configurations are detected
  • Suite × configuration grid — the execution matrix for multi-configuration plans, off by default (enable it in Settings → Report sections); it can appear even when the results table is disabled, but is hidden when no configuration is declared
  • Traceability — Epic → User Story → Test Case → Bug (3-column table, one line per test case with a grouped status) + untraced suites
  • Bugs — the bugs of the report, newest first, with creation date, test cases, state and severity, under a line naming their source
  • Flaky tests — tests with a high outcome-flip rate
  • Charts — pass/fail donut + results-by-suite bar, rendered locally (works offline)
  • Attachments — PNG/JPEG inline; every other file listed in a table with a readable type and its name as a link to the attachment. Shown by default since v2.69.0.
  • Objectives, Entry criteria, Exit criteria — multi-line scoping fields
  • Signature page — configurable signatories with pre-fill and a sign line

​
HTML — standalone & interactive

A single HTML file that you can open locally: no server is needed to display its text and tables. Charts load the Chart.js library from cdn.jsdelivr.net and require permitted network access.
  • Interactive charts (donut + bar) when the library has loaded successfully
  • Clickable Azure DevOps links for work items, bugs and test cases; opening them still requires Azure DevOps access
  • Full results table with outcome badges and suite grouping
  • Traceability matrix and bugs list

​
Word (.docx) — editable

Fully editable in Microsoft Word, with the following main sections depending on their settings and the available data: cover page, KPI metrics, results table, traceability (Test Case → User Story → Epic → Bug), bugs table, and a signature page (if enabled). The suite × configuration grid can also be included — opt-in, same toggle as the PDF (Settings → Report sections). The Objectives, Entry criteria and Exit criteria sections are also included when visible, enabled and filled in.
Word does not include the automatic or custom executive summary, charts or attachments. Use PDF or HTML for the executive summary, and PDF for links to the evidence.

​
Excel (.xlsx) — data

Four worksheets: KPIs, Results (outcome, suite, suite path, date, tester, configuration), Traceability (Test Case → User Story → Epic → Bug), and Bugs (state, severity, priority, assignee, created, test cases — newest first). When the report consolidates several test plans, two more sheets are added: Per plan breakdown (totals, pass rate and execution rate plan by plan) and Quality per plan (verdict, requirement coverage and marked steps per plan, with a consolidated row).

​
PowerPoint (.pptx) — slides

A five-slide presentation: Cover, KPIs, Results, Traceability, Bugs. The Bugs slide lists the 15 most recent bugs.

​
Custom fields and visibility

Additional form fields appear on the PDF cover, in the HTML information section and on the Word cover. They are not included in Excel or PowerPoint. A field’s visibility setting applies to the form and to export sections that honour it. Excel and PowerPoint use their own fixed metadata fields: hiding a field in the form does not guarantee its absence from those files. Check the export before sharing it.

​
Signatures

The signature page is available in PDF and Word exports and is configured in Settings. HTML, Excel and PowerPoint do not carry a signature.

Show or hide export buttons

Control the toolbar.

Generate a report

Build the report first.