What are Console Logs?
Console Logs capture every message that the browser produces during a test run, including console.log, console.error, console.warn, and other console output.
Thunders automatically records these logs with timestamps during test execution and stores them so you can download them later from the Test Run Report toolbar.
This is especially useful for debugging failures that don’t produce a visible UI bug but leave traces in the browser console.
When to use it
Debug a failing test where the screenshot alone doesn’t explain what went wrong.
Investigate JavaScript errors or warnings that occur during execution.
Verify API responses logged to the console by the application under test.
Share logs with developers to help them reproduce and fix issues faster.
How Console Logs are collected
During every test execution, Thunders subscribes to the browser’s console events. Each message is captured with:
Timestamp — when the message was emitted.
Type — the console method used (e.g.
log,error,warning).Text — the full message content.
At the end of the run, all collected entries are uploaded to storage as a console-logs.txt file.
How to download Console Logs
Open a completed Test Run Report.
In the toolbar at the top of the report, locate the Console Logs button (it has a download icon).
Click the button.
The file
console-logs.txtwill be downloaded to your machine.
What the downloaded file looks like
The file is a plain-text .txt file. Each line follows this format:
[2026-01-15T10:32:45.123Z] [log] User login successful
[2026-01-15T10:32:46.456Z] [error] Failed to fetch /api/dashboard: 500 Internal Server Error
[2026-01-15T10:32:47.789Z] [warning] Deprecation notice: use v2 endpoint
Good to know
Console logs are collected for all test runs, not only failed ones.
Logs are stored per test run, so each run has its own independent file.