Static code analysis
Examining code, or a representation of it, without running the application’s workflows to do so.
What is static code analysis?
Static code analysis examines program code or a representation derived from it without exercising the business workflow as a runtime test would. Depending on the tool, it can find suspicious data paths, possible errors or rule violations. The analysis tool itself does run. Included files, languages and rules determine the scope of its findings.
In a fictional portal, analysis might flag a variable used before assignment. The team checks the finding in context and records which code was examined. A report without warnings proves neither correct user journeys nor complete security. Excluded files and missing models can leave gaps. Static analysis therefore complements business tests and code review rather than automatically replacing them.
Sources
Related terms
- Typing in programmingHow a programming language handles kinds of values and suitable operations.
- LinterA tool that examines code for particular problems using configured rules.
- Unit testA focused check of a small, defined part of software, such as a rule or function.
- Code reviewFocused examination of a source change for design, behaviour, clarity and appropriate checks.
- Contract testA test of agreed messages between a consumer and a provider at an application interface.
- Test coverageThe share of an explicitly defined set, such as executable statements or requirements, that has been tested.
Your project with ASES
Describe your project to us. We will get back to you with an initial assessment.