developer.chrome.com
developer.chrome.com copied to clipboard
Add smoke-tests after builds and prior (production) deploys
Before actually pushing a build to production we should perform smoke-tests which automatically go over well-known click paths using a headless browser, matching response codes and parts of content with snapshots and fail deploys if results do not match.