R. David Murray <rdmur...@bitdance.com> added the comment: Testing regrtest is distinctly non-trivial, since options have interactions (some of the somewhat unobvious). Ideally we'd refactor the code so that we could point it at a test test-directory so we could write some automated tests for it :) But if you are going that far you might as well rewrite it.
This is, I suspect, why nobody has yet done this conversion. My best suggestion if you really want to go ahead is to go through each option individually, with and without command line arguments, and test how it currently behaves and make good notes. Anything that doesn't make sense, ask on (#)python-dev. And then...build a matrix and test each option in combination with each other option, again keeping notes. Which is something that has probably never been done, and will doubtless reveal some interesting bugs. You might be able to automate some tests using doctest and subprocess. I'm not sure about that easy tag. This could easily be more than a one day project. I suspect you will find your fingers itching to refactor more than just the argument parsing code. You should probably resist that urge insofar as possible :) ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10848> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
