An integrated development environment for creating, debugging, and analyzing Gatling-based load tests with Kubernetes injection.
Kraken is a load testing integrated development environment (IDE) based on Gatling. It provides a complete development environment for creating, debugging, and analyzing load tests, with features like code editing, simulation debugging, and comprehensive reporting through InfluxDB and Grafana. The platform enables multi-host load injection using Kubernetes clusters for scalable performance testing.
Software programmers and load testers who use Gatling for performance testing and want a more integrated development experience with enhanced tooling and analysis capabilities.
Developers choose Kraken because it combines Gatling's powerful load testing capabilities with an IDE that simplifies simulation creation, debugging, and result analysis. Its unique selling point is the integrated environment that supports the entire testing workflow, including Kubernetes-based distributed load injection.
The Load Testing IDE
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Combines a code editor with autocomplete and snippets for Scala simulations, debugging tools, and HAR import, streamlining the entire testing process from creation to analysis.
Enables distributed load testing across multiple hosts using Kubernetes clusters, allowing for high-scale performance evaluations as highlighted in the README.
Leverages InfluxDB for data storage and Grafana for visualization, providing detailed, visual reports on test outcomes directly within the platform.
Supports simulation debugging and comparison, including importing HAR files from browser recordings to quickly generate load testing scenarios.
Requires Docker, docker-compose, Kubernetes, JDK 11, and make, making initial setup and ongoing maintenance resource-intensive for teams without dedicated DevOps support.
As an open-core product, some components are closed-source and require licenses from OctoPerf, potentially leading to unexpected costs and vendor lock-in.
Tightly coupled with Gatling's Scala-based approach, which may pose a steep learning curve for testers not familiar with programming or Scala, limiting accessibility.