Hi All,
Delivery Model in general says that how are you going to delivery me what i ask for with effective reviews, Optimum usage of resources & cost.Testing Delivery Model.... What does it mean by? It is nothing but what type of model we will follow for the execution of a particular testing project. The model changes according to the domain & complexity of the project. For example, A banking project it goes with clear communication processes where in it starts with Proposal, Knowledge Transfer , Test Preparation, Management, Defect Management,Test Maintance & Automation.
So a Test Delivery Model works on what type of project we work for based on that only lot of things are decided & we proceed on....:)
Happy Testing...:)
Thursday, July 22, 2010
Thursday, July 15, 2010
I Pledge for a Health Heart
I Pledge to work toward the heart-healthy of me health. the most important thisng is you need to start somewhere. I Start from today towards this path of a Healthy world...:)
Saturday, July 3, 2010
New Product Testing
Wow a new product in the market...Cool what does it do? Why is it here? So many questions we ask before we think of buying it. How do we know that the customers are going to accept this/like it. So what do i have to do to answer the above questions.
There is a light at the end of the tunnel for the above questions. So what is that? Lets explore more on that:
1.Feasibility testing – Using this technique we can find out whether the new product we planning to launch in the market is technically feasible to the business we are into.Patsula.com in its small business dictonary link defines this as "An analysis of a possible business opportunity that emphasizes income potential and likely expenses, with recommendations for an advantageous marketing approach". (Reference Link http://www.patsula.com/smallbusinessdictionary/ )
2.Verification & Validation – Popularly called as a V&V method it helps us to verify that the product meets the requirements and Validate the functionalities.Validation tells us that "Are you building the right thing?" and Verification says are "Are you building it right?"
3.PoC – Proof of Concept, small piece of business scenarios will be created for testing and then we will go for trial run with the required test environment needed for it. A Poc is mostly done, for an existing product which is successfully running in a windows (for example) the company may try to test it in a another platforms for a reaching more audiences. To find out whether the product is able to work on those platforms based on the outcomes of these test, they may either proceed or holdon.
There is a light at the end of the tunnel for the above questions. So what is that? Lets explore more on that:
1.Feasibility testing – Using this technique we can find out whether the new product we planning to launch in the market is technically feasible to the business we are into.Patsula.com in its small business dictonary link defines this as "An analysis of a possible business opportunity that emphasizes income potential and likely expenses, with recommendations for an advantageous marketing approach". (Reference Link http://www.patsula.com/smallbusinessdictionary/ )
2.Verification & Validation – Popularly called as a V&V method it helps us to verify that the product meets the requirements and Validate the functionalities.Validation tells us that "Are you building the right thing?" and Verification says are "Are you building it right?"
3.PoC – Proof of Concept, small piece of business scenarios will be created for testing and then we will go for trial run with the required test environment needed for it. A Poc is mostly done, for an existing product which is successfully running in a windows (for example) the company may try to test it in a another platforms for a reaching more audiences. To find out whether the product is able to work on those platforms based on the outcomes of these test, they may either proceed or holdon.
Sunday, June 6, 2010
Change the way
When things didn't go the way it has to go don't change the way but change the approach
Wednesday, June 2, 2010
Tuesday, June 1, 2010
Some Basic Test Metrics
Lets learn some basic test metrics...
The below metrics are some of the basic metrics which comes handy for testing professionals. There are more to add but below are the basics. Read them & use them...Happy Learning...:)
Effort(HM)= productivity(Hour-men/FP) * size (FP) FP means Functional Points.
For Example:
---------------------------
Effort = (Productivity * total afp)/ 21 *8
(here 21 is the no: of working days & 8 (is the number of working hrs per day)
so the total effort comes to = (12 * 400) / (21*8)= 28.57 manmonths~= 29 manmonths
12 is a random figure in hrs
Now assuming your average manmonth cost is 1 lakh ,so the total cost of developing
the software comes to 29 *1 = 29 lakhs
To Calculate Man Days = Total Effort/8 ( 8 is the 8hrs perday of work)
To Calculate Man Months = Man Days * 22 days.( No.ofdays depends on the company)
To Calculate Productivity ( test cases executed per day)= Effort /Size .
Rework Effort Ratio:
{(Actual rework efforts spent in that phase / Total actual efforts spent in that phase)} * 100
Test Case Adequacy:
No. of actual test cases / No: of test cases estimated
Test Case Effectiveness:
This defines the effectiveness of test cases which is measured in number of defects found in testing without using the test cases.
It is calculated as
No. of defects detected using test cases*100/Total no: of defects detected
Effort Variance :
{(Actual Efforts-Estimated Efforts) / Estimated Efforts} *100
Schedule Variance:
{(Actual Duration - Estimated Duration)/Estimated Duration} *100
The below metrics are some of the basic metrics which comes handy for testing professionals. There are more to add but below are the basics. Read them & use them...Happy Learning...:)
Effort(HM)= productivity(Hour-men/FP) * size (FP) FP means Functional Points.
For Example:
---------------------------
Effort = (Productivity * total afp)/ 21 *8
(here 21 is the no: of working days & 8 (is the number of working hrs per day)
so the total effort comes to = (12 * 400) / (21*8)= 28.57 manmonths~= 29 manmonths
12 is a random figure in hrs
Now assuming your average manmonth cost is 1 lakh ,so the total cost of developing
the software comes to 29 *1 = 29 lakhs
To Calculate Man Days = Total Effort/8 ( 8 is the 8hrs perday of work)
To Calculate Man Months = Man Days * 22 days.( No.ofdays depends on the company)
To Calculate Productivity ( test cases executed per day)= Effort /Size .
Rework Effort Ratio:
{(Actual rework efforts spent in that phase / Total actual efforts spent in that phase)} * 100
Test Case Adequacy:
No. of actual test cases / No: of test cases estimated
Test Case Effectiveness:
This defines the effectiveness of test cases which is measured in number of defects found in testing without using the test cases.
It is calculated as
No. of defects detected using test cases*100/Total no: of defects detected
Effort Variance :
{(Actual Efforts-Estimated Efforts) / Estimated Efforts} *100
Schedule Variance:
{(Actual Duration - Estimated Duration)/Estimated Duration} *100
Subscribe to:
Posts (Atom)