Static testing is performed on the software/requirement documentation.
Dynamic testing is performed on the build that is coded.
Most verification techniques are static tests.
Feasibility Reviews – Tests for this structural element would verify the logic flow of a unit of software.
Requirements Reviews – These reviews verify software relationships; for example, in any particular system, the structural limits of how much load (e.g., transactions or number of concurrent users) a system can handle.
Test Document Reviews - These reviews verify the test scenarios and cases coverage that are developed matching with requirement
Most validation tests are dynamic tests. Examples of this are:
These tests verify the system functions properly; for example, pressing a function key to complete an action.
The system runs tasks that involve more than one application or database to verify that it performed the tasks accurately.
The tests simulate operation of the entire system and verify that it ran correctly.
This real – world test means the most to your business, and unfortunately, there’s no way to conduct it in isolation. Once your organization’s staff, customers, or vendors begin to interact with your system, they’ll verify that if functions properly for you.