-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[patch] Run Doctest #18
Conversation
I can't get the test to nicely see the error message; since we anyhow have unit tests for this I am not hung up on whether the docstrings remain perfectly verbatim correct and am content to leave the printed warning as plain-text docstring instead of tested-code docstring.
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences🚀 Don’t miss a bit, follow what’s new on Codacy. Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more |
Pull Request Test Coverage Report for Build 9570593710Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9571690727Details
💛 - Coveralls |
@deprecate I'm playing around just now, but it's all a bit awkward. Since there are the unit tests, we could just add |
Pull Request Test Coverage Report for Build 9581360703Details
💛 - Coveralls |
Now that doctest ignores it anyway
Pull Request Test Coverage Report for Build 9585341114Details
💛 - Coveralls |
@pmrv perfect, thank you! I had been trying to accomplish something similar, but I think I was using Now that you got the skip working, I've reverted my ugly formatting of the expected output. |
Adds automatic testing of the docstring. I cut some corners on the deprecator example because I just couldn't get the output parsing to work nicely with the fact that it is a warning being printed and not plain output.