Add code for calculating stable identifiers #13
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
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.
As per #9 one of the things we need for getting the example database working is a way of referencing what "the current test is" to the best of our ability. This is made slightly more problematic by the nature of how we're defining tests and how other people are defining tests - in hypothesis-python it's just the fully qualified name of the test function.
There's pretty much no way to do this other than special casing the test runners AFAICT, and even that isn't straightforward.
This PR also makes explicit that we'll be supporting minitest, though RSpec is definitely the priority.