A community-driven Cypress testing suite for Magento 2, covering frontend and backend e-commerce workflows.
Magento 2 Cypress Testing Suite is an open-source collection of end-to-end tests built with Cypress for Magento 2 e-commerce platforms. It automates testing of critical store functionalities like user accounts, product searches, shopping cart operations, and checkout processes. The suite helps developers and QA teams ensure store reliability across both Hyvä and Luma themes.
Magento 2 developers, QA engineers, and agencies who need to automate testing for e-commerce storefronts and backend workflows. It's particularly valuable for teams maintaining multiple Magento 2 installations or implementing custom themes.
Developers choose this suite because it provides pre-built, community-vetted tests for common Magento 2 scenarios, saving weeks of test development time. Its focus on revenue-critical workflows and support for both major Magento themes makes it more practical than building tests from scratch.
A community-driven Cypress testing suite for Magento 2
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Includes 69 pre-built tests covering revenue-dependent scenarios like account creation, cart operations, and checkout, prioritizing real-world e-commerce use over 100% coverage.
Provides separate test suites for both Hyvä and Luma themes, allowing teams to validate storefronts across Magento's major frontend options without rewriting tests.
Uses Magento's REST API with admin tokens to set up test data and validate backend processes, ensuring tests can manipulate database state reliably.
Supports cypress-tags to run subsets of tests (e.g., 'hot' vs. 'cold'), enabling faster feedback loops in CI/CD pipelines by focusing on critical paths.
Explicitly requires manual customization for stores without default sample data; tests rely on specific product IDs and selectors that must be adapted, increasing initial setup time.
Lacks inheritance or modular updates; users must copy the entire suite into their project, making it cumbersome to merge upstream changes or maintain custom versions.
Built with assumptions like Single Store Mode, English default language, and specific viewports, which may not align with multilingual or multi-store deployments.
Acknowledges missing tests for features like password reset, order confirmation emails, and backend admin processes, leaving gaps that teams must fill themselves.