tests(e2e): vendor Elgentos Playwright E2E test suite

[digitalrisedorset]

This PR adds a browser-based Playwright E2E test suite under dev/tests/e2e for Mage-OS (Hyvä), preserving the upstream Elgentos inheritance model and providing runnable user-journey tests without introducing CI enforcement.

• Adds E2E tests only — no production or framework code is changed
• Does not introduce CI enforcement or gating
• Does not replace or modify existing integration or legacy test suites
• Keeps the test structure aligned with upstream Elgentos to allow future updates

Description (*)

This PR adds the Elgentos Playwright End-to-End (E2E) test suite under dev/tests/e2e,
adapted for Mage-OS and the Hyvä storefront.

The suite includes both the shared base-tests and Mage-OS–specific tests,
preserving the upstream inheritance and extension model used by Elgentos.

The result is a complete, runnable, browser-based E2E test setup for Mage-OS
that validates real user journeys against a live storefront.

This change is intentionally additive and does not introduce CI enforcement.

Related Pull Requests

N/A

Fixed Issues (if relevant)

N/A

Manual testing scenarios (*)

1. Tests can be executed locally via Playwright from dev/tests/e2e
2. The suite supports a two-phase execution model:
   • setup phase (shared browser state)
   • execution phase (user journey validation)
3. Verified locally against a Mage-OS + Hyvä setup

Questions or comments

N/A

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any require an update
• All automated tests passed successfully (all builds are green)

[rhoerr]

Thanks Herve. Not having looked to compare yet, how close of a match is this to the Elgentos suite?

[digitalrisedorset]

Thanks Herve. Not having looked to compare yet, how close of a match is this to the Elgentos suite?

Hi Ryan, I copy the PR i made to Elgentos' team for you to see the differences. elgentos/magento2-playwright#209 (comment)

[digitalrisedorset]

this file (renamed to .env) is required to run the e2e test suite: the data should point to the test Magento url. I do not know what this url is?

Assuming the demo url may be https://mageos.demo.co.uk/, the below is a possible content:
PLAYWRIGHT_BASE_URL=https://mageos.demo.co.uk/
PLAYWRIGHT_PRODUCTION_URL=https://mageos.demo.co.uk/
PLAYWRIGHT_REVIEW_URL=
MAGENTO_ADMIN_SLUG=admin
MAGENTO_ADMIN_USERNAME=admin
MAGENTO_ADMIN_PASSWORD=P1ssw0rd
MAGENTO_THEME_LOCALE=en_US
MAGENTO_NEW_ACCOUNT_PASSWORD=NewTest1234!
MAGENTO_EXISTING_ACCOUNT_EMAIL_CHROMIUM=test-user@magsite.co.uk
MAGENTO_EXISTING_ACCOUNT_EMAIL_FIREFOX=test-user@magsite.co.uk
MAGENTO_EXISTING_ACCOUNT_EMAIL_WEBKIT=test-user@magsite.co.uk
MAGENTO_EXISTING_ACCOUNT_PASSWORD=TestPassword123!
MAGENTO_EXISTING_ACCOUNT_CHANGED_PASSWORD=Test2Password123!
MAGENTO_COUPON_CODE_CHROMIUM=H20
MAGENTO_COUPON_CODE_FIREFOX=H20
MAGENTO_COUPON_CODE_WEBKIT=H20

[rhoerr]

We'll need something to integrate it with the github-action at https://github.com/mage-os/github-actions/pull/313/changes -- the action should provide the access URL to the instance or test runner. CC @michielgerritsen

[digitalrisedorset]

Happy to pair on this @michielgerritsen if helpful.