1. ## Testing estimates

User (KIvanov@STSSystems.com) posted:

If any of you out there have any formulas/hints about how to estimate a
testing effort, I would really appreciate them. The information we are
provided with a development estimates for the features and very, very high
level requirements. The testing estimates would include learning all the
business rules and functions, developing test plans for those areas, and
executing them once. TIA.
Katherin Ivanov
Quality Assurance Team Leader, Connected Customer*

STS, an NSB Company
kivanov@stssystems.com www.stssystems.com
Tel: (514) 426-0822, ext. 2175

---

2. ## Re: Testing estimates

User (david.marsh@gb.abb.com) posted:

Think how long you want, quadruple it,, project manager cuts the time in
half, another quarter lost through late delivery. Test time just long
enough to do the job.

---

3. ## Re: Testing estimates

User Ian Blair (blairi@gaelnospammquality.co.uk) posted:

We use a formula based on the number of test cases to be executed and the
number of failures expected.

E.g. for a first release of a particular app we estimate 10 mins per test
case and expect 50% failure rate. For failed cases we estimate 30 mins.
Adjust the numbers to suit your own project. Its simple but we find it to be
surprisingly accurate.

Ian.

---

4. ## Re: Testing estimates

User Aidy Rutter (AidyR@TrustMarque.com) posted:

As soon as you get a requirements doc the test-plan should be developed in
concurrence with technical doc/model. They should finish about the same
time.

Business rules/functions - tell them you need use-cases, both textual and
visual. I don't want to learn about the A-U-T, I should be able to look at a
use-case to figure out how software/ a system works.

From the req doc you enter test-cases in TestManager. So how many
requirements have you got? how many test cases? How long would it take to
run those test cases?

Break the testing down into phases and iterations. In the discpline of
testing you must plan test, design test, implement test, execute test and
evaluate test.

Aidy

5. ## Re: Testing estimates

User Crunk John (ext3jpc) (ext3jpc@ups.com) posted:

All I can suggest is to think about how long you think it will take you and
multiple by 4. Tell them that is how long it will take, and when you finish
in record time just by coasting through it; they will think you are a genius

John

6. ## Re: Testing estimates

User Ian Blair (KIvanov@STSSystems.com) posted:

Interesting.

Just so I'm clear. You estimate that 50% of cases will fail. So that is:

10 mins per test for 50% of tests
30 mins per test for 50% of tests

Is that it?

Does that include the time to read the requirements, prepare the test plans,
and manually execute them? If not, what are you accomplishing in that time?
TIA

Katherin Ivanov
Quality Assurance Team Leader, Connected Customer*

STS, an NSB Company
kivanov@stssystems.com www.stssystems.com
Tel: (514) 426-0822, ext. 2175

From: "Ian Blair" <blairi@gaelnospammquality.co.uk>
Date: Wed, 18 Jul 2001 15:21:14 +0100

We use a formula based on the number of test cases to be executed and the
number of failures expected.

E.g. for a first release of a particular app we estimate 10 mins per test
case and expect 50% failure rate. For failed cases we estimate 30 mins.
Adjust the numbers to suit your own project. Its simple but we find it to be
surprisingly accurate.

Ian.
---

7. ## Re: Testing estimates

User Ian Blair (blairi@gaelnospammquality.co.uk) posted:

Sorry, on re-reading you post I realise I did not answer accurately. That
does not include any of the preparation work, planning etc. Only the
estimated time required to execute the known and documented test cases.
These are valid numbers for a past project. We have 30mins per failed case
to allow for investigation, re-test and writing the report. After a few
projects we refine the numbers and it works very well. In the first release
of the project referred to 60% of cases actually failed. Obviously time
taken to execute a test will vary greatly with the type of AUT.

Regards,
Ian.
---

8. ## Re: Testing estimates

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Robot:
User Ian Blair (blairi@gaelnospammquality.co.uk) posted:

We use a formula based on the number of test cases to be executed and the
number of failures expected.

E.g. for a first release of a particular app we estimate 10 mins per test
case and expect 50% failure rate. For failed cases we estimate 30 mins.
---
<HR></BLOCKQUOTE>

How do you estimate the number of test cases? Also, do you include the time to create the test cases in that 10 minutes, or is that separate?

------------------

#### Posting Permissions

• You may not post new threads
• You may not post replies
• You may not post attachments
• You may not edit your posts
•

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.