User Acceptance Testing
I have recently been hired as a computer consultant at a rather large corporation. Among a number of tasks that have come up is the process of performing User Acceptance Testing. I have never done anything like this on a formalized scale, having preferred hallway usability & rapid prototyping to illustrate a program's function to my clients in the past.
Do they have a formal requirements document and/or use cases? There are your templates for testing...
Not really. This project was an ad hoc solution to a reporting problem that grew into a full solution through featuritis. As such, I coded it with a bent towards its output (the reports) as opposed to the usability, which was placed second. I have high level use cases (basically ten or so scenarios for using the system), but no standard requirements documentation or project doc.
You'll need to go back and reverse engineer something like Use Cases in order to generate the right questions to ask.
This I am fine with. I think my baseline cases give me good grounds to start with and I'm certainly familiar with more formal use case / project planning processes than were used on this system. It shouldn't be a problem to get the user acceptance worked out as far as determining which business flows to place in the documentation.
Isn't "User Acceptance Testing" an odd phrase? I've never found a user yet that I would accept. Maybe I am not testing them thoroughly enough.
Fog Creek Home