Tomorrow's Chrome runs your smoke suite tonight

The regression you'll ship on Tuesday is already visible in Chrome Beta today. Nobody on your team runs Beta.

A cron entry does, nightly. It calls /start?browser_id=1&chromiumVersion=beta; the call blocks while the build downloads, then the instance is up. The smoke suite runs through /browse and /eval against staging, and GET /console?browser_id=1&type=error collects what broke. A second entry does the same with chromiumVersion=canary. A third restarts an instance with browser=firefox, because the engine is a parameter of /restart.

Three browsers nobody installed, exercised every night on the box staging already runs on. The morning report is the console errors that don't exist in stable yet.

Cross-browser testing used to be a vendor with a per-minute meter. Now it's three cron lines. You stop finding out what Chrome changed from your users.