ci: added minimal testing setup with coverage #88
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
ErikBjare
changed the title
|
I realized I've implemented similar changes in #93, where examples aren't run in CI, so it passes. Should probably prefer that PR over this one. |
9 tasks
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.
fixes #77
This simply runs all the examples with pytest + pytest-cov (for coverage) + nbval (for
.ipynbfiles).All the
*.pyfiles in the example folder are ignored since I'm not sure how to deal with the test collection when the entire file is the test (and may do things that require interaction).Since most of the notebooks seem to not run correctly I think it might make sense to try and figure out how to run the auto_examples as tests, but I can't figure out a way for pytest to treat each file like a test without running it at collection-time...