No, mabl performance tests can only be run in the cloud.
Baseline performance testing is a great way to identify reasonable failure criteria for performance tests. Organizations may also have codified performance SLAs that can be used for failure criteria. Learn more about which metrics you can use to set failure criteria here.
We currently support a static IP range for performance testing:
22.214.171.124/27. Mabl Link is not currently supported for performance testing. If testing through mabl Link is important to your team, please let us know in the mabl Product Portal.
No, configuring load traffic from different geographies is not currently supported. If this functionality is important to your team, please let us know in the mabl Product Portal.
No, at this point in time, we do not support import for JMeter scripts. However, users can import their Postman tests into mabl and then reuse those API tests within a performance test. If this functionality is important to your team, please let us know in the mabl Product Portal.
Mabl measures performance testing in virtual user hours (VUH).
- VUH for API load testing is the number of concurrent users multiplied by the number of hours.
- VUH for browser load testing is the number of concurrent users multiplied by the number of hours times two.
|API test||40 concurrent users x 15 minutes = 10 VUH|
|Browser test||40 concurrent users x 15 minutes x 2 = 20 VUH|
Virtual user hours (VUH) for API test runners (i.e. virtual users running API tests) tests are billed in 15 minute increments, rounding up to the nearest 15 minutes.
For example, if you run an API test with a concurrency of 20 virtual users as part of a performance test with a duration of 10 minutes, the duration is rounded up to 15 minutes: 20 users x 0.25 hours is 5 VUH in total.
VUH for browser test runners (virtual users running browser tests) are billed in the same way except that each browser test VUH counts as 2 VUH for the purposes of billing.
Using the same example, if you run a browser test with a concurrency of 20 virtual users as part of a performance test with a duration of 10 minutes: 20 users x 0.25 hours x 2 is 10 VUH in total.
VUH allocations are yearly.
No, performance tests will not impact API test or browser test allocation. They are billed separately and pulled from an allocated bucket of virtual user hours.
If you stop a performance test, it takes up to one minute for all tests to stop running. Stopped performance tests consume the number of VUH up until the test stopped.
The following are limitations with performance tests:
- Performance tests cannot simulate traffic by geography, networking throttling, or service mocking.
- Mabl Link is not yet supported for performance tests.
- Performance tests do not support API requests with a “binary” request body type.
- Virtual users will reuse connections, assuming the server under test permits it, so that multiple requests from the same virtual user as well as the associated responses from the server will all pass over the same underlying TCP connection.
Updated 18 days ago