Load Testing Process
Why to do Load Testing
• Load Testing evaluates application performance under user load.
• Ensures APIs can handle concurrent user requests efficiently.
When to do Load Testing
• Perform after functional testing completion.
• Target critical API endpoints used frequently by users.
How to do Load Testing
• Perform tests during off-hours or at night to avoid user impact.
• Identify key test parameters:
• - API details
• - Number of users/threads
• - Ramp-up time
• - Test duration
• Collaborate with Tech Lead/Dev Team to finalize test configurations.
Apache JMeter for Load Testing
• JMeter is a widely used load testing tool.
• Steps to use JMeter:
• 1. Download and install Apache JMeter.
• 2. Navigate to the bin folder.
• 3. Run 'sh JMeter' in the terminal to launch JMeter UI.
• 4. Configure test parameters (Threads, Ramp-up time, Duration).
Observing Load Test Results
Key result views:
• - View Result Tree
• - Aggregate Report
• - Summary Report
Metrics to analyze:
• - Error % (Capture and share errors for analysis)
• - CPU Utilization (Monitor via AWS or other tools)
Load Testing Checklist
• Login to the app while running load tests.
• Use test accounts with extensive data.
• Test with different user types.
• Monitor logs and system behavior.
• Capture key parameters:
• - CPU utilization
• - Memory utilization
• - RDS logs
• - Error %
• - Response time (Throughput)
• Gather API-specific test parameters from developers.
• Optimize test iterations using:
• - Number of Threads (Users)
• - Ramp-up Time (seconds)
• - Execution Time (minutes)
Below scenarios to be tested through app
during load testing
