LR Script Creation: For a full script creation (which includes recording and customization), script creation may take from 3hr to a day or two. Time requirement mainly depends on:
- complexity of the flow
- values to be parameterized
- frequency of dynaminc values that are to be customized.
I would recommend before start on script recording, test person should spend atleast 1-2 days in understanding the application and flow(s) that is/are to be recorded and executed, identifying test data requirements and workflow dependencies (any). (You may include this as part of test efforts estimation)
LR Script Execution: Execution efforts should include time to:
- Create and setup of Test load scenarios (Average, peak load scenario, etc) as per requirements.
- Set up test data (this test data is similar. However, quantity is different depending on testing time range)
- Execute individual script on controller (directed to actual performance test environment) for small cycles to remove/fix run-time issues.
- Execute average test load scenario / individual script for small cycles to remove/fix run-time issues before executing full range tests. This is very important to prevent unwanted issues during full range tests.
- Test result analysis and reporting.
- If scripts are using ‘destructive data’, include time for creation of test data between test cycles.
Also, few things to keep in mind:
- Average or Normal Load Test execution cycle should be atleast 3 with 2-3 full range test executions within each cycle. Normally, Normal Load Test execution is 1 hr per test run.
- Any performance issues / application issues observed should be fixed before start of next cycle.
- Peak Load and other test load scenarios should be executed once Normal (Average) load test(s) gives positive results.
- Scenario Run-time for Normal (Average) and Peak loads should be similar
- Make sure, you have enough Vuser license to simulate load conditions, as per NFRs.
No comments:
Post a Comment