Deep Dive Reporting and Analytics

BesTest reporting goes beyond pass/fail counts to answer the questions stakeholders actually ask: are we ready to release, and where is the biggest risk? Every report can be previewed with sample data before you run it, then scoped to a cycle or campaign, a date range, or a folder of requirements.

Test Execution Results shows the outcome of a set of cycles, with defects and execution progress, and comes as a printable list too. Actual vs. Planned Estimation compares reported execution time with planned time and projects a completion date. Defect Analysis plots the Jira defects created and resolved over time. Execution trends, scorecards by tester and top failing tests are also available as Jira dashboard gadgets.

On the requirements side, the Requirements Traceability Matrix flags risky requirements - not tested well enough for their significance, or connected to unresolved bugs. Coverage uses the same Covered / Partly covered / Not covered value everywhere, so the report, the catalog and the gadgets never disagree. The Work Item Traceability report points the same view at a single Jira work item: give it an epic, story or release and it rolls up every linked requirement (and their children), their test cases, latest results and open defects into a calculated risk level. The same readiness summary sits on the work item itself, in the BesTest panel.

When it is time to present, export the report to PDF - no spreadsheets to compile and no metrics to calculate by hand.

Coming soon: advanced reporting. Data sets over your requirements, test cases, cycles and executions, and custom reports built on them - for the questions the ready-made reports do not answer yet.