Then, three weeks later, your CI build fails because the browser auto-updated but the driver didn’t.
npx selenium-standalone install Pro tip: Add --singleDriverInstall=chrome if you only need Chrome to save bandwidth. npx selenium-standalone start You will see output like: selenium-standalone
Run your test while selenium-standalone start is running in another terminal. They will connect automatically. The CLI is great, but the real power is using the API inside your test setup hooks. Then, three weeks later, your CI build fails
before(async function() { // Ensure drivers are installed (safe to call every time) await install(); // Start the server server = await start(); console.log('Selenium ready'); }); They will connect automatically
// setup.js const { start, install } = require('selenium-standalone'); let server;
Try selenium-standalone and reclaim your sanity. Have a tip for managing WebDriver in large monorepos? Let me know in the comments below!