-
Notifications
You must be signed in to change notification settings - Fork 50
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
Mint - Run subsequent system tests even if a test fails #325
Comments
Also refering to a discussion in slack: https://minio.slack.com/archives/C3NDUB8UA/p1615891367010200 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 15 days if no further activity occurs. Thank you for your contributions. |
There are still some open PRs related to this issue. -> minio/minio-go#1475 And a change in minio-java that needs to be reverted: 721525f We will rebase those PRs and add a new one for minio-java. |
The two PRs are now up to date: The change in the minio-java call (721525f) does not need to be reverted. |
Is your feature request related to a problem? Please describe.
Whenever the Mint test suite is executed, a single failing test in minio-java or minio-go causes all the remaining tests from the same "test package" to be skipped. The disadvantage is, that you don't see all failing tests but only the first failing test (at least in minio-java and minio-go tests). Ok the advantage is, that you don't need to run the whole test suite to see if "something" is broken.
Describe the solution you'd like
We suggest to introduce an optional runtime variable RUN_ON_FAIL.
By setting the variable
RUN_ON_FAIL=1
all tests from all packages should be executed even if a preceeding tests is failing.Describe alternatives you've considered
Changing the default behavior to ALWAYS run every test independent of failing tests.
This would change the default behavior of the Mint test suite.
Additional context
We implemented this feature for minio-go and minio-java and we will create appropriate PRs and link them to this issue, so that there is a single place for discussions for this.
The text was updated successfully, but these errors were encountered: