A library for UI snapshot testing of React Native components and screens, comparing pixel data to detect visual regressions.
PixelsCatcher is a testing library for React Native that enables visual regression testing by capturing and comparing UI snapshots. It helps developers ensure their components render correctly across different states and configurations by detecting pixel-level changes.
React Native developers and QA engineers who need to automate visual testing of UI components and screens across Android and iOS platforms.
Developers choose PixelsCatcher for its automated pixel-level comparison, multi-platform support, and seamless CI/CD integration with detailed reporting, reducing manual testing effort.
:eyes: Library for UI snapshot testing of React Native
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Generates JUnit test reports and supports Azure DevOps pipelines with attachment uploads for failed tests, as shown in the CI/CD integration examples and Azure DevOps tasks.
Provides render timing metrics and pixel mismatch counts in console logs, with examples in the log report showing min/max render times and failure analysis.
Waits for InteractionManager to complete and allows manual overrides in componentDidMount, as described in the async handling section and demo WebViewTest.
Supports React Native Navigation and React Navigation via configurable wrappers and getRootElement, with code examples in the README for both libraries.
The README explicitly states physical iOS device testing is not yet supported, limiting comprehensive testing for iOS apps in real-world conditions.
Requires manual generation of APK or iOS app files, separate entry points, and JSON configuration, which can be error-prone and time-consuming, as detailed in the 'Run android' and 'Run iOS' sections.
Integrating with navigation libraries needs additional wrapper code and configuration, such as registerComponent or getRootElement, adding complexity compared to simpler testing tools.