A deprecated utility for regression testing the visual appearance of web pages across multiple browsers.
Gemini is a utility for regression testing the visual appearance of web pages. It captures screenshots of specific elements across different browsers and compares them to reference images to detect visual changes. The tool helps ensure UI consistency and catch unintended visual regressions in web applications.
UI library developers and frontend engineers who need to maintain visual consistency across multiple browsers and versions, particularly those working on large-scale web applications or design systems.
Developers choose Gemini for its ability to test specific UI elements, support for multiple browsers, and features like CSS test coverage and artifact ignoring. Its integration with WebDriver and extensible plugin system make it a flexible tool for visual regression testing workflows.
๐๐๐[DEPRECATED] Use hermione
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports browsers from IE8+ and Opera 12+, which is rare and essential for testing in enterprise or older environments, as highlighted in the README's browser list.
Allows capturing specific page sections rather than full pages, enabling focused visual checks on UI components, which is ideal for design systems and libraries.
Includes box-shadow and outline properties when determining element bounds, ensuring accurate visual comparisons for styled elements without manual adjustments.
Features a plugin architecture that supports add-ons like HTML reporters, allowing customization and integration into diverse workflows, as mentioned in the plugins section.
Depends on external WebDriver servers like Selenium, which requires installing Java and managing browser instances, adding significant initial configuration effort.
Test suites and reference images must be updated manually via CLI commands like `gemini update`, which can be cumbersome in fast-paced development cycles.
Running tests across multiple browsers, especially legacy ones, can be slow and resource-heavy, impacting developer productivity and CI pipeline efficiency.