[wtr-general] Re: Safriwatir issue with clicking links

2009-11-09 Thread QAguy
Anything else you can suggest? Thanks On Nov 4, 5:57 pm, Željko Filipin wrote: > On Wed, Nov 4, 2009 at 11:53 PM, QAguy wrote: > > puts browser.link(:text, /Sign/).text gives me a result of Sign Out > > It is late here, my brain is sleeping. What do you get when you run this? > > puts browser.

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-04 Thread QAguy
That gives me the same result: host73:watir_site_regression employee$ spec specs/connect_spec.rb ...Sign Out . We can pick this up tomorrow and I am also pretty tired. Thanks for the help on this. QAguy On Nov 4, 5:57 pm, Željko Filipin wrote: > On Wed, Nov 4, 2009 at 11:53 PM, QAguy wrote:

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-04 Thread Željko Filipin
On Wed, Nov 4, 2009 at 11:53 PM, QAguy wrote: > puts browser.link(:text, /Sign/).text gives me a result of Sign Out It is late here, my brain is sleeping. What do you get when you run this? puts browser.link(:text, /Sign/).text.inspect Željko --~--~-~--~~~---~--~---

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-04 Thread QAguy
puts browser.link(:text, /Sign/).text gives me a result of Sign Out when i run my .rb file (see below) host73:watir_site_regression employee$ spec specs/connect_spec.rb ...Sign Out . QAguy On Nov 4, 5:45 pm, Željko Filipin wrote: > On Wed, Nov 4, 2009 at 7:42 PM, QAguy wrote: > > This: browse

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-04 Thread Željko Filipin
On Wed, Nov 4, 2009 at 7:42 PM, QAguy wrote: > This: browser.link(:text, /Sign/).text gives me no errors when I run > it in my test. I did not make it explicit that you should run that code in IRB. :) If you are running that code from a file, then try this and let me know what do you get for out

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-04 Thread QAguy
I have safariwatir (0.3.7, 0.3.3) checked with gem list This: browser.link(:text, /Sign/).text gives me no errors when I run it in my test. When I try this: @browser.link(:text, /Sign Out/).click I get: unable to locate Link element with text of (?-mix:Sign Out) When I try this: @browser.link(

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-02 Thread Željko Filipin
On Mon, Nov 2, 2009 at 6:05 PM, QAguy wrote: > BTW I tried browser.link(:text, "Sign Out").click but I get a > response that safariwatir could not find a link element with text Sign > Out. Which version of SafariWatir do you have? What do you get from this? browser.link(:text, /Sign/).text

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-02 Thread QAguy
BTW I tried browser.link(:text, "Sign Out").click but I get a response that safariwatir could not find a link element with text Sign Out. The element is as follows: Sign Out So I tried: @browser.div(:text, "Sign Out").click but this results in: SafariWatir does not currently support fin

[wtr-general] Re: Safriwatir issue with clicking links

2009-11-02 Thread QAguy
Thank you. I will vote for that ticket. QAguy On Oct 30, 5:33 am, Željko Filipin wrote: > On Fri, Oct 30, 2009 at 11:27 AM, Željko Filipin < > > zeljko.fili...@wa-research.ch> wrote: > > You can report the bug: > > No need for that, it is already reported: > > http://jira.openqa.org/browse/WTR-

[wtr-general] Re: Safriwatir issue with clicking links

2009-10-30 Thread Željko Filipin
On Fri, Oct 30, 2009 at 11:27 AM, Željko Filipin < zeljko.fili...@wa-research.ch> wrote: > You can report the bug: No need for that, it is already reported: http://jira.openqa.org/browse/WTR-370 You can vote for it. In general, tickets with more votes get fixed first. Željko --~--~-~--

[wtr-general] Re: Safriwatir issue with clicking links

2009-10-30 Thread Željko Filipin
On Thu, Oct 29, 2009 at 5:47 PM, QAguy wrote: > This highlights the link in the browser window yellow but doesn't > actual cause the click action to occur, I'm using safariwatir. Really, I reproduced it too: >> b.link(:id, "signout_link").click => nil This is probably a bug. List of open bugs i