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.

Sign up for GitHub

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

Jump to bottom

E2E tests setup #20

Open
alexandrudanpop opened this issue Jan 21, 2021 · 1 comment
Open

E2E tests setup #20

alexandrudanpop opened this issue Jan 21, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@alexandrudanpop
Copy link
Contributor

Current situation

We currently have the default Unit / Integration testing setup with the Karma (angular default). This also runs the tests in CI.
We want to decide if we use the default Angular E2E test setup (Protractor) or if we setup E2E tests with Cypress, or another solution?

Expected

  • create the E2E test setup and a few sample tests
  • the E2E tests should spin up the environment with docker-compose and then run the tests. Keycloak and the BE API are not mocked in those tests.
@alexandrudanpop alexandrudanpop added the enhancement New feature or request label Jan 21, 2021
@alexandrudanpop
Copy link
Contributor Author

A better approach would be to have the backend (Keyclaok & Sormas Rest) - on a Dev Server. In this case we don't have to wait a long time until the E2E test setup would spin an environment with all the necessary BE components.

We have a PR demonstrating this here:
#45

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexandrudanpop