[Pharo-project] modal windows and unit tests
laza at blobworks.com
Wed Oct 13 09:03:50 EDT 2010
There are also some basic things that would need some adjustment as I
see it. I think core or basic classes and models shouldn't make any
assumptions about the UI or even if there is an UI at all.
So things like Object inform: aString would be something I'd rather
see to disappear.
Or Class rename: aString, which kindly pops up a Dialog to inform the
"user" when there are still references in Undeclared. I think that
check should better move to the sending method in Browser renameClass,
where chances are very high that a real user initiated the rename of a
class and not some filein.
2010/10/13 Stéphane Ducasse <stephane.ducasse at inria.fr>:
> I think that we will have to reconsider a lot of the infrastructure decision and the hudson server will kick us
> On Oct 12, 2010, at 10:45 PM, Alexander Lazarević wrote:
>> I was just looking at something similar.
>> I guess for modal windows that are a kind of DialogWindow something
>> like this should work
>> [UIManager default confirm: 'Got milk?']
>> on: ProvideAnswerNotification
>> do: [:ex | ex resume: (ex messageText = 'Got milk?')]
>> But which modal windows do pop up in your scenario, that do not send a
>> 2010/10/12 Alexandre Bergel <alexandre at bergel.eu>:
>>> A modal window is pop up by one of my tests. Is there a way to capture this situation and simply remove the modal window?
>>> Apparently, no notification is raised...
>>> Alexandre Bergel http://www.bergel.eu
>>> Pharo-project mailing list
>>> Pharo-project at lists.gforge.inria.fr
>> Pharo-project mailing list
>> Pharo-project at lists.gforge.inria.fr
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
More information about the Pharo-dev