Replace Ginkgo and Gomega with Testify #111
Merged
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
sergefdrv
force-pushed
the
ginkgo-replacement
branch
3 times, most recently
from
92cb632
to
0805890
Compare
sergefdrv
force-pushed
the
ginkgo-replacement
branch
from
0805890
to
2a7aa27
Compare
Some of the reasons to prefer native Go testing with Testify: - Ginkgo doesn't seem very convenient to use, e.g. running an arbitrary subset of tests - Ginkgo doesn't seem to have native integration with Go's benchmark or fuzz testing facilities Signed-off-by: Sergey Fedorov <sergey.fedorov@protocol.ai>
sergefdrv
force-pushed
the
ginkgo-replacement
branch
from
2a7aa27
to
25fde3f
Compare
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.
Some of the reasons to prefer native Go testing with Testify:
arbitrary subset of tests
or fuzz testing facilities