What is the best testing method to carry out for an evaluation tool.?

I designed a software evaluation tool for research purposes. It helps monitor what kinds of errors users come across. What is the best test method I can use for testing.


Any info would be great.

What is the best testing method to carry out for an evaluation tool.?
Strange.





The design of a software evaluation tool should have taken into a kind what kinds of errors users were most likely to come across. Allowances for these errors or mechanisms to test them would then have been built into the tool.





More importantly, I can say from experience, that when you consider what kinds of errors users come across, first you'll have to separate system, application, hardware, driver, and user-related (read user-caused) errors.





Unfortunately, users cause most errors! So, from the design standpoint it will be extremely difficult to test for "errors" without considering 'normal' system operation in the hands of clueless users.





Evaluating software in the lab is concerned most with how well applications relate to the system, how well applications inter-relate with each other, how software functions across different browsers, how well it will recover from error conditions, all of the things that will matter before a user gets his/her hands on it.





Then the fun begins.





Where in the life-cycle of a software package will you be able to define a set of parameters that test its design functionality and tests its operation under normal operating conditions, meaning at the hands of users?
Reply:I would say some kind of beta testing with some trusty people (if you don't want your project to be published all over the net already.)
Reply:Get a group of people to test and break your software. Then, use a bug tracker to track what errors people are getting. Most of this can be done through the web.