vitest.dev / vitest
[READ-ONLY] Mirror of https://github.com/vitest-dev/vitest. Next generation testing framework powered by Vite. vitest.dev
test testing-tools vite
12
Fork 0

Configure Feed

Select the types of activity you want to include in your feed.

docs: add trace viewer screenshot to trace-view guide (#9791)

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

authored by

Hiroshi Ogawa
Claude Opus 4.6 and committed by
GitHub (Mar 5, 2026, 9:59 AM +0100) fc2006e9 3a89a0aa

+3
docs/public/trace-viewer-dark.png

This is a binary file and will not be displayed.

docs/public/trace-viewer-light.png

This is a binary file and will not be displayed.

+3
docs/guide/browser/trace-view.md
··· 111 111 112 112 Alternatively, you can open the Trace Viewer in your browser at https://trace.playwright.dev and upload the trace file there. 113 113 114 + <img alt="Trace Viewer showing the trace timeline and rendered component" img-light src="/trace-viewer-light.png"> 115 + <img alt="Trace Viewer showing the trace timeline and rendered component" img-dark src="/trace-viewer-dark.png"> 116 + 114 117 ## Source Location 115 118 116 119 When you open a trace, you'll notice that Vitest groups browser interactions and links them back to the exact line in your test that triggered them. This happens automatically for: