The software testing market has exploded with methodologies, tools, and processes over the last several years. Much of that tooling, however, only revolves around ensuring software works as intended.
58% of our survey respondents utilize some form of software testing.
Visual testing is emerging as a more scalable and practical approach to frontend testing from a visual standpoint.
47% of our survey respondents are currently involved in projects involving visual testing or have in the past.
We’ve also seen a massive acceleration in visual testing adoption in the past two years and foresee that trend to continue.
Visual testing works by comparing UI screenshots against baselines to see if anything has changed. By integrating with your test suite and workflow, visual testing is designed to run on every commit, providing continuous visual feedback and detecting visual changes across browsers and screen sizes.
Visual testing is designed to run alongside your day-to-day workflow. To get consistent and truly automated visual testing, most teams opt to run their tests along with their continuous integration and continuous delivery (CI/CD) processes.
90% of Percy all builds run as part of CI/CD.
When getting started with visual testing, it’s important to think about and plan the level of visual coverage that's feasible and useful to your team. In addition to balancing the depth and breadth of visual coverage, getting the right coverage across browsers and widths is crucial.
Depending on your test suite robustness and size of your app, we recommend balancing the breadth of coverage across your app and depth of their different variations.
While every project is different, Percy projects have an average of 62 snapshots—excluding variations across widths and browsers—per build.