>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? Sent from my iPhone > On Jul 7, 2017, at 1:53 PM, jonathandly...@gmail.com wrote: > > Thank you, Jacqueline > > Sent from my iPhone > >> On Jul 7, 2017, at 1:39 PM, J. Landman Gay via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> http://hyperactivesw.com/resources_testing.html >> >> >>> On July 7, 2017 6:59:52 AM Jonathan Lynch via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> What steps do you guys follow for accurate testing when you don't have a >>> budget for proper official testing procedures? >> >> -- >> Jacqueline Landman Gay | jac...@hyperactivesw.com >> HyperActive Software | http://www.hyperactivesw.com >> >> >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
