Test Configuration

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

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 test steps.

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: [e-mail]
    MY_KEY: 123
---
- launchApp
- inputText: ${MY_EMAIL}

On Flow Start

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

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

On Flow Complete

The onFlowComplete option can be used to run any test steps 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.

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