Any rules of thumb for estimation of UAT effort - like 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 at least combining 1 requirement test with at least one other.
but that's just my initial guess. If there are some best practices, I'm all ears. Again, this is not for unit testing or systems testing, this is for user acceptance testing.
Answer
The best estimate you will get comes from the testers doing the testing. Outside of that type of estimate from the testers, you may be able to come up with some sort of percentage of testing time compared to development time.
Say that you had a 100 hour development task. You spend 20 hours on design, 80 hours on build. You might be able to come to the conclusion that it will take 15 hours to test, or 15% of development time. You could then apply 15% to your overall development estimate for UAT testing knowing that some will take longer, some less.