On Apr 20, 4:52 pm, Christopher Lee <l...@chem.ucla.edu> wrote:
> - let's try to make the default mode of runtest as quiet (unverbose) > as possible. E.g. I preferred it when it just printed a dot for each > successful test. When too much text races across the screen it > becomes easy to miss an important piece of error information one suggestion, it won't solve the problems but may mitigate some, running the tests in strict mode -s will stop after a suite with errors. > * does runtest have a "make clean" option that ensures no side- > effects from previous test runs are possible (deletes any leftover > files)? > * provide an option to strictly insulate each test from any side For this purpose there used to be a reset_tempdir function in the testlib that was meant to remove then recreate the root temporary directory. Looks like it did not make it into the trunk. The original goal was to have it invoked at the start (or if the --clean flag was passed). It was never fully implemented so I guess that's why it is not there now. We could call the reset_tempdir() for each testsuite or even test, although that would probably be a little overkill. I can add this back in. > * it would be awesome if runtest provided some way of helping to > track down order sensitivity effects to their cause, sort of like git > bisect. For example, if I define a Python function that can check > whether the "bad side-effect condition has occurred yet", I'd like I guess if there were no side effects at all then you'd not need this. Maybe it's better to look into removing those. Istvan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-dev@googlegroups.com To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
