Mobile QA Zone

A Mobile Application Testing Community

Testing effort estimation methods used by companies..

There are basically lots of test estimation methods like
delphi method
Analog based testing technique
software size base technique
test case emuration based technique
Task or event or velocity based technique
etc...
Delphi,analog and software size base testing is not quantative or u will not get the accuracy.but if we use case emuration based technique and task based technique will give u a better accuracy as compare to others.so mostly companies prefer these two techniques.u can able to audit also.

before this i will tell u about kind of testing and what is velosity or task.
White box testing-->Basically it is done by the developre this is the first phase.
white box testing contain
Integration testing and system testing it will be done by both developer or a tester.
Black box testing-->In this testing tester is envolved and done testing behalf of his previous experience and with the help of test case.

Kind of testing in black box
Functional-->related to test case/application dependent
load -->depends stand alone /client server app
stress-->same
volume--the software to a high volume of data and see the
performance, whether it degrades
end to end-->after intigration testing
possitive testing-->use case refer
negative ntesting-->test case contain both(+-)
user mannual testing-->compare with user mannual or help text
user acceptance testing-->this testing is based on requiremt and use case.this is the final docs before production release.
deployment testing
install/uninstall->it comes under smoke testing for mobile domain this is a first testing createria to pass the build with out any error.
camparision testing-->basically companies are creating comparision matrics behalf of that we will do testing.
initutive testing-->This is a very basic testing which is done by any body inside the company or out side the company without using help and other docs.

now come to the point
Test Case Enumeration based Estimation
1. list down all the test cases
2. Estimate testing effort required for each test case(hours/days)
3.define use Best Case, Normal Case and Worst Case scenarios for estimating effort
needed for each test case
4. Compute Expected Effort for each case using Beta Distribution
mantra for estamation (Best Case + Worst Case + (Normal Case) /2)
test caseid discription best worst normal expected
1 check test environment 1 2 1.5 1.5
2 install software 0.75 1.5 0.5 1.04
3 insure defect mach 1 3 1.5 2.02
4 login screen 0.05 0.2 0.1 0.108
4.668
etc
4.668 hours are the estimated time for your project

Next is event based testing but with same mantra
taskid phase task specification best worst normal expected
1 test planning determine type of test 1 2 1.5 1.5
2 test planning test env.. 0.75 1.5 0.5 1.04
3 test planning est cost,resourse 1 3 1.5 2.02
4 design test case module 1 0.05 0.2 0.1 0.108
5 design test case module2 12 20 15
6 conduct test module3 10 18 15
7 conduct test conduct test cse 10 18 15
8 unit module1 13 25 14
9 acceptance inter 20 25 22
10 defect report logging 2 5 3

total=Best Case + Worst Case + (Normal Case) /2)

got it.........

Cheer's

Views: 970

Comment

You need to be a member of Mobile QA Zone to add comments!

Join Mobile QA Zone

Comment by Rakesh on January 30, 2012 at 1:08pm

Compute Expected Effort for each case using Beta Distribution
mantra for estamation (Best Case + Worst Case + (Normal Case) /2) so i wanna to ask that  what is this "(Normal Case) /2)"  ?

Comment by Rakesh on January 10, 2012 at 4:57pm

K...Thx a lot Sanjay.... :)

Comment by sanjay kumar on January 10, 2012 at 4:23pm
both u will adopt generally i am using average formula to estimate
Comment by Rakesh on January 10, 2012 at 4:21pm

Sanaj what do you think which estimation is good and well accepted the Formula one or if we take the average ?

Comment by sanjay kumar on January 10, 2012 at 4:17pm
yes some times people are using test case or some times people using use case to estimate testplan or project plan.
each test case phase is requriment gathering,test design,write bug in bug tracking,verify,it is collected the whole time.based of that we will estimate.
Comment by Rakesh on January 10, 2012 at 4:12pm

Thnks but sorry i asked some other Q too that "Can we apply this formula in any case for estimation or taking average is the good one" ?

Comment by sanjay kumar on January 10, 2012 at 3:38pm
p=best time
n=normal time
e=worst time
no problem whenevr u have any doubt u can ask qestion..thanks sanjay
Comment by Rakesh on January 10, 2012 at 3:35pm

Many Many Thanks to u but in the given formula ... what is 4 and 6  and can you please explain shortly if possible i mean can we apply this formula in any case for estimation or taking average is the good one ?  And is there any nomenclature for thei 'P" "N"... ? i hope this will be my   last Question or doubt..Pardon me

Comment by sanjay kumar on January 10, 2012 at 12:05pm
Test Estimate = P + (4*N) + E / 6
3+4*2.5+5/6=10.0/3=3.3
3.3 is an estimate time for test case

second method is take an avarage=(3+5+2.5)/3=3.5 there is no big difference.
thanks
sanjay
Comment by Rakesh on January 9, 2012 at 10:24pm

I understood...and thx a lot ..... i just want to ask you one thing .As there is a feature for best base it takes 3hrs and worse 5 hrs and for narmal it takes 2.5hrs  can you pleae tell me the estimation  and what is this formula actually  total = bestcase+worsecase+normalcase/2  my mail id is mobile.rakesh@gmail.com

Sorry to asking this much but actually i have been assigned by  many features and i have to give the estimation for this and tht to i am doing it 1st time...so ....

 

 

 

© 2014   Created by Anurag Khode.

Badges  |  Report an Issue  |  Terms of Service

Welcome to Mobile QA Zone, a Next Generation Software Testing Community.Invite your friends to join this community.Write to us to become a featured member.