Le 21 avr. 2015 à 16:32, Otto Behrens a écrit :
Thanks. I do <alt>jc on a method sometimes when I have changed a method. So sometimes I so <alt>jm and then immediately <alt>jc to check all the tests in the class.
Indeed, Nautilus logic to run test differs a bit from the TestRunner logic.
Does it really have to be?
No, it should not.
For example, if your test fails, it is run a second time to open a debugger but it could do side effects.
This has been a problem for me for a long time. I would *love* it if Nautilus runs a single test in debug mode (and not a second time). It is especially painful when running selenium tests in our environment, because firefox is launched on every test suite run, which makes running a single test relatively expensive. I suppose solving the problem of tests running a long time is first prize.
Why don't you just run your tests from the test runner or using MyTestClass run: #testSelector ?
Because I normally run the tests that I work on while I'm in the Nautilus browser (using shortcut keys). Why would I want to launch a different browser, search for the class I'm working on and run the tests there?
It was a suggestion for your use case. If you only want to run the test you are working on, Nautilus helps.
I could be missing it totally here. I'm quite interested to know how other people work. A sort of work flow, to the point of running tests.
We miss a functionality in Pharo to easily run (a shorcut) a set of selected tests (ex: your project tests). This way, you can have a quick feedback on your updates. As it is not so easy, I often fallback to run tests from Nautilus (a test class or sometimes only a test method).
To run all my tests take a long time. There are quite a few.
We will need to clean this kind of logic that should not be part of Nautilus. Could you open a bug entry for that?
https://pharo.fogbugz.com/f/cases/15374/exception-handling-when-running-test...
Yes.