A self-hosted screenshot testing service that integrates with Android, iOS, and Web tests to track visual changes and notify teams.
Screenshotbot is an open-source screenshot testing service that integrates with existing Android, iOS, and web test suites to track visual changes over time. It automatically notifies teams of screenshot differences via pull requests, Jira, Slack, and other platforms, helping catch unintended UI regressions early in development.
Development and QA teams working on Android, iOS, or web applications who need automated visual regression testing as part of their CI/CD pipeline.
Developers choose Screenshotbot for its self-hostability, extensive platform integrations, and hot-reload configuration, offering full control over their visual testing workflow without relying on third-party SaaS services.
A Screenshot Testing service to tie with your existing Android, iOS and Web screenshot tests
Integrates with multiple VCS platforms (GitHub, GitLab, Phabricator, etc.) and notification channels like Slack and email, enabling seamless workflow incorporation directly from the README.
Allows live updates to settings via a Common Lisp config file without downtime, providing flexibility and control for site-admins as highlighted in the configuration section.
Offers full ownership over the visual testing pipeline as an open-source solution, deployable on-premises or in the cloud, aligning with the value proposition of avoiding third-party SaaS.
Supports various SSO methods including built-in email/password, OpenID Connect, and Google OAuth, catering to enterprise security needs without extra plugins.
Key integrations like Jira and Trello are only planned or not supported on some Lisp implementations (e.g., SBCL lacks Java support), limiting immediate usability compared to the commercial version.
Site-admin settings require writing and maintaining Common Lisp code in config.lisp, which can be a significant barrier for teams without Lisp expertise or desire for code-driven setup.
The CLI tool binaries can exceed 100MB in size (e.g., 105MB for SBCL), making distribution and CI/CD integration potentially cumbersome and resource-intensive.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.