Summit Report: Linting best practices
summary
Demonstrates using eslint and polylint to catch common element errors before runtime, and using web-component tester plus the test-fixture element to run unit and integration tests against a concrete Paper-Checkbox example. Shows how to wire tests into Travis CI and Sauce Labs so every commit runs across multiple browsers, exposing cross‑browser failures early. Claims this setup reliably prevents regressions and reports failing browsers during CI runs.
AI-written summary · about
chapters (3)
related talks
35mTesting in Frontend World
29mBuilding Accessibility Testing into Your Workflow
30mWait, before you write your next test...
26mModern Testing Practices in Frontend Applications
42mWait, I have to test the front end too?
49mWait, I have to test the front end too?
31mHow to do Good Without Doing Anything
53mWait, I have to test the front end too?
