Spotted another Facebook UI bug since one of my previous posts. UI bugs are not generally considered show stoppers. However if Usability and User Interface are your strongest product assets, these bugs should be considered release blockers. I am wondering if Facebook`s QA team ever reproduced this issue in-house!
With an exponential growth in web applications combined with the ease of accessibility via smart devices, it is important to maintain rigorous quality standards. A trivial bug on your website can take away the “wow” experience from your users and divert them to the competitors. Any team responsible for driving the testing of web products should be able to differentiate the different facets of web app testing:
- Web User Interface Testing
- Web Usability Testing
- Web application Testing
Though all three might end up having a sub set of shared test cases but all of them need to have their own release checklists. For example, Web User Interface Testing checklist could include:
- Colors – hyperlinks color standard, field backgrounds and page background color to be distraction free.
- Contents – uniform font size, uniform content when switching between previous and new pages, text alignment, text cases.
- Images – graphics properly aligned, graphics optimized to load, text wrapping around the image.
- Instructions – tool tips, activity progress messages
- Navigation – scroll bars, pop up message buttons – Cancel/OK, Link to home page on every page, keyboard enabled
- Look and Feel – consistent across all the pages
Here is an example of Web UI bugs from my recent browsing experience of Facebook: