-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
Unit Test Improvements #5087
Unit Test Improvements #5087
Conversation
- Compare how long the unit tests take
- To get unit tests to run
- Remove coverage task - Add --coverage flag to test task
- Should cause migration unit tests to be run
- Should save some time
- Display time taken to load each plugin
@SchrodingersGat has slowtests a sizeable impact? |
- Might remove this entirely? - For now, bypass for unit testing
- Display time taken to load registry
- env var updates - change paths-filter output
- Actually need to set the output
@matmair in summary:
Overall this is a 50% reduction in unit testing time - further improvements can still be made but I suspect with diminishing returns. |
Looks great @SchrodingersGat ! Is there any inherent reason to spilt out the migration tests into a separate file? The job could also be run parallel as a separate job in the main qc.yaml IIRC. |
No inherent reason, I just thought it made sense to keep them distinct. The ci checks file is getting very difficult to understand |
Would you be open to merging the files? Having one QC file makes monitoring and automation easier downstream. |
I'm not opposed to it :) if you submit a PR I'll merge! |
* merge workflows from #5087 * syntax fix
Closes #4821
Not running the migration tests shaves 10 minutes (25%) off the unit testing