Test your Percy knowledge with a free interactive quiz — 19 questions with answers and explanations. No signup needed to play.
Question 1/12Score 0
Why might a team specifically add Percy on top of an already-existing Cypress/Playwright end-to-end test suite, rather than relying on those functional tests alone?
In this round
Why might a team specifically add Percy on top of an already-existing Cypress/Playwright end-to-end test suite, rather than relying on those functional tests alone?
What does it mean for Percy to support snapshotting "component-level" UI (e.g. via Storybook integration) in addition to full application pages?
What is a general trade-off between a cloud-hosted visual testing service like Percy versus a self-hosted tool like BackstopJS?
What is a practical reason a team might configure Percy to ignore/mask certain regions of a page (e.g. via a CSS selector) rather than fixing the underlying non-determinism directly?
What is the purpose of Percy's integration with CI/CD pipelines (e.g. as a required GitHub status check on pull requests)?
What is a Percy "build," and what does it represent?
What does "cloud-based rendering" mean in Percy's architecture, and what advantage does it provide over a purely local screenshot-diffing tool?
What does Percy typically capture as the "snapshot" data at the moment `percySnapshot()` is called — is it a literal screenshot taken by the local browser?
What is a reasonable way to think about Percy's pricing model implication (typically usage/snapshot-based) when deciding how aggressively to add visual test coverage?
What does Percy do to reduce false-positive visual diffs caused by non-deterministic page content (like a live timestamp or randomized data)?
What is the relationship between Percy and BrowserStack?
How does Percy typically integrate with an existing test suite, e.g. using Cypress?