Skip to content
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

Open
simrin051 opened this issue Sep 25, 2021 · 4 comments
Open

Test Cases for the components #62

simrin051 opened this issue Sep 25, 2021 · 4 comments

Comments

@simrin051
Copy link
Contributor

No description provided.

@simrin051
Copy link
Contributor Author

simrin051 commented Nov 1, 2021

@arey / @vfedoriv

Is it recommended to write test cases for form validation. Can you please advice.

@Holger-Mayer
Copy link
Contributor

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:

  • Gherkin - feature descriptions

  • step definition glue code in js (later maybe ts)

  • page objects and support code in js

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?

  • easily readable test description

  • Users can reuse Gherkin test feature descriptions (with adaptations) in other test project platforms, such as Rest on a Java environment for API-Tests using Karate test automation.

@arey
Copy link
Member

arey commented Aug 31, 2024

@Holger-Mayer I've been hearing a lot about Playwright recently. But Cypress remains a safe bet.
Using Gherkin is a good idea. We could use it for testing the REST API.

@Holger-Mayer
Copy link
Contributor

Antoine,

The Gherkin feature files should be reusable.
Besides an import for Gherkin the Cucumber glue code is independent from the test tool.
Page objects and support functions are filled with cypress functions, but with some refactoring and introduction of a test tool independent layer it should be possible to prepare a test suite that is easy to port from one test tool to another as long as it is Javascript/Typescript based.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants