BlinqIO Reports
The Reports page displays a list of executions, where each execution represents a full test session. This is different from viewing individual test runs—multiple test cases and example rows can be part of a single execution.
Test Execution Overview
The Reports page lists executions in the form of runs, where each run provides the following details:
Execution Date: The date and time when the test execution occurred.
Run Type: This indicates the type of run, such as Local execution or Local AI generation.
Status: Whether the run was successful (Passed) or failed (Failed).
Pass Ratio: Shows the number of passed tests versus the total number of tests.
Executed By: The user who triggered or initiated the test execution.
Environment: The environment in which the test was executed, typically represented as an environment URL or name.
A search bar is available to help quickly locate a specific run.
Viewing Detailed Run Reports
Click on a run entry to access the detailed report. Inside each report, you will find scenarios related to that particular execution. For each scenario, the following information is available:
- Start Time: The exact time the scenario started.
- Status: The outcome of the scenario (e.g., Passed, Failed).
- Error Message: If the scenario failed, the specific error message will be displayed.
- Root Cause: An analysis of why the test failed.
- Retraining Reason: If the failure was fixed by AI, the reason for retraining will be shown.
- Duration: The total time taken for the scenario to execute.
- Past Executions: Displays a history of the last 5 runs, with a color-coded status. Green represents a passed run, while red indicates a failed one.
- User Comment: Option to add a comment for the scenario to document insights or observations.
Each scenario section also includes all steps and substeps executed during that run, providing detailed information for analysis.
Scenario Step Details
Each scenario's steps and substeps are fully detailed, including:
- Screenshots: Visual evidence captured during each step.
- Console Logs: Logs from the application's console during test execution.
- Network Logs: Information about network requests and responses during the test.
- Errors: Any errors encountered during the execution, with specific messages and stack traces if available.
You can also view full network logs.
This comprehensive breakdown of steps, along with detailed logs and screenshots, ensures that users can easily troubleshoot issues and gain full visibility into their tests.