Detailed Web Application Testing Checklist: Functionality and UI

This assignment presents a comprehensive web application testing checklist designed to ensure the quality and functionality of web applications. The checklist is divided into two main sections: Functionality and User Interface (UI) testing. The Functionality section covers essential aspects like link verification, form validation (including input validation, handling of optional and mandatory fields, and numeric field validation), and compatibility across different browsers and screen resolutions. The UI testing section focuses on the visual aspects and user experience, including color schemes, content presentation, navigation, and usability. It checks for consistent fonts, correct alignment, proper error messages, and efficient navigation, including considerations for accessibility features like tab order and micro-help text. The checklist also emphasizes ensuring the site's responsiveness across different screen resolutions and connection speeds, as well as providing a clear and user-friendly experience. The goal is to provide a structured approach to identify and address potential issues, thereby improving the overall user experience and reliability of the web application.

Web Application Testing Checklist
FUNCTIONALITY
1.1 LINKS
1.1.1 Check that the link takes you to the page it said it would.
1.1.2 Check all of your links
1.1.3 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.
1.2 FORMS
1.2.1 Acceptance of invalid input
1.2.2 Optional versus mandatory fields
1.2.3 Input longer than field allows
1.2.4 Radio buttons
1.2.5 Default values on page load/reload(Also terms and conditions should be disabled)
1.2.6 Is Command Button can be used for HyperLinks and Continue Links?
1.2.6 Is all the data inside combo/list box are arranged in chronological order?
1.2.7 Are all of the parts of a table or form present? Correctly laid out? Can you confirm that selected texts
are in the "right place?
1.2.8 Does a scrollbar appear if required?
2.3 NUMERIC FIELDS
2.3.1 Assure that lowest and highest values are handled correctly.
2.3.2 Assure that numeric fields with a blank in position 1 are processed or reported as an error.
2.3.3 Assure that fields with a blank in the last position are processed or reported as an error an error.
2.3.4 Assure that both + and - values are correctly processed.
2.3.7 Assure that upper and lower values in ranges are handled correctly. (Using BVA)
2.4 ALPHANUMERIC FIELD CHECKS
2.4.1 Use blank and non-blank data.
2.4.2 Include lowest and highest values.
2.4.3 Include invalid characters & symbols.
2.4.4 Include valid characters.
2.4.5 Include data items with first position blank.
2.4.6 Include data items with last position blank.
3. COMPATIBILITY
3.1 BROWSERS
3.1.1 Is the HTML version being used compatible with appropriate browser versions?
3.1.2 Do images display correctly with browsers under test?
3.1.3 Verify the fonts are usable on any of the browsers

4.2 Screen resolution
4.2.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
4.2.1 and image alignment
4.2.1 Colours of text, foreground and background
4.3 CONNECTION SPEED
4.3.1 Does the site load quickly enough in the viewer's browser within 8 Seconds?
User Interface Testing Checklist
1. USER INTERFACE
1.1 COLORS
1.1.1 Are hyperlink colors standard?
1.1.2 Are the field backgrounds the correct color?
1.1.3 Are the field prompts the correct color?
1.1.4 Are the screen and field colors adjusted correctly for non-editable mode?
1.1.5 Does the site use (approximately) standard link colors?
1.1.6 Are all the buttons are in standard format and size?
1.1.7 Is the general screen background the correct color?
1.1.8 Is the page background (color) distraction free?
1.2 CONTENT
1.2.1 All fonts to be the same
1.2.2 Are all the screen prompts specified in the correct screen font?
1.2.3 Does content remain if you need to go back to a previous page, or if you move forward to another new
page?
1.2.4 Is all text properly aligned?
1.2.5 Is the text in all fields specified in the correct screen font?
1.2.6 Is all the heading are left aligned
1.2.7 Does the first letter of the second word appears in lowercase? Eg:
1.4 INSTRUCTIONS
1.4.1 Is all the error message text spelt correctly on this screen?
1.4.2 Is all the micro-help text(i.e tool tip) spelt correctly on this screen?
1.4.3 Microhelp text(i.e tool tip) for every enabled field & button
1.4.4 Progress messages on load of tabbed(active screens) screens
1.5 NAVIGATION
1.5.1 Are all disabled fields avoided in the TAB sequence?
1.5.2 Are all read-only fields avoided in the TAB sequence?
1.5.3 Can all screens accessible via buttons on this screen be accessed correctly?

1.5.4 Does a scrollbar appear if required?
1.5.5 Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the
default unless otherwise specified.
1.5.6 Is there a link to home on every single page?
1.5.7 On open of tab focus will be on the first editable field
1.5.8 When an error message occurs does the focus return to the field in error when the user cancels it?
1.6 USABILITY
1.6.1 Are all the field prompts spelt correctly?
1.6.2 Are fonts too large or too small to read?
1.6.3 Are names in command button & option box names are not abbreviations.
1.6.4 Assure that option boxes, option buttons, and command buttons are logically grouped together in
clearly demarcated areas "Group Box"
1.6.5 Can the typical user run the system without frustration?
1.6.6 Do pages print legibly without cutting off text?
1.6.7 Does the site convey a clear sense of its intended audience?
1.6.8 Does the site have a consistent, clearly recognizable "look-&-feel"?
1.6.9 Does User cab Login Member Area with both UserName/Email ID ?
1.6.9 Does the site look good on 640 x 480, 600x800 etc.?
1.6.10 Does the system provide or facilitate customer service? i.e. responsive, helpful, accurate?
1.6.11 Is all terminology understandable for all of the site’s intended users?