-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test Cases for the components #62
Comments
The currently included e2e test automation tool Protractor reached end-of-life in August 2023. I am currently working on integrating a Cypress/Cucumber test suite as a test automation tool into the project. Step one will be form validation tests only. Once these tests are running well (after a verified pull request), it will be easy to enhance this test suite for more complex e2e tests. The test suite will live under e2e/cypress with added configuration changes in package.json and tsconfig.json and an additional cypress.config.ts in the project’s root directory. The test suite comprises:
There are several node modules for the dev environment to install. A detailed installation description will be part of the pull request (probably next week). Why Cypress? free to use common test automation tool You can use it for E2E, component, and API tests. JavaScript/Typescript as test language Why Cucumber extension?
|
@Holger-Mayer I've been hearing a lot about Playwright recently. But Cypress remains a safe bet. |
Antoine, The Gherkin feature files should be reusable. |
No description provided.
The text was updated successfully, but these errors were encountered: