Skip to content
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

Enable test shuffle for more robust test suite #3349

Open
rbroggi opened this issue Oct 28, 2021 · 0 comments
Open

Enable test shuffle for more robust test suite #3349

rbroggi opened this issue Oct 28, 2021 · 0 comments

Comments

@rbroggi
Copy link
Contributor

rbroggi commented Oct 28, 2021

Requirement - what kind of business use case are you trying to solve?

Go 1.17 introduced the -shuffle flag to avoid deterministic test execution order. The goal of using -shuffle is to make sure that the test suite is stable and each test is well isolated from the other.

I suggest we introduce -shuffle in the test target

rbroggi added a commit to rbroggi/jaeger that referenced this issue Oct 28, 2021
rbroggi added a commit to rbroggi/jaeger that referenced this issue Oct 28, 2021
rbroggi added a commit to rbroggi/jaeger that referenced this issue Oct 30, 2021
rbroggi added a commit to rbroggi/jaeger that referenced this issue Oct 31, 2021
rbroggi added a commit to rbroggi/jaeger that referenced this issue Oct 31, 2021
yurishkuro pushed a commit that referenced this issue Oct 31, 2021
* Issue #3349 - enable `-shuffle=on` in tests

Signed-off-by: rbroggi <[email protected]>

* fixing test interdependency due to shared global variable (which is written to)

Signed-off-by: rbroggi <[email protected]>

* fixing test interdependency due to shared global variable

Signed-off-by: rbroggi <[email protected]>

* enforcing method immutability

Signed-off-by: rbroggi <[email protected]>

* temporarily disable shuffle

Signed-off-by: rbroggi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant