Implementing Nose2 tests #44
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
…ell as examples for input and output tests
|
Note that this is just a beginning. I'll continue development on this branch, until I'm satisfied. |
|
The |
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 begun with the implementation of Nose2 tests. Nose2 is the successor of Nose, which is no longer maintained. The tests are far from complete. My goal is eventually to implement tests for all inputs, filters, and outputs which are used by NLExtract. Also the framework should have sufficient coverage. Currently the framework has only coverage for the "happy flow", but not for exceptions.
In order to run the tests, you need to install nose2 and mock. If you would like to get a coverage report, you also need to install cov-core. See tests/README.txt for the details.