Split the integration tests into "fast" and "slow" sets #1554
Labels
enhancement
New feature or request
infrastructure
Relates to infrastructure around Fury
minor
An annoyance, but not serious
testing
Relates to testing and testability
Projects
Milestone
Some integration tests are decidedly slower than others. As far as I know, slowness is mostly caused by compilation (especially if external layers are involved) and also by importing of said layers, but the certain way to check that is inspecting the timestamps in the CI logs.
I think the tests should be split into two sets: the fast ones (those that take less than 10 seconds in CI) and the slow ones. The CI runner should start the slow set after the fast set passes.
There should also be a single command to run all the sets (fast, slow, and pending) in succession.
The text was updated successfully, but these errors were encountered: