Test Case Design

Test Case ID: It is unique number given to test case in order to be identified.Test description: The description if test case you are going to test.Revision history: Each test case has to have its revision history in order to know when and by whom it is created or modified.Function to be tested: The name of function to be tested.Environment: It tells in which environment you are testing. Test Setup: Anything you need to set up outside of your application for example printers, network and so on.Test Execution: It is detailed description of every step of execution.Expected Results: The description of what you expect the function to do. Actual Results: pass / failed If pass - What actually happen when you run the test. If failed - put in description of what you've observed.
Test Case Design Techniques:
Black box techniques: Boundary value analysis, Equivalence partitioning. White box testing techniques are Branch Testing, Condition Testing.

Equivalence Partitioning:
Is the process of taking all of the possible test values and planning them into classes (groups). Test cases should be designed to test one value from each group. So that it uses fewest test cases to cover maximum input requirements.

Boundary Value Analysis:This is a selection technique where the test data lie along the boundaries of the input domain.

Branch Testing:
In branch testing, test cases are designed to exercise control flow braches or decision points in a unit.


Characteristics of a Good Test: They are: likely to catch bugs, no redundant , not too simple or too complex. Test case is going to be complex if you have more than one expected results.