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
Make sage -coverage
aware of TestSuite
#7209
Comments
This comment has been minimized.
This comment has been minimized.
Attachment: trac_7209-coverage-TestSuite-nt.patch.gz |
This comment has been minimized.
This comment has been minimized.
Reviewer: Florent Hivert |
comment:4
With the new category framework there will be a lot of parent which will be tested by the testsuite machinery. It is very useful that sage-coverage stop complaining about missing Cheers, Florent |
Changed keywords from none to TestSuite |
comment:5
Notice that #5819 is somewhat related to this. It would be nice to fix that issue eventually... |
comment:6
Replying to @jhpalmieri:
Sure. But right now our primary goal is to finish the category stuff ASAP... Cheers, Florent |
Merged: sage-4.2.alpha1 |
With the attached patch for sage/local/bin,
sage -coverage
scans for either a loads(dumps(s)) or a TestSuite(s).run() doctest, and suggests using the later.Also refines the test whether the file defines a class.
CC: @sagetrac-sage-combinat
Component: doctest coverage
Keywords: TestSuite
Author: Nicolas M. Thiéry
Reviewer: Florent Hivert
Merged: sage-4.2.alpha1
Issue created by migration from https://trac.sagemath.org/ticket/7209
The text was updated successfully, but these errors were encountered: