Defining Test Executions | Complex, manual scripting done by a devops engineer. | Simple GUI interface that testers, developers and DevOps engineers can use to easily build simple to complex test executions. |
Triggering Automated Tests | CI/CD triggers. | CI/CD triggers Manual Scheduled From other test sequences Changes in underlying K8s resources. |
Scaling Automated Testing | Expensive third-party infrastructure. Third-party software to parallelize or shard your functional or load tests. | Utilize your own K8s infrastructure. Included test workflows for sharding and parallelizing functional and load tests. |
Troubleshooting | Either build elaborate retrieval mechanisms to centralize test automation logs and artifacts or implement lax security to allow access to clusters for retrieval. | Centralized and secure logs and artifacts. |
Reporting | Third-party tooling to track reporting. Third-party tools have no inherent awareness of which tests have been run, hence reporting tool has to be hooked up to tests leaving large blind spots. | Built-in reporting. Since Testkube triggers all tests, Testkube can retrieve and centralize all test results in a single pain of glass. |