Brian,
Good point.
The selector I'm using is ....
saveButton { $('button[id=save-button]') }
which is specific enough, but our app had two buttons on the page that used
this same ID (a "no-no"). Once we corrected this the geb test passed. Glad
to see that geb 1-rc-1 caught this!
Brian
On Mon, Oct 3, 2016 at 10:39 AM, Brian Kotek <[email protected]> wrote:
> Hmm...if older versions of Geb handled this, I'd say *that* is probably a
> bug, rather than the behavior you're seeing. Trying to click on two
> elements at once is something I'd expect to fail, because it means
> uncertainty about what is actually happening. Will it click the first
> element? The last one? Loop over them and click them both? I think the
> right thing to do would be to use a more specific selector, so that you're
> positive about what's going to be clicked on?
>
>
>> If I pause test execution in the debugger, I can see that there are 2
>> context elements defined for the navigator. I also see 2 elements when
>> using the older version of geb, though it seems to be able to handle this.
>>
>>>
>>>
--
You received this message because you are subscribed to the Google Groups "Geb
User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/geb-user/CAMvxi92SYFQ__bcTubxhXXnQUtmZ-%3DqdyX5p6NCp9EZisPLZNA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
