Alexandre Bergel-7 wrote
>
> I opened an issue: http://code.google.com/p/pharo/issues/detail?id=5010
>
Fix (although I guess there are more widgets to fix?) in 1.4 inbox
SLICE-Issue-5010-Testing-GUI-widgets-SeanDeNigris.1
Alexandre Bergel-7 wrote
>
> This is very valuable. Currently it is really hard to test GUI in Pharo.
>
I think it could be very easy with a little work
Alexandre Bergel-7 wrote
>
> One problem I faced several times is that GUI are not uniformly managed:
> some GUI widgets use of exceptions (which is cool), some other are
> blocking the currently thread (which is not cool).
>
The hook points are in MorphicUIManager's "ui requests" protocol. For each
type of interaction (e.g. confirm), in the method that takes the most
arguments (e.g. #confirm:label:, not #confirm:), ProvideAnswerNotification
is signaled.
Alexandre Bergel-7 wrote
>
> For example, I can write...
>
Thanks for the examples. I wrote them into Morphic tests (incl. in fix
above)
Alexandre Bergel-7 wrote
>
> self should: ['/tmp' = ([UIManager default chooseDirectory]
> valueSupplyingAnswer: #('/tmp'))]
>
This works now, but the syntax is ...valueSupplyingAnswer: { 'Choose
Directory'. FileDirectory on: '/tmp' }.
HTH,
Sean
--
View this message in context:
http://forum.world.st/GUI-Testing-Library-tp4097866p4100236.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
