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
  • Run automated tests in the cloud regularly
  • Why use schedules?
  • Run all tests every hour
  • Get email notifications with reports for scheduled results
  • Customize schedule

Was this helpful?

  1. Running tests

Schedules

PreviousRun in cloudNextParallel runs

Last updated 8 months ago

Was this helpful?

Run automated tests in the cloud regularly

Why use schedules?

When you've already prepared automated tests, you should run them on a regular basis to monitor if your web app works properly.

Fortunately, you don't need to log in to BugBug and click "Run" every week . BugBug can automatically and notify you about failed tests with .

To use schedule and cloud runs you need to have a paid subscription -

Run all tests every hour

Creating an hourly schedule is not the only option you can choose. You can also select and create from other available schedules, such as: Every 5 minutes / Hourly / Daily / Weekly / Monthly.

Scheduling cloud monitoring with automated tests doesn't require any engineering knowledge or additional infrastructure. Here's how to do it:

  1. Go to "Schedules"

  2. Click on the "New schedule" button

  3. Select "Hourly" and fill out all of the required fields

  4. Select "All suites" or any other specific suite

  5. Make sure "Schedule enabled" is turned on

  6. Click on the "Create schedule" button

That's it! Based on this example, BugBug will now run your tests every hour. You will receive email notifications when all tests have been completed.

Get email notifications with reports for scheduled results

Customize schedule

Create more schedules to have control over which suites are run and when.

Important! Only suites can be scheduled - you can't schedule running individual tests.

  1. Create separate test suites

  2. Go to "Schedules"

  3. Click the "New schedule" button

  4. Fill out the name field

  5. In the "Time" section, select the type of run from Every 5 minutes/Hourly/Daily/Weekly/Monthly (for this example, we'll select Daily).

  6. Select the suites you want to run and set the scheduled time range

  7. Make sure "Enabled" is turned on

  8. Click on the "Create schedule" button

Make sure your selected test suite passes when you

You will receive notifications with scheduled test results directly in your inbox. You can .

Emails notifying about failed schedules are marked with a symbol.

Important! By default all suites use the setting to avoid sending you false-alarm notifications from unstable, flaky tests.

Tip! Add a filter in your email to avoid inbox clutter. Or .

The email contains details about the results and direct links to the tests that failed. After clicking the link you will see a read-only report of this run from the .

Did you know? You can also

If you work on a large project, you may want to have more than one schedule. For example, you can run production tests every hour but monitor your just once a day at night.

❌
run them in the cloud
configure who gets notifications in project settings
run history
integrate BugBug notifications with your Slack
test environment
😄
run the tests in the cloud
see pricing
email notifications
auto-retry failed tests
disable notifications for passed runs
Empty screen for Schedules
Add new schedule modal
Filled form for with a new schedule
Enabled schedule with all tests running every hour
Email notifications with various statuses
Email notification for a failed schedule
Test suites selected for the daily schedule
List of all created schedules