LogoLogo
BugBug HomepageContact SupportLoginSign up free
  • Documentation
  • Tutorial for beginners
  • Best practices
  • BugBug App FAQ
  • Quick Start
    • What is test automation?
    • Start for free
    • Create your first project
    • Install Chrome extension
    • Create and run the tests
  • Creating Tests
    • Your first test
    • Independent tests
    • Duplicating tests
    • New test from here
  • Recording tests steps
    • BugBug overlay
    • Recording clicks
    • Recording hover
    • Recording keyboard typing
    • Recording assertions
    • Recording drag & drop
    • Record from here
    • Re-recording steps
    • Recording pop-up window actions
    • Using keyboard shortcuts
  • Editing tests
    • Grouping steps
    • Components
    • Manually editing steps
    • Actions
    • Assertions
    • Tabs & iframes
    • Variables
    • Local variables
    • Profiles
    • Custom JavaScript actions
  • Running tests
    • Running the tests
    • Statuses
    • Run (locally)
    • Run and pause here
    • Run in cloud
    • Schedules
    • Parallel runs
    • Running via API
    • Test your local build or protected web page using ngrok
  • Preventing failed tests
    • Waiting conditions
    • Smart click
    • Smart scroll
    • Selectors
    • Timeout
    • Delay / Sleep
    • Project settings
  • Debugging Tests
    • Runs history
    • Screenshots
    • Debug in Chrome
    • Breakpoint (run step-by-step)
  • Organizing tests
    • Naming your tests
    • Searching tests
    • Suites
    • Components
    • Projects
  • Workflow Tips
    • Edit & Rewind
    • Changing the test screen size
    • Multiple environments
    • Testing registration & login
    • Integrating with build systems
    • Mobile version testing
  • Collaboration
    • Organizations
    • Inviting team members
    • Alerts
      • Sending email notification
      • Sending webhook
      • Sending Slack message
      • Sending Teams message
  • Integrations
    • CLI
    • Zapier
    • Slack
    • GitHub
    • Bitbucket
    • Gitlab
    • Trello
    • Jira
  • Your account
    • Account settings
    • Edit your name and email
    • Forgot password
    • Manage Subscriptions
    • Account FAQ
  • Troubleshooting
    • Prohibited behaviors
    • Updating Chrome extension
    • Clear cookies and site data for BugBug
    • Testing basic auth password protected websites
    • Common selectors issues
    • CAPTCHA in automation testing
    • Cloud tests sometimes failing
    • IPs list of cloud runners
    • VPN or a Firewall
    • A/B tests
    • Report a bug
  • IN-DEPTH GUIDES
    • Beginners tutorial to automation testing
    • XPath Selectors without coding
    • Tech Leader's Guide to Automation Testing
    • Test automation guides
  • FREE TOOLS
    • BugBug Testing Inbox
    • Example SaaS App
    • No-code XPath Selector Builder
  • Other links
    • BugBug Homepage
    • Pricing
    • Terms & conditions
    • Privacy Policy
Powered by GitBook
On this page
  • Why run tests in parallel?
  • Parallel testing pricing
  • Enable parallel runs
  • Parallel runs within your organization

Was this helpful?

  1. Running tests

Parallel runs

PreviousSchedulesNextRunning via API

Last updated 1 month ago

Was this helpful?

Why run tests in parallel?

You can run your tests in parallel, which means that more than one test will be executed at the same time. Multiple tests will run simultaneously, resulting in up to 32x shorter testing time.

You can have up to 32 parallel runs, depending on your subscription plan.

Parallel testing pricing

You can purchase parallel runs on the PRO and BUSINESS plans—either directly in the BugBug app or when selecting your plan.

Each additional parallel run costs $80/month for users on a monthly subscription.

If you're on an annual plan, you’ll receive a 15% discount on this price.

Number of parallel test runs
-
2
4
8
16
32

Billed monthly

$119

$199

$359

$679

$1,319

$2,599

Billed yearly

$99

$167

$303

$575

$1,119

$2,207

Enable parallel runs

  1. Go to Suites view

  2. Edit or create a suite

  3. Change the option for Parallel cloud runs

When you trigger suite to run, your tests in that suite will run in parallel.

Suites run in your local browser will always run sequentially because your browser cookies and storage are shared among all incognito windows, so only one test can be run at a time.

Parallel runs within your organization

Parallel runs let you run more than 1 test at the same time.

If you are using BugBug with one of the paid subscriptions, you can run tests in the cloud, but only 1 test can be in progress at the same time.

If you have multiple projects and run tests at the same time, they will be queued, they won't run in parallel - they will be executed one by one.

To run more tests in parallel you need to upgrade to one of the paid plans and purchase parallel runs either directly in the BugBug app or when selecting your plan.

We support up to 32 parallel tests.

Parallel testing is only possible when tests are

All cloud runs can be performed in parallel, regardless of whether they are manually triggered or .

The number of tests you can simultaneously run within your depends on your subscription plan.

run in the cloud
initiated via API
in the cloud
organization