Use-Cases
For DevOps/Platform Teams
As the person tasked with making sure our application can withstand extreme load, I need to run testing tools like K6 or jMeter, and scale them up to hundreds and thousands of users across geographies. I usually run these tools manually — when the “time is right."
As the person responsible for infrastructure costs, I need to make sure that Kubernetes pods are optimized for running automated tests.
As the person responsible for GitOps, I need to trigger test execution when certain resources have been updated in my cluster.
As the person responsible for our Kubernetes environment, I need to automatically trigger a sequence of tests each time the configuration of the environment or a component is updated.
As the person who assists the people who test applications, I need to provide them with the artifacts and logs from the testing tools they are running.
As the person responsible for build quality, I need a way to see the results of all my testing in a single dashboard.
For Teams Who Execute Tests
As someone responsible for cloud testing costs, I want to bring test execution into our existing Kubernetes infrastructure to reduce expenses, strengthen security, and improve efficiency.
As a build engineer responsible for our CI/CD pipelines, I need to parallelize our tests to cut down on test execution time and costs.
As someone who runs tests, I need a way to trigger tests based on the CI/CD pipeline, but also manually, on a schedule, an external event, or based on some underlying change in the application.
As the person responsible for test automation, I need to build a central repository of available test executions so that teams can select the most appropriate tests to run.
As someone who runs tests, I need to configure and schedule my testing tool (K6, Cypress, Postman, etc.) for execution.