[
http://jira.openqa.org/browse/WTR-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19837#action_19837
]
Jarmo Pertman commented on WTR-452:
-----------------------------------
Again, i personally feel that 5 minutes is more than enough and if some page
for some reason doesn't load in that time then there are more important
problems to deal with than not-configurable-timeout-setting-in-watir :) If
tester doesn't open up a bug right at that point in fear of the developers or
whoever then that tester shouldn't be a tester at all. I would let him/her go
immediately if i would be in charge. Tester should not be quiet or think "oh,
i'm not gonna bother anyone with this small detail, because everyone has
already a lot of work to do - just let it be that slow". Tester should act to
make those changes.
If tester is afraid to talk with developers directly, address them through
manager instead. If that is also a problem, well, i think there are then just
too much problems already and that particular tester should consider a career
change.
There is 2 reasons why not having a configurable timeout:
1) So pages would be fixed instead of ignoring the problem
2) The less configuration options the better. Why is iPhone so popular? Not
because it's so good (it isn't :P), but because it is so easy to use and you
just don't have to (and can't) configure too much.
Again, if it is really-really-really needed to increase the timeout, then just
go through the trouble to monkey-patch the code :P
Also wanted to say that currently Firewatir has already a 5 minute timeout
implemented. Don't know since when. Should this be changed also?
Sorry if i sounded too straightforward and/or harsh.
> adding timeout to #wait
> -----------------------
>
> Key: WTR-452
> URL: http://jira.openqa.org/browse/WTR-452
> Project: Watir
> Issue Type: Improvement
> Components: Wait
> Affects Versions: 1.6.5
> Environment: all envs
> Reporter: Jarmo Pertman
>
> Currently it is possible that Watir will block forever in it's #wait method
> under some circumstances. There are questions once in a while in the group
> also about the timeout of Watir.
> Unfortunately currently there is no timeout!
> I have a proposal to add a timeout. And make it hardcoded - let's say 5
> minutes. Why hardcoded? Because i think that if your page is unable to load
> in 5 minutes then your page is broken and should be fixed/changed anyway.
> This would be a small indicator to the developers and testers that they
> shouldn't waste so much time of their lives for waiting some bad application
> to render a page.
> Charley proposed to create an issue and let people to vote (not downvote) it!
> So, what do you guys think about making Watir a little as an Opinionated
> Software as Rails tries to be?
> (PS, if your page loads more than 5 minutes and you cannot get yourself
> together to fix it or tell your developers to fix it and you really need to
> have longer timeouts, then you can always monkey-patch #wait. We're talking
> about Ruby where everything is possible, remember?)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.openqa.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Wtr-development mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-development
