HOW TO Start For NEW QA Process ?
Printed From: One Stop Testing
Category: Quality Assurance @ OneStopTesting
Forum Name: Quality Methodologies / Streams @ OneStopTesting
Forum Discription: Any Good Testing Engineer must know about All the Quality Certifications & Methodologies like ISO, IEEE, CMM, PCCM, CMMMi, XP, Agile and many more.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=1146
Printed Date: 02Apr2025 at 1:17pm
Topic: HOW TO Start For NEW QA Process ?
Posted By: Vivek98
Subject: HOW TO Start For NEW QA Process ?
Date Posted: 30Apr2007 at 5:29am
The Testing
estimation process in place was quite simple. The inputs for the
process, provided by the development team, were: the size of the
development team and the number of working days needed for building a
solution before starting systems tests. The testing estimation process
said that the number of testing engineers would be half of the number
of development engineers and one third of the number of development
working days. A spreadsheet was created in order to find out the
estimation and calculate the duration of tests and testing costs.
They are based on the following formulas:
Testing working days = (Development working days) / 3.
Testing engineers = (Development engineers) / 2.
Testing costs = Testing working days * Testing engineers * person daily costs.
As
the process was only playing with numbers, it was not necessary to
register anywhere how the estimation was obtained. To exemplify how the
process worked, if one development team said that to deliver a solution
for systems testing it would need 4 engineers and 66 working days then,
the systems test would need 2 engineers (half) and 21 working days (one
third). So, the solution would be ready for delivery to the customer
after 87 (66+21) working days. Just to be clear, in testing time, it
was not included the time for developing the test cases and preparing
the testing environment. Normally, it would need an extra 10 days for
the testing team.
Time Estimation method for Testing Process
Note: following method is based on use case driven specification.
Step 1 : count number of use cases (NUC) of system
step 2 : Set Avg Time Test Cases(ATTC) as per test plan
step 3 : Estimate total number of test cases (NTC)
Total number of test cases = Number of use cases X Avg test cases per a use case
Step 4 : Set Avg Execution Time (AET) per a test case (ideally 15 min depends on your system)
Step 5 : Calculate Total Execution Time (TET)
TET = Total number of test cases * AET
Step 6 : Calculate Test Case Creation Time (TCCT)
usually we will take 1.5 times of TET as TCCT
TCCT = 1.5 * TET
Step 7 : Time for ReTest Case Execution (RTCE) this is for retesting
usually we take 0.5 times of TET
RTCE = 0.5 * TET
Step 8 : Set Report generation Time (RGT
usually we take 0.2 times of TET
RGT = 0.2 * TET
Step 9 : Set Test Environment Setup Time (TEST)
it also depends on test plan
Step 10 : Total Estimation time = TET + TCCT+ RTCE + RGT + TEST + some buffer...
Example
Total No of use cases (NUC) : 227
Average test cases per Use cases(AET) : 10
Estimated Test cases(NTC) : 227 * 10 = 2270
Time estimation execution (TET) : 2270/4 = 567.5 hr
Time for creating test cases (TCCT) : 567.5*4/3 = 756.6 hr
Time for retesting (RTCE) : 567.5/2 = 283.75 hr
Report Generation(RGT) = 100 hr
Test Environment Setup Time(TEST) = 20 hr.
|
|