for url" on our build server when running tests with internet explorer. The
problem was that Chrome browser was installed as the default browser and
every time a test would run with internet explorer, the popup to setup
internet explorer as the default browser would open and make the test fail.
After making sure that all browsers don't ask to be the default browser,
the exception disappeared. Hope that helps!
Le mardi 24 janvier 2012 23:22:34 UTC+1, Scott M. a écrit :
mrstevegross -
You should be able to.
Our Ops team, from my understanding, setup an exception group and
added my test machines IP addresses to that group. This group has no
connection limit set and the proxy server essentially ignores my test
machines. I was out of the loop on the exact fix but in a nutshell
after digging through the old threads that's what happened.
My recommendation would be to work with your Ops team or sys admin.
What helped me prove to Ops that is wasn't the test itself and more a
proxy configuration issue was that I wrote a simple console app which
uses the selenium binaries and generates a request over and over via
Firefox and used that to show them the issue.
Hope that helps.
due to limit imposed on requests-per-minute, can we raise that limit?
--Steve
--You should be able to.
Our Ops team, from my understanding, setup an exception group and
added my test machines IP addresses to that group. This group has no
connection limit set and the proxy server essentially ignores my test
machines. I was out of the loop on the exact fix but in a nutshell
after digging through the old threads that's what happened.
My recommendation would be to work with your Ops team or sys admin.
What helped me prove to Ops that is wasn't the test itself and more a
proxy configuration issue was that I wrote a simple console app which
uses the selenium binaries and generates a request over and over via
Firefox and used that to show them the issue.
Hope that helps.
On Jan 17, 7:00 am, mrstevegross wrote:
After further investigations on my side it appears there was a
connection limit set on our proxy servers (about 40 requests per
workstation for a given minute), this was not only wreaking havoc on
my automation efforts using Selenium but it aided in identifying the
cause of some other intermittent issues my teammates have had with
their test tools.
So... is there any solution to this problem then? If we know that it'sAfter further investigations on my side it appears there was a
connection limit set on our proxy servers (about 40 requests per
workstation for a given minute), this was not only wreaking havoc on
my automation efforts using Selenium but it aided in identifying the
cause of some other intermittent issues my teammates have had with
their test tools.
due to limit imposed on requests-per-minute, can we raise that limit?
--Steve
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/d/msg/selenium-users/-/6ObrP0n7QWAJ.
For more options, visit https://groups.google.com/groups/opt_out.