Selenium mess

45 views
Skip to first unread message

Antonis Christofides

unread,
May 17, 2017, 10:45:18 AM5/17/17
to django...@googlegroups.com

Hi,

I am the author of django-selenium-clean.

I'm happy I wrote extensive unit tests for it, which has made it much easier to see what's up in various Python/Selenium/Browser combinations. But I have some trouble and I was wondering whether there's any Selenium expert who can help. Or if anyone knows where I could ask for help. Or if anyone could just investigate and verify these findings and come up with any ideas.

Here's the situation (copied from the ticket):
  • Selenium 2.53, Firefox 45: Everything runs fine (but tests are run twice, but this is probably not a Selenium issue).
  • Selenium 2.53, Firefox 53: Browser opens, then nothing happens, after a while testing terminates with an error.
  • Selenium 3.4, Firefox 53: Browser opens, tests start. Two tests run successfully, then it hangs. Maximizing the browser and restoring it to the original size may unhang it, and it may re-hang. It always hangs after a test finishes and before another starts. Some tests fail, but it can't be said whether it's a problem until the hanging is fixed.

The above behavior is with Python 3. With Python 2, the behavior is the same, except that, in addition, if it manages to terminate properly (such as in Selenium 2.53 and Firefox 45), the browser stays open and there's an error message in the console.

Regards,

A.
-- 
Antonis Christofides
http://djangodeployment.com

Tim Graham

unread,
May 17, 2017, 12:10:44 PM5/17/17
to Django users
I haven't been able to run the selenium tests in Django's test suite without errors similar to what you describe since the geckodriver became required for testing with Firefox. I suspect this is a selenium/geckodriver issue rather than anything Django related. In the meantime, we're running the selenium tests with Google Chrome.

XaviP

unread,
May 18, 2017, 11:54:12 AM5/18/17
to Django users
My experiences with django-selenium-Firefox were really painful. When finally switch to phantomjs, all was better, but from time to time, the tests still freeze in travis-ci. Hope it helps.

El dimecres, 17 maig de 2017 16:45:18 UTC+2, Antonis Christofides va escriure:
Reply all
Reply to author
Forward
0 new messages