Thanks:  0
Likes:  0
Dislikes:  0

# Thread: Linda's PAPER on estimating testing

1. ## Linda\'s PAPER on estimating testing

Hello everybody, I've read every single post in this forum and found lots of great insights to estimating testing. Particularly the posts on the topic "How long it will take". And I was wondering if anybody has a copy of Linda's paper. Did Linda ever publish the paper on the download section?

I am very interested in knowing the details of Linda's estimating approach. If you have a copy please send me a copy to my email: dgarcia@baufest.com

Thanks a lot!
Diego

2. ## Re: Linda\'s PAPER on estimating testing

Linda Hayes has quite a few white papers posted on http://www.stickyminds.com but I didn't recall anything on test estimating so I just checked and found nothing. If you could tell me the name of the paper, maybe I could find it. Rex Black does have a paper on it though.

Rich

3. ## Re: Linda\'s PAPER on estimating testing

Rich

He may be referring to Linda Wilkins - ljwilkins

Below is the approach she has posted here many times.

If it is after test requirements are developed, but before test cases are written:
(# test requirements) /3 = # test cases
(# test cases) X 2 hours = amount of time required to develop test cases
If it is after test cases are written:
(# test cases) X 1/2 hour = time to manual test
(#test cases) X 1 hour = time to develop new automated tests
(time to manual test) X 1/3 = run debugged automated tests
If it is during testing itself, you can take the above figures and determine the current error rate by dividing the number of errors found by the number of tests run. For example, 35 errors found by 200 tests executed = 17.5%. Apply this number to the number of scripts left to run for an expected errors figure. Add the known errors to the expected errors. Assume you'll have to run at least one script to verify each error, again using the 1/2 hour per test figure.
Here's an example of the whole process:
I've identified 2000 test conditions.
2000/3 = 667 test cases
667 test cases X 2 hrs = 1334 hours to document test cases
667 test cases X 1/2 hr = 334 hours to manually test
667 test cases X 1 hr = 667 hours to automate
tests

(334 hours to manually test) X 1/3 = 112 hours to rerun automated scripts
Thus far, 250 scripts run, 42 errors found.
42 errors divided by 250 = 16.4% error rate
417 scripts left to run X 16.4% error rate = 68 anticipated errors
42 + 68 = 110 bugs/retests
110 tests X 1/2 hr = 55 hours
Time left to test = (417 X 1/2 hour) + 55 hours = 263 hours

4. ## Re: Linda\'s PAPER on estimating testing

I believe corklad is correct. At one point, Ms. Wilkins stated that she had a paper that covered the info in-depth, and that she would eventually post it. So far, no one has found this paper.

See the following for the original thread:
http://www.qaforums.com/cgi-bin/foru...;f=40;t=000062

5. ## Re: Linda\'s PAPER on estimating testing

Oops, my bad! Sorry, I should have read the other thread too. Those are impressive numbers, I just wonder about their accuracy. She's allowing a half hour per manual test. Does that include setup, teardown, documentation, and artifacts archiving time? We usually use 1 hour per manual test, but that depends on the complexity of the test itself. Plus the data transfer rates vary tremendously.

Oh well, maybe it's a little better than a 1:1 against development time.

Rich

6. ## Re: Linda\'s PAPER on estimating testing

I have used this method to get an early figure based on some form of calculation as opposed to just guessing and I have to say that I find it very useful.
It means at requirements phase, I can give fairly reliably, the number of test cases to write, the amount of time this will take, the number of test cases to run, the amount of time this will take. Plus I have been also tracking the number of errors we log in execution over the last number of projects so at that early stage I am able to predict the number of errors we will find as well.

This is a lot of information and all before the developers have even coded and a lot better than 1:1.33 (Dev Time:Test Time).

It might need a bit tweaking (look at historical data - this is what I did) but I’d recommend it

7. ## Re: Linda\'s PAPER on estimating testing

Well, the topic heading got my attention....

I checked with my management some time ago and since the white paper is their "intellectual property", I would have to do a total rewrite, removing client names and company references throughout in order to post in a PUBLIC forum.
I just haven't had the time, and frankly, their response made me a little nervous. They do not, however, own the estimating methodology or any of the published references in the paper.

What I can and have been doing, however, is sending a copy to individuals that EMail me or send me a private message with their return EMail account. I've updated my profile to allow my EMail address to be viewable.

Just to give a helpful hint to everyone else out there, we had a few go-getters in our firm write a slick little macro where you just put in a few figures and all of the estimates are calculated for you...

- Linda

8. ## Re: Linda\'s PAPER on estimating testing

Linda

Your email address does not appear on your profile - could I get a copy plz - you can email to:

aoleary@csedge.com

Thanks

Adrian

9. ## Re: Linda\'s PAPER on estimating testing

I have a lot of material on test estimation: my unpublished book on this subject runs about 400 pages, with another equally sized book on test planning, and others on specialized topics such as performance testing and database testing which contain stimating methods. I'll share my material on the condition that you are willing to do some work to apply it and feed back your estimate data on projects (context details, estimates, actuals) for anonymous aggregation.

Ross

10. ## Re: Linda\'s PAPER on estimating testing

I'd be delighted to help out Ross! My email address is aoleary@csedge.com

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•
Search Engine Optimisation provided by DragonByte SEO v2.0.36 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Resources saved on this page: MySQL 8.11%
vBulletin Optimisation provided by vB Optimise v2.6.4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.2.8 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominate (Lite) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 01:34 PM.

Copyright BetaSoft Inc.