In Pharo 2.0 Nautilus have a better integration of test and of shortcuts. Because of a lack of time (or of people) Nautilus is not maintained in 1.4, since the focus is 2.0 since a while.
About the combination with AutoTest, it's really possible (and could be really cool) to implement a AutoTest plugin for Nautilus (the whole plugin mechanism has been designed for AutoTest actually ^^) Can you try in 2.0 and give some feedback ? :) Thanks in advance, Ben On Dec 18, 2012, at 3:32 AM, Stuart Herring wrote: > On 18 December 2012 13:10, Tim Mackinnon <[email protected]> wrote: >> I really like the new Toggle from Class to Test (cmd-j) option that got >> introduced - someone has definitely been writing tests in Pharo - however it >> does my head in that pressing it after editing a method doesn't jump me >> back. I also find the same problem when editing a test - that pressing cmd-t >> to run it, just puts a "t" in my source code and doesn't run the test. >> > I have the same frustration with alt/cmd-t it kind of defeats the > purpose of a keyboard shortcut if you've got to click somewhere on the > screen first before you can use it. > > Have you looked at Autotest? http://squeaksource.com/Autotest.html > It will run tests whenever you save them, and also tries to determine > which tests to run when you modify model classes. The only thing > that's a little bit disappointing is that it doesn't update the test > indicators in the browser. > > I wonder if in Pharo 2.0 someone could combine the concepts of the > in-browser test runner and Autotest. So that accepting changes in the > browser uses the same heuristics autotest does to run the tests, and > then uses the Growl style notifications for failures, with the > green/red/yellow test indicators being updated. > > Regards, > Stuart >
