Test Case Concepts
& Template
Author: <Author Name>
Last updated: Mar-2014
© FPT Software 1
Agenda
Duration: 2 Hours
Audience: Testers
Content:
1. Test case concepts
2. Test case guideline
3. Test case review checklist
4. Test case management
© FPT Software 2
Objectives
After the course, student will:
• Understanding what is Test Case
• Aware about Test case template
• Able to understand how to read & create
test case
• Using checklist to review Test Case
© FPT Software 3
What is Test Case?
• A set of pre-requisites/pre-conditions, input value,
execution steps, expected results
• Developed for a particular objective or test condition
For example:
Exercise a particular program path or to verify compliance with a
specific requirement
Microsoft Office
Excel Template
© FPT Software 4
Inputs for creating Test case
• Test plan
• Test design
• Requirement (User requirement, SRS - Software
Requirement Specification, User stories,…)
• GUI design
• Database design
• Prototype
• User manual, technical manual
• Domain knowledge, business experience
• …
© FPT Software 5
Test Case ID
• Unique number to identify test case. It should be ID to:
- Easy to say it belong to which module
- Easy to add new one into a module and don’t change ID of other
- Should not replaced by deleted one
For example:
- USER_MGT_Create_01
- USER_MGT_Create_02
-…
- USER_MGT_Delete_01
- USER_MGT_Delete_02
- USER_MGT_Delete_03
-…
- USER_MGT_Login_01
© FPT Software 6
Test case description
• The description of objective or condition
– Should be clear, brief
– Describe generally about test case as same as a title of test case
For example:
Add user successfully
Or
Can not add user with special characters
Or
Can not add duplicated user name
Or
Can not add user without email
© FPT Software 7
Test Pre-Condition
• A set of actions need to be done before run a case.
• It maybe set for one or a set of test cases
For example:
1. Open IE
2. Access to [Link]
3. Login with Admin role (admin/admin)
4. Select Admin menu and then User menu item
5. Search to ensure that user test not existed (E.g. “test”)
© FPT Software 8
Test case procedure
• A set of steps/actions need to be run to complete a particular
objective or condition
– Must be detailed, specific
– Should be shortly, single step
– Should be ordered by number for more clear
For example:
1. On User list screen, click on [+] button
2. Input username that not existed (E.g. “test”)
3. Input Full name, email (E.g. “test”, test@[Link])
4. Use other values by default and click on [Save] button
© FPT Software 9
Expected Output
• A set of output/result after run test case procedure
For example:
1. Create User screen is displayed
4. “test” is displayed in User list with order of username, number of list
increase one
© FPT Software 10
More few common Elements
• Test Data
• Test Result (Pass / Fail)
• Test Date
• Executer
• Priority of Test case
• Traceability
• Author
• Remark / Note
• Inter-test case Dependence
© FPT Software 11
Example - Test case which have Test data
• Test data is the data that is used in tests of a software
system. Test data can be:
– In excel sheet which can be entered manually
– Or read automatically from files (XML, Flat Files, Database,…)
by automation tools.
• Test data may be prepared during or after creating Test
case, but make sure that it’s prepared before executing
Test case.
© FPT Software 12
Example - Test case which have Test data
• Test case sheet
• Test data sheet
© FPT Software 13
Example - Create Test case on TestLink tool
A. Create a Test suite
1) Access [Test Specification] -> select [Universal Profile]
project:
-> a screen creating a new Test suite is displayed
© FPT Software 14
Example - Create Test case on TestLink tool
A. Create a Test suite
2) Click [Create] button -> input detail information for Test
suite, example as below
© FPT Software 15
Example - Create Test case on TestLink tool
A. Create a Test suite
3) Click [Create Test Suite] button to finish work
-> A new Test suite is created
© FPT Software 16
Example - Create Test case on TestLink tool
B. Create a Test case
1) Access [Test Specification] -> select Test suite in the
left menu, example [Smoke Test] test suite
2) Click [Create] button in the right menu
-> a screen for adding test case is displayed as below
3) Input detail information for Test case, example as
below
© FPT Software 17
Example - Create Test case on TestLink tool
© FPT Software 18
Example - Create Test case on TestLink tool
B. Create a Test case
4) Click [Create] button again to finish work
-> A new Test case is created
© FPT Software 19
Manage Test case
Some information about Test case need to be
managed:
• Result after executing Test case
• Number of Test case for a component or system
• Status of Test case (how many Test case is passed, how
many Test case is fail,…)
….
Test case can be managed manually (example use an
excel file) or a tool to support management (example
TestLink tool).
© FPT Software 20
Tips for good Test case
• Structure of TC is clear and reasonable.
• Follow requirement closely.
• Cover all of cases that can occur.
• Title easy to understand and cover requirement (as user, I can do or
can’t do…)
• Test step and expected result is a step by step process
* 4 C principal
• Correctness: A good test case should be correct
• Clear: The test cases should be simple and easy to understand
• Completeness: 100% coverage of the requirements
• Consistency: consistency in writing the test cases
© FPT Software 21
Test Case Review Checklist
• TC checklist? Common questions to ensure that TC
created enough and right format
• Who do? Reviewer (Test leader, PM, Developers, QA,
customer)
Microsoft Office
Excel 97-2003 Worksheet
© FPT Software 22
QUIZ
© FPT Software 23
