Today I was testing a change to the add to cart/basket page UI on my current project and I came across this age-old classic bug:
The above screenshot (heavily cropped) shows two quantity selectors on a basket page, alongside redacted product names, stock indicators and prices. One quantity selector has a value of ‘e’ (Euler’s number), and the second has a value of ‘-200’.
In this case, nonsense values like this don’t actually cause any real problems - user input is effectively ignored until a valid value (1 or higher, integers only) is typed in the field. It also raises the question of what should happen when 0 is typed - should it instantly remove items from the basket (replicating the trash can button that is shown when the quantity is 1), or does that create more problems than it solves?
Anyway, this example got me thinking about some of the common quick, low-hanging fruit tests that I will perform when exploring a new feature, and I thought it might be fun for people to share their own - so… what are yours?
More examples of quick tests:
- Emojis and other unicode characters in input fields.
- Visiting URLs that should be restricted to a specific user while logged out and/or logged in as a different user.
- Uploading an obnoxious animated GIF as a profile picture that will be viewed by other users.