Errors

When tests fail, the Test Report shows error details with full context. Each failed test shows its errors inline. An error includes:

• Error message — the assertion or exception message
• Stack trace — the full call stack with ANSI colors preserved from the terminal
• Code snippet — when the reporter embeds source files, the viewer shows the relevant lines of code around the failure location

see

Error output retains the original terminal colors. Assertion diffs, syntax highlighting, and framework-specific formatting all render as they would in your terminal.

Errors Tab

Test Report includes an Errors tab that aggregates all unique errors across the report into a summary table.

The table sorts by impacted test count (most common errors first), making it easy to identify systemic issues — like a shared service being down or a common assertion pattern failing across many tests.

Clicking an error filters the report to show only tests with that specific error.

Filtering by Error

Use FQL to search for tests by error text:

$timeout            # tests with "timeout" in the error
$undefined          # tests with "undefined" in the error
$"connection refused" f:api   # connection errors in API test files

Multiple Errors Per Test

A single test can produce multiple errors — for example, when using soft assertions that continue execution after a failure. Test Report displays all errors for the test, not just the first one.

Infrastructure errors that occur outside of a specific test (e.g., during setup or teardown) are shown separately at the Test Report header.