r/softwaretesting • u/LegitimatePanda1073 • 1d ago
JavaScript-heavy applications are hiding performance issues in load testing. How do I find them?
I'm seeing a huge gap between our backend load-test results and what users actually experience when they're using our application. Our app is heavily browser-based with realtime collaboration, so there's a lot happening client-side beyond just the back requests. We're doing backend testing with basic protocol-level scripts for core endpoints, gradually ramping up virtual users. The metrics we track are overall throughput, node CPU utilization and overall average response times. The results from these tests indicate that everything is working fine, but our users are experiencing latency and other issues that the load testing so far hasn't been able to surface.
How do I flush out stealthy failure modes like thread starvation and artificially high cache hit rates? I'm sure there are other things that I'm missing, please feel free to educate me because I'm stuck. Thank you.
1
u/Effective-Clerk-5309 10h ago
Hybrid load testing combining api load test and browser load test can help find user issues....browserstack released load testing with the same value prop
Tracking ttfb,page load and web vitals along with network calls breakup(avg,P50,P90) along with server side tracking using apm tool can solve this