What is Static Testing? Static testing is the testing of the software work products manually, or with a set of tools, but they are not executed. It includes the reviews and provides the overview of how they are conducted.
The primary objective of static testing is to improve the quality of software products by assisting engineers to recognize and fix their own defects early in the software development process.
Most static testing techniques can be used to ‘Test’ any form of the document including source code, design documents and models, functional specifications and requirement specifications.
Static testing is the form of software testing where you do not execute the code. This technique could be called non-execution technique. It is primarily syntax checking of the code or manually reviewing the code, requirements documents, design documents etc. to find errors.
From the black box testing point of view, static testing involves reviewing requirements and specifications. This is the verification portion of Verification and Validation.
The fundamental objective of the static testing technique is to improve the quality of the software products by finding errors in early stages of software development life cycle.
Following are the main Static Testing techniques used:
Static Code Analysis