Biased testing and micro-coaching

J. Landman Gay jacque at hyperactivesw.com
Fri Jul 7 16:09:31 EDT 2017


That's a good summary. It's tedious sometimes but essential. The hardest 
part by far is keeping your mouth shut. If I had a one-way mirror in a 
sound-proofed room I'd use that. Another method might be to have the 
user share their screen and turn off your microphone, but screen sharing 
is not easy on mobile apps.

On 7/7/17 2:49 PM, Jonathan Lynch via use-livecode wrote:
>>From reading these, it looks like my basic steps are these:
> 
> 1. Make changes to the app
> 
> 2. Test for usability myself a dozen times, trying things in different orders  and in different ways to make it fail
> 
> 3. Have my testers, which is really about 3 family members, test it to make it fail
> 
> No coaching, no hints
> 
> Directly observe their tests very closely
> 
> Make notes on any moments of confusion, even if they minor
> 
> Interview them, asking what they were thinking at each step
> 
> Adjust the help file and add hints - and test those as well
> 
> 4. Fix as needed and retest
> 
> 5. Publish
> 
> 6. Try to find virgin testers for next time, varying in age and mindset
> 
> Does that sound about right?
-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com




More information about the Use-livecode mailing list