Static testing

Static testing is a method of software testing that examines the artifact without executing the source code. Static testing can be used to test or verify source code, design documents, functional and non functional specifications and requirement.

According to ISTQB, Testing of a component or system at specification or implementation level without executing of the software.

Static testing is not magic and not replacement for dynamic testing, but all software organization should consider using reviews in all major aspects of their work including requirement, design, implementation testing and maintenance.
It diagnose the all source code and done before compilation.

It is verification method that used to prevent the bug in early phase itself.

It start early in the life cycle, detecting defects, evaluation by team and early feedback on quality issues can be established.

It finds syntax errors and source code and achieves 100% statement coverage.

It is cost effective.

It is tested manually or automatic tool but they are not executed.

Advantage of static testing -:
– Help to improve quality and productivity
– Rework cost is low and relatively cheap improvement
– Scope to exchange of information due to evaluation
– Achieve more statement coverage

Types or techniques of static testing -:
1. Code review
2. Code walk-through
3. Code inspection
4. Static analysis

Example -:
Review, meeting, recording and inspection
Review -: Examine the process to find out defect

Meeting -: It is held to review the process before, in process, nearly completion and after completion of process.

Recording -: Record all issues raised and generate report for improvement.

Inspection -: Inspect whole source code to discover anomalies.

Leave a Reply