Initial support for unit tests #201
Merged
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
|
Great idea, thanks! I enabled oletools in Travis CI, so it should work. |
Closed
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've added an initial support for unit tests and my sample test case was for #185.
The initial idea is to add test cases as the bugs are fixed to prevent regressions, but this can be further extended to some test first-like approach for new implementations.
Currently the tests run on Python 2.x only, so we still need to add support for v3.
I have also added Travis CI integration and its status badge to the README page. Currently the badge points at my fork, but if this is accepted I can change it before it gets merged (and @decalage2 also needs to authorize Travis on this repo).