Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add info on multiple screenshots in trace #589

Merged
merged 1 commit into from
Oct 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions src/content/snapshot/troubleshooting-snapshots.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,13 @@ Once you rerun a build, the subsequent build will feature a "Traces" column. Thi

![Build 2 was a rerun build so it has an additional "traces" column](../../images/view-trace.png)

<details>
<summary>Why does the Trace Viewer indicate that Chromatic captured multiple screenshots for a test?</summary>

During the capture process, Chromatic continually takes screenshots until it either reaches the maximum allowed timeout or it captures two matching screenshots, indicating that the page has settled. This ensures the snapshot is consistent and that UI is in its final state.

</details>

### How to use the snapshot trace?

Chromatic uses Playwright to render and capture snapshots in its [Capture Cloud](/docs/infrastructure-release-notes), even if your tests are written using Cypress or Storybook. Therefore, it's able to leverage Playwright's [built-in capability](https://playwright.dev/docs/trace-viewer#network) to generate these traces. These traces capture network activity, console logs, DOM snapshots, and other debugging information.
Expand Down
Loading