From 862041c33dc50b4385adfe9459b7f3e838b8cfd9 Mon Sep 17 00:00:00 2001 From: jonniebigodes Date: Wed, 21 Aug 2024 16:06:30 +0100 Subject: [PATCH] Update src/content/snapshotOptions/ignoring-elements.mdx Co-authored-by: Varun Vachhar --- src/content/snapshotOptions/ignoring-elements.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/snapshotOptions/ignoring-elements.mdx b/src/content/snapshotOptions/ignoring-elements.mdx index 88943cb6..5d39c897 100644 --- a/src/content/snapshotOptions/ignoring-elements.mdx +++ b/src/content/snapshotOptions/ignoring-elements.mdx @@ -58,7 +58,7 @@ export const Default: Story = { ### With E2E -By default, Chromatic's E2E integration runs tests and captures a snapshot at the end of each Playwright or Cypress test; either it passes or fails. However, if you've enabled targeted snapshots with [Playwright](/docs/playwright/targeted-snapshots) or [Cypress](/docs/cypress/targeted-snapshots) to pinpoint visual changes when the test reaches a specific point, you can opt out of the automated snapshotting process by enabling the `disableAutoSnapshot` configuration option. This is useful when capturing snapshots at specific points in your test, such as when a particular element is visible or when a specific action is performed. +By default, Chromatic's Playwright and Cypress integrations run tests and captures a snapshot at the end of each E2E test; either it passes or fails. However, if you've enabled targeted snapshots with [Playwright](/docs/playwright/targeted-snapshots) or [Cypress](/docs/cypress/targeted-snapshots) to pinpoint visual changes when the test reaches a specific point, you can opt out of the automated snapshotting process by enabling the `disableAutoSnapshot` configuration option. This is useful when capturing snapshots at specific points in your test, such as when a particular element is visible or when a specific action is performed. {/* prettier-ignore-start */}