static analysis
Checking code for problems by reading it, without running it.
In more detail
Linters and type checkers are the most common static analysis tools, and they run in seconds on every change. When imports are written as fixed statements, tools can also map which modules use which, catch missing exports and remove unused code. It usually runs beside unit tests before a deployment gate.
Related terms
- linter — A tool that reads code or configuration without running it and flags likely mistakes and style problems.
- unit test — An automated check of one small piece of code, such as a single function, that runs quickly and on its own.
- ECMAScript modules — The standard JavaScript module system, written with import and export statements, used by browsers and modern tools.
- tree shaking — Removing code that is exported but never imported from the final bundle, so less code is shipped.
Taught in
- Design Systems Architecture: Foundations, Layers & Taxonomy — Design Systems & Component Engineering
- Test First, DevOps And Shift Left — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Static Testing: Finding Defects Without Running Anything — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Risk: Likelihood, Impact And Risk-Based Testing — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Monitoring, Control And Test Reports — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Defect Reports That Get Fixed — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Test Tools And The Truth About Automation — ISTQB Certified Tester Foundation Level (CTFL v4.0) Exam Prep
- Native Module Systems: ESM Loader Hooks vs CommonJS — Node.js Internals & Backend Services