Who Guards the Guards? – Finding Bugs in Your Tests
summary
Three concrete testing bugs and how static analysis finds them: tests that silently have no assertion, expectations written with swapped actual/expected values, and incomplete expectations that never call an assertion, all shown against Mocha/Chai examples from Kibana, Angular and eslint. VS Code with the SonarLint extension flags the exact lines and messages; SonarQube/SonarCloud run the same rules in CI, highlighting the failing pattern and the minimal code change needed to make the test meaningful.
AI-written summary · about
chapters (4)
related talks
28mTreat test code as application code by linting
58mSecurity Static Analysis - Avoiding an Angry Mob of Engineers
34mFantastic Bugs and Where to Find Them
19mFunctional Testing of GraphQL APIs: Simple Checks That Catch Real Bugs
42mThe top 5 JavaScript issues in all our codebases
55mSquash Bugs with Static Analysis
27mFantastic Bugs And Where To Find Them by Iris Schaffer (Eng) | JSConfAM19
41mTesting done right: From bugs to brilliance