WIP: Implement Bigtable conformance tests #20
Closed
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
There are two main reasons for this: 1. to enable integration & conformance tests to be run separately 2. to benefit from faster test compilation by reducing the number of crates we're compiling
jneem
force-pushed
the
bigtable/conformance-tests
branch
from
fefe29b
to
6ea406b
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.
This PR implements the Bigtable conformance tests from googleapis/conformance-tests. The implementation is mostly ported from Google's Go implementation here.
These tests currently fail, but I wanted to have the draft PR open to make the progress visible (& so that others can pick up the work if they want to).