Teams lack flexible orchestration for multi-stage test suites
Developers and test engineers need to run test scripts and subsets in a chosen order, with different configurations or in parallel. Across several runners, they report falling back to shell scripts, manually scheduled scenarios, or separate configurations; built-in options can also be tied to dashboard recording or lack the debugging and configuration workflow they need. The signals point to test execution orchestration, though framework-specific needs such as sandbox networking and threaded RSpec execution are outside a general orchestrator’s scope.
For developers and test engineers maintaining integration and performance test suites. Mentioned from Jan 2014 to Feb 2026 on Bluesky and GitHub.
11 different people described this problem in 8 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 6.5/10
- Frequency
- 9.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Something like this can currently be achieved by a simple shell script that sequentially calls k6 run "$scriptpath" for all files in a folder, but that workaround is not very convenient without an external output like InfluxDB. It also doesn't work well with k6 cloud, and isn't efficient in general
The only way you can currently implement something like a test suite in k6 is if you manually calculate and specify the startTime property of each scenario. Depending on your use case, it might be easier to simply have a shell script that calls k6 run scriptN.js sequentially for your scripts
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 5 places to find your first customers
- 10 more quotes from people who have this problem
- Current workarounds, existing solutions and risks