fix issue 61: test coverage #74
Open
Conversation
This file contains hidden or 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
...fail noisily if a REST-API-v2-like client class tries to use entity wrapping without explicitly implementing all the essential parts of it. This change also includes a truing-up of these essential-to-implement base class properties so that the new integration API clients don't get errors.
Deconstrained
force-pushed
the
61-test-coverage
branch
from
802be29 to
96f9fff
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 ensures every module has its own tests and that abstract / base classes have dummy classes to test with.
TODO
unittest.mock.patchfordatetime.datetime.now(the assumption that it is immutable is wrong and we could eliminate the epsilon or make it far smaller, and create some static assertions)