Just out of curiosity I ran all tests using a #20593 image and the latest Mac OS X pharo vm on my machine. 9749 run, 9686 passes, 2 skipped, 58 expected failures, 3 failures, 2 errors, 0 unexpected passes Failures: ReleaseTest>>#testUndeclared SimulateKeystrokesSpecification>>#testSimulateKeystroke SimulateKeystrokesSpecification>>#testSimulateKeystrokes Errors: MCStReaderTest>>#testCommentWithStyle MCStReaderTest>>#testMethodWithStyle And the fact that Undeclared was not empty was due to extra loaded code of my own. Like Marcus said, I already reported the time problem close to midnight: https://pharo.fogbugz.com/f/cases/7602 https://code.google.com/p/pharo/issues/detail?id=7643 The other remarks are valid of course. Sven On 20 Mar 2013, at 08:51, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mar 20, 2013, at 12:54 AM, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
First thing, congrats to Pharo community, I observe a good trend. It may seem dumb, but it's great to have pharo executable and pharo icons. Once the image launched, my general feel is good too, though I'm not fan of multiple keys shortcuts. It stressed me to the point that I didn't realize the single key shortcuts were still active in text editor (desperately seeking cmd b+ something... when cmd + shift + N would just browse ivar references). I guess I'll get used to it. Browsing the class Object seems a bit long, I guess there's time wasted scanning the class hierarchy...
Of course, there's a few things to polish. First I ran the tests, and here is what I have to say about it - there were two interactions requests, IMO, there shouldn't be any (a pop up for my name, and a menu)
How to not require a name when a tests does something that needs it? When running tests on the build server it sets a name before and removes it later, but I don't think that the test runner should do that by default.
- there are some failures (10) and errors (3), is this expected? (see attachment)
-> There are some tests that fail when running like this that do not fail on the build server. We should put issues for them on the tracker and fix them.
-> There seems to be a strange Time related bug happening only around midnight. Yes, someone should have a look a that, too. (First step is to submit an issue).
- more annoyingly, during the test, the progressbar feedback disappeared (sporadically flashing) and the TestRunner feedback too (number of succeded test updates went scarce)
ProgressBar still needs to be improved. I think there is even an issue for that.
When I opened a FileBrowser to browse the filedOut TestRunner report, I typed *.txt as a filter and got a RegexSyntaxError nullable closure, that's surprising.
FileBrowser is not used a lot and there are of course no UI level tests. So there will be bugs.
There I stopped exploring the features and inquired a bit about the failures. Most failures are related to DateAndTime. I guess they occured because I was playing with image around midnight with a +01:00 offset.
Yes, two people already saw this bug happening, we should add an issue to the tracker.
In general it just shows: Any issue that is not fixed by someone is not fixed. ;-)
Marcus