Dynamic Black Box and Dynamic White Box tesing
With some discussion with my Tester friends I came to know about a term "Dynamic White Box Testing"....I verified it and found it in a book and some Glossary too....
I believe from what I have read is that WhiteBocx Testing are more of Verification activities...like code reviews, walkthrus, Inspections, coverage analysis...Logical Error finding, syntax testing etc...
And I doubt on the need to Execute the code for these procedures..which makes this testing static
I am doubtful about term and method "Dynamic White Box testing".
Is it related to tracing a execution path in the code? Or the method in which Testers impart error in the code and check whether it is detected or not...
Waiting eagerly to clear my doubts....
PS: Dear moderators please excuse me for posting in this section as I could relate Dynamic Testing only to functional testing and Dynamic WhiteBox testing is new term I heard.
Re: Dynamic Black Box and Dynamic White Box tesing
Hi Amit Dharkar,
Split the terms in two: you have static and dynamic technics, you have black box and white box techniques.
On black and white box testing, there is currently a discussion going on in this forum.
Static testing: you do not execute the code. We are talking about inspections, walktroughs, etc. Even a compiler can be considered static testing as it gives you syntax errors but does not execute the code.
Dynamic testing: you execute the code
So you can have static and dynamic white box, and static and dynamic black box.
You also mentioned "coverage analysis". I wouldn't really put it specifically under any of the above. It is more an analysis of what the application does compared to what the tests cover. So you can base your coverage analysis on information you get from any test technique. E.g. requirements coverage can be analysed using black box techniques while condition coverage of a module might be easier analysed using white box techniques.