[slinkanand]

Static analysis also involves code complexity metrics, which is very important. In this type of analysis you can imploy complexity metrics such as Cyclomatic Complexity (gives you an idea of how maintainable the code is).

What you call Glass Box is also known as White Box testing methods. And these can involve code execution, which is a dynamic analysis technique. An example is Function/Module Logic Branch coverage. When you execute the code within the module/function (white box) can all the logic paths (branches) be reached at least once. There are other types of dynamic analysis methods that are "white" box.

Integration testing can also be a "white" box type test. You can exercise the parameter lists of the functions/modules in the compiler. This can be done to exercise intra-functionally (within the same code module with local functions) and inter-functionally (calls between different modules with public functions). Also, you can exercise the code to do Call-Called pair analysis.

[naveen_p25]

Hi,

In Static Testing we are not going to run the application or build for the correctness and completeness of requirements. It contains the Testing Methods like Inspections, Walkthroughs, Meetings and Reviews.

Where as in Dynamic Testing we will run the application or build for the validation of requirements. It contains the Testing Methods like Functionality Testing, Usability Testing and Performance Testing.

Regards,
Naveen

[slinkanand]

Hi naveen,

ur usage for the above is absolutely correct, my answer was eloborated one..ur answer to the above question is simple to understand..

bye..

[AjayKumar.Kataram]

thanks to all..

[aforarun]

thanks to all... good info...