Static Analysis

Static Analysis definition

• Static analysis, also called static code analysis, is a method of computer program debugging that is done by examining the code without executing the program.

Static Analysis purpose

• One the primary uses of static analyzers is to comply with standards.
• So, if you’re in a regulated industry that requires a coding standard, you’ll want to make sure your tool supports that standard.

Static Analysis time

• Static code analysis is performed early in development, before software testing begins :
  • For organizations practicing DevOps, static code analysis takes place during the “Create” phase.

Static Analysis tools benefits

• The best static code analysis tools offer speed, depth, and accuracy :
  • Speed
    • It takes time for developers to do manual code reviews.
    • Automated tools are much faster.
    • Static code checking addresses problems early on.
    • And it pinpoints exactly where the error is in the code.
    • So, you’ll be able to fix those errors faster.
    • Plus, coding errors found earlier are less costly to fix.
  • Depth
    • Testing can’t cover every possible code execution path.
    • But a static code analyzer can.
    • It checks the code as you work on your build.
    • You’ll get an in-depth analysis of where there might be potential problems in your code, based on the rules you’ve applied.
  • Accuracy
    • Manual code reviews are prone to human error, automated tools are not.
    • They scan every line of code to identify potential problems.
    • This helps you ensure the highest-quality code is in place — before testing begins.
    • After all, when you’re complying with a coding standard, quality is critical.

Static Analysis practice

• Static Analysis is performed in a non-runtime environment.
  • Typically, a static analysis tool will inspect program code for all possible run-time behaviors and seek out coding flaws, back doors, and potentially malicious code.
  • Static code analysis is a method of debugging by examining source code before a program is run.
  • It’s done by analyzing a set of code against a set (or multiple sets) of coding rules.

More informations for Scrum Testing

More informations for the Scrum PSD certification here.