-
Notifications
You must be signed in to change notification settings - Fork 160
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
tests: make our test suite and CI faster #1378
Comments
Yes, very good point. Before the hackathon, we should
|
another idea would be caching test results across CI runs within a feature branch and then executing only the previously failed tests with every new push: something like:
note the NOTE: this seems a bit hacky and should be tested carefully! |
yet another idea to speed up CI would be to call only the tests of the changed files, e.g., using https://testmon.org/ this could look something like:
|
Currently, we have a great set of tests which take a considerable amount of time for PRs. Potentially we want to mark some more tests as "slow" for the hackathon to ensure faster feedback during development. The goal would be to prioritize core functionality tests for PR validation while allowing more time-intensive tests to run separately at a later stage.
The text was updated successfully, but these errors were encountered: