Performance testing FAQs

Can I run a performance test locally?

No, mabl performance tests can only be run in the cloud.

How do I know what my failure criteria should be?

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.

Does mabl allow performance testing in private environments?

We currently support a static IP range for performance testing: 34.31.138.224/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.

Can I generate load from different geographies?

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.

Can I import tests from JMeter?

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.

How does mabl measure usage of performance testing?

Mabl measures performance testing in virtual user hours (VUH). VUH is a combination of the concurrency of users and the duration of the test. For example, if you run 500 users for 30 minutes, the total VUH is 500 users x 0.5 hours, for a total of 250 VUH.

How are virtual user hours (VUH) billed?

Virtual user hours (VUH) for performance tests are billed in 15 minute increments, rounding up to the nearest 15 minutes. For example, if you run a performance test with a concurrency of 20 virtual users for a duration of 10 minutes, the duration is rounded up to 15 minutes: 20 users x 0.25 hours is 5 VUH in total.

Are VUH allocations monthly or yearly?

VUH allocations are yearly.

Do performance tests pull from my API allocation?

No, performance tests will not impact API test allocation. They will be billed separated and pulled from an allocated bucket of virtual user hours.

What happens if I stop a performance test?

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.

What are the current limitations with performance testing?

The following are limitations with performance tests:

• Browser tests not yet supported.
• 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.