Testcasing is a Modular approach.

Why i used this title , just for the fact that i am talking about Test case and did not want to concrete on Test case writing as it would mean different.

Modularity is maintained in Programming and were is it followed in Test case writing and how are we seeing this approach in Test. Well I need to mention this a software Product or a Piece of enhancement that goes in to a live system under goes testing for sure , ans any such thing will have a set of rules or Business logic i call it salient features. when we list down the salient features of a product as x,y,z and so on were every x has 1...n variations and y has 1...n variations ...so on, If we take a general peek into it , If we make X and Y as different modules and start writing cases w.r.t each feature and continue to do so for other features we can call it a modular approach.

I have below highlights for this approach.

1. when you start for X and complete all the variations for this feature [ 1.....n] . i would say you have a coverage done for 1 salient feature.

2. When you are in the process of writing for Y you may see some common cases as in X which would have some re usability and by reducing redundancy you can jump to next feature.

3. By the time you start and reach the last salient feature i would say you will have accomplished the Test case writing for a Product or a Change request avoiding redundancy and having complete coverage.