BrowserStack Load Testing FAQs
BrowserStack Load Testing FAQs offer guidance for seamless test experience.
This section provides FAQ resources for troubleshooting and optimizing load tests
Can I test private or internal websites?
Not yet but it’s on the roadmap. If testing private or internal sites is critical for you, contact our technical support team. We will notify you as soon as it’s available or discuss potential workarounds for your use case.
Is there a limit on the number of tests I can run each month?
Yes. You can run up to 10 tests per month. Your quota resets every 30 days, starting from the day you run your first test (based on UTC time). Need more than 10? contact our technical support team to increase your limit.
What is the maximum duration for a single test?
Each test can run for up to 20 minutes. If your tests need more time, contact our technical support team. We can help extend your test durations based on your scenario.
How many virtual users (VUs) can I run in a single test?
By default, you can run up to 100 VUs per test. If your tests need more load, contact our technical support team. We will scale it up to meet your needs.
Can I run tests from additional regions?
We support a limited set of regions at the moment. If your test needs coverage in a specific location, contact our technical support team, we are open to expanding based on demand.
Which Playwright version is supported on your end for test execution?
We currently support v1.51 and regularly update to newer versions to keep up with the latest features and improvements.
Which Selenium version is supported on your end for test execution?
We currently support v4.25.0 and regularly update to newer versions to keep up with the latest features and improvements.
How do I add think time to my load test scripts?
Think time is a deliberate pause between consecutive actions in your test script. It simulates the time a real user spends reading a page, filling out a form, or deciding what to do next. Without think time, virtual users send back-to-back requests that do not reflect real traffic, which inflates throughput and skews response time percentiles.
Best practice: Use randomized delays rather than fixed sleeps. Fixed delays synchronize all virtual users into request waves and distort your results.
For browser-level tests, add think time only between user-facing actions to simulate reading and decision time. Do not use it as a substitute for proper element waits, which handle synchronization.
The following sections show how to add randomized think time in each supported framework.
k6: Use sleep() from the k6 module with Math.random() for variability.
JMeter: Add a Constant, Uniform Random, or Gaussian Random Timer as a child of the sampler you want to delay. For example, set a Uniform Random Timer under an HTTP Request with Constant Delay Offset = 2000 and Random Delay Maximum = 3000 to get a 2 to 5 second think time before that request.
Gatling: Use pause(min, max) in the scenario DSL.
Locust: Set wait_time on the User class using the between() helper.
Selenium (Java): Use Thread.sleep() with ThreadLocalRandom to randomize the pause.
Selenium (Python): Use time.sleep() with random.uniform().
Playwright: Use page.waitForTimeout() with a random value.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!