Saturday, July 31, 2010

Static Testing

Static testing is a form of software testing where the software isn't actually used. This is in contrast to dynamic testing. It is generally not detailed testing, but checks mainly for the sanity of the code, algorithm, or document. It is primarily syntax checking of the code and/or manually reviewing the code or document to find errors. This type of testing can be used by the developer who wrote the code, in isolation. Code reviews, inspections and walkthroughs are also used.

From the black box testing point of view, static testing involves reviewing requirements and specifications. This is done with an eye toward completeness or appropriateness for the task at hand. This is the verification portion of Verification and Validation.

Even static testing can be automated. A static testing test suite consists of programs to be analyzed by an interpreter or a compiler that asserts the programs syntactic validity.

Bugs discovered at this stage of development are less expensive to fix than later in the development cycle.[citation needed]

The people involved in static testing are application developers, testers, and business analysis.

There are some Standard Tools used in the Software Industry like.

QAC/QAC++/MISRA , LDRA, some Internal Tools etc.

Each of them has a configuration file which has to be configured depending upon Compiler/Machine/Host and Code base.

1 comment:

Suseela Susiee said...



Great and useful article. Creating content regularly is very tough. Your points are motivated me to move on.


SEO Company in Chennai