Test Case

A test case is a document that describes an input, sequence of actions and the expected output, in order to determine a product/system/applications requirement is correctly working or not. A test case should have the following information

a) Test case number

b) Test case name/title

c) Objective

d) Test conditions/setup

e) Input data requirements and sequence of steps

f)  Expected result

(Note1) Always prepare test cases from use cases it’s a good practice.

(Note2) Preparation of test cases should be started once SRS & design documents are

              Frozen. This type of approach is changed depending on the life cycle model

  That is selected for the execution for the project.

(Note3) IEEE – is a standard(s) for writing test cases.

Software Testcase Preparation

The primary objective of test case(s) preparation is to see weather requirements of the application/system/product are fully covered or not. Test Cases can be prepared from the use cases. If use cases or not available then, test cases can be Prepared from SRS & design documents.

Test cases are prepared using following techniques

Boundary value analysis

A test data selection technique in which values are chosen to lie along data extremes.  Boundary values include maximum, minimum, just inside/outside boundaries, typical values, and error values. The hope is that, if a systems works correctly for these special values then it will work correctly for all values in between.

Equivalence class path: -

Is a technique where test cases are designed with a valid and invalid range of Values Range is decided with reference to SRS. Examples are

a) Range

b) Set

c) Number of inputs

d) Exists/constraint

Error guessing

Is a test case design technique where the experience of the tester is used to guess what faults might occur and to design test cases specifically to expose them.

Few of the techniques are:-

a) Null input.

b) Long input.

c) Random input.

d) Almost correct input.

e) Spaces in strings.

f) Quoted strings.

g) All CAPS.

h) Negative numbers.

i) Special characters

(Note) All the above mentioned techniques for error guessing are valid if SRS has a Limitation(s) on it.