How to Create Test Cases

In this post we will discuss about How to Create Test Cases. One of the major points to start with testing of any solution or application is to first create test cases for the same. Let’s see what test cases are.

What are Test Cases?

One of the common question which arises in mind while start testing application. Test case is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works completely..

This is a good practice to work on test cases before starting with actual testing. It also comes under the testing workflow.

How to Create Test Case

What are The Use of Test Cases?

  1. Test cases are prepared to verify that the product is build as per requirement defined by our organization or client. It also helps the tester to identify whether all functionality has been covered or not.
  2. While creating test pan and test strategy document, Manager Need to define test cases inside the document.
  3. Test cases could be a only key to understand process of entire solution.

Test Case Template:

Template will contain various elements to be defined while creating test cases. Companies must be using some tool to define test cases sometimes companies use their own management tool created by them in organization itself. Some of the management tolls available in market are:

  1. Bugzilla
  2. TFS (Team Foundation Server)
  3. Quality Center

 

Refer below test case Template:

Test Suite ID ID to identify test suite
Test Case ID

 

ID to identify test case
Test Description

 

Contains description of test case
Requirement Covered

 

Reference of requirement defined in BRD or SRS
Test Precondition

 

Defined resources need to be installed in system before starting with actual testing.
Steps

 

Series of steps defined in the form of Step1, Step2.
Test Data

 

Define data required for testing.
Test Procedure

 

Step by step procedure to execute tests.

 

Input

 

Values need to input while conducting test.

 

Actual Result

 

Actual result of the test after test execution.

 

Expected Result

 

Expected result defined in requirement after execution.
Priority

 

Priority of test case should be defined. High, Low and Moderate.
Test Status

 

Pass or Fail, if test is not executed status will be “NOT EXCEUTED”.
Remarks

 

If any other comments are there could be defined here by tester.
Creation Date

 

Date of creation of test case.
Executed Date

 

Date of execution of test case.

 

Created By

 

Name of the tester who has created the test.

Define Environment in which test has been executed; Need to define Hardware, Software and Network compliance.

Test Environment.

 

Sample Test Case:

Test Suite ID

 

TS_001

 

Test Case ID

 

TC_001

 

Test Description

 

Test to verify that authentic user should able to login into the application

 

Requirement Covered

 

Req001

 

Test Precondition

 

User should be authorized to login inside application.

 

Test Precondition

 

User should be authorized to login inside application.

 

Steps

 

Step 1

 

Test Data

 

User Id: admin
Password: Pass@1234 
Test Procedure

 

1. Open application with “Defined URL”.                                                                                                           2. Enter user ID in user id textbox.

3. Enter Password in password text box.

 

Input

 

1. Enter User Id
2. Enter Password                                                                                   3. Click on ‘Submit’ button 
Actual Result

 

Authenticated user, After input system redirecting user to home page.
Expected Result 1. System should display the Login dialog with
2. User id (edit box) (label)
3. Password (edit box) (label)
4. Submit, Cancel, Help buttons (enabled)
and Company Logo
Priority

 

High

 

Test Status

 

Pass

 

Remarks

 

Optional Remarks

 

Creation Date

 

22/08/2017

 

Executed Date

Created By

 

23/08/2017

Marc Jonathon

Test Environment.

 

OS: Mac                                                                                                      Browser: Google chrome 10

 

Things to Remember:

  1. Test cases should be easily understood, try to not write complicated test cases.
  2. Always refer requirement document thoroughly before writing test cases.
  3. Test cases should be accurate, Traceable and reusable.
  4. Test cases should be defined in such a way that they can be used over and over.
  5. Ensure that both negative and positive scenarios should be covered.
  6. Don’t make any changes in fields defined in requirement. Forms, Fields etc.

Leave a Reply

Your email address will not be published. Required fields are marked *