browserup

Load Testing for Engineers

Use your existing code to power your load tests, so you don't repeat yourself.

Load test with your own:
Playwright	Javascript, Python, C#, etc (Page objects, too)
Selenium	JavaScript, Java, Python, Ruby, C#(Page objects, too)
PostMan	Using Newman command line runner
A REST API client	Use your own libraries/language
Curl	If it makes requests, it can be a load test!
A Mobile App or IOT App	Run it, let requests happen naturally

These items have easy, out-of-the box, support, but you can create a custom image with almost anything that you want--any language, framework, etc!

See our Documentation for more details.

Differences between BrowserUp and other tools:

• BrowserUp runs your asset and code libraries.
• Because this isn't an import it doesn't create a second implementation to maintain in a script for HTTP, or in some other language.
• No correlation, No stale-capture mistakes, No weird web IDEs, No weird scripting languages, No weird DSLs, No bespoke test framework to learn.
• Your code repo becomes the source of truth.
• If you're using browser tests, use your page objects. As soon as they are ready, so is your load test.
• If you're using API tests, use your programmatic REST client, or PostMan. As soon as it is ready, so is your load test.
• By using assets created early in the release cycle, load testing shifts left. Faster feedback means you release sooner.

BrowserUp's instrumented containers collect your performance stats for you, without a separate load test scripting step.

Oh, One More Thing:

For any browser-based test, get Core Web Vitals metrics from your existing tests, with no extra code or work.

Installation

npm install -g browserup

# prepare the local Docker environment by fetching images
browserup cluster install 

For installations where the local cluster is not used, like CI/CD, you can skip browserup cluster install

Requirements

Local Cluster

• Docker Installed and Running (make sure it is current)
• Mac Arm64 (M1/M2/M3) or Linux AMD64 or Windows 10+
• 32 GB Ram or more Recommended
• 8 CPU Cores or more Recommended

Cloud Cluster

• Amazon AWS account
• Local Mac Arm64 (M1/M2) or AMD64 or Linux to operate the BrowserUp Command line Util
• Local Docker is not required for remote AWS execution, so CI/CD setup is simple

Documentation

https://browserup.github.io/docs/en/load/quick-start

Running from the command line:

browserup

Help

For help, run any command with -h

Or, Join us in Slack

Licensing

This NPM package is the command-line interface for BrowserUp. This package is AGPL-3.0 licensed, but licensing for BrowserUp itself is handled separately, with a separate license and terms.

Summary of the licensing for BrowserUp

Free For

• Non-commercial use, personal use, education, and non-commercial open source projects.
• Commercial use at companies with less than 10 million in revenue and fewer than 250 employees
• Commercial use at companies with more than 10 million in revenue or more than 250 employees, but only for 30 days from date of first installation.

See BrowserUp.com for details.

Documentation | @browserup | Questions?