"Usability Testing" a.k.a. testing the software from a users point of
How can a QA/QC person really do this, and do it well? Should the testers
also do this Usability testing? In our company, the QA/QC staff construct
functionality lists and the test outlines from the specifications directly.
We get to know these specifications intimately! We are also responsible
for the usability testing. Therefor we are biased and know what the
program will and won't do.
The problem comes down to trying to perform the usability testing in an
objective, fresh way. How do you experts keep your familiarity with the
specs from clouding your "user" judgement?
Interested in automating your Laboratory results, accurately and quickly?
Visit us at www.labtronics.com for our complete list of software packages.
Pick up our free Labtimer as well!