Hi,
Based on my exp, It may occurs in 3 diff condition
1. Internet limit crossed
2. Connection interrupt between test server and browser.
3. Memory allocation issue
Solution : Get a help from System Admin to debug this issue. Nothing is
required in code level(If u r very good in Ruby memory all
looks like your browser crashed or closed by 'some other way' before you
close it in your teardown because this exception happens when you are doing
@browser.close
gems/watir-webdriver-0.6.2/lib/watir-webdriver/browser.rb:135:in `close'
i have seen this during parallel execution in the same bo
Another solution would be to use
tbl = ie.frame(:id,'ReportFramectl144').frame(:id,'report').table
(:class, /a3/)
This should cover both cases.
On Dec 1, 10:24 am, Steve Hamlett wrote:
> I'm using Watir to automate the testing of a report generated by MS
> SQL Reporting Services. The report g
Thanks, Ethan. Your solution is spot on!
--
You received this message because you are subscribed to the Google Groups
"Watir General" group.
To post to this group, send email to watir-general@googlegroups.com
Before posting, please read the following guidelines:
http://wiki.openqa.org/display/
I should add that re-writing the "rescue" line in any of the following
ways has no effect on the problem:
rescue Exception
rescue UnknownObjectException
rescue Watir::Exception::UnknownObjectException
--
You received this message because you are subscribed to the Google Groups
"Watir G
Hmmm, well sure, if the web server is down you don't want to run the suite
at all. I'd check for that first thing. Otherwise you can still catch the
time out exception from wait_until and handle it, if there's a way to
recover and move on.
hth,
Charley Baker
blog: http://blog.charleybaker.org/
L
Thanks!
I wanted to ensure, though, that if the element didn't exist, that I
caught the exception, refreshed the page and the caused the script to
exit, if the element still did not produce. (i.e.: if the web-server
is down, neither the rescue nor wait until will work).
On Apr 28, 12:59 pm, Char
I suppose you could, but the smarter thing would be to wait until a certain
element exists, using Watir's wait_until.
http://wiki.openqa.org/display/WTR/FAQ#FAQ-HowdoIdealwithtimingissuesandnotusesleep%3F
wait_until should by default poll for a given condition every .2 seconds up
until 60 seconds
The actual resolution is (drum-roll, please):
rescue
self.exit
end
Thanks to all who helped!
On Apr 27, 3:27 pm, «°¤§ømåtïçCðrp§ë¤°»
wrote:
> You hit the nail on the head, thanks, Adam!
>
> I tried using 'break', but the ruby syntax didn't like seeing the
> 'break' before 'end'.
>
> Tha
You hit the nail on the head, thanks, Adam!
I tried using 'break', but the ruby syntax didn't like seeing the
'break' before 'end'.
Thanks!
On Apr 27, 2:39 pm, AR wrote:
> Just to make sure I understand, let's lay out a basic rescue.
>
> <-- code -->
>
> begin
> assertion
> actions if asse
Just to make sure I understand, let's lay out a basic rescue.
<-- code -->
begin
assertion
actions if assertion passes
rescue
actions if assertion failed
end #rescue block
<-- unrelated actions/functions here -->
It sounds like you want the rescue to force the program to end safely
rat
Alex,
It's not that I don't want the code to run, at all, but only if it
successfully binds/attaches to the browser.
My issue is that it's rescueing the error, but not halting after the
rescue; it continues to the next line of code.
If I know it's going to fail, and I want the code to terminate,
John,
Asking the obvious, if you don't want the code to run, why not remove
it or comment it out? I'm not entirely sure what you are after, so a
general response which I hope may still be useful.
Firstly, the protected code block has the structure:
begin
expr..
[re
13 matches
Mail list logo
