Skip to content
This repository has been archived by the owner on Feb 13, 2020. It is now read-only.

Should be more resilient against remote webdriver failures #62

Closed
rtyler opened this issue Apr 10, 2012 · 3 comments
Closed

Should be more resilient against remote webdriver failures #62

rtyler opened this issue Apr 10, 2012 · 3 comments

Comments

@rtyler
Copy link
Contributor

rtyler commented Apr 10, 2012

Sporadically (~0.5%) tests will fail with an unhandled error coming out of the remote web driver, like this traceback.

In these cases it's probably best to try to re-run the test case or mark the test as skipped

@ghost ghost assigned rtyler Apr 10, 2012
@rtyler
Copy link
Contributor Author

rtyler commented Apr 13, 2012

Looks like this is occurring a closer to 1% for @lookout tests. I'll have to bump the priority of this.

@rtyler
Copy link
Contributor Author

rtyler commented Apr 14, 2012

Starting work on this now.

(This message brought to you by Hub board)

@rtyler
Copy link
Contributor Author

rtyler commented Apr 27, 2012

Since we're already using an Around block for Sauce tagged cucumber scenarios, I think it might be feasible to use the Ruby retry to re-run the scenario (block.call) up to 2-3 times.

@rtyler rtyler closed this as completed in 2ada3d1 Apr 27, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant