✨ Random / parallel testing to speed up testing #1186
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
akutz
force-pushed
the
feature/randomize-and-parallelize-tests
branch
3 times, most recently
from
32f4fa3 to
0ca88f8
Compare
github-actions
bot
added
size/M
akutz
force-pushed
the
feature/randomize-and-parallelize-tests
branch
2 times, most recently
from
3f1bd19 to
c9c16e4
Compare
github-actions
bot
added
size/L
akutz
force-pushed
the
feature/randomize-and-parallelize-tests
branch
4 times, most recently
from
28611c8 to
dcfcc61
Compare
This patch updates VM Op to run its unit/integration tests in a random order, in parallel (using as many processes as there are CPUs). This change reduces the time to test one of the larger packages, ./pkg/providers/vsphere, from 502s to only 88s. The randomization also ensures both the production code and test code is reslient and more decomposed. Finally, if there is a need to maintain ordering, because VM Op uses Ginkgo v2, the Ordered decorator may be utilized. There are examples of this in the code-base already, such as in ./pkg/exit/exit_test.go. Just search the project for `Ordered,` to find such examples, ex.: `grep -r 'Ordered,' * `.
akutz
force-pushed
the
feature/randomize-and-parallelize-tests
branch
from
dcfcc61 to
684682e
Compare
lubronzhan
approved these changes
Sep 18, 2025
Contributor
lubronzhan
left a comment
lubronzhan
left a comment
There was a problem hiding this comment.
Thanks for refactoring! Especially those in snapshot
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do, and why is it needed?
This patch updates VM Op to run its unit/integration tests in a random order, in parallel (using as many processes as there are CPUs).
This change reduces the time to test one of the larger packages, ./pkg/providers/vsphere, from 502s to only 88s.
The randomization also ensures both the production code and test code is reslient and more decomposed.
Finally, if there is a need to maintain ordering, because VM Op uses Ginkgo v2, the Ordered decorator may be utilized. There are examples of this in the code-base already, such as in ./pkg/exit/exit_test.go. Just search the project for
Ordered,to find such examples, ex.:grep -r 'Ordered,' *.Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes
NAAre there any special notes for your reviewer:
Please add a release note if necessary: