testing
-
https://github.com/elgentos/magento2-playwright
This project offers an End-to-End testing suite for Magento 2, designed to help identify potential issues in online shops. It utilizes Behavior Driven Development (BDD) principles, Gherkin syntax, and Playwright for clearer test writing and execution. The documentation provides guidance on installation, usage, and contributing to the project.
22101 Jul 2025
-
https://github.com/elgentos/magento2-bdd-e2e-testing-suite
A Playwright End-To-End (E2E) testing suite for Magento 2 that helps you find (potential) issues on your webshop.
Or with more jargon: a Behavior Driven Development (BDD) End-To-End (E2E) testing suite for Magento 2 using Gherkin syntax in JSDoc and Playwright.
21430 Jan 2025
-
https://dev.to/playwright/organizing-playwright-tests-effectively-2hi0
Author note: Not Magento specific, but I found it really useful.
When working with end-to-end (E2E) testing in Playwright, maintaining a clean and scalable test suite is crucial. A well-organized structure not only improves maintainability but also makes it easier to onboard new team members. In this post, we'll cover how to best organize your Playwright tests, from folder structures to using hooks, annotations and tags.
28 Jan 2025
-
https://github.com/EcomDev/magento2-test-essentials
Using mocking frameworks for testing Magento 2 modules is counterproductive as you replicate line by line your actual calls to a magento implementation.
Binding your tests to the details of implementation leads to very fragile test suite that no-one wants to work with afterwards as a small change in underlying code like extraction of the class requires complete rewrite of the test case.
This package solves this problem by providing fake objects for most common operations you might want to interact with core.
41814 Jan 2025
-
https://github.com/ProxiBlue/m2-hyva-playwright
The goal of this project is to create an extensible Playwright testing environment for Magento 2 + Hyva projects. The main focus of this project was to:
- have a base set of Hyva tests, which can be extended / updated by community members without affecting your own site specific tests
- Have a set of sub-tests (site tests) on a private repo that you can layer 'ontop' of the base hyva tests.
120
