-
Notifications
You must be signed in to change notification settings - Fork 605
Improve the coverage of the e2e test suite #2069
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
Conversation
| pytest -v test/e2e/tests --env aws --skip-autoscaling --skip-load --skip-long-running | ||
| pytest -v test/e2e/tests --env aws -k test_autoscaling | ||
| pytest -v test/e2e/tests --env aws -k test_load |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can be summed up to a single command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be ideal - and it is possible, but we'd have to create dependencies (within pytest) between the single-request tests and the load/autoscaling tests. There's no point in letting a load test run if the single-request test failed. I saw this plugin https://pytest-dependency.readthedocs.io/en/stable/usage.html that we could use, but from what I read, this only works for tests that sit in the same module.
The simplest next thing is to just create these "dependencies" by separating the pytest command into multiple ones.
checklist:
make testandmake lint