Applitools vs Percy: What are the differences?

Introduction

In the world of automated visual testing, Applitools and Percy are two popular tools that help teams ensure the visual quality of their web applications. While both tools serve similar purposes, there are key differences between Applitools and Percy that set them apart.

1. Test Execution Approach:

   • Applitools follows a traditional test execution approach, where test scripts are written in programming languages such as Java, Python, or JavaScript. These scripts interact with the Applitools SDK to capture and compare screenshots, validating the visual correctness of the application.
   • Percy, on the other hand, adopts a declarative approach. Instead of writing test scripts, developers integrate Percy into their existing testing framework (e.g., Jest, Cypress, etc.). Percy automatically captures and compares snapshots of the application's visual state during tests, without requiring developers to explicitly interact with the SDK.

2. Integration Options:

   • Applitools offers a wide range of integrations and plugins, allowing users to seamlessly integrate visual testing into their preferred testing frameworks and CI/CD pipelines. This flexibility enables teams to incorporate visual testing at various stages of the development lifecycle effortlessly.
   • Percy also provides integrations with popular testing frameworks and CI/CD tools, but its range of integrations is relatively more limited compared to Applitools. However, Percy focuses on providing deep integration with specific testing frameworks, such as Cypress, making it an ideal choice for teams heavily reliant on a specific framework.

3. Visual Baselines Management:

   • Applitools employs a centralized approach to manage visual baselines. The visual baselines, which define the expected visual appearance of the application, are stored in the Applitools cloud. This centralized management allows teams to easily update or manage the baselines.
   • Percy takes a decentralized approach to baseline management. Each snapshot taken during the test is stored locally, allowing teams to manage baselines directly from their code repositories. This approach gives developers more control over their baselines, with the ability to review and approve changes through pull requests.

4. AI-Powered Visual Testing (Applitools specific):

   • Applitools leverages AI and machine learning algorithms to enhance visual testing capabilities. Its "Applitools Eyes" feature uses sophisticated AI algorithms to automatically detect and ignore dynamic visual elements, reducing false positives and providing more reliable test results.

5. Pricing Model:

   • Applitools operates on a commercial pricing model, where users pay for the number of tests executed and the types of services required. This model gives teams more flexibility in terms of scaling their visual testing efforts, as they only pay for what they use.
   • Percy offers both free and paid pricing plans. The free plan includes basic functionality for small teams, while the paid plans offer additional features and scalability for larger projects. This pricing approach works well for teams on a tight budget or those looking to try out visual testing without financial commitments.

In summary, Applitools and Percy differ in their test execution approach, integration options, visual baselines management, AI-powered visual testing capabilities (Applitools specific), and pricing models. Applitools provides more traditional test execution and rich integration options with AI-powered testing, while Percy takes a declarative approach with deep integration into specific frameworks. The choice between these tools depends on the team's testing needs, preferred frameworks, and budget considerations.