Static Testing

This article explains the details about static testing.

The verification activities fall into Static Category. We’ll have a checklist during verification process to check whether we are following the organizational standards. These standards can be applicable for coding, Integrating and deployment. 

The following are the static testing methodologies.

       Review , Inspection, Walk through

Static testing is a type of software testing in which the software will not be actually used. It’s just opposite to Dynamic Testing. In general, it’s not a detailed testing mainly checks the code syntax, algorithm and document. The main purpose of this testing is to make sure that there is no syntax or document errors. This type of testing is mainly used by the developer who wrote the code. He can use these type of testing in an isolation environment. He may use this type of testing for code reviews and inspections.

From the testing type view, this can be used for reviewing the requirements or specifications. This is the verification part of verification and validation. Bugs discovered during this stage is less expensive than fixing in other development cycles.

Static code analysis is performed on the computer software without executing its functionality. It means the portion of the code will be reviewed for checking the syntax and common errors.

A growing commercial use of static analysis is in the verification of properties of software used in safety-critical computer systems and locating potentially vulnerable code.

Posted in: Static Testing