Moropo
RoadmapTerms
  • Welcome to Moropo
  • Quick Start
  • Uploading your app
    • Producing an Android Build
    • Producing an iOS Build
    • Uploading Your Build To Moropo
  • Creating Tests
    • Using the Test Creator
    • Test Configuration
    • Test Step Commands
      • addMedia
      • assertNotVisible
      • assertTrue
      • assertVisible
      • back (Android only)
      • clearKeychain (iOS Only)
      • clearState
      • copyTextFrom
      • doubleTapOn
      • eraseText
      • evalScript
      • extendedWaitUntil
      • hideKeyboard
      • inputRandomEmail
      • inputRandomNumber
      • inputRandomPersonName
      • inputRandomText
      • inputText
      • launchApp
      • longPressOn
      • openLink
      • pasteText
      • pressKey
      • repeat
      • runFlow
      • runScript
      • scroll
      • scrollUntilVisible
      • setLocation
      • startRecording
      • stopApp
      • stopRecording
      • swipe
      • takeScreenshot
      • tapOn
      • travel
      • waitForAnimationToEnd
    • Test Step Selectors
    • Importing From Maestro
    • Environment Variables
      • ${BUNDLEID}
      • ${EXPORELEASECHANNEL}
      • ${MOROPO_TEST_EMAIL}
      • ${MOROPO_EMAIL_URL}
    • Advanced Use Cases
      • JavaScript
      • Conditionals
      • Network Connection
      • Drag and Drop
  • Running Tests
    • Manually Trigger a Test Run
    • Scheduling a Test Run
    • Tags
    • Supported Devices
    • Test Execution Limits
    • Flakiness Tolerance & Retries
  • CI Integration
    • Initial CI Setup In Moropo
    • GitHub Action
    • Moropo API
      • Branches
      • Builds
      • Test Runs
      • Tests
  • Test Results
    • Results Explorer
    • Slack Reporting
    • Email Reporting
  • App Frameworks
    • Flutter
    • React Native
  • Guides
    • React Native Expo
    • Access Emails During A Test Flow
    • Git workflow using Moropo API
  • Infrastructure
    • IP Addresses
  • Security
    • Services Infrastructure
    • Security Best Practices
Powered by GitBook
On this page
  • Create a Scheduled Test Run ID
  • Connected to CI

Was this helpful?

Edit on GitHub
  1. CI Integration

Initial CI Setup In Moropo

Last updated 10 months ago

Was this helpful?

Once you've created your tests, you'll likely want to trigger a test run automatically using your continuous integration pipeline or build server.

Create a Scheduled Test Run ID

The first step is to create a new scheduled test run inside Moropo. This will tell Moropo which devices, tests, and builds to use when triggered by CI.

  1. Navigate to scheduled tests in the left-hand bar

  2. Press add schedule in the top-right corner

  3. Enter a name for your trigger (e.g. GitHub Pull Request Test Run)

  4. Select CI-CD (the last option on the list):

  5. Follow the wizard to choose the builds, devices and tests you wish to trigger.

  6. Finish creating the scheduled test run, and you'll be given a unique Scheduled Test Run ID. This one is just an example; ensure you generate your own.

Connected to CI

Once you have a Scheduled Test Run ID, please use the platform-specific guide to complete the setup:

GitHub Action

If we don't list your platform-specific guide yet, you can use our simple API instead:

Moropo API

An example Scheduled Test Run ID