PHPackages spryker/cypress-tests - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Testing & Quality](/categories/testing) 4. / 5. spryker/cypress-tests ActiveSpryker-test[Testing & Quality](/categories/testing) spryker/cypress-tests ===================== This repository is dedicated to housing an extensive collection of UI end-to-end tests, meticulously crafted using Cypress for Spryker applications. These tests are designed to thoroughly evaluate the user interface, ensuring that all interactions and visual elements function as intended in real-world scenarios. By leveraging Cypress's advanced browser automation capabilities, this suite provides an efficient and effective means of validating the user experience, confirming the seamless operation and aesthetic integrity of Spryker's front-end components. Our commitment to rigorous UI testing helps maintain the high standard of quality and reliability that Spryker users expect. 016.9k↓46.8%[12 PRs](https://github.com/spryker/cypress-tests/pulls)9TypeScriptCI failing Since Sep 24Pushed 1w ago3 watchersCompare [ Source](https://github.com/spryker/cypress-tests)[ Packagist](https://packagist.org/packages/spryker/cypress-tests)[ RSS](/packages/spryker-cypress-tests/feed)WikiDiscussions master Synced 2d ago READMEChangelogDependenciesVersions (113)Used By (9) Description ----------- [](#description) This repository is dedicated to housing an extensive collection of UI end-to-end tests, meticulously crafted using Cypress for Spryker applications. These tests are designed to thoroughly evaluate the user interface, ensuring that all interactions and visual elements function as intended in real-world scenarios. By leveraging Cypress's advanced browser automation capabilities, this suite provides an efficient and effective means of validating the user experience, confirming the seamless operation and aesthetic integrity of Spryker's front-end components. Our commitment to rigorous UI testing helps maintain the high standard of quality and reliability that Spryker users expect. Setup ----- [](#setup) To get started with these tests, follow these setup steps: 1. **Install Dependencies:** - Install all necessary dependencies required for running the tests. ``` npm install ``` 2. **Environment Configuration:** - Set up your environment variables for Cypress. - Copy the `.env.example` file to a new file named `.env`. - Open the `.env` file and fill in the necessary environment variables. - These variables are crucial for Cypress to connect with your Spryker application and perform tests effectively. Running Tests ------------- [](#running-tests) To run the Cypress tests, use the following command: ``` npm run cy:open ``` This command opens the Cypress Test Runner, a powerful interface that allows you to see tests running in real time. Note: to run tests against different demoshops automatically, use [Multi-Store-Runner script](tools/scripts/multi-store-runner/readme.md). Development workflow in the shop (suite-nonsplit or demoshop) ------------------------------------------------------------- [](#development-workflow-in-the-shop-suite-nonsplit-or-demoshop) To use a different branch, modify the project `composer.json` ``` "require-dev": { "spryker/cypress-tests": "dev-YOUR_BRANCH_NAME" } ``` and run `composer update spryker/cypress-tests`, then commit `composer.json` and `composer.lock` files. Troubleshooting --------------- [](#troubleshooting) ### URI malformed [](#uri-malformed) ``` The following error originated from your test code, not from Cypress. > URI malformed When Cypress detects uncaught errors originating from your test code it will automatically fail the current test. Cypress could not associate this error to any specific test. We dynamically generated a new test to display this failure. ``` When you encounter a "URI malformed" error in Cypress, it NOT always indicates that there is an issue with the URL used in your tests. To resolve this error, you can try the following steps: - Ensure "Node.js" version is **22.16.0** or higher. - Ensue "npm" version is **11.6.0** or higher. - If you changed version of Node or npm, delete the `node_modules` folder and reinstall dependencies. (`rm -rf node_modules/ && npm install`) - Clear Cypress App Data following [this guide](https://docs.cypress.io/app/references/troubleshooting#Clear-App-Data). ### Other issues [](#other-issues) If you encounter other issues not described here, refer to the [Troubleshooting](https://docs.cypress.io/app/references/troubleshooting) for common problems and solutions. Test Tagging ------------ [](#test-tagging) When adding a new test or extending the coverage of an existing test - add the tag for the covered feature. The tag should be named the same as the corresponding feature in the Release App. E.g. if you create a new test that touches Marketplace Agent Assist feature, you should add tags `marketplace-agent-assist` and `marketplace-merchantportal-core`. Please see the existing tests for the tag syntax. ### Health Score 39 — LowBetter than 84% of packages Maintenance64 Regular maintenance activity Popularity25 Limited adoption so far Community32 Small or concentrated contributor base Maturity36 Early-stage or recently created project Bus Factor4 4 contributors hold 50%+ of commits How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://avatars.githubusercontent.com/u/10738957?v=4)[Spryker Bot](/maintainers/spryker-bot)[@spryker-bot](https://github.com/spryker-bot) --- Top Contributors [![annakotiuk](https://avatars.githubusercontent.com/u/79214317?v=4)](https://github.com/annakotiuk "annakotiuk (333 commits)")[![dmiseev](https://avatars.githubusercontent.com/u/32021063?v=4)](https://github.com/dmiseev "dmiseev (306 commits)")[![abitskil](https://avatars.githubusercontent.com/u/10989183?v=4)](https://github.com/abitskil "abitskil (154 commits)")[![OKrivtsova](https://avatars.githubusercontent.com/u/50324133?v=4)](https://github.com/OKrivtsova "OKrivtsova (116 commits)")[![asmarovydlo](https://avatars.githubusercontent.com/u/15832795?v=4)](https://github.com/asmarovydlo "asmarovydlo (78 commits)")[![kraal-spryker](https://avatars.githubusercontent.com/u/42177964?v=4)](https://github.com/kraal-spryker "kraal-spryker (73 commits)")[![ilyakubanov](https://avatars.githubusercontent.com/u/45764294?v=4)](https://github.com/ilyakubanov "ilyakubanov (69 commits)")[![olhalivitchuk](https://avatars.githubusercontent.com/u/77281282?v=4)](https://github.com/olhalivitchuk "olhalivitchuk (66 commits)")[![ZakirovDamir](https://avatars.githubusercontent.com/u/17432833?v=4)](https://github.com/ZakirovDamir "ZakirovDamir (56 commits)")[![pyvovarov-s](https://avatars.githubusercontent.com/u/58219818?v=4)](https://github.com/pyvovarov-s "pyvovarov-s (49 commits)")[![supproduction](https://avatars.githubusercontent.com/u/16482929?v=4)](https://github.com/supproduction "supproduction (40 commits)")[![tsybenko](https://avatars.githubusercontent.com/u/24249745?v=4)](https://github.com/tsybenko "tsybenko (38 commits)")[![geronica](https://avatars.githubusercontent.com/u/86779768?v=4)](https://github.com/geronica "geronica (36 commits)")[![aleksandr-velikanov](https://avatars.githubusercontent.com/u/105643831?v=4)](https://github.com/aleksandr-velikanov "aleksandr-velikanov (35 commits)")[![vitaliiShveider](https://avatars.githubusercontent.com/u/95642976?v=4)](https://github.com/vitaliiShveider "vitaliiShveider (25 commits)")[![limeeugenia](https://avatars.githubusercontent.com/u/25685017?v=4)](https://github.com/limeeugenia "limeeugenia (23 commits)")[![mantasmuliar](https://avatars.githubusercontent.com/u/97101411?v=4)](https://github.com/mantasmuliar "mantasmuliar (22 commits)")[![matweew](https://avatars.githubusercontent.com/u/454530?v=4)](https://github.com/matweew "matweew (22 commits)")[![gechetspr](https://avatars.githubusercontent.com/u/42143273?v=4)](https://github.com/gechetspr "gechetspr (21 commits)")[![gerner-spryker](https://avatars.githubusercontent.com/u/30629375?v=4)](https://github.com/gerner-spryker "gerner-spryker (14 commits)") ### Embed Badge ![Health badge](/badges/spryker-cypress-tests/health.svg) ``` [![Health](https://phpackages.com/badges/spryker-cypress-tests/health.svg)](https://phpackages.com/packages/spryker-cypress-tests) ``` ### Alternatives [dms/phpunit-arraysubset-asserts This package provides ArraySubset and related asserts once deprecated in PHPUnit 8 14429.2M361](/packages/dms-phpunit-arraysubset-asserts) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)