Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A administrate
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 32
    • Merge requests 32
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thoughtbot, inc.
  • administrate
  • Merge requests
  • !188

Set up visual regression testing with Percy

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Administrator requested to merge percy into master Nov 07, 2015
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 5

Created by: gracewashere

See https://percy.io/

Problem:

For pull requests with UI changes, it can be difficult to tell if the changes affect elements on other pages. It can also be tedious to pull the changes down to a local machine if the contributor has forgotten to add screenshots.

Solution:

Add visual regression snapshots to our test suite with Percy. After we record the inital set of screenshots, future test suite runs will be compared against them to recognize and call out any changes.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: percy