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
  • Tags
  • Environment Variables
  • On Flow Start
  • On Flow Complete

Was this helpful?

Edit on GitHub
  1. Creating Tests

Test Configuration

Last updated 1 year ago

Was this helpful?

Moropo uses the Maestro Open Source format for test configuration and .

When you start a new test in Moropo, Test Creator will automatically populate the only mandatory field (appId):

appId: ${BUNDLEID}
---
- launchApp

NB: if this is your first test, there is nothing else you need to do here. Proceed to .

Tags

Use the tags configuration option to add tags to your test runs. These can then be used as a filter when setting up a test run.

appId: ${BUNDLEID}
tags:
    - regession
    - smoke
---
- launchApp
- inputText: ${MY_EMAIL}

Environment Variables

Use the env configuration option to provide variables to your test. These can then be used in the steps with the ${MY_VARIABLE} syntax.

appId: ${BUNDLEID}
env:
    MY_EMAIL: example@moropo.com
    MY_KEY: 123
---
- launchApp
- inputText: ${MY_EMAIL}

On Flow Start

appId: ${BUNDLEID}
onFlowStart:
  - runFlow: mySetup.yaml
  - setLocation:
      latitude: 51.45052532643149
      longitude: -2.594704204455719
---
- launchApp

On Flow Complete

appId: ${BUNDLEID}
onFlowComplete:
  - runFlow: myTeardown.yaml
  - stopApp
---
- launchApp

The onFlowStart option can be used to run any before the test starts. This is useful for running setup actions.

The onFlowComplete option can be used to run any after the test has been completed, and will execute even if the main body of the test fails. This is useful for running clean-up operations that must be run even if the test fails.

test steps
test steps
test steps
test steps