Changes between Version 6 and Version 9 of Ticket #9224


Ignore:
Timestamp:
Jul 15, 2010, 7:32:32 AM (12 years ago)
Author:
Mitesh Patel
Comment:

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.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9224

    • Property Cc Leif Leonhardy added
  • Ticket #9224 – Description

    v6 v9  
    11We 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.
    22
    3 Related: #2379, #7993, #7995, #8641, #9243, #9316.
     3Related: #2379, #7993, #7995, #8641, #9225, #9243, #9316.