It depends of which estimation techniue you are using...if it is WBS then you will have to break all the performance testing activities in smaller parts then using your prior experience you can estimate no of days for each activities. Also take some time for each activity in spare so that you can get time in case of any environmental or deploymental delay or issue. Incase of WBS following activities can be considered:
A. Planning
1. Understanding of application
2. Identifing of NFR
3. Finilazing the workload model
4. setup of test environment and tools& monitors
5. Preperation of Test plan
B. Preperation
1. Creation & validation of Test scripts
2. Creation of Test Data
3. Creation of business scenarios
4. Getting approval
C. Execution
1.Run a dummy test
2. Baseline test
3. Upgrade or tune the environment (if needed)
4. baseline test2
5. final performance run
6. Analysis
7. Final performance run2
8. Benchmarking etc..
D. Reporting
1. Creation of performance test report
2. Review with seniors or peers
3. Update the report
4. Publish the final report.
5. Getting signoff
A. Planning
1. Understanding of application
2. Identifing of NFR
3. Finilazing the workload model
4. setup of test environment and tools& monitors
5. Preperation of Test plan
B. Preperation
1. Creation & validation of Test scripts
2. Creation of Test Data
3. Creation of business scenarios
4. Getting approval
C. Execution
1.Run a dummy test
2. Baseline test
3. Upgrade or tune the environment (if needed)
4. baseline test2
5. final performance run
6. Analysis
7. Final performance run2
8. Benchmarking etc..
D. Reporting
1. Creation of performance test report
2. Review with seniors or peers
3. Update the report
4. Publish the final report.
5. Getting signoff
No comments:
Post a Comment