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-wor
Installs: 14 123
Dependents: 9
Suggesters: 0
Security: 0
Stars: 1
Watchers: 7
Forks: 0
Open Issues: 9
Language:TypeScript
Type:spryker-test
pkg:composer/spryker/cypress-tests
- dev-master
- dev-feature/cc-36444-improve-ci-feedback-time
- dev-bugfix/cc-36499-issues-with-data-import-mp
- dev-bugfix/cc-36488/master-fix-cypress-checkout
- dev-bugfix/cc-36444-make-possible-to-run-dynamic-fixture-in-prod-mode
- dev-feature/frw-11111/master-provided-backoffice-filter
- dev-readme-with-tags-info
- dev-bugfix/cc-36485/master-fix-tests
- dev-feature/paralilaise-cypress-run-in-non-split
- dev-refactoring-for-enabling-tags
- dev-tags-for-tests
- dev-bugfix/cc-36470-fix-fixtures-old
- dev-feature/cc-36278-product-export-merchant-portal
- dev-feature/ssp-1636/master-create-model-with-asset
- dev-bugfix/ssp-1654/ssp-fickery-test
- dev-feature/ssp-1473/master-tests
- dev-feature/ssp-1176/master-asset-attach-widget
- dev-feature/cc-35898-update-bootstrap
- dev-tmp/do_not_merge_FRW-10952
- dev-flaky-test-fix
- dev-feature/ssp-1521/b2b-test
- dev-test-branch
- dev-feature/ssp-1116/master-model-creation
- dev-ssp-master-b2b
- dev-ssp-1333/master-fix-tests
- dev-feature/ssp-595-sf-bo-renaming-translations
- dev-ssp-master-b2b-skip-shipment-env-var
- dev-add-ssp-conditional-execution-env-var
- dev-feature/frw-9814/master-agent-dashboard-making-stable
- dev-feature/ssp-795/master-unify-url-structure
- dev-feature/frw-9814/master-bugifx
- dev-bugfix/ssp-1240/master-fix-cypress-tests-artefacts
- dev-feature/frw-9814/master-introduced-mfa-for-merchant-portal
- dev-bugfix/ssp-901/master-refactor-file-attachment
- dev-bugfix/ssp-1029-dashboard-flickery-test
- dev-feature/dqib-3237/cypress-parallelisation
- dev-bugfix/ssp-9/master-asset-cypress
- dev-feature/ssp-4/b2b-mp
- dev-feature/ssp-4/fix-after-merge
- dev-feature/ssp-4/master-asset-bo
- dev-feature/ssp-4/asset-services
- dev-feature/ssp-484/asset-files-display
- dev-feature/ssp-484/asset-files
- dev-bugfix/cc-35103-flaky-post-deploy-cypress-e2e-test_1
- dev-bugfix/ssp-776/ssp-539-create-relation-between-services-and-assets
- dev-bugfix/supesc-912-missing-cache-bursting-in-backoffice
- dev-bugfix/cc-35506-cancel-amendable-orders
- dev-feature/ssp-3/ssp-335-service-cancel-functionality
- dev-feature/ssp-4/master-ssp-asset-management
- dev-bugfix/ssp-574/download-file-name
- dev-feature/ssp-451/asset-permissions
- dev-feature/ssp-529/asset-detail-page
- dev-bugfix/frw-9435-imported-split-pr
- dev-feature/ssp-445/asset-list-page
- dev-feature/ssp-471/create-asset-claim
- dev-feature/ssp-461/create-asset-sf
- dev-feature/frw-9083/master-update-customer-email-confirmation-test
- dev-bugfix/frw-9924-fixed-ability-to-enable-disable-company-user-accounts-by-privileged-administrators
- dev-bugfix/CC-34804-exception-on-manage-company-roles-tests
- dev-bugfix/cc-34245-bootstrap-dependency-upgrade
- dev-bugfix/supesc-812/customer-invalidated-storage-sync-plugin_1
- dev-bugfix/frw-9007/master-cy-test-for-home-page
- dev-feature/cc-33327-dms-smoke
- dev-feature/cc-34423/dev-product-concrete-table-mp
This package is auto-updated.
Last update: 2025-10-30 17:51:18 UTC
README
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
To get started with these tests, follow these setup steps:
- Install Dependencies:
- Install all necessary dependencies required for running the tests.
npm install
- Environment Configuration:
- Set up your environment variables for Cypress.
- Copy the
.env.examplefile to a new file named.env. - Open the
.envfile and fill in the necessary environment variables. - These variables are crucial for Cypress to connect with your Spryker application and perform tests effectively.
- Copy the
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.
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
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_modulesfolder and reinstall dependencies. (rm -rf node_modules/ && npm install) - Clear Cypress App Data following this guide.
Other issues
If you encounter other issues not described here, refer to the Troubleshooting for common problems and solutions.
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.