On 28/03/13 3:11 AM, Marcus Denker wrote:
On Mar 28, 2013, at 4:56 AM, Yanni Chiu <yanni-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org> wrote:
Another thing I've noticed is occasional sluggishness in the UI. It's hard to pinpoint, I often feel like my clicks are being lost.
I have not seen that one.
After some more usage I'll pinpoint where it's happening, since it interrupts the train of thought otherwise.
The behaviour of the TestRunner was odd. Eventually I discovered running tests via the Nautilus browser, but the UI feedback is extremely confusing for "abstract" test cases. I still don't quite understand the results I see there, so I do a final run of the tests in the TestRunner.
Odd in which sense? related to the progress bar?
The TestRunner was sluggish when selecting test cases. This was the case in Pharo-1.4 too, but a little worse in Pharo-2.0. I had some tests that caused the UI to stop responding (had to kill the image, but the image's cpu usage was normal). Once the test cases passed, I've not seen the problem again. The main problem is that if I see a test failure in the TestRunner. Then when I try to browse that test case, the actual test code is in a superclass. But, it's unclear how to invoke that test case for the subclass through Nautilus, and it's not clear where the test result is shown in Nautilus (i.e. where is the green icon when the actual test method is in the superclass).
Another strange issue I had with test cases was to do with the interaction of the deprecation warnings. In by build script, I run: Deprecation raiseWarning: false. Deprecation showWarning: false. so the build can run headless. It took me a few hours, and a careful single stepping, to find that the deprecation exceptions were being swallowed. I'm sure the TestRunner did not behave this way before. If you ran a test, you would still see the deprecation exceptions. It was really frustrating to see your test fail, but have the stack cleared out before you could debug the exception that caused the test failure.
Can you add a bug tracker entry for that one?