Static Testing Phase

The static testing phase starts with all team members reviewing documentation for thoroughness and appropriateness for the end goal of the product.

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
Functional Specifications
Design Documents or Mockups
Prototypes
Prototype Specifications
Test Plans

Test Cases
Manual or Automated Test Scripts
Unit Test Cases
System Use Cases
Field Dictionaries
Help Documents or Training Guides

If you’re part of the large group that feels static testing is too expensive to implement, or if you just don’t know how to get started, give QA Mentor a call to talk about our unique Static Testing and Inspection Services. With QA Mentor’s help in this phase, you can achieve full test coverage with lower production defects rates, shorter dynamic testing cycles, and an amazing ROI.

Other Test Phases

Module & Unit Testing Phase

Module & Components Integration Testing Phase

System & System Integration Testing Phase

User Acceptance Testing Phase

Production Verification & Acceptance Testing Phase