Static Testing Phase

Static Testing Phase

Static testing is the first phase in software quality assurance, but unfortunately nearly 80% of the companies out there don’t perform this vital step.

Why You Should Static Test

Eliminate defects before they’re coded

Identify usability issues

Find deviation standards

Defects fixed more efficiently

Defect costs reduced

Near 100% coverage

More effective than dynamic testing alone

In this phase, defects are much easier to identify than they are when in production.

Studies have shown that nearly half of the defects found in dynamic testing could have been identified and fixed in a proper static testing phase.

Team members review documentation for thoroughness

Formal and informal reviews are completed for all documentation

Reviews are done by developers, QA, BAs, Managers

Reviews can be walkthroughs, technical reviews, or formal inspections

Some types of documentation that are commonly reviewed are:

Business Requirement Specifications

Test Cases

Functional Specifications

Design Documents or Mockups

Unit Test Cases

Prototypes

System Use Cases

Prototype Specifications

Field Dictionaries

Test Plans

Help Documents or Training Guides

Manual or Automated Test Scripts