1. Test Effort Estimation

Hi,

Does anybody know how to do the effort estimate based on the following attributes

No.of lines of code, no.of tables, no.of stored procs and no.of functions.

e.g.
1.No.of lines of code = 159,218
2.Total no.of tables = 38
3.Total no.of stored procs = 292
4.Total no.of functions = 95

It would be great if you can share your experiences, case studies, estimation templates based on the above attributes.

2. Re: Test Effort Estimation

That's exactly what this forum is all about. If you do a search in this forum I think you will find many different methods of calculating the effort. Bare in mind, accuracy is not something you will find though.

3. Re: Test Effort Estimation

Vish,

You could consider the relative complexity of the code and try to ascertain the number of tests you need to perform. The following example is purely fictitious to illustrate the kind of logic you might use for estimating, based on experience in your organization:

[AIV] Average input variables passed
[ASI] Average # sample inputs per variable

Make some assumptions and apply that to your test estimating example:

095 Functions. x [AIV] x [ASI] = #### Tests
292 Procedures x [AIV] x [ASI] = #### Tests
038 Tables.... used in the tests
-------------------------------------------
Total number of tests to execute #### Tests
Number of tests per person hour: #### Tests /
-------------------------------------------
Number of person hours for tests #### Hours
Number of testers available # /
-------------------------------------------
Number of hours per test cycle ### Hours

Error rate experience 5 @ 800 lines of code
Error expectation 159,218 / 800 = 199 errors
Total number of bug fixes / hour 6 (4 dev.)
--------------------------------------------
Number of hours waiting for fixes 33 hours
2nd Cycle @ 40% of cycle 1 fixes 13 hours
3rd Cycle @ 40% of cycle 2 fixes 5 hours
--------------------------------------------
Total hours to use for regression 51 hours

Many posts are asking about the use of metrics in testing, unfortunately in the context of making performance judgements. In this example you can see how you can make positive use of "averages" that allow you to estimate future work effort. It is never perfect, and this is certainly not the only way to approach it, but it is one way if you start of with basic attributes as listed above.

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.