Run your gatling tests on the Testable platform without having to make any changes while gaining many useful and time saving features to help you run and automate your performance tests.
Either upload a zip file with your simulations and other required artifacts (e.g. CSVs, jars, etc) to Testable or link Testable with your git repository. The git repo does not have to be publicly accessible or even hosted on a public git service. If you link Testable with git we will clone your repo onto each Gatling engine at test execution time.
Run a distributed test with as many gatling engines as your tests require without a master node becoming the processing bottleneck.
Gatling’s open source edition does not come with any support for distributed testing with multiple Gatling engines. Testable’s proprietary distributed grid runs will run each Gatling engine independently. Each test runner reports results via a highly efficient binary protocol to an infinitely scalable test processing service that aggregates them together for real-time reporting and analysis.
Run your test across 100+ cloud regions on AWS, Azure, and Google Cloud or on-premises. Test runners can be automatically spun up at the start of your test and terminated at the end. Alternatively setup long running test runner grids to run multiple tests. Automated infrastructure spun up in our cloud accounts or yours. Simply grant us enough access and we automate the rest. Non-public applications inside your private network can be tested with zero infrastructure setup before the test. For on-prem, spin up our self-host test runners on any Docker or Kubernetes enabled infrastructure. No connection IN from Testable to the test runner container is required.All charts, metrics, and aggregations available in Gatling reports are also available on Testable. We also capture several additional items:
A full trace includes all metrics, and a timeline view of the request that includes all request/response headers + body. Testable intelligently samples to ensure you have at least one example for every combination of URL + response code but without capturing so many traces that it affects the test performance. Having these traces can be really useful to analyze and debug application errors.
Export the raw results (i.e. one row per request) to a CSV. Scales up to millions of requests without affecting the test performance. Do your own offline aggregation and analysis as required.
Testable offers a variety of analysis tools:
Any files your Gatling tests write to a special directory will be captured and made available for download in your test report. So if you want to generate a Gatling report for example, simply write it to the special directory (System.getProperty("output_dir") + "/filename") and it will appear in real-time in your test results.
Some examples include:
Success criteria can be evaluated at the end of the test or actively during the test, stopping on failure. Get notified via email, SMS, and WhatsApp when a test starts, succeeds, and/or fails. Customize notifications as required.
