Static Code Analysis
Automated examination of source code for errors and risks without running the program.
Static code analysis automatically examines source code for possible errors, security risks and violations of coding conventions without running the program. Tools such as PHPStan, ESLint or SonarQube evaluate the structure of the code and typed signatures and report anomalies such as unreachable code, wrong types or unsafe function calls.
Because the analysis works without a runtime environment, it also finds problems that would only occur in rare program paths and that classic tests easily miss. It does not replace tests, however, but complements them with a different class of errors.
What Provimedia uses it for
Provimedia runs static code analysis automatically on every commit in order to find structural errors before delivery.
Want to use Static Code Analysis for your project?
In a free conversation, let's find out how we can implement this for you.
More from Software quality
Clean Code
Guiding idea for code that is designed to be understandable for humans and not just for the compiler.
Learn moreCode Review
Systematic examination of code by other developers before it is merged into the main branch.
Learn moreCode Smell
Conspicuous pattern in code that is not necessarily wrong but points to a deeper problem.
Learn moreDefinition of Done
Written list of criteria agreed in the team that a task must meet in order to count as done.
Learn moreLinting
Automated checking of code for style and formatting errors according to fixed rules.
Learn moreMutation Testing
Technique that deliberately introduces small errors into the code to check how meaningful the tests are.
Learn moreQuality Gate
Check stage in the development pipeline that lets a change pass only if fixed criteria are met.
Learn moreRefactoring
Targeted restructuring of existing code without changing its external behavior.
Learn more