General Guidelines for writing Test Cases:

Following points need to be consider, while writing test cases for regression or functional
testing scenarios:
Checklist for Test Case preparation:
1. Check for whole page.
2. Layout of whole page: Page name (title, address bar, location of logo, top links, top
na!igation bar, breadcrumbs, na!igation paths, Page title on page, left na!igation bar,
"ight na!igation bar(if present, e!er# panel present on page, $ottom na!igation bar.
1. Page name (title): Check whether it is as per desired one. (Font, font si%e, color,
alignment
. !ddress "ar: Check whether it is redirecting to proper site (internal parameters if
an#.
#. Location of logo: Check for logo of &Carpahonewarehouse'. (t should be present as
per new changed one ) as per protot#pe at desired location (left top corner
$. Top links: Check for that specific links present abo!e top na!igation bar. ($#
clicking (Font, font si%e, color, alignment. Check link b# opening same link, b#
right click *pen in +ew ,indow.
%. Top na&igation "ar:
Check for displa# of each specific link (Font, font si%e, color, alignment ) $#
clicking
Check for focus (should be in highlighted
Check link b# opening same link b# right click *pen in +ew ,indow.
'. (readcrum"s: check for breadcrumb-s na!igation path b# clicking ((Font, font si%e,
color also for &$utton-- if an# as per protot#pe are present.
). *ight na&igation "ar(if present):
Check for displa# of each specific link (Font, font si%e, color, alignment ) $#
clicking
Check for focus (should be in highlighted
Check link b# opening same link b# right click *pen in +ew ,indow
+. Page title on page: Check for title of specific internal page. (e.g. .ummar# of /#
/obile phone
(Font, font si%e, color, alignment
.ub +aming if used (Font, font si%e, color, alignment ) $# clicking
Check for 0elp information needs to be displa#ed as per protot#pe ((Font, font
si%e, color, alignment
Check for 0eading needs to be displa#ed as per protot#pe (Font, font si%e, color,
alignment
,. -&ery panel present on page:
+on 1ditable Panel:
.ub +aming if used (Font, font si%e, color, alignment
$ackground color, images if present per protot#pe.
Check for 0elp information needs to be displa#ed as per protot#pe(Font,
font si%e, color, alignment
Check for 0eading needs to be displa#ed as per protot#pe (Font, font si%e,
color, alignment
Check for displa# of each specific link (Font, font si%e, color, alignment )
b# clicking. heck link b# opening same link b# right click *pen in
+ew ,indow
Check for each label heading (e.g. Tariff : (Font, font si%e, color,
alignment
Check for displa# of each information like if information is getting
displa#ed in tabular format per protot#pe. (Font, font si%e, color,
alignment
Check if information is re2uiring being in editable format or onl# displa#ing
which should be as per protot#pe. (Font, font si%e, color, alignment
Check for information needs to be displa#ed as per protot#pe (Font, font
si%e, color, alignment check for indi!idual re2uirement specific
conditions i.e. if &password' information then it should be
displa#ed in encr#pted format.
Check if an# drop down field present then test for that particular field
Check if an# check bo3 is present then test for that particular field, i.e.
actual functionalit# that will reflect
Check whether an# blank space is getting displa#ed, is as per protot#pe or
not.
Check if altte3t functionalit# for each label or information if e3ist as per
protot#pe.
Check for 4atabase 1ntr# details for each re2uired field in respecti!e
database.
Check for each labels C/. related article asset information as per protot#pe
or business re2uirement.
5dditional test cases will be as per new C" or functionalit#.
1ditable Panel:
.ub +aming if used (Font, font si%e, color, alignment
$ackground color, images if present as per protot#pe.
Check for 0elp information needs to be displa#ed as per protot#pe(Font,
font si%e, color, alignment
Check for 0eading needs to be displa#ed as per protot#pe (Font, font si%e,
color, alignment
+ame of Field, T#pe of field (Te3t Field, 4rop down, 5ll buttons present
on panel.
Check for each field !alidation: Considering all possible combination for
happ# path ) negati!e combination. .pecif# test data (combination need
to be tested b# tester.
Check for mandator#, non6 mandator# field.
13. For postcode field, 1.Tester should test using links present ne3t to te3t
field (find address, use link. 2. Cross check addresses with same
functionalit# present on CP, site. 7. 5ll field le!el !alidation with test
data combination should be written in test cases. 8. 5ddress te3t field should
get change to 4rop 4own for selection of address.
Check for error page also if negati!e test data used.(1rror /essage: (Font,
font si%e, color, alignment
Check for 1ach $uttons desired functionalit#. (e.g. &Cancel' button: click
on cancel should delete all entered data ) re6direct to desired page as per
protot#pe.
Check for indi!idual field-s functional re2uirement as per desired protot#pe.
Check whether an# blank space is getting displa#ed, is as per protot#pe or
not.
Check if altte3t functionalit# for each label or information if e3ist as per
protot#pe.
Check for 4atabase 1ntr# details for each re2uired field in respecti!e
database once data is submitted or updated or confirmed.
Check for each labels C/. related article asset information as per protot#pe
or business re2uirement.
5dditional test cases will be as per new C" or functionalit#.
1.. (ottom na&igation "ar(if present):
Check for displa# of each specific link (Font, font si%e, color, alignment ) $#
clicking
Check link b# opening same link b# right click *pen in +ew ,indow