Website Testing Checklist

1. FUNCTIONALITY
1.1 LINKS
1.1.1 Check that the link takes you to the page it said it would.
1.1.2 Ensure to have no orphan pages (a page that has no links to it)
1.1.3 Check all of your links to other websites
1.1.4 re all referenced web sites or e!ail addresses hyperlinked"
1.1.# $f we have re!oved so!e of the pages fro! our own site% set up a custo! 4&4 page that redirects
your visitors to your ho!e page (or a search page) when the user try to access a page that no longer e'ists.
1.1.( Check all !ail to links and whether it reaches properly
1.2 FORMS
1.2.1 cceptance of invalid input
1.2.2 )ptional versus !andatory fields
1.2.3 $nput longer than field allows
1.2.4 *adio buttons
1.2.# +efault values on page load,reload(lso ter!s and conditions should be disabled)
1.2.( $s Co!!and -utton can be used for .yper/inks and Continue /inks "
1.2.( $s all the datas inside co!bo,list bo' are arranged in chronolgical order"
1.2.0 re all of the parts of a table or for! present" Correctly laid out" Can you confir! that selected te'ts
are in the 1right place"
1.2.2 +oes a scrollbar appear if re3uired"
1.3 ATA !"RIFICATION AN !ALIATION
1.3.1 $s the 4rivacy 4olicy clearly defined and available for user access"
1.3.2 t no point of ti!e the syste! should behave awkwardly when an invalid data is fed
1.3.3 Check to see what happens if a user deletes cookies while in site
1.3.4 Check to see what happens if a user deletes cookies after visiting a site
2. A##LICATION S#"CIFIC FUNCTIONAL R"$UIR"M"NTS
2.1 ATA INT"%RATION
2.1.1 Check the !a'i!u! field lengths to ensure that there are no truncated characters"
2.1.2 $f nu!eric fields accept negative values can these be stored correctly on the database and does it
!ake sense for the field to accept negative nu!bers"
2.1.3 $f a particular set of data is saved to the database check that each value gets saved fully to the
database. (i.e.) -eware of truncation (of strings) and rounding of nu!eric values.
2.2 AT" FI"L C&"CKS
2.2.1 ssure that leap years are validated correctly 5 do not cause errors,!iscalculations.
2.2.2 ssure that 6eb. 22% 27% 3& are validated correctly 5 do not cause errors, !iscalculations.
2.2.3 $s copyright for all the sites includes 8ahoo co9branded sites are updated
2.3 NUM"RIC FI"LS
2.3.1 ssure that lowest and highest values are handled correctly.
2.3.2 ssure that nu!eric fields with a blank in position 1 are processed or reported as an error.
2.3.3 ssure that fields with a blank in the last position are processed or reported as an error an error.
2.3.4 ssure that both : and 9 values are correctly processed.
2.3.# ssure that division by ;ero does not occur.
2.3.( $nclude value ;ero in all calculations.
2.3.0 ssure that upper and lower values in ranges are handled correctly. (<sing -=)
2.' AL#&ANUM"RIC FI"L C&"CKS
2.4.1 <se blank and non9blank data.
2.4.2 $nclude lowest and highest values.
2.4.3 $nclude invalid characters 5 sy!bols.
2.4.4 $nclude valid characters.
2.4.# $nclude data ite!s with first position blank.
2.4.( $nclude data ite!s with last position blank.
3. INT"RFAC" AN "RROR &ANLIN%
3.1 S"R!"R INT"RFAC"
3.1.1 =erify that co!!unication is done correctly% web server9application server% application server9database
server and vice versa.
3.1.2 Co!patibility of server software% hardware% network connections
3.2 "(T"RNAL INT"RFAC"
3.2.1 .ave all supported browsers been tested"
3.2.2 .ave all error conditions related to e'ternal interfaces been tested when e'ternal application is
unavailable or server inaccessible"
3.3 INT"RNAL INT"RFAC"
3.3.1 $f the site uses plug9ins% can the site still be used without the!"
3.3.2 Can all linked docu!ents be supported,opened on all platfor!s (i.e. can >icrosoft ?ord be opened on
@olaris)"
3.3.3 re failures handled if there are errors in download"
3.3.4 Can users use copy,paste functionality"+oes it allows in password,C==,credit card no field"
3.3.# re you able to sub!it unencrypted for! data"
3.' INT"RNAL INT"RFAC"
3.4.1 $f the syste! does crash% are the re9start and recovery !echanis!s efficient and reliable"
3.4.2 $f we leave the site in the !iddle of a task does it cancel"
3.4.3 $f we lose our $nternet connection does the transaction cancel"
3.4.4 +oes our solution handle browser crashes"
3.4.# +oes our solution handle network failures between ?eb site and application servers"
3.4.( .ave you i!ple!ented intelligent error handling (fro! disabling cookies% etc.)"
'. COM#ATI)ILITY
'.1 )ROWS"RS
4.1.1 $s the .A>/ version being used co!patible with appropriate browser versions"
4.1.2 +o i!ages display correctly with browsers under test"
4.1.3 =erify the fonts are usable on any of the browsers
4.1.4 $s Bava Code,@cripts usable by the browsers under test"
4.1.# .ave you tested ni!ated C$6s across browsers"
'.2 !I"O S"TTIN%S
4.2.1 @creen resolution (check that te't and graphic align!ent still work% font are readable etc.) like 1&24 by
0(2% (&&'2&&% (4& ' 42& pi'els etc
4.2.2 Colour depth (2#(% 1(9bit% 329bit)
'.3 CONN"CTION S#""
4.3.1 +oes the site load 3uickly enough in the viewerDs browser within 2 @econds"
'.' #RINT"RS
4.4.1 Ae't and i!age align!ent
4.4.2 Colours of te't% foreground and background
4.4.3 @calability to fit paper si;e
4.4.4 Aables and borders
4.4.# +o pages print legibly without cutting off te't"
Use* Inte*+,ce Testing Checklist
1. US"R INT"RFAC"
1.1 COLORS
1.1.1 re hyperlink colors standard"
1.1.2 re the field backgrounds the correct color"
1.1.3 re the field pro!pts the correct color"
1.1.4 re the screen and field colors adEusted correctly for non9editable !ode"
1.1.# +oes the site use (appro'i!ately) standard link colors"
1.1.( re all the buttons are in standard for!at and si;e"
1.1.0 $s the general screen background the correct color"
1.1.2 $s the page background (color) distraction free"
1.2 CONT"NT
1.2.1 ll fonts to be the sa!e
1.2.2 re all the screen pro!pts specified in the correct screen font"
1.2.3 +oes content re!ain if you need to go back to a previous page% or if you !ove forward to another new
page"
1.2.4 $s all te't properly aligned"
1.2.# $s the te't in all fields specified in the correct screen font"
1.2.( $s all the heading are left aligned
1.2.0 +oes the first letter of the second word appears in lowercase" EgF
1.3 IMA%"S
1.3.1 re all graphics properly aligned"
1.3.2 re graphics being used the !ost efficient use of file si;e"
1.3.3 re graphics opti!i;ed for 3uick downloads"
1.3.4 ssure that co!!and buttons are all of si!ilar si;e and shape% and sa!e font 5 font si;e.
1.3.# -anner style 5 si;e 5 display e'act sa!e as e'isting windows
1.3.( +oes te't wrap properly around pictures,graphics"
1.3.0 $s it visually consistent even without graphics"
1.' INSTRUCTIONS
1.4.1 $s all the error !essage te't spelt correctly on this screen"
1.4.2 $s all the !icro9help te't(i.e tool tip) spelt correctly on this screen"
1.4.3 >icrohelp te't(i.e tool tip) for every enabled field 5 button
1.4.4 4rogress !essages on load of tabbed(active screens) screens
1.- NA!I%ATION
1.#.1 re all disabled fields avoided in the A- se3uence"
1.#.2 re all read9only fields avoided in the A- se3uence"
1.#.3 Can all screens accessible via buttons on this screen be accessed correctly"
1.#.4 +oes a scrollbar appear if re3uired"
1.#.# +oes the Aab )rder specified on the screen go in se3uence fro! Aop /eft to botto! right" Ahis is the
default unless otherwise specified.
1.#.( $s there a link to ho!e on every single page"
1.#.0 )n open of tab focus will be on first editable field
1.#.2 ?hen an error !essage occurs does the focus return to the field in error when the user cancels it"
1.. USA)ILITY
1.(.1 re all the field pro!pts spelt correctly"
1.(.2 re fonts too large or too s!all to read"
1.(.3 re na!es in co!!and button 5 option bo' na!es are not abbreviations.
1.(.4 ssure that option bo'es% option buttons% and co!!and buttons are logically grouped together in
clearly de!arcated areas 1Croup -o'1
1.(.# Can the typical user run the syste! without frustration"
1.(.( +o pages print legibly without cutting off te't"
1.(.0 +oes the site convey a clear sense of its intended audience"
1.(.2 +oes the site have a consistent% clearly recogni;able 1look959feel1"
1.(.7 +oes <ser cab /ogin >e!ber rea with both <serGa!e,E!ail $+ "
1.(.7 +oes the site look good on (4& ' 42&% (&&'2&& etc."
1.(.1& +oes the syste! provide or facilitate custo!er service" i.e. responsive% helpful% accurate"
1.(.11 $s all ter!inology understandable for all of the siteHs intended users"