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
  • Available actions
  • Example - Download Tests
  • Example - Upload Tests

Was this helpful?

Edit on GitHub
  1. CI Integration
  2. Moropo API

Tests

Last updated 2 months ago

Was this helpful?

API URL -

Available actions

  1. Download Tests

  2. Upload Tests

Example - Download Tests

Note this request uses GET to inform the API that tests are being downloaded

curl -X 'GET' \
  'https://api.moropo.com/tests' \
  -H 'accept: application/zip' \
  -H 'x-app-api-key: MOROPO_API_KEY' \
  -H 'x-branch-name: main' --output tests.zip

Where;

  • MOROPO_API_KEY is the API key for the target app, found in your .

  • BRANCH_NAME is the name of the target branch to download tests from.

Expected Response

blob:https://api.moropo.com/[UUID]

Example - Upload Tests

Note this request uses POST to inform the API that tests are being upload

curl -X 'POST' \
  'https://api.moropo.com/tests' \
  -H 'accept: */*' \
  -H 'x-app-api-key: MOROPO_API_KEY' \
  -H 'x-merge-strategy: MERGE_STRATEGY' \
  -H 'x-branch-name: BRANCH_NAME' \
  -H 'Content-Type: multipart/form-data' \
  -F 'file=@FILE_NAME.zip;type=application/zip'

Where;

  • BRANCH_NAME is the name of the target branch to download tests from.

  • MERGE_STRATEGY is the strategy for merging. One of;

    • overwrite which will overwrite the existing test with a new copy if the names match

    • changes_only which will only upload tests which do not match existing tests

  • FILE_NAME is the name of the test file being uploaded. Must be a .zip.

Expected Response

1 - TEST_NAME:

   - Status: Success!
   - Path: TEST_NAME.yaml
   - Directory: DIR
   - Dependencies: DEPENDENCIES

MOROPO_API_KEY is the API key for the target app, found in your .

https://api.moropo.com/tests
Moropo settings
Moropo settings