Test Case Design

We look at a list of methodologies used in the process of designing test cases. The obvious questions that folks new to / not too familiar with testing tend to ask is ... why Test Case Design and why all of these methodologies ?

The answer to the why is based on a fundamental premise of Software Testing i.e. "Complete" or "100%" testing is not possible.

Yep, sounds a little negative to the uninitiated, but thats the fact. The derivative of the above statement implies that "all" Testing is incomplete, although the degree of incompleteness varies. In reality, testing is performed within various limitations and boundaries defined by variables such as resources, time, cost, etc.

Given these constraints, Testers need to come up with a set of Test Cases that has the highest probability of unearthing the greatest number of defects. This is where Test Case Design plays a significant role.

In this post, we'll keep things short and only take a really quick, very high-level view of the methodologies. These cover both Black and White box techniques. Here they are ...

1) Equivalence Partitioning
2) Boundary Value Analysis (BVA)
3) Cause-Effect Graph / Decision Table
4) Error Guessing
5) Statement Coverage
6) Decision Coverage
7) Condition Coverage
8) Combination of Decision & Condition Coverage
9) Multiple Condition Coverage
 
We'll look at some of the above in upcoming posts. For now, if you are really keen to deep dive, Googling might be a good idea or better still grab a book on Software Testing and let the concepts soak in. One other thing since we are on this subject of Test Case Design ... while it sure is important to test to check if the program does what its supposed to do, its also very important to test to check if the program does what its not supposed to be doing ...


Add to Technorati Favorites | Slashdot   Slashdot It! | Submit to del.icio.us

Comments:

Hello more interesting artikel. I can only divide theirs knowledge

Posted by stefan on September 03, 2007 at 08:47 PM IST #

Thanks very much for your feedback, Stefan.

Posted by John Morrison on September 04, 2007 at 01:41 AM IST #

Yup, negative test cases are as important as the positive ones. Some naive users may key in some data that can crash the product :)

Posted by Kalyan on September 05, 2007 at 03:24 AM IST #

Thanks for the feedback, Kalyan. You are very right about negative testing ...

Posted by John Morrison on September 05, 2007 at 05:20 AM IST #

For some evaluation board manufacture that produces embedded processor board(pxa320, etc.) acceptance testings are not done by a group of end-users.

Posted by Paul Y.K. Lee on October 11, 2007 at 12:57 AM IST #

Thanks for the added insight, Paul Y.K. Lee. Very much appreciated.

Posted by John Morrison on October 11, 2007 at 02:50 PM IST #

Flirt und flirten in Chatworld 14 channels zum flirten - kennenlernen und verlieben Themenchats und Events 24 Stunden am Tag

Posted by chatodalari on April 08, 2009 at 09:00 PM IST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

John Morrison

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today