Reports
Understanding why tests fail is more valuable than knowing that they failed. The Reports page gives you a centralized view of every test execution in your project, so you can trace failures back to root causes, verify fixes, and track overall test health over time.
Report Types
BlinqIO generates different report types depending on how the execution was triggered:
- Run Report: created for manual or local test executions. Contains the standard step-by-step results and screenshots.
- AI Recovery Report: created when a test is executed with AI Recovery enabled. Includes the error message, root cause analysis, and the retraining reason that triggered recovery.
- AI Generation Report: created when AI generates new test steps. Shows the AI-generated steps and their execution results.
Execution Summary
At the top of the Reports page, a summary bar shows high-level metrics for the current project:
- Total Executions: the number of test runs recorded.
- Successful: executions where all scenarios passed.
- Failed: executions where one or more scenarios did not pass.
These counters update based on the active time filter.
Execution Table
The main table lists every execution with the following columns:
| Column | Description |
|---|---|
| Execution Info | Name of the execution and the scenarios it covered |
| Execution Date | When the execution started |
| Execution Type | How it was triggered: manual, scheduled, or CI/CD |
| Status | Pass or Fail |
| Pass Ratio | Percentage of scenarios that passed |
| User | Who initiated the execution |
| Environment | The target environment used for the run |
Filtering Executions
Use the time-range filter above the table to narrow results:
- Last 24 hours: show only today's executions.
- Last week: executions from the past 7 days.
- Last 2 weeks: executions from the past 14 days.
- Show all: display every execution in the project.
Opening a Report
Click any row in the execution table to open the full report. The report header shows:
- Start Time: when the scenario started executing.
- Status: pass or fail.
- Error Message: the error that caused the failure (if applicable).
- Root Cause: the AI-determined reason for the failure (AI Recovery reports only).
- Retraining Reason: why the step was retrained (AI Recovery reports only).
- Duration: how long the scenario took to complete.
- Past Executions: a history of previous runs for the same scenario.
- User Comment: any notes added by the user after reviewing the report.
Step-by-Step Details
Expanding a scenario within a report reveals the granular execution data for each step:
- Screenshots: a capture of the browser at each step, useful for visual verification.
- Console Logs: browser console output recorded during the step.
- Network Logs: HTTP requests and responses captured during the step.
- Errors: any JavaScript or application errors encountered.
- Stacktrace: the full error stacktrace when available.
- Substeps: lower-level actions that make up the step (clicks, inputs, navigations).
TIP
Use the screenshots alongside network logs to quickly correlate UI state with backend responses when debugging failures.