Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to start performance testing project

This presentation explains about how to start performance testing. Visit www.QAInsights.com for more such articles.

  • Login to see the comments

How to start performance testing project

  1. 1. How to start Performance Testing project? A practical guide to performance testers Author: NaveenKumar Namachivayam Writer at www.QAInsights.com
  2. 2. ● Send business proposal to the clients
  3. 3. ● Once your client agreed, start collecting Non-Functional Requirements
  4. 4. ● Non-Functional requirements such as Response Time, Throughput, Transactions per sec, CPU usage, Memory, Disk, Network etc.
  5. 5. ● Industry standards like Response Time < 5 seconds, CPU and Memory usage < 60%
  6. 6. ● Identify Critical Scenarios
  7. 7. ● If your client is not able to provide critical scenarios and workload models, we can derive it from the server logs.
  8. 8. ● Tools like 123loganalyzer, Deep Log Analyzer, AWstats, Analog etc.
  9. 9. ● If no server logs available, analyze the business applications and identify the critical scenarios.
  10. 10. ● E.g. Banking application.Critical Scenarios will be1. Login2. Check Balance3. Apply for Loans4. Pay Bills...etc...
  11. 11. ● Identify the performance testing tool
  12. 12. ● Record your critical scenarios
  13. 13. ● Enhance your scripts such as1. Inserting Transactions2. Correlations3. Think Time4. Run time settings5. Browser settings6. Cache settings... etc...then perform a unit test to baseline thescript
  14. 14. ● Create Scenarios to execute. Define following:1. Ramp-up period2. Steady State3. Ramp-down period4. Loops5. Mix of transactions6. IP Spoofing...etc...
  15. 15. ● Execute the scenario at least three cycles.1. Baseline Test Perform the test with 15-20% of target load2. Load Test Perform with actual load for three cycles. Steady State duration: min. 1 hr3. Stress Test Perform load test and then slowly ramp-up theload step-by-step. Disable Think time and Cachesettings Steady State duration: min. 2-3 hr4. Endurance Test Perform load test for 10-14 hours to identifymemory leaks
  16. 16. ● Collect metrics such as1. Response Time2. Throughput3. Transactions per second4. CPU Usage5. Memory6. Disk utilization● Prepare Report● Baseline the report● Compare with Benchmarks and previous results
  17. 17. Thank you! Happy Performance Testing!Visit www.QAInsights.com | www.Testifications.com | www.QAJobOpenings.com

×