WRITING GOOD TEST CASES

1. As far as possible, write test cases in such a way that you test only one thing at a time. Do not overlap or complicate test cases.
3. Ensure that all positive scenarios and negative scenarios are covered.
4. Language: Write in simple and easy to understand language.
5. Use active voice: Do this, do that, Make sure, Verify
6. Use exact and consistent names (of forms, fields, etc).

Characteristics of a good test case:

1. Accurate: Exacts the purpose.
2. Economical: No unnecessary steps or words.
3. Traceable: Capable of being traced to requirements.
4. Repeatable: Can be used to perform the test over and over.
5. Reusable: Can be reused if necessary.

Tips for Writing Effective Test Cases for Any Application

1 Test Case Naming Conventions
2 Test case Name Field
3 Assumptions and Preconditions
4 Input Test Data
5 Cover all Verification Points in Test Design Steps
6 Attach the Relevant Artefacts
7 Expected Result
9 Review
10 Reusable
11 Maintenance & Updates
12 Post Conditions
y that you test only one thing at a time. Do not overlap or complicate test cases.
scenarios are covered.
and language.
erify
s, etc).

ments.
er and over.

Application
Name the Test Cases so to represent the module name or functional area you are going to verify in that test case.
Enter as much information as possible in Description!
Make sure to add as much information as possible for any conditions to be met before running the test case.
To make your life easy as a tester (and your fellow-testers!), wherever applicable, you can give Test Data to be used for the Test Case within TC Description or w
This savesDesign
The Test a lot ofSteps
timeshould
in the long run as
not only youthe
cover won’t have to flow
functional huntbut
a new
alsotest
eachdata every time
verification you which
point need toshould
execute
be the test.
tested!
wherever possible you should attach the relevant artefacts to your test case.
Each test design step should clearly mention what you expect as outcome of that verification step.
So, whilecan
Review writing
be done testby
cases,
peermention in detailaswhat
testers (termed ‘Peerpage/screen you
Review’), BA, expect to appear
developers, productafter the test
owners and,
or any any changes
relevant you expect to be done to any backend lega
stakeholders.
You should write test cases keeping in mind that they could be re-used in the future for some other project/teams.
On that consider
Always note, before writing
updating a new
the TestTest
existing CaseCases
for your project/module,
(if any) always
before you start try and
writing Newfind out
Test if there are Test Cases written already for the same area? That re
Cases!
Post-conditions basically specify the various things that need to be verified after the Test has been carried out.
In addition, post-conditions are also used to give guiding instruction to restore the system to its original state for it not to interfere with subsequent testing.
User Story Number on Jira:

QA Task ID on JIRA:

Testcase Task ID on TFS/Jira:

Test Case ID Test Case Type

Functional/Positive

Functional/Positive

UI/UX
Functional/Positive
Functional/Positive
UI/UX
Functional/Positive
UI/UX
UI/UX
Functional/Positive
Functional/Positive
Functional/Positive
Functional/Positive
UI/UX
Scenario Based

Functional/Positive

Scenario Based

Functional/Positive

Functional/Positive

Functional/Positive
Functional/Positive
Functional/Positive
Functional/Positive
UI/UX

UI/UX

UI/UX
UI/UX
 Test Case Sheet for
<<Wallethub>>, <<Settings>>

Test Case Description Expected Output

User will be redirected to the login screen by clicking User should be redirected to the Login screen
the
Userfollowing
should belink https://wallethub.com/
redirected to the Dashboard/Home User should be redirected to the Home screen
screen by logging in throught correct credentials

User will be able to view Navigation Menu labeled User should able to view Navigation Menu "Nipun"
"Nipun" User should able to view and select the "Settings"
User will atbethe
abletop
to header
view and select "Settings" option in option in the menu list
the
By selecting the "Settings"over
menu list by hovering to the
option userlabel "Nipun"
will be User should be redirected to the "Settings" module
redirected
"Public Info" to block
the "Settings" module
will be visible to the user on the "Public Info" block should visible to the user
Settings
By clicking on the "Public Info"title
screen under Settings option user will be User should be redirected to the "Public Info" page
redirected
User will betoablethe to
"Public Info" page
see "Upload Image" button on the User should able to see "Upload Image" button
Profile Info screen
"Upload Image" button will be clickable "Upload Image" button should clickable
By clicking "Upload Image" button user will be
redirected to the File Uploader window User should be redirected to the File Uploader window
User
After will be able
selecting andto opening
select any supported
image filebe able to
user will User should able to select any supported file
adjust it's size
By selecting Profile Image user will be able to see User should able to adjust the size of the image
"Save" and "Cancel" buttons under selected profile User should able to see "Save" and "Cancel" buttons
"Save" and "Cancel" buttons are clickable Both button should be clickabled
Scenario 1: Selection of the 'Save" button

When the user clicks on the "Save" button then profile

photo will be uploaded succesfully Profile photo should be uploaded successfully
Scenario 2: Selection of the 'Cancel" button

When the user clicks on the "Cancel" button then

profile photo will not be uploaded and user will be
redirected to the Public Info page User should be redirected to the Profile Info page

Verify that uploaded image will also visible in the image

section
User willofbe
the Profile
able module
to upload profile image with image file Uploaded
User shouldimage
able should visible
to upload in the
profile Profile
image withmodule
image file
of different
User will be extensions
able to upload profile image with of different
User shouldextensions
able to upload profile image with
supported
User will beimage files
able to seeonly
alert/error message when user supported image files only
tries
Verify that user will not be greater
to upload image with size then
able to upload expected
a duplicate User should able to see alert/error message
name image User should not able to upload a duplicate name image
User will be able to change the profile image User should able to change the profile image
Verify that all the fields and place holders are properly All fields and place holders should be properly aligned
aligned

Verify that font styles and formatting are implemented Font styles and formatting should be implemented
Verify that all the fields/tabs/buttons are
correctly correctly
tapable/clickable All the fields/tabs/buttons should tapable/clickable
 Verification Status
Actual Output (Fail/Pass)
User is redirected to the Login screen Pass
User is redirected to the Home screen Pass

User is able to view Navigation Menu "Nipun" Pass

User is able to view and select the "Settings" option in
the menu list Pass
User is redirected to the "Settings" module Pass
"Public Info" block is visible to the user Pass
User is redirected to the "Public Info" page Pass
User is able to see "Upload Image" button Pass
"Upload Image" button is clickable Pass
User is redirected to the File Uploader window Pass
User is able to select any supported file Pass
User is able to adjust the size of the image Pass
User is able to see "Save" and "Cancel" buttons Pass
Both button are clickabled Pass
Pass
Pass

Profile photo is uploaded successfully

Pass
Pass

User is redirected to the Profile Info page

Pass

Uploaded
User is ableimage is visible
to upload in the
profile Profile
image withmodule
image file of
different extensions Pass
User is able to upload profile image with supported
image files only Pass
User is able to see alert/error message Pass
User is not able to upload a duplicate name image Pass
User is able to change the profile image Pass
All fields and place holders are properly aligned Pass

Font styles and formatting are implemented correctly Pass

All the fields/tabs/buttons are tapable/clickable Pass
Yes Functionality/Positive

No Nagitive
UI/UX
Console
Scenario Based
Impacts
Database