Test case ID - The test case id must be unique across the 
application 
Test case description - The test case description must be 
very brief.
Test prerequisite - The test pre-requisite clearly 
describes what should be present in the system, before the 
test can be executes.
Test Inputs - The test input is nothing but the test data 
that is prepared to be fed to the system.
Test steps - The test steps are the step-by-step 
instructions on how to carry out the test.

Expected Results - The expected results are the ones that 
say what the system must give as output or how the system 
must react based on the test steps.
Actual Results – The actual results are the ones that say 
outputs of the action for the given inputs or how the 
system reacts for the given inputs.
Pass/Fail - If the Expected and Actual results are same 
then test is Pass otherwise Fail.
The test cases are classified into positive and negative 
test cases. Positive test cases are designed to prove that 
the system accepts the valid inputs and then process them 
correctly. Suitable techniques to design the positive test 
cases are Specification derived tests, Equivalence 
partitioning and State-transition testing. The negative 
test cases are designed to prove that the system rejects 
invalid inputs and does not process them. Suitable 
techniques to design the negative test cases are Error 
guessing, Boundary value analysis, internal boundary value 
testing and State-transition testing. The test cases 
details must be very clearly specified, so that a new 
person can go through the test cases step and step and is 
able to execute it. The test cases will be explained with 
specific examples in the following section.