Skip to content

feat(tracing): show browser console errors in the trace file - #203

Merged
shossain786 merged 1 commit into
masterfrom
feat/trace-console-errors
Oct 25, 2026
Merged

shossain786 merged 1 commit into
masterfrom
feat/trace-console-errors

Conversation

@shossain786

Copy link
Copy Markdown
Contributor

What & why

Refs #130 (console entries in the trace).

browser.captureConsoleErrors already collects JS errors per test, but the trace file never showed them. A shared trace should include what the browser logged, so this adds a Console Errors section (HTML-escaped, omitted when empty).

Scope

Console errors only, at test level. Per-step console/network entries, locators per step and DOM snapshots are not in this PR.

Verification

  • New test buildHtml_rendersConsoleErrors_escaped failed before the change and passes after; a second test checks the section is omitted when there are none.
  • mvn test: 827 passed, 0 failures.

🤖 Generated with Claude Code

Console errors were already collected per test but never rendered in the
trace. Add a Console Errors section (HTML-escaped), omitted when empty.

Refs #130

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@shossain786
shossain786 merged commit 0c0f2dd into master Oct 25, 2026
2 checks passed
@shossain786
shossain786 deleted the feat/trace-console-errors branch October 25, 2026 02:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant