On Jan 26, 2009, at 10:21 PM, William Stein wrote: >>> The main problem I see with the above is that it is hard to see what >>> the test coverage of the files in local/bin/ is. >> >> I'm all for keeping doctests as local as possible--it would be nice >> to put the test for sage -preparse in the sage-preparse file itself. >> We could add a line to sage -testall to run tests in this directory >> as well. >> >> - Robert > > OK, but now you need to describe the format for the tests. Normal > doctesting exactly as we do in the sage library tree doesn't > immediately make any sense in this context (at least I can't see how). > It's also important to keep things in temp directories, etc. So > propose something more local :-)
The format would be exactly the same as you proposed. Many of the scripts in sage-bin are Python files, so we'd just run the normal doctests on them (maybe there'd be some issues as they don't end in .py). Perhaps we could search for doctests in the comments of bash scipts as well, or have separate python scripts there just to hold their doctests (though preferably in the same repository to make keeping things in sync easier). - Robert --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
