Browsers are memory hogs, so your computer can run a limited number of parallel tests. Break free from those limitations and run all your tests in parallel.
Many end-to-end testing tools use Selenium under the hood. You don't need to rewrite existing tests to improve your tests' performance.
When browsers are shared across tests, one test can make others fail randomly. We start a new browser for every test so your tests are isolated.
This is a drop-in replacement for your Selenium Grid. You get an API token and endpoint to configure the Selenium library of your choice.
We support headless Chrome. Browsertron isn't designed for cross browser testing; its goal is the quickest first pass in Chrome. If your application doesn't work in Chrome (~60% of global browser usage), there's no need to wait for your cross browser tests.
We charge per second, rounded to the nearest second, with a minimum of one second per test. The timer begins after a browser is created, so you're not charged while a test is starting.
There's a 290 second timeout for each test. It's important that you close or quit each Selenium session to avoid unnecessary charges.
Testing is expensive when developers wait for tests or switch contexts while tests are running. Some teams skip end-to-end tests at their customers' expense, but your customers deserve better. Test quickly and reliably on every commit with Browsertron.