#9224: Unify sage-test and sage-ptest
---------------------------+------------------------------------------------
   Reporter:  mpatel       |       Owner:  mvngu
       Type:  enhancement  |      Status:  new  
   Priority:  minor        |   Milestone:       
  Component:  doctest      |    Keywords:       
     Author:               |    Upstream:  N/A  
   Reviewer:               |      Merged:       
Work_issues:               |  
---------------------------+------------------------------------------------

Old description:

> We currently have separate single and multi-threaded Sage doctest
> scripts.  In particular, `sage -t ...` invokes `SAGE_ROOT/local/bin/sage-
> test` and `sage -tp ...` invokes `sage-ptest`.  These files share many
> lines of almost functionally identical identical code.  Unifying these
> scripts should make it easier to maintain and extend the Sage doctest
> system.
>
> Related: #2379, #7993, #7995, #8641, #9243, #9316.

New description:

 We currently have separate single and multi-threaded Sage doctest scripts.
 In particular, `sage -t ...` invokes `SAGE_ROOT/local/bin/sage-test` and
 `sage -tp ...` invokes `sage-ptest`.  These files share many lines of
 almost functionally identical identical code.  Unifying these scripts
 should make it easier to maintain and extend the Sage doctest system.

 Related: #2379, #7993, #7995, #8641, #9225, #9243, #9316.

--

Comment(by mpatel):

 If the interface above (or a variation) is reasonable, we could populate
 `doctest.py` with most of the non-parsing-related, non-redundant parts of
 `sage-doctest` and `sage-(p)test`.  To ensure that we test `doctest.py`
 regularly, I suggest we put it in the sage repository, under `misc/`.
 Then we'd put just the command-line parsing code in a `sage-test` in the
 scripts repository.  This script would `import sage.misc.doctest` and
 instantiate/call a `Doctester` object to run the tests.

 More keyword arguments for `Doctester`'s constructor: `timeout`,
 `timeout_long`, `testdir`, and various Valgrind settings.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9224#comment:9>
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