CloudBeat Docs
HomeRequest a DemoContactSign In
  • What is CloudBeat?
  • Get Started
    • Quick Start
  • SUPPORTED FRAMEWORKS
    • Java JUnit
    • .NET MSTest
    • Playwright (JS/TS)
  • Fundamentals
    • Creating Projects
    • Creating Environments
    • Creating Tests Cases
    • Running Tests Cases
    • Creating Tests Suites
    • Running Tests Suites
    • Creating Releases
    • Adding Apps
  • Sample Projects
    • Introduction to Cloudbeat sample projects
    • Oxygen Cucumber project
    • Oxygen project
    • TestNG project
  • Features
    • Integrations
      • CI/CD Pipeline
        • Jenkins
        • Azure DevOps
      • Cloud Providers
        • Genymotion
        • Applitools
        • Perfecto
    • Supported Frameworks
    • Data-Driven Testing
      • DDT - Oxygen Framework
  • CloudBeat Synthetic
    • What is CloudBeat Synthetic?
    • Creating your first monitor
    • Review general monitor results
    • Review specific monitor dashboard
    • Create SLA
    • Create Reports & Alerts
    • Changing Runtime Setting
    • Run Monitors
    • Maintenance
    • Incidents
    • Full Monitor Test - Example
  • Settings & Administration
    • Managing Notification Groups
    • Managing Permissions
    • Managing Users
    • Managing Account
    • Managing My Profile
  • References
    • Active Runs
    • Test Results
    • Projects
      • Oxygen Project
      • Cucumber + Java Project
      • .Net Project
      • TestNG Project Setup
    • Reports
Powered by GitBook
On this page
  • First let's make sure we have our test case ready.
  • Now let's define our browser and choose our test case
  • Now let's define our SLA settings and set reports & alerts
  • Finally let's define our runtime settings and schedule

Was this helpful?

  1. CloudBeat Synthetic

Full Monitor Test - Example

PreviousIncidentsNextManaging Notification Groups

Last updated 4 years ago

Was this helpful?

First let's make sure we have our test case ready.

for this example I've created a simple web script which includes transactions.

Environments are optional, but for this example I've included one with a single value of url, for better practice

Now we are ready to create our monitor, let's head over to Monitors and click on Add Monitor

Select the project which includes your test scripts, and the test mode, Web or Mobile

Now let's define our browser and choose our test case

Click on browsers and choose your desired browser

Click on cases and add your test case

Now let's define our SLA settings and set reports & alerts

Click on SLA and then click on ( + ) New General SLA

Choose your SLA goal, whether availability or performance

You can set the SLA scope to monitor over the cases which you added in the previous step, or choose a specific test and transaction

Transactions will appear after the monitor has run at least once

Click on save and head over to reports & alerts, then click on ( + ) Add Group

Choose your desired group and the frequency

You can do the same for alerts if you wish

Finally let's define our runtime settings and schedule

head over to runtime and set the environment to QA, which we created earlier, and configure the runtime as you desire, for this example I will keep it as a single iteration.

If you're using parameters in your case, make sure they are uploaded correctly to avoid trouble

And for the last step, go to schedule and set your desired schedule

Click on save changes and we're all set, come back after 10 minutes and see your results!