I was able to write some pretty reasonable tests for gui elements in Dolphin. Getting something to open/close and in between, firing a few commands at it can be informative, sometimes ~:0
________________________________________ From: [email protected] [[email protected]] On Behalf Of Stéphane Ducasse [[email protected]] Sent: Thursday, July 21, 2011 3:09 PM To: [email protected] Subject: Re: [Pharo-project] Time Profile mostly unusable this is mainly a ui concern. On Jul 21, 2011, at 8:58 PM, Igor Stasenko wrote: > On 21 July 2011 20:29, Mariano Martinez Peck <[email protected]> wrote: >> >> >> On Thu, Jul 21, 2011 at 6:14 PM, Stéphane Ducasse >> <[email protected]> wrote: >>> >>> it depends on your scenario and when users do not use or use the tool >>> differently you get different feedback. >> >> Or even better: if noboy says anything in the last 6 months while Pharo 1.3 >> was being developed/tested then we cannot do magic. >> I am tired of saying that anything that YOU don't test, can be broken. >> > > why "can be"? it definitely will be broken. > > What would be nice is to write tests for TimeProfileBrowser to prevent > regressions. > Any ideas? > > -- > Best regards, > Igor Stasenko AKA sig. >
