feat: implement skip utility function for testing #181
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
I implement a new function to use as testing utility. It skips the test if the provider is not reachable or well provisioned. You have to declare it in your test, so if you depend on Docker and you know you need it just keep doing as you are doing today. In my use case we use testcontainers only for some particular tests, and I do not like the idea to mark the testsuite as `FAILED` if a colleague does not have Docker enabled in their local environment. Worst case if something has to fail CI/CD will tell the truth. Signed-off-by: Gianluca Arbezzano <gianarb92@gmail.com>
gianarb
added
feature
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I implement a new function to use as testing utility.
It skips the test if the provider is not reachable or well provisioned.
You have to declare it in your test, so if you depend on Docker and you
know you need it just keep doing as you are doing today.
In my use case we use testcontainers only for some particular tests, and
I do not like the idea to mark the testsuite as
FAILEDif a colleaguedoes not have Docker enabled in their local environment. Worst case if
something has to fail CI/CD will tell the truth.
Signed-off-by: Gianluca Arbezzano gianarb92@gmail.com