3 ms·
One thing I always think is worth mentioning in posts like this is that the above setup (and any setup using Selenium, really) is going to be super slow. More
by diminoten 13y ago
One thing I always think is worth mentioning in posts like this is that the above setup (and any setup using Selenium, really) is going to be super slow. More than one order of magnitude slow, when compared to direct HTTP requests.
It's only ever worth using Selenium when you literally can't do anything else to get your testing done.
Edit: Going through my bookmarks bar and found this, from 2008 - http://www.alittlemadness.com/2008/03/05/running-selenium-headless/ http://www.alittlemadness.com/2008/03/05/running-selenium-he...
Might help anyone if they run into issues.
- recuter 13y agoWhy is the overhead so great?
- iamchrisle 13y agoBecause it has to load a virtual frame buffer (Xvfb), the chrome browser, a Selenium server, and then your testing framework. All that adds up to crap performance. There's a lot of pieces that could be simplified with a smaller set of requirements. But like @diminoten said: it's worth it if you have no other choice.