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

Investigate e2e with supertest (or equivalent) #14

Open
GuillaumeDeconinck opened this issue Jul 26, 2021 · 0 comments
Open

Investigate e2e with supertest (or equivalent) #14

GuillaumeDeconinck opened this issue Jul 26, 2021 · 0 comments
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Milestone

Comments

@GuillaumeDeconinck
Copy link
Owner

Currently the e2e run as two containers, the API and the tests-runner. The API is the release Docker image (no dev-dependencies). While it's good to test the actual release Docker image, in the long run it can take a long time to bootstrap and execute. Using supertest (or equivalent) might help to speed up the tests.

Of course for the moment, the time taken to run the e2e tests isn't an issue (yet).

The solution might be to have both

  • E2E tests with supertest => faster with more coverage
  • E2E tests like now, but just a few to be sure the API runs correctly (but not checking all the product requirements)
@GuillaumeDeconinck GuillaumeDeconinck added enhancement New feature or request help wanted Extra attention is needed question Further information is requested labels Jul 26, 2021
@GuillaumeDeconinck GuillaumeDeconinck added this to the Future milestone Jul 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant