Static testing is a form of software testing where the software isn't actually used. This is in contrast to dynamic testing

Dynamic testing

Dynamic testing is a term used in software engineering to describe the testing of the dynamic behavior of code. That is, dynamic analysis refers to the examination of the physical response from the system to variables that are not constant and change with time...

. 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 review

Code review

Code review is systematic examination of computer source code. It is intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers' skills...

s, inspection

Software inspection

Inspection in software engineering, refers to peer review of any work product by trained individuals who look for defects using a well defined process...

s and walkthrough

Walkthrough

A walkthrough may refer to one of the following topics:* Strategy guide* Software walkthrough* Tutoring* Rehearsal* Audit* Virtual tour-See also:* Classroom walkthrough* Cognitive walkthrough* List of gaming topics...

s are also used.

From the black box testing

Black box testing

Black-box testing is a method of software testing that tests the functionality of an application as opposed to its internal structures or workings . Specific knowledge of the application's code/internal structure and programming knowledge in general is not required...

 point of view, static testing involves reviewing requirement

Requirement

In engineering, a requirement is a singular documented physical and functional need that a particular product or service must be or perform. It is most commonly used in a formal sense in systems engineering, software engineering, or enterprise engineering...

s 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

Verification and Validation

In software project management, software testing, and software engineering, verification and validation is the process of checking that a software system meets specifications and that it fulfills its intended purpose...

.

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

Software bug

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways. Most bugs arise from mistakes and errors made by people in either a program's...

 discovered at this stage of development are less expensive to fix than later in the development cycle

Software development process

A software development process, also known as a software development life cycle , is a structure imposed on the development of a software product. Similar terms include software life cycle and software process. It is often considered a subset of systems development life cycle...

.

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

Sources

• Kaner, Cem; Nguyen, Hung Q; Falk, Jack (1988). Testing Computer Software (Second ed.). Boston: Thomson Computer Press. ISBN 0-47135-846-0.
• Static Testing C++ Code: A utility to check library usability