How to Design an Effective Test Case?

A test case caters the need to test an aspect of a feature completely in detail. A test case is little different from test plan, as it shows how to perform a particular test, whereas test plan shows what to test. A test plan includes a number of tests, for which you need to develop a test case, i.e. a test case for each test.

While performing testing, the designing of test cases takes place at a later stage, i.e. after developing the test lab, as shown below.

Create a test plan

|

Plan the test lab

|

Design the test lab

|

Develop the test lab

|

Design test cases

|

Conduct tests

|

Use the lab after deployment

While designing a test case, you must consider and include the following:

It is very important to understand the technology being tested. So, a test case should be preferably written by someone who is good at it. Moreover, peer review is equally important.

There are a number of ways of writing test cases; ranging from detailed steps to general description. A detailed test case includes the details of how to perform a test, whereas a descriptive test case also includes the data to be used. The descriptive test cases help in determining pass and fail criteria and are preferred by most of the organizations. However, they are unlikely to be preferred when it comes to automating. Here, detailed test case holds the edge, as they are easier to automate, but takes a lot of time.

Test Case Design

ID: Unique number given to a test case

Description: Detail of the test case

History: Creation and modification details

Function: Name of the function to be tested

Environment: Environment in which the test will take place

Setup: Any setup outside the application

Execution: Details of each step to be executed

Expected Results: Expected functionality

Actual Result: Pass/Fail

You might also like: How to Manage Test Cases with Test Rail?

SHARE THIS

Get A Free Quote