Agenda

— Test case concepts

— Test Case Elements
— Common errors
— Practice writing testcase
What is Test Case?
— A set of pre-requisites/pre-conditions, test steps, input value, expected
results
— Developed for a particular objective or test condition
Test Case Elements
• Test case ID
• Test case description
• Test Case Procedure
• Expected Output
• Inter-test case Dependence
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 one module and don’t change ID of other

For example:
— USER_MGT_Create_01
— USER_MGT_Create_02
— …
— USER_MGT_Delete_01
— USER_MGT_Delete_02
— USER_MGT_Delete_03
Test case description
The description of objective or condition
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
Test case procedure
A set of steps/actions need to be run to complete a particular objective or
condition

For example:
1. On User list screen, click on [+] button
2. Input username that not existed (E.g. “abc”)
3. Input Full name, email (E.g. “abc”, abc@gmail.com.vn)
4. Use other values by default and click on [Save] button
Expected Output
A set of output/result after run

For example:
1. Create User screen is displayed
4. “abc” is displayed in User list with order of username, number of list
increase one
Inter-test case Dependence
One or more test cases what is input for others. If they are blocked,
we can not run next cases

For example:
USER_MGT_Login_01
Pre-requisite
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 http://10.10.122.123/TestABC
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. “abc”)
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
Check GUI (Graphic User Interface)
Check about prototype, layout, format: color, font, size,
status, default, length, …

For example:
* [Account] textbox at Search screen:
- Status = enable
- Default = blank
- List items loaded from the Account List in database
* [Account] textbox at Add screen:
- Status = editable
- Default = blank- Max length = 50
-…
Check GUI
Check Function
• For example:
— Search
— Add new
— Update
— Delete
Check Function - Search
Check Function – Add new
Check Function – Delete
Common errors
• ID is wrong
• Lack (thiếu sót) of GUI testcase
• The Test Case Procedure does not describe the test conditions
clearly
• Test Case Description is not clear for each test case
• Expected Output has not specifically described an error in SRS
• ………….
Practice writing testcase
• Write a blackbox testcase for the search screen below:
Practice writing testcase
Write a blackbox testcase for the Add New screen below :
— Thông báo:
— “Item XXX bắt buộc nhập.”;
— “Biển số phải có format alpha numeric.”;
— “Ngày đăng kí không đúng định dạng.” ;
— “Giá phải là kiểu số.”
Q&A