James Bach wrote about “Blink testing” back in 2005 on the back of Malcolm Gladwell’s book Blink, recognising this as a powerful heuristic for testing. I’ve just gotten around to reading the book, rather than skimming, and have some further thoughts on some of the premises.
What is blink testing?
A blink test is any test that alters someway of viewing the application—size, time, position, focus, or sensory mode—to take advantage of people’s ability to spot patterns (or pattern exceptions) quickly. Like snap judgment, rapid pattern recognition is something that testers use all the time. It’s not always reliable, it’s often improved by removing information, and it can be improved by changing the observer’s context.
– Bolton & Bach
Your brain is very good at pattern recognition. It can spot anomalies in the ‘blink of an eye’.
In psychology, this is given the name ‘Thin-Slicing’. The ability to find patterns in events based only on ‘thin slices’ or narrow windows of experience.
It can be applied to any software to spot patterns, and conveniently, as I was writing this, Richard Bradshaw posted some excellent examples for mobile testing here: http://www.thefriendlytester.co.uk/2015/02/blink-testing-in-mobile-context.html
So, searching for more I also came across Joe Strazzere’s examples here:
These examples show effective ways blink testing, or thin slicing can be used to identify problems.
Using thin slicing in this way isn’t the only way it can be used though.
Experienced testers can thin slice to effectively analyse the quality of an application in seconds using their knowledge and expertise. That is, being able to make a swiftly informed opinion based on your knowledge of a particular application by using your subconscious as the comparator.
So for example: You have been testing some software for weeks or months. Your subconscious recognises any changes very quickly. You are able, in a split second to tell that something isn’t correct, without having any comparison.
In the book Blink, Gladwell relates a story of an ancient Greek statue that the Getty Museum was considering for purchase. All the scientific tests indicated that it was authentic, yet an art expert, within seconds of setting eyes on it, felt something was wrong with the statue. That the statue was a fake. And was indeed correct. This is an example of the power of in-depth expertise that is stored in long-term memory.
Even for software that you don’t have much experience of, this initial contact, what you see in the first few seconds or minutes, gives you an excellent idea of whether it works or not.
When exploratory testing, this kind of intuition is used constantly. Our unconscious makes good decisions, particularly in regard to things we don’t know how to verbalise. Which is another reason that being able to write effect test cases is the domain of very few experts.
Testing is problem solving and if you have to write down your thoughts to solve the problem you solve 30% fewer problems.1 i.e. writing test cases
Heuristics and First Impressions
Testing, uses both logic and insight and these first impressions need interpretation.
How each of us look at something will be different. How each person uses something will have different levels of responses. It is one facet of testing to identify these different interpretations and recognise the possible issues these interactions may cause.
Heuristics create conditions for successful spontaneity.
Knowing, for example:
Eyetracking visualizations show that users often read Web pages in an F-shaped pattern: two horizontal stripes followed by a vertical stripe.
…and armed with this knowledge, in your conscious, how does the web application that you’re testing perform when you view or use it this way; you may use it in combination with the blink test…noting what stands out whilst clicking through links and exploring further. Is there anything out of place? Does the design stand up to scrutiny? Is the most used path easy to use? Are common functions placed in a coherent way? Are important functions easy to spot? Does the amount of memory muscle required to use this application feel right for someone that uses the application rarely?
Testing is questioning and asking the right questions is important. Identifying something isn’t correct is a start, but being able to say why is an important skill for a tester. Particularly in cases where there may be disagreement.
If you’re testing, sometimes de-focus, don’t think about the problem in front of you and use your unconscious to uncover problems too. It can be effective.