Test Reporting and Dashboards in PractiTest

PractiTest's reporting system separates into two layers: built-in reports with fixed structures (traceability matrix, test cycle summary), and a dashboard builder where you compose custom views from widgets. Both layers pull from live execution data, so reports reflect the current state without any manual refresh.

Built-In Reports

Access all reports via the Reports tab in your project. The ones most teams use regularly:

Traceability Matrix

Shows the relationship between requirements and test cases, with execution status per test instance. Each row is a requirement, each column is a linked test case, and cells show Pass/Fail/No Run status.

To get value from this report, requirements must be linked to test cases and test cases must have been executed at least once. An unlinked test shows as a gap. A requirement with no linked tests shows as uncovered.

Filter options:

• Release -- scope to tests run against a specific release
• Test Set -- scope to a specific execution cycle
• Environment -- if you tagged test sets with environment fields

Export: top-right export button, choose PDF or Excel. The Excel export includes a full pivot table you can manipulate further.

Test Cycle Summary

Shows an overview of a specific Test Set (test cycle): total instances, how many passed, failed, blocked, and not run. Includes a breakdown by custom field values.

If you added a Component custom field to your tests, this report can show pass/fail rates per component side by side. A checkout component with 40% failure rate stands out immediately when charted next to an auth component at 95% pass.

Open this report from inside a Test Set by clicking Reports > Test Cycle Summary.

Test Progress Over Time

Tracks execution velocity: how many tests were run per day across a test cycle. Useful for sprint planning -- if the team runs 20 tests per day and you have 200 tests left, the math on whether you finish before release is visible without a spreadsheet.

Requirement Coverage Report

Separate from the traceability matrix, this report focuses purely on coverage: what percentage of requirements have at least one linked test case. A requirement with tests but with all instances in No Run status counts as "covered but not executed" -- PractiTest distinguishes between the two.

Building Custom Dashboards

Go to Dashboards (the home icon in the left sidebar). Click New Dashboard. Dashboards are composed from widgets. Each widget is a query against your project data displayed as a chart or table.

Available widget types:

• Pie Chart -- good for test status distribution (pass/fail/blocked)
• Bar Chart -- good for comparisons across components or releases
• Counter -- a single number, e.g. "Total failures today"
• Table -- a mini report embedded in the dashboard
• Gauge -- shows a value against a target threshold

Building a Release Health Dashboard

A practical dashboard for tracking release readiness:

1. Widget 1 -- Overall Status Pie: Filter by current Test Set, group by execution status. Gives an immediate visual of how the run is going.
2. Widget 2 -- Failures by Component: Bar chart filtered to Status = Failed, grouped by the Component custom field. Shows which areas have the most failures.
3. Widget 3 -- Requirement Coverage Counter: Single number showing "% of requirements with passing tests". Set a threshold at 90% -- the gauge turns red below that.
4. Widget 4 -- Open Defects Table: Pull from your defect tracker (Jira if integrated) filtered to defects created from this project in the last 7 days.

Arrange the four widgets in a 2x2 grid. Share the dashboard URL with stakeholders -- it auto-refreshes every 5 minutes.

Exporting Reports

From any report view, click the Export button:

• PDF: formatted for printing or attachment to release notes
• Excel: raw data with filters intact -- useful when stakeholders want to slice the data themselves
• CSV: plain data for piping into other tools

The Excel export from the Traceability Matrix is the most requested one. It exports one row per test case with columns for each requirement linked to it, plus execution status. QA managers paste this directly into release readiness documents.

Scheduling Automated Reports

PractiTest supports scheduled report delivery via email. Go to any report, click Schedule, and configure:

• Recipients: comma-separated email addresses (does not require a PractiTest account)
• Frequency: Daily, Weekly, or specific days
• Time: Hour and timezone
• Format: PDF or Excel

A practical setup: schedule the Test Cycle Summary to send every day at 08:00 to the engineering lead and product manager during active testing sprints. They see the previous day's results in their inbox without logging into PractiTest.

Scheduled reports are scoped to the filter state at the time you set up the schedule. If you want the report to always reflect the latest test set, use a dynamic filter that resolves to "most recently created test set" rather than hardcoding a specific set ID.

Report Performance Considerations

Large projects (10,000+ test cases, years of execution history) can generate slow reports. Two things help:

First, scope reports aggressively with filters. A traceability matrix for all requirements and all tests across all time is expensive. Scoped to the last release and the current test set, it runs in seconds.

Second, use the dashboard widgets for daily monitoring and reserve the full traceability matrix export for release gates. Widgets are backed by cached aggregations and respond faster than on-demand full report generation.

Next Step

Open the Traceability Matrix report after your next test run and export it to Excel. Share it with whoever owns your release sign-off process. The conversation that follows -- "what does 'no run' mean?" "why is this requirement uncovered?" -- is exactly the kind of gap analysis the report is designed to surface.