gopal

• Jan 24th, 2007

 

Code-Coverage Analysis gives you an insight into what parts of the production code are executed when the tests are run.

vel

• Feb 6th, 2007

 

This a purly a white box testing so surly developer wants to test that.

Minty

• Feb 7th, 2007

 

But how do you test your tests? How do you find code that is not yet tested -- or, in other words, not yet covered by a test? How do you measure testing completeness? All these questions are answered by a practice called Code-Coverage Analysis. Code-Coverage Analysis gives you an insight into what parts of the production code are executed when the tests are run.Code coverage analysis is a structural testing technique. Structural testing compares test program behavior against the apparent intention of the source code. This contrasts with functional testing which compares test program behavior against a requirements specification. Structural testing examines how the program works, taking into account possible pitfalls in the structure and logic. Functional testing examines what the program accomplishes, without regard to how it works internally. The basic assumptions behind coverage analysis tell us about the strengths and limitations of this testing technique.Any additions to the anwers r welcomed :)

nikhilk265

 Profile Answers by nikhilk265 

• Nov 19th, 2007

 

Code coverage testing is white box testing technique. This can be done by developer if it is unit level or tester if it is other than unit level.
Some tools like Jcover,Junit which are used for coverage testing which shows how much code has been covered.The part which has not covered may have logical errors.