1. ## Effort Estimation

Hi Folks,

Please let me know how to calculate estimated effort for test case authoring and execution for maintenance project.

Cheers
D G

2. ## Re: Effort Estimation

Testcase authoring effort you can calculate by formula is

#no.of testcases/Acual hours you spent for authoring

Testcase Execution effort

#no.of testcases/Exuction effort in hours

Effor variations

(ActualEffort-Planned Effort)*100/Planned Effort

let me know if any clarifications

Regards,
Kishore

3. ## Re: Effort Estimation

[ QUOTE ]
#no.of testcases/Acual hours you spent for authoring
#no.of testcases/Exuction effort in hours

[/ QUOTE ]

What does this have to do with creating an estimate?

4. ## Re: Effort Estimation

Based on above calculation. You can estimate ur Testing process for the project

2) you can also find weather your in schedule or not

3) And also you find how effect ur testcases finding the issues.

Please let me know if any clarification

Regards,
Kishore

5. ## Re: Effort Estimation

[ QUOTE ]
Based on above calculation. You can estimate ur Testing process for the project

[/ QUOTE ]

Sorry, but that makes no sense.

The original poster asked how to estimate.
You gave formulas to calculate "testcases written per hour" and "testcases executed per hour".

6. ## Re: Effort Estimation

This is a difficult task if you have no historical data. Ideally, you'd have a couple other projects under your belt that you could compare the current project to.

If you have this data then you need to estimate the approximate size of the project compared to the other. Now, when I say size, that doesn't necesasrily mean lines of code. This could mean the number of interface elements, decisions to be made within the application, and any benchmarks that are in place.

If you have this type of information then you can get a pretty good idea of how long it might take to write test cases for the project based on comparing the two. Otherwise, you can also try estimating the number of test cases required and then take that into consideration along with a good average time to write a test case.

In either case, you should also add some sort of a buffer, whether it be 10% or 15%, which will afford you time for unexpected issues or low-ball estimates.

As far as estimating execution, I think this is much more reliant on historical data, in my opinion. If you are expected to give an estimate of time that is somewhat accurate, then it's very difficult to do so if you have never tested an app before. If you have, then you can probably come pretty close. If you know of components in this app that have been tested in other apps, this is another piece of the pie that you at least have a rough idea on.

In general, when I'm estimating for a new project (never been tested before) I will throw out more extreme buffers than if I'm estimating for a more mature product. I think that it's important that you don't get yourself into a position where your testing is running 2 or 3 times longer than expected. However, I think that if you have a little overage on a new project, it is usually more acceptable.

7. ## Re: Effort Estimation

[ QUOTE ]

Please let me know how to calculate estimated effort for test case authoring and execution for maintenance project.

[/ QUOTE ]

From your post, it appears that you are working on a "maintenance" project!
Do you have access to the existing metrics for the project?(prior to moving to maintenance phase)
That might be helpful to perform some guesstimates!

8. ## Re: Effort Estimation

hey folks,

What i want is the expected time require to author and execute test cases for a project in maintenance phase. I mean how much time it will take to author test case of a screen having a small change of 2,3 text boxes functionality.

9. ## Re: Effort Estimation

yea you are right Joe , i m more concerned about the estimated effort not actuals [img]/images/graemlins/smile.gif[/img]

Regards
D G

10. ## Re: Effort Estimation

[ QUOTE ]
hey folks,

What i want is the expected time require to author and execute test cases for a project in maintenance phase. I mean how much time it will take to author test case of a screen having a small change of 2,3 text boxes functionality.

[/ QUOTE ]

Hey common, how will we know how long will it take for your testers to have a test case of a screen having a small change of 2,3 text boxes functionality.????

Each tester is different. 1 tester might take 4 hours, the other tester for the same task might take 3 hours.

Effort Estimation can be made through past experiences (If you have worked on a similar task) or as Brent said... through Historical Data.. There are other methods too which can be googled.?
The tester/Developer himself is the best judge for Estimation. He will know how long he will take to do the job, and can get the estimation approved.

There is no way for some XYZ to answer this question [img]/images/graemlins/confused.gif[/img]

Page 1 of 2 12 Last

#### 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.