From ec771e51fa8632a746b484e35bd2b786ddc7bc6f Mon Sep 17 00:00:00 2001 From: prklm10 Date: Tue, 26 Mar 2024 17:15:56 +0530 Subject: [PATCH] addressing readme comments --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index eed4d5a6..dc328cab 100644 --- a/README.md +++ b/README.md @@ -10,15 +10,15 @@ The benefits of utilizing Percy for visual testing include the following: -- Efficiency: Improves efficiency by reducing the time and effort required to manually spot visual regressions. - Consistency: Promotes consistent user experience by identifying visual discrepancies early in the development process. +- Efficiency: Improves efficiency by reducing the time and effort required to manually spot visual regressions. - Integrations: Percy integrates with popular tools and services like GitHub, GitLab, Bitbucket, and more. - Collaboration: Improves collaboration between developers, designers, and QA teams by providing a visual representation of changes. Prevent regression: Prevents you from experiencing unintended visual regressions. ## How does Percy work? -Percy compares new snapshots against relevant baselines to detect visual changes. Percy manages baseline picking across branches so your tests are always relevant. If visual changes are detected, Percy highlights and groups the resulting diffs for you to review. +Percy compares new snapshots against relevant baselines to detect visual changes. Percy manages baseline selection across branches so your tests are always relevant. If visual changes are detected, Percy highlights and groups the resulting diffs for you to review. # Run your first build with percy [Percy’s sample build tutorial for Storybook.](https://www.browserstack.com/docs/percy/sample-build/storybook)