655 reputation
314
bio website
location
age
visits member for 2 years
seen 2 days ago

Oct
3
answered How do I keep Selenium test cases DRY?
Oct
3
revised Automated tests pass every time when run individually, but when they are clumped into a test suite it's a toss up if the tests will pass
added 617 characters in body
Oct
3
comment Automated tests pass every time when run individually, but when they are clumped into a test suite it's a toss up if the tests will pass
Resource problems may be it. The speed at which the tests are run varies from each execution. For each test we start and then kill a Firefox driver, so I do not think anything inter-test would cause this
Oct
3
comment Automated tests pass every time when run individually, but when they are clumped into a test suite it's a toss up if the tests will pass
Ah, I agree it is definitely similar. My main concern is that the goal is to eventually integrate the tests into our nightly build, and if a test fails, the build will not be made. For that reason, it is critical we have 100% pass rates for tests that should pass
Oct
3
asked Automated tests pass every time when run individually, but when they are clumped into a test suite it's a toss up if the tests will pass
Sep
26
awarded  Commentator
Sep
26
comment Selenium Webdriver cannot locate element for right click event
Has anyone had success with the contextClick action command? I've run into the same problem as @Karol where the context menu doesn't show, but left-clicking and finding the element is not a problem
Sep
25
revised Selenium Webdriver and OpenLayers
tried to make the question readable, I may have failed but it's better than it was.
Sep
25
answered Why does IE9 running WebDriver scripts gets out of focus if other applications are open?
Sep
25
suggested suggested edit on Selenium Webdriver and OpenLayers
Sep
25
answered How to deal with automated test cases that always fail?
Sep
21
awarded  Critic
Sep
21
awarded  Scholar
Sep
21
comment Is there a way to shorten the time Selenium2/Webdriver takes to look for an element when a failure is expected?
Surprisingly, this worked great. I was under the impression from looking at the API doc previously that it could only be used for EXTENDING the time it looked, but I set it to 150 milliseconds and now a test that took 60 seconds takes 7. Thanks a lot!
Sep
21
accepted Is there a way to shorten the time Selenium2/Webdriver takes to look for an element when a failure is expected?
Sep
20
comment Is there a way to shorten the time Selenium2/Webdriver takes to look for an element when a failure is expected?
That is correct. The entire snippet up there runs for ~60+ seconds, hanging while trying to find the element that is not present
Sep
20
comment Is there a way to shorten the time Selenium2/Webdriver takes to look for an element when a failure is expected?
I added the code and updated the question. Hopefully it is a little clearer. I am a little long-winded at times.
Sep
20
revised Is there a way to shorten the time Selenium2/Webdriver takes to look for an element when a failure is expected?
added 722 characters in body
Sep
20
asked Is there a way to shorten the time Selenium2/Webdriver takes to look for an element when a failure is expected?
Sep
7
comment Capture screen during exploratory testing
SnagIt is really great.