Em 30/12/2009 17:50, Bart Gauquie < [email protected] > escreveu:
> I highly agree also !! > Its related to Pharo for Professional Development thread I started > 2 weeks ago. It basically says the same. My gut feeling is still > that stability should be the number one focus. Its great to > innovate, but innovation must not harm stability. > For me stability is keeping regression bugs to a minimum. To test > the stability of the GUI/Morphic parts of Pharo, I started to create > a little project: http://www.squeaksource.com/MorphicsRecordNPlay/. > This can record mouse events and replay them afterwards. My idea was > to take this as a sort of automated integration testing of Pharo. > You can then record all kinds of stuff: opening a browser, clicking > on a class, try every option out, ... . I've also attempted to > automatically convert these recordings into sunit test cases so they > can be automatically replayed, but I stumbled upon following > limitation: Long method can not be compiled using #compile: > aString. Haven't looked into it further yet. Any ideas here how > these can be replayed? Bart, Can't you store the events in a collection and run them iterating over the collected events instead of attempting to compile all them at once? -- Cesar Rabak _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
