Join Morten Rand-Hendriksen for an in-depth discussion in this video Break and edge-case testing, part of Mapping the Modern Web Design Process.
- When accessibility testing is done and any accessibility issues have been addressed and remedied the next step is what I call Break and Edge-case testing. Here you are submitting the site to scenarios where things don't work the way they're supposed to or the user does something unexpected. This can usually be done in-house but also benefits from some third party testing. Break Testing, consist of literally breaking a component of the site and seeing how it behaves.
Ensure image all texts follow the alternative text decision tree, that videos are accompanied by full transcripts for when the video or audio does not work, and that the visitor is clearly notified if a crucial element is not being displayed. Edge-case testing means making sure rare or unusual behavior on the site is accounted for. The most basic forms of Edge-case testing involve visiting a broken link to test the 404 page and entering searches with no results.
You should also test for archive and search pages with only one result, pages with a high number of comments, and other low or high volume scenarios that may cause problems with the layout of a view. I also like to run tests on text, especially titles to make sure long sentences and very long words are accounted for. Forms must also be tested. Check all form validation steps and messages, ensure tab sequences are correct, and make sure character limits are not too low.
This is a personal pet peeve of mine. For whatever reason, name fields are often limited just below the length of my own name. Twitter for example, won't allow me to enter my full name. So for names, I use mine as an example. My name is Morten Rand-Hendriksen with a hyphen and it's usually too long and maxes out most fields. If my name fits, we're all good. Speaking of forms, the development team also needs to do a series of security tests to make sure entries are escaped properly.
Code injection, is a common vulnerability on modern websites and this should be accounted for and tested early on to ensure everything is secure. As with accessibility testing run every element through the necessary tests, take notes, and remedy any issues that arise before testing again. Only move on once everything is working properly.
- Understanding what your users care about
- Creating user personas
- Creating content priority hierarchies
- Testing wireframes and interaction patterns
- Establishing a three-track build process
- Incorporating accessibility principles
- Using content blocks
- Testing and revising your web design
- Optimizing for social media and SEO
- Launching your web design
- Getting feedback from users