SOTWARE TESTING

Test Case Template

Course Instructor: IMAD

REHMAN
What is Test Case?

 A Test Case is defined as a set of actions executed to verify a particular feature or functionality
of the software application.
 A test case contains:

 A sequence of Steps describing actions to be performed,

 Test data to be used

 An expected response for each action performed.

 Test Cases are written based on Business and Functional/Technical requirements

 There can be 1:1 or 1:N or N:1 or N:N relationship between requirements and Test cases
Test case (cont…)

 Construction of Test Cases also helps in Finding issues or gaps in the

requirements .
 As Test Case construction activity would make tester to think through
different possible Positive and Negative scenarios.
 It is test cases against which tester will verify the application is working as
expected.
 Number of test cases to be created depends on the size, complexity and type
of testing being performed
Login Page
Test cases for a web page

 Testing without entering any username and password

 Test it only with Username
 Test it only with password.
 User name with wrong password
 Password with wrong user name
 Right username and right password
 Cancel, after entering username and password.
 Enter long username and password that exceeds the set limit of characters.
 Try copy/paste in the password text box.
 After successful sign-out, try “Back” option from your browser. Check whether it
gets you to the “signed-in” page.
 The format of Standard Test Cases
Test Case ID Test Scenario Test Steps Test Data Expected Actual Pass/Fail
Results Results

TU01 Check 1. Go to Userid = User should As Expected Pass

Customer site www.abc.c admin Login into an
Login with om Password = application
valid Data 2. Enter UserId pass123
3. Enter
Password
4. Click Submit

TU02 Check 1. Go to Userid = User should As Expected Pass

Customer site www.abc.c admin not Login into
Login with om Password = an application
invalid Data 2. Enter UserId pass
3. Enter
Password
4. Click Submit
Best Practice for writing good Test Case

 Test Cases need to be simple and transparent

 Create test cases that are as simple as possible. They must be clear and concise as the author of the test
case may not execute them.
 Use assertive language like go to the home page, enter data, click on this and so on. This makes the
understanding the test steps easy and tests execution faster.

 Create Test Case with End User in Mind

 The ultimate goal of any software project is to create test cases that meet customer requirements and is
easy to use and operate. A tester must create test cases keeping in mind the end user perspective

 Avoid test case repetition.

 Do not repeat test cases. If a test case is needed for executing some other test case, call the test case by its
test case id in the pre-condition column
Best Practice for writing good Test Case (cont…)
 Do not Assume
 Do not assume functionality and features of your software application while
preparing test case. Stick to the Specification Documents.

 Ensure 100% Coverage

 Make sure you write test cases to check all software requirements mentioned in
the specification document.

 Test Cases must be identifiable.

 Name the test case id such that they are identified easily while tracking defects or
identifying a software requirement at a later stage.
End!