#9225: New doctesting features
---------------------------+------------------------------------------------
   Reporter:  mpatel       |       Owner:  mvngu
       Type:  enhancement  |      Status:  new  
   Priority:  major        |   Milestone:       
  Component:  doctest      |    Keywords:       
     Author:               |    Upstream:  N/A  
   Reviewer:               |      Merged:       
Work_issues:               |  
---------------------------+------------------------------------------------

Old description:

> This is an umbrella ticket for various improvements to the Sage
> doctesting framework.  For example:
>
>   When we doctest several files in parallel or in sequence, it might be
> helpful to print stats relating to the test suite's progress, e.g.,
> {{{
> #!sh
> $ sage -t monoids/
> sage -t  "monoids/monoid.py"
>  1/10    1.9 s / 1.9 s
> sage -t  "monoids/free_monoid.py"
>  2/10    2.0 s / 3.9 s
> [...]
> }}}
>   What other columns would be useful?  Coverage?
>
> Please see the comments for more ideas.  Suggestions are welcome!
>
> Related: #9224.

New description:

 This is an umbrella ticket for various improvements to the Sage doctesting
 framework.  For example:

   When we doctest several files in parallel or in sequence, it might be
 helpful to print stats relating to the test suite's progress, e.g.,
 {{{
 #!sh
 $ sage -t monoids/
 sage -t  "monoids/monoid.py"
  1/10    1.9 s / 1.9 s
 sage -t  "monoids/free_monoid.py"
  2/10    2.0 s / 3.9 s
 [...]
 }}}
   What other columns would be useful?  Coverage?

 Please see the comments for more ideas.  Suggestions are welcome!

 Related: #9224, #9739, #10458.

--

Comment(by leif):

 #10458 improves cut & paste of doctest code & output from an actual Sage
 session, in that it allows also "`....: `" for line continuations.
 (Previously, for some reason only "`...`" was supported in docstrings;
 also the confusion with an ellipsis intended to mean arbitrary
 '''output''' should be reduced by this ticket.)

 Another problem still has to be addressed: The original (non-preparsed)
 source code of continuation lines gets "lost", i.e. doesn't end up in the
 end-of-line comments of the generated test files (`.doctest_*`) as it does
 for ordinary lines, hence also won't be shown on doctest errors or when
 one doctests in verbose mode.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9225#comment:14>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to