Lets have first web testing checklist.

1) Functionality Testing
2) Usability testing
3) Interface testing
4) Compatibility testing
5) Performance testing
6) Security testing
1) Functionality esting!
Test for - all the links in web pages, database connection, forms used in the web pages for
submitting or getting information from user, Cookie testing
"heck all the links!
Test the outgoing links from all the pages from specific domain under test
Test all internal links
Test links !umping on the same pages
Test links used to send the email to admin or other users from web pages
Test to check if there are any orphan pages
"astly in link checking, check for broken links in all abo#e-mentioned links
est for#s in all $ages!
Forms are the integral part of any web site Forms are used to get information from users
and to keep interaction with them So what should be checked on these forms$
First check all the #alidations on each field
Check for the default #alues of fields
%rong inputs to the fields in the forms
&ptions to create forms if any, form delete, #iew or modify the forms
"et's take e(ample of the search engine pro!ect currently I am working on, In this pro!ect
we ha#e ad#ertiser and affiliate signup steps )ach sign up step is different but dependent
on other steps So sign up flow should get e(ecuted correctly There are different field
#alidations like email Ids, User financial info #alidations *ll these #alidations should get
checked in manual or automated web testing
"ookies testing!
Cookies are small files stored on user machine These are basically used to maintain the
session mainly login sessions Test the application by enabling or disabling the cookies in
your browser options Test if the cookies are encrypted before writing to user machine If
you are testing the session cookies +ie cookies e(pire after the sessions ends, check for
login sessions and user stats after session end Check effect on application security by
deleting the cookies +I will soon write separate article on cookie testing,
%ali&ate your '(L)"**!
If you are optimi-ing your site for Search engines then .T/"0CSS #alidation is #ery
important /ainly #alidate the site for .T/" synta( errors Check if site is crawlable to
different search engines
+atabase testing!
1ata consistency is #ery important in web application Check for data integrity and errors
while you edit, delete, modify the forms or do any 12 related functionality
Check if all the database 3ueries are e(ecuting correctly, data is retrie#ed correctly and
also updated correctly /ore on database testing could be load on 12, we will address
this in web load or performance testing below
2) ,sability esting!
est for navigation!
4a#igation means how the user surfs the web pages, different controls like buttons, bo(es
or how user using the links on the pages to surf different pages
Usability testing includes5
%eb site should be easy to use Instructions should be pro#ided clearly Check if the
pro#ided instructions are correct means whether they satisfy purpose
/ain menu should be pro#ided on each page It should be consistent
"ontent checking!
Content should be logical and easy to understand Check for spelling errors Use of dark
colors annoys users and should not be used in site theme 6ou can follow some standards
that are used for web page and content building These are common accepted standards
like as I mentioned abo#e about annoying colors, fonts, frames etc
Content should be meaningful *ll the anchor te(t links should be working properly
Images should be placed properly with proper si-es
These are some basic standards that should be followed in web de#elopment 6our task is
to #alidate all for UI testing
-ther user infor#ation for user hel$!
"ike search option, sitemap, help files etc Sitemap should be present with all the links in
web sites with proper tree #iew of na#igation Check for all links on the sitemap
7Search in the site8 option will help users to find content pages they are looking for easily
and 3uickly These are all optional items and if present should be #alidated
3) .nterface esting!
The main interfaces are5
%eb ser#er and application ser#er interface
*pplication ser#er and 1atabase ser#er interface
Check if all the interactions between these ser#ers are e(ecuted properly )rrors are
handled properly If database or web ser#er returns any error message for any 3uery by
application ser#er then application ser#er should catch and display these error messages
appropriately to users Check what happens if user interrupts any transaction in-between$
Check what happens if connection to web ser#er is reset in between$
4) "o#$atibility esting!
Compatibility of your web site is #ery important testing aspect See which compatibility
test to be e(ecuted5
2rowser compatibility
&perating system compatibility
/obile browsing
Printing options
/rowser co#$atibility!
In my web-testing career I ha#e e(perienced this as most influencing part on web site
testing
Some applications are #ery dependent on browsers 1ifferent browsers ha#e different
configurations and settings that your web page should be compatible with 6our web site
coding should be cross browser platform compatible If you are using !a#a scripts or
*9*: calls for UI functionality, performing security checks or #alidations then gi#e
more stress on browser compatibility testing of your web application
Test web application on different browsers like Internet e(plorer, Firefo(, 4etscape
na#igator, *&", Safari, &pera browsers with different #ersions
-* co#$atibility!
Some functionality in your web application is may not be compatible with all operating
systems *ll new technologies used in web de#elopment like graphics designs, interface
calls like different *PI's may not be a#ailable in all &perating Systems
Test your web application on different operating systems like %indows, Uni(, /*C,
"inu(, Solaris with different &S fla#ors
(obile browsing!
This is new technology age So in future /obile browsing will rock Test your web pages
on mobile browsers Compatibility issues may be there on mobile
0rinting o$tions!
If you are gi#ing page-printing options then make sure fonts, page alignment, page
graphics getting printed properly Pages should be fit to paper si-e or as per the si-e
mentioned in printing option
5) 0erfor#ance testing!
%eb application should sustain to hea#y load %eb performance testing should include5
%eb "oad Testing
%eb Stress Testing
Test application performance on different internet connection speed
In web loa& testing test if many users are accessing or re3uesting the same page Can
system sustain in peak load times$ Site should handle many simultaneous user re3uests,
large input data from users, Simultaneous connection to 12, hea#y load on specific pages
etc
*tress testing! ;enerally stress means stretching the system beyond its specification
limits %eb stress testing is performed to break the site by gi#ing stress and checked how
system reacts to stress and how system reco#ers from crashes
Stress is generally gi#en on input fields, login and sign up areas
In web performance testing web site functionality on different operating systems,
different hardware platforms is checked for software, hardware memory leakage errors,
6) *ecurity esting!
Following are some test cases for web security testing5
Test by pasting internal url directly into browser address bar without login
Internal pages should not open
If you are logged in using username and password and browsing internal pages
then try changing url options directly Ie If you are checking some publisher site
statistics with publisher site I1< =>? Try directly changing the url site I1
parameter to different site I1 which is not related to logged in user *ccess should
denied for this user to #iew others stats
Try some in#alid inputs in input fields like login username, password, input te(t
bo(es Check the system reaction on all in#alid inputs
%eb directories or files should not be accessible directly unless gi#en download
option
Test the C*PTC.* for automates scripts logins
Test if SS" is used for security measures If used proper message should get
displayed when user switch from non-secure http500 pages to secure https500 pages
and #ice #ersa
*ll transactions, error messages, security breach attempts should get logged in log
files somewhere on web ser#er