1.Web Application - Functional Testing Checklist
Links
1.Check that the link takes you to the page it said it would.
2.Check all referenced web sites or email addresses are hyper linked
3.Check all mail to links and whether it reaches properly
4.If we have removed some of the pages from our own site, set up a custom 404 page that redirects your visitors to your home page (or a search page) when the user try to access a page that no longer exists
Data Integration
1.Check the maximum field lengths to ensure that there are no truncated characters?
2.If a particular set of data is saved to the database check that each value gets saved fully to the database. (i.e.) Beware of truncation (of strings) and rounding of numeric values.
Date Field checks
1. Assure that leap years are validated correctly & do not cause errors/miscalculations.
2 .Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations
Numeric Fields
1.empty string, if possible
2.0
3.in range positive, small and large
4.in range negative, small and large
5.out of range positive
6.out of range negative
7.with leading zeros
8.syntactically invalid (e.g., includes letters)
Alpha Numeric
1.Use blank and non-blank data.
2.Include lowest and highest values.
3.Include invalid characters & symbols.
4.Include valid characters.
5.Include data items with first position blank.
6.Include data items with last position blank.
2.Web Application UI Checklist
Testing user interface for web application is slightly different from testing user interface of traditional applications. Irrespective of the web application there are certain things which should be tested for every web application. Following checklist will give some information on items that should be tested to ensure quality of the user interface of your web application.
Colors
1.check all the hyper link colors are standard
2.Does the site use (approximately) standard link colors?
3.Is the general screen background the correct color?
4.Are all the buttons are in standard format and size?
Content
1.All fonts to be the same
2.Does content remain if you need to go back to a previous page, or if you move forward to another new page?
3.Is all text properly aligned
4.Is the text in all fields specified in the correct screen font
5.Is all the heading are left aligned
6.Does the first letter of the second word appears in lowercase
Images
1.Are all graphics properly aligned
2.Are graphics being used the most efficient use of file size
3.Are graphics optimized for quick downloads
4.Banner style & size & display exact same as specified
5.Does text wrap properly around pictures/graphics
6.Is it visually consistent even without graphics
Instructions
1.Is all the error message text spelt correctly on this screen
2.Is all the micro-help text(i.e tool tip) spelt correctly on this screen
3.Microhelp text (i.e tool tip) for every enabled field & button
Navigation
1.Are all disabled fields avoided in the TAB sequence
2.Are all read-only fields avoided in the TAB sequence
3.Does a scrollbar appear if required
4.Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
5.Is there a link to home on every single page?
6.On open of tab focus will be on first editable field
7.When an error message occurs does the focus return to the field in error when the user cancels it
Usability
1.Are all the field prompts spelt correctly
2.Are fonts too large or too small to read
3.Are names in command button & option box names are not abbreviations.
4.Can the typical user run the system without frustration
5.Do pages print legibly without cutting off text?
6.Does the site convey a clear sense of its intended audience?
7.Does the site have a consistent, clearly recognizable "look-&-feel"
8.Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate
9.Is all terminology understandable for all of the site’s intended users
3.GUI Testing Checklist
Compliance for each window in the application
1.Window caption for every application should have application name and window name. Specially, error messages.
2.Title of the window and information should make sense to the user.
3.If screen has control menu, use the entire control menu like move, close, resize etc.
4Text present should be checked for spelling and grammar.
5.If tab navigation is present, TAB should move focus in forward direction and SHIFT+TAB in backward direction.
6.Tab order should be left to right and top to bottom within a group box.
7.If focus is present on any control, it should be presented by dotting lines around it.
8.User should not be able to select greyed or disabled control. Try this using tab as well as mouse.
9.Text should be left justified
10.In general, all the operations should have corresponding key board shortcut key for this.
11.All tab buttons should have distinct letter for it
Text boxes
1.Move mouse to text box and it should be changed to insert bar for editable text field and should remain unchanged for non-editable text field.
2.Test overflowing text box by inserting as many characters as you can in the text field. Also test width of the text field by entering all capital W.
3.Enter invalid characters, special characters and make sure that there is no abnormality.
4.User should be able to select text using Shift + arrow keys. Selection should be possible using mouse and double click should select entire text in the text box.
Radio Buttons
1.Only one should be selected from the given option.
2.User should be able to select any button using mouse or key board
3.Arrow key should set/unset the radio buttons
Check boxes
1.User should be able to select any combination of check boxes
2.Clicking mouse on the box should set/unset the check box.
3.Space bar should also do the same
Push Buttons
1.All buttons except OK/Cancel should have a letter access to them. This is indicated by a letter underlined in the button text. The button should be activated by pressing ALT
2.Clicking each button with mouse should activate it and trigger required action.
3.Similarly, after giving focus SPACE or RETURN button should also do the same.
4.If there is any Cancel button on the screen, pressing Esc should activate it.
Drop down list boxes/Combo/List box
1.Pressing the arrow should give list of options available to the user. List can be scrollable but user should not be able to type in.
2.Pressing Ctrl-F4 should open the list box.
3.Pressing a letter should bring the first item in the list starting with the same letter.
4.Items should be in alphabetical order in any list.
5.Selected item should be displayed on the list.
6.There should be only one blank space in the drop down list.
4.Checklist for Browser Compatibility
Browser
1.Is the HTML version being used compatible with appropriate browser versions?
2.Do images display correctly with browsers under test?
3.Verify the fonts are usable on any of the browsers
4.Is Java Code/Scripts usable by the browsers under test?
5.Have you tested Animated GIFs across browsers?
Video Settings
1.Screen resolution (check that text and graphic alignment still work, font are readable etc.) like 1024 by 768, 600x800, 640 x 480 pixels etc
2.Color depth (256, 16-bit, 32-bit)
Connection Speed
1.Does the site load quickly enough in the viewer's browser within 8 Seconds?
Printers
1.Text and image alignment
2.Colors of text, foreground and background
3.Scalability to fit paper size
4.Tables and borders
5.Do pages print legibly without cutting off text
5.Checklist for Security Testing
1.Does the site prompt for user name and password?
2.Are concurrent log-ons permitted?
3.Have you verified where encryption begins and ends?
4. Are there Digital Certificates, both at server and client?
5.Does the application include time-outs due to inactivity?
6.Is bookmarking disabled on secure pages?
7. Does the key/lock display on status bar for insecure/secure pages?
8.Is Right Click, View, Source disabled?
9.Are you prevented from doing direct searches by editing content in the URL?
10.Do your users know when they are entering or leaving secure portions of your site?
11.Does your server lock out an individual who has tried to access your site multiple times with invalid login/password information?
12.Test both valid and invalid login names and passwords. Are they case sensitive? Is there a limit to how many tries that are allowed? Can it be bypassed by typing the URL to a page inside directly in the browser?
13.What happens when time out is exceeded? Are users still able to navigate through the site?
14.Relevant information is written to the log files and that the information is traceable.
15.Scripting on the server is not possible to plan or edit scripts without authorization.
16.Have you tested the impact of Secure Proxy Server?
17.Test should be done to ensure that the Load Balancing Server is taking the session information of Server A and pooling it to Server B when A goes down.
18.Have you verified the use of 128-bit Encryption?
