Thanks:  0
Likes:  0
Dislikes:  0

1. How to estimate Testing

Is there any model for testing estimation? I want information on how to estimate testing ? on what basis estimation can be made?

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

2. Re: How to estimate Testing

There is a forum on Estimation - you are better off asking this question there. And, more specifically, post *after* you've read the threads there.

------------------
-Suresh Nageswaran
punekar@yahoo.com
Cognizant Technology Solutions,
Pune, India.

3. Re: How to estimate Testing

Moving to Estimation and planning....

------------------
Jean James, CSTE
J.James Consulting, Inc.
"I deliver what I promise, and I only promise what I can deliver."

4. Re: How to estimate Testing

We estimate based on prior experience. How long did it take last time we did a similar test effort? How long were the delays we hit in the past? Are those delays likely on this project?

http://www.idiom.com/~zilla/Work/Softestim/html/

5. Re: How to estimate Testing

How to estimate testing?

If you have tested something simular, you can always use that as a basis. But lets look at testing something new and complex.

To me, estimating for such is all about properly partitioning the system into right-sized and equal-sized pieces. If I have decomposed the system into approximately equal-size pieces that are not too big, then it has been my experience that estimating by summing the parts into a whole is an easy and fairly accurate process.

I like to use Data Flow Diagrams (Activity Diagrams is the OOA equivalent). I decompose the system into individual functions that each can be rigorously described (using text or graphics) on a page or so.

Tony Markatos

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

6. Re: How to estimate Testing

Addendum to my last post on this subject:

Again, it has been my experience that estimating, especially for unfamiliar and larger-scale systems, is all about breaking the system down into right-sized (i.e., not to big) and equal-sized pieces.

It is especially important as Functional Testers that we break down a logical, essential model of the system - and NOT break down modules, units, and/or components. Modules, units, and components are a designers implementation.

It is crucial that we deal with a logical functional system - not the physical design of a system because, as Functional Testers, our main goal is to test essential functionality (i.e., test what MUST be tested). And our estimating needs to be in-line with that goal.

Tony Markatos

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

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.