Skip to main content

Diffy vs Percy

Percy (http://percy.io) is a visual services very tightly connected to your build process. It has a lot of integrations with various testing frameworks and CI systems.

When you create a project in Percy you need to specify what SDK you are using and getting instructions how to set it up.

As you will write actual script you can do screenshots via SDK on various stages of test execution. So it is fairly easy to do things like run screenshots for authenticated user or after certain actions were completed (submitted forms, clicking on different buttons etc.).

 

Feature

Percy

Diffy

Coding required

Yes

No. Simply provide list of URLs and you are good to go

Integration with functional testing frameworks

Yes

No

Take screenshots as authenticated user

Yes. As a part of functional test.

Yes. Via configuration.

Manipulate DOM prior taking screenshots: masking, removing, isolating elements

No

Yes

Image comparison

Pixel perfect

Pixel perfect and custom (recognizes vertical shifts)

Performance

Up to your infrastructure. Percy simply receives images.

Based on Diffy’s infrastructure.

Billing model

Based on number of screenshots you send per month

Based on number of pages all your projects have altogether


 

Even though both platforms aimed to do visual testing they work completely different and serve different purposes. Percy is more for adding visual coverage for your functional tests and Diffy is verifying visuals of your pages in bulk.