Percy Common FAQs

Troubleshoot issues you encounter when using Percy with SDKs.

Percy is a visual testing platform that helps teams catch UI bugs. It streamlines the testing workflow by automatically capturing and comparing visual snapshots of web applications, ensuring consistent and pixel-perfect user interfaces across various environments and code changes. This page contains information on common issues, warnings, and troubleshoot method for various Percy SDKs. If you don’t find the issue you are looking for listed on this page, feel free to contact us.

Common issues

• Asset(s) never requested by asset discovery
• Assets not captured
• Assets only accessible locally
• Asset discovery timeout after 30 seconds
• Canvas elements not captured/bad state
• Videos & poster’s
• iframe content not captured (CORS)
• Unsuccessful capture of responsive DOM snapshots
• Invalid HTML
• Bad character encoding
• Chromium failed to launch browser
• Screenshots do not capture the full page
• Broken lazy loading images
• Configuring Proxy Requests
• Disallowing requests
• Disable the automatic sending of logs to Percy
• Browser upgrade issues
• Browser compatibility and maximum page height
• The webpage is not loading icon assets

Common warnings

• Fix percyCSS for invalid DOM

Troubleshooting specific SDKs

• Troubleshoot - Ember
• Troubleshoot - Capybara
• Troubleshoot - Cypress
• Troubleshoot - TestCafe

Common issues with Percy On Automate

• Handling CSP on website before running percyScreenshot

Limitations

• Support for websites with horizontal scrolling
• Support for websites with scrollable divs