get doctests running as part of test actions#713
Conversation
|
I will automatically update this comment whenever this PR is modified
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## development #713 +/- ##
============================================
Coverage 65.65% 65.65%
============================================
Files 37 37
Lines 3051 3051
Branches 396 396
============================================
Hits 2003 2003
Misses 971 971
Partials 77 77 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The unit tests will continue to fail due to #723. Going to merge so we can get that fix through without the other version update distractions. |
While working on #712, I noticed that the codecov report showed some lines as untested that should have been tested by the docstring (and also that some of those same doctests should be failing!). I discovered that despite
--doctest-modulesbeing set inpytest.ini, it wasn't running the docstring tests. This PR modifies the pytest.ini file to help it find all the docstring tests and run them (local testing) and the unit_test.yml action to include them in CI testing. It also starts fixing some of the failing docstring tests.This lack of docstring tests running explains a not-yet-documented mismatch in what
product_summary_infoprovides in v2 after #685 versus the short summary it previously showed.