OBSUnitIntegration is already providing some of those: > 1) When you are in the browser writing a test method, you can press ctrl + t > to save the method and run the test. If the test runs, it will show the > green dot in the browser, if it does not, it popups the debugger directly on > the error. So, this is a way to avoid pressing ctrl + s (save) then going to > the method list, rigth click an select run test and if it fails select that > you want to debug it.
Ctrl+T does not save, but it runs the tests and shows the debugger. I don't think that I like the two things to be combined :-) > 2) Same as ctrl + t but ctrl + r to directly debug the test. It saves the > method, puts a breakpoint in it and debugs it. Unfortunaly, in Pharo > breakpoints dont show very well in the debuger (it highlights incorrect > collaborations) Ctrl+D opens a full debugger on the first line of the selected test, no matter if the test fails or not. It doesn't use breakpoints. And I use it all the time :-) So maybe we could combine some of that code? Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
