pytest sometimes failed with The browser appears to have exited before we could connect[Random failure] about pytest-selenium HOT 5 CLOSED

the traceback hooks deep into selenium, and the exception orginates in the selenium package

from pytest-selenium.

It would be helpful if someone can tell what could be the reason for such issue.

from pytest-selenium.

The reason is given in your trace: "WebDriverException: Message: The browser appears to have exited before we could connect." this suggests that Firefox was closed or crashed during the test. Can you provide the command line you're using to run these tests, and anything else that might help me to reproduce it such as what operating system you're using, and if there are any additional configuration options specified anywhere? Also, can you try running with Firefox 47.0.1 to see if you can still replicate the issue?

from pytest-selenium.

1> for you questions,

• the OS is CentOS 7.2,
• for tests, it was just simple test our application, not anything special
• for run commandline it is simple like this:

py.test --base-url http://127.0.0.1:8000 --driver Firefox mytest  -x

2> For firefox 47.0.* I could also find some issues from the web . like this

https://snakeycode.wordpress.com/category/selenium/

From that link it also talked about issue like
"WebDriverException: Message: The browser appears to have exited before we could connect"

seems suggest use this way
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette/WebDriver

I will try if Marionette could solve the issue or not.

from pytest-selenium.

You could try to replicate your issue without using pytest-selenium by creating a python script that just launches Firefox a number of times. From your traceback it doesn't look like this is an issue with the plugin, and reproducing without the plugin would help to identify the issue in Selenium, which you can raise here: https://github.com/SeleniumHQ/selenium/issues

That said, for Firefox 48 and above it is necessary to use Marionette and GeckoDriver (as you mention), and if you can get that to work then this issue may no longer be a concern. I'm going to close this for now. Please reopen if you have more evidence that pytest-selenium if the cause of the issue.

from pytest-selenium.