[Chandler-dev] Command-line option changes related to testing

[Bryan Stearns]

I mentioned in IRC yesterday that I wanted to change a few command-line 
options; I've just checked in the changes.

First:
--nocatch causes us to run without an outermost exception handler, which 
is good if you're debugging in Wing and want the debugger to stop on 
unhandled exceptions (instead of putting up the feedback UI). I 
discovered, though, that the new code that runs the functional test 
suite is adding an exception handler of its own that I also want to turn 
off to allow debugging of functional test failures; however, Bear 
pointed out that the tinderboxes currently run the functional test suite 
with --nocatch, and need to keep the current behavior.

So, I proposed to change --nocatch to --catch=(normal|tests|never), 
where "normal" is the default and matches the current default behavior 
(both exception handlers in place), "tests" just removes the outer one 
(the current --nocatch behavior), and "never" removes both exception 
handlers (for me and anyone else who debugs functional test failures). 
This seemed OK with bear, especially when I promised to leave --nocatch 
in place until he could switch the tinderboxes at his convenience, so 
I've done it.

Second:
I whined that I'm constantly adding and removing "-f 
tools/cats/functional/FunctionalTestSuite.py" in the debug options box 
in Wing, so I've added "-T" (that's capital T) (as well as the long form 
"--chandlerTestSuite") to do this. (I forgot to mention this in the 
checkin notes - oops.).

Third:
I notice that --chandlerTests has no shorter option, so I'm planning on 
moving "-t" (lower case t) from --testScripts to --chandlerTests (the 
existing cats list-of-tests option, which didn't have a shortcut until 
now) because I don't think it makes sense to run 'all the scripts' 
anymore. (I haven't done this last one yet - I didn't want to hose 
anyone who does still use the -t form of --testScripts; speak up if you 
do -- hi, Donn!).

...Bryan