Static and Dynamic Testing

According to one of the Testing Principles "Early Testing is very important" in SDLC. The important question that arises here is that when application or project is not even completed how one can start Testing.

This gives us an opportunity to understand the two major types of Testing:

-Static Testing

-Dynamic Testing

Static Testing

Static testing includes testing without execution of the application or running the test cases. Static Testing includes review of the documents that form the part of the development e.g. of such document include SRS (Software Requirement Specification).

Code review is also a part of Static Testing. On coding Level several static techniques can be used at initial stage

-Static Code analysis

-Coding Standards

-Code metrics

Review forms a major part of Static Testing:

On Broad level Review are of two types:

-Informal Review-Informal Review is the type of static testing which do not require any formal notification or documentation for review to take place .e.g. a developer writes a code and asks his Peer or colleague to have a look at it.

-Formal Review-Formal Review is a type of Static Testing which requires a proper notification and documentation before a review could actually start.

Types of Formal Review:

1) Walk through-

2) Technical Review

3) Inspection

Phases for a formal Review Process:

-Planning

-Kick Off

-Preparation

-Review Meeting

-Rework

-Follow up

Dynamic Testing

Dynamic Testing includes actual testing of the application under development, execution of the test cases form the integral part of this type of testing.

To design these test cases which would be used for execution some of the methods are:

A) Black Box Testing

-Equivalence Partitioning

-Boundary Value Analysis

-Decision Table

-State Transition

-Use case Testing

B) White Box Testing

-Decision Coverage

-Branch Coverage

C) Exploratory Testing

D) Experience Based Testing