Load & Stress Testing for Ticketing Platform (Web + QR Scanning)
Budget: $30 – $250 USD
I need an experienced performance-testing specialist to stress-test our live event ticketing platform before a high-traffic launch.
Here’s what I’m looking for:
• Simulate up to 500 simultaneous users moving through the event page, ticket selection, and the checkout initialization flow (no real payments required).
• Run a separate scenario that imitates roughly four mobile devices scanning QR codes in parallel to confirm there are no duplicate validations and that the API remains stable.
• Track and report response time throughout every step; flag any spikes, bottlenecks, or failures uncovered.
Testing will be performed only on a staging environment, not on production.
I’ll supply dedicated test credentials and access to the staging environment. No application changes are required—just actionable insights.
Deliverables
1.- A concise report outlining the test plan, key findings, and clear recommendations.
2.- Evidence of the tests (scripts, logs, graphs) so results can be reproduced or shared internally.
Feel free to use JMeter, k6, Gatling, Locust, or a comparable tool—whichever you handle best—so long as the results are reliable and easy to read.
Here’s what I’m looking for:
• Simulate up to 500 simultaneous users moving through the event page, ticket selection, and the checkout initialization flow (no real payments required).
• Run a separate scenario that imitates roughly four mobile devices scanning QR codes in parallel to confirm there are no duplicate validations and that the API remains stable.
• Track and report response time throughout every step; flag any spikes, bottlenecks, or failures uncovered.
Testing will be performed only on a staging environment, not on production.
I’ll supply dedicated test credentials and access to the staging environment. No application changes are required—just actionable insights.
Deliverables
1.- A concise report outlining the test plan, key findings, and clear recommendations.
2.- Evidence of the tests (scripts, logs, graphs) so results can be reproduced or shared internally.
Feel free to use JMeter, k6, Gatling, Locust, or a comparable tool—whichever you handle best—so long as the results are reliable and easy to read.
Related categories:
Testing / QA
Software Testing
Test Automation
Website Testing
Usability Testing
API Testing
JMeter
Web Testing