Knowledge Base

Your go-to hub for product insights, guides, and updates. Our roadmap is shaped by real user feedback and focused on delivering powerful, intuitive, and affordable solutions.

Latest Version
Version 2.39
Latest Update
25 April 2026
  1. Home
  2. >
  3. Reports

Reports

The Reports feature helps teams analyze test case execution, test run results, failure trends, and requirement coverage using visual and tabular reports. Reports provide actionable insights that help teams track quality, identify problem areas, and make data-driven decisions.

Creating a New Report

To create a report, navigate to: Project → Reports → Create Report

This opens the New Report form where you can configure the report type, data source, and filters.

[New Report – Create Report Screen]

Basic Report Information

1. Name

The Name identifies the report. Use a clear and descriptive title that reflects the purpose of the report.

Examples:

  • Test Execution Status by Priority
  • Failure Rate by Test Case
  • Requirement Traceability Matrix
2. Description

Use the Description field to explain what the report represents. This helps other users understand the intent and scope of the report.

Report Output Types

Tuskr supports five report output types, each designed for different analysis needs. You can switch between output types using the Output selector in the report form.

  • Bar
  • Line
  • Pie
  • Tabular
  • Matrix

[Report Output Types – Bar, Pie, Line, Tabular, Matrix]

Bar, Line, and Pie Reports

The Bar, Line, and Pie reports share the same configuration and are used for visual trend and distribution analysis.

[Bar / Line / Pie Report Configuration]

Common Configuration Fields
X-Axis

Select the dimension you want to analyze, such as status, priority, or assignee. This represents the categories or labels in the chart.

Y-Axis

Defines the metric being measured, such as the count of test cases or executions. One or more Y-axis values can be selected depending on the report.

Sort By

Controls how the results are ordered. Example: Largest to Smallest.

Limit

Restricts the number of results shown in the chart. Useful for focusing on top results.

Include Entries with Blank Label

When enabled, records without a value for the selected field are included in the report.

These reports are ideal for:

  • Visualizing execution status trends
  • Tracking distribution of test cases
  • Quickly identifying high-risk areas

Tabular Reports

The Tabular report displays data in a table format, making it suitable for detailed analysis and exporting.

[Tabular Report Configuration]

Tabular-Specific Fields
Table Of

Choose the entity you want to report on, such as Test Cases.

Columns

Select which columns should appear in the table. Columns can be reordered or removed as needed.

Common columns include:

  • Name
  • Key
  • Status
  • Priority
Group By

Group rows based on a selected field. Useful for summarizing large datasets.

Sort By and Sort Order

Control how table rows are ordered.

Tabular reports are useful for:

  • Detailed reviews
  • Sharing structured data
  • Exporting results for external analysis

Matrix Reports

The Matrix report provides a multi-dimensional view of test data and supports two specialized modes.

[Matrix Report Configuration]

1. Test Execution Matrix

[Matrix – Test Execution]

Key Fields
  • Recent Runs: Defines how many recent test runs should be analyzed
  • Failure Threshold: Displays test cases that failed at least the specified number of times

Example use cases:

  • Identifying flaky or unstable test cases
  • Tracking repeatedly failing tests across multiple runs
2. Requirement Traceability Matrix

[Matrix – Requirement Traceability]

Columns
  • References
  • Requirement Key
  • Requirement Name

This matrix helps teams:

  • Verify requirement coverage
  • Identify requirements without test cases
  • Support audit and compliance needs

Failure Rate Report

The Failure Rate Report allows teams to track how often test cases fail over time.

[Failure Rate Configuration]

Failure Threshold

Use the Failure Threshold field to specify how many times a test case must fail to appear in the report.

Example: Show test cases that failed at least 3 times.

This report is especially useful for:

  • Detecting unstable test cases
  • Prioritizing fixes for frequently failing tests
  • Improving overall test reliability

Filters in Reports

All report types support Filters, allowing you to narrow down the data included in the report.

[Report Filters]

Using Filters
  • Add one or more filters based on available fields
  • Combine filters to create highly targeted reports

Examples:

  • Filter by test case priority
  • Filter by execution status
  • Filter by requirement or tag

Filters help ensure reports display only the most relevant data for your analysis.

Saving and Using Reports

  • Click Save to create the report
  • The report becomes available in the Reports section
  • Reports can be reused, reviewed, and updated as project data evolves