#12415: Update doctesting framework
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Reporter: robertwb
| Owner: jdemeyer
Type: enhancement
| Status: needs_work
Priority: major
| Milestone: sage-5.7
Component: doctest
| Resolution:
Keywords:
| Work issues:
Report Upstream: N/A
| Reviewers: Jeroen Demeyer
Authors: David Roe, Robert Bradshaw
| Merged in:
Dependencies: #13147,#13146, #13145, #12723, #12392, #12393, #12395,
#12396, #12397, #12381, #12382, #12383, #12384, #11871, #13195, #13121, #13748,
#13899, #12719, #5155, #14070, #14079 | Stopgaps:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Comment (by jdemeyer):
Replying to [comment:190 roed]:
> I agree that the line describing which file is being tested should come
at the beginning.
OK, so you agree with
{{{
sage -t file.py
<messages>
[1 test, 1 failure, 1.7 s]
}}}
I would move the part of `report()` which prints the "sage -t ..." header
to a new function `report_start()` (for example) and then correct the
logic in `forker.py` to call that function at the appropriate time. Does
that sound good?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12415#comment:191>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
