Having led QA efforts in scale-up environments, I’ve learned that simplicity and developer buy-in are key.
“Using k6 OSS + Gradual Cloud Transition”
@dimplesaini.230 approach reminds me of our journey—except we landed on load testing with k6. We started with the open-source version, and what stood out was the developer-friendly design. Writing tests in JavaScript made it easier to get the whole team involved, and our scripts now live alongside the application code in Bitbucket.
We use thresholds, parameterized data, and iterations to reflect end-user behavior. Recently, we’ve begun migrating larger tests to k6 Cloud. The OSS version handled CI (Bitbucket Pipelines) just fine, but cloud helped scale tests for pre-production scenarios and gave us trend visibility.
What I appreciate is that k6 makes load testing feel like code—not some separate QA ritual. It grows with your team, from local runs to cloud-scale stress.