Console logs

BugBug can capture browser console logs during test execution, both in local and cloud runs. This helps you diagnose JavaScript errors, warnings, and custom log messages without leaving the test results view.

---

Enabling console logs

Console logs are disabled by default. To turn them on, go to Project Settings and find the Console logs section.

Three modes are available:

• Disabled - No logs are collected. This is the default setting.

• Console logs - Collects browser console logs for each test run. Logs are then available in Runs history.

• Full BugBug debugging - Collects extended internal BugBug logs. Use this only if you encountered a BugBug problem and want to help the support team debug it — not intended for everyday use.

Enabling console logs can slow down (or even break) your tests if your application generates a large volume of logs.

---

How to access console logs

Console logs are available for any completed test run (local or cloud) when collection is enabled.

Option 1 — from the test run view

1. Go to the Runs history

2. Click on the test run to open its details

3. Click the Logs button at the top of the page (next to "Go to test")

Option 2 — from Artifacts

1. Go to the Runs history

2. Click on the test run to open its details

3. Click Details on the test run

4. In the Artifacts section, click Download test run logs

Sometimes you have to wait a few seconds after test execution to catch and present logs in the UI