4 ms·
This looks nice, but there are a lot of sugar libraries over the webdriver protocol, its the smallest part of the problem of real browser testing but it has lot
by daleharvey 13y ago
This looks nice, but there are a lot of sugar libraries over the webdriver protocol, its the smallest part of the problem of real browser testing but it has lots of solutions, the real problems have almost 0 choice.
What I really want is a selenium server 30MB, firefox speaks the webdriver protocol natively, I dont see why a proxy server to a browser needs to be 30MB (40 including chromedriver?, it pretty much needs to launch browsers and proxy requests, the project that launches the browsers should probably be its own project for that matter.
If anyone can point me to a project working on that, I would highly appreciate it :)
- scriby 13y agoI'm working on https://github.com/scriby/browser-harness https://github.com/scriby/browser-harness. It's a little different in approach because it doesn't use selenium at all (rather it uses a websocket connection with the browser to control it). It's considerably more lightweight and compatible with all browsers you care about, but you can't do everything you can do with selenium. We've been using it for about 6 months at work and having good results.
- Scriptor 13y agoThis looks interesting and I have something I'd like to use it on, but the documentation could add a few things. How do I install this? How do I run a script?
- scriby 13y agoGood point. Check out https://github.com/scriby/browser-harness-bootstrap-tests https://github.com/scriby/browser-harness-bootstrap-tests for a full example. Browser harness itself is just a conduit between node and a browser - you need to provide the test framework yourself (mocha, vows, etc.).
- Scriptor 13y agoAwesome! I'm going to try it out now.
- cnp 13y agoWow, this is awesome! Excellent work on this. Going to give it a spin over the weekend.