Cross Browser Testing - Basics - Learner's Series - 3

BCT for User Experience

To test user experience, we might need to consider the following: 

Check	Remarks
Font size validation	Text Size validations through Browser
Page layout in different resolutions	640x480, 800x600, 1024x768, 1366x768(as applicable, based on the resolutions supported) with respect to Oses supported
All images and alignment	Are all graphics properly aligned? Assure that command buttons are all of similar size and shape, and same font & font size. Banner style & size & display exact same as existing windows Does text wrap properly around pictures/graphics?
Time & Date(Display as well as Functionality)	1) Time outs(for any operation which needs to be completed with in a duration)( Online Bank, Transport Reservation, Email account etc) 2) Time Zone difference 3) Year 3K(Y2K issue) 4) Day Light Savings 5) Crossing Time Zones( + Machines in different time zones/Geographies) 6) Leap Days 7) Leap Days in Non Leap Year 8) Always Invalid days( February 30, 31, 31st on Odd months) 9) Year end + January 1st 10) Previous Centuries 11) Different Time / Date formats 12) Reset Clock forward or backward 13) Country Specific public holidays
Page zoom-in and zoom-out functionality
GUI Colors	Are hyperlink colors Uniform across the application? Are the field backgrounds the correct color? Are the field prompts the correct color? Are all the buttons are in standard format and size? Is the page background (color) distraction free?
Content	All fonts to be the same Are all the screen prompts specified in the correct screen font? Does content remain if you need to go back to a previous page, or if you move forward to another new page? Is all text properly aligned? Is the text in all fields specified in the correct screen font? Is all the heading are left aligned? Does the first letter of the second word appears in lowercase?
Instructions	Is all the micro-help text(i.e. tool tip) spelt correctly on this screen?(as applicable) Progress messages on load of tabbed(active screens) screens
Navigation	Are all disabled fields avoided in the TAB sequence? Are all read-only fields avoided in the TAB sequence? Can all screens accessible via buttons on this screen be accessed correctly? Does a scrollbar appear if required? Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified. Is there a link to home on every single page? On open of tab focus will be on first editable field When an error message occurs does the focus return to the field in error when the user cancels it?
Usability	Are all the field prompts spelt correctly? Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas “Group Box” Do pages print legibly without cutting off text? Does the site convey a clear sense of its intended audience? Few more testing can be done with respect to CSS validation, HTML or XHTML validation, Ajax and JQeury functionality, Header and footer sections, Page content alignment to center, LHS or RHS, Special characters with HTML character encoding, Page zoom-in and zoom-out functionality, CSS Reset
Preferences	JavaScript Off,   Cookies Off,   Security( High, Medium,  Low), Pop Up blocker, Download File Blocker,   Delete Browsing History

When?

Based on your Project context, it is better to consider the below points when deciding about the schedule of BCT

• Important & Complex functionality of the applications tested and is in stable condition
• GUI Design is relatively stable and is not scheduled for a major haul
• Contains browser plug-in’s related to Flash, Flex, Silver light etc

Depending up on the Application stability, Environment availability BCT is generally done towards the end of the project or just before UAT; however there is no defined time during which you need to do BCT. 

The suggestion would be consider your project context to decide, when you would do BCT.