Nasreen Azam
Joined: 24 Apr 2008 Posts: 2 Location: Bangalore
|
Posted: Thu Apr 24, 2008 7:26 am Post subject: |
|
|
To Estimate test schedule, you need to know the complexity of the funationality to be validated, need to know the importance or priority of the functionality to the customer, need to see how much is the feasibility of testing, meaning how much % of validation is possible with your current test set up etc.,
Normally, if you have a similar product developed in the organization, then it makes it easier to borrow the estimates and add your justifications for plus/minus.
If you have a totally new feature to estimate, then the best you can do is to break down the requirement specifications for this feature and arrive at number of test cases. Normally the effort per test case creation would be b/w 5-20 minutes (see complexity) and test case execution effort would be 10-20 minutes.
Risk factors are...
1. Not enough test setup.
2. % of validation that can be achieved with the current competency and test setup
3. Inadequate requirement specifications.
4. Possibility of changes in requirement specifications during development of the feature.
5. Unplanned leaves/resignations.
6. Shrunken test schedules.
7. Inadequate pre-integration and Unit tests.
etc etc., |
|