Test your Percy knowledge with a free interactive quiz — 19 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is the review workflow for a Percy build showing visual differences?
Questions in this quiz
What is the review workflow for a Percy build showing visual differences?
What is a Percy "build," and what does it represent?
What is a general trade-off between a cloud-hosted visual testing service like Percy versus a self-hosted tool like BackstopJS?
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 strategy for deciding WHERE in a test suite to add `percySnapshot()` calls, rather than snapshotting after every single test assertion?
What is the relationship between Percy and BrowserStack?
What does "cloud-based rendering" mean in Percy's architecture, and what advantage does it provide over a purely local screenshot-diffing tool?
What is the purpose of the Percy CLI/agent process that typically runs alongside a test execution (e.g. `percy exec -- cypress run`)?
What does Percy do to reduce false-positive visual diffs caused by non-deterministic page content (like a live timestamp or randomized data)?
Why does capturing DOM state rather than a raw pixel screenshot matter for Percy's ability to detect the SAME underlying content change across multiple browser/viewport renders from one snapshot call?
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 the purpose of Percy's integration with CI/CD pipelines (e.g. as a required GitHub status check on pull requests)?