This repository has been archived by the owner on Apr 29, 2021. It is now read-only.
Manage test dependencies #261
Open
Conversation
This file contains 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Very often, tests have pre-requisites. This may be services to be on, packages to be installed, or others. When these pre-requisites are not present, depending tests fail with cryptic messages, generally causing a bunch of errors to be displayed, forcing the user to decrypt that all these errors have the same root cause.
The change proposed here adds a mechanism to check whether one or more previous tests succeeded. The idea is to skip depending tests when one or more pre-requisite tests fail. In such case, you will get only significant failure(s) and avoid a cascade of useless and disturbing error messages.
More details in the README.md file.