uat

Structured UAT approaches

As a developer I often release different versions of applications that I want tested by users to identify bugs and to confirm requirements are being met. I give the users a rough idea of what I have changed or new features that need testing, but this seems a bit slap-dash and not very well strucutured. I'd like to know what approaches ...

Does anyone have any rules of thumb for esimtation of UAT effort - like what's a rule of thumb for number of scripts as compared to the number of business requirements?

I'm attempting to estimate the number or testers required to test out a project. One method is to determine the number of scripts that will be required and was wondering if there was a rule of thumb for number of scripts as compare to number of requirements. I'm estimating 2 - 3. 1 for a sunny day type test 1 for a negative test 1 for...

How to get your clients to test

Hey, I build web apps for a living. An important but often painful process is client/user acceptance testing. How do you manage this process? i.e. How do you get them to test? Do you give them test scripts? Do you give them a system to log bugs and change requests/feedback. How do you get the client to understand the difference betwe...