What are Test Cases?

Test cases consist of different set of conditions and inputs that are used to ascertain expected results or judge functional capability of a system. Rational Unified Process (RUP), a software development methodology, recommends creating test cases with both positive and negative perspective. Test cases help in determining if the system works as it is intended to work in a given situation. Testing is an important activity to ensure software quality.

Structure of a Test Case

A formal written test case would have 5 columns:

• Test Conditions
• Operator Action
• Input Specification
• Expected Output
• Actual Output

A system tester or the testing team as a whole have the responsibility of filling in data for these columns after executing the test case. Eventually, the data can be used to understand how the system responds to user actions and rectify if necessary.

It is also necessary for a tester to record the following parameters during the testing process:

• Purpose of the test
• Software and Hardware requirements (if any)
• Configuration requirements
• Description on how to perform the test

Measuring Test Execution Complexity

Test case specifications describe tests in terms of the test precondition, list of testing steps and the test post condition.
We can measure the complexity of test cases based on their specifications. To measure the execution complexity of a test case, we perform the activities given below for each test defined in its specification:

• Evaluate the level of complexity for performing the test step based on the functional and nonfunctional characteristics of the system exercised by it.
• Rate the level of execution complexity in execution points.

To arrive at a test execution complexity figure, we have to sum up all the execution points of each of its steps.