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 - Triggering a Test Run
  • Example - Reading Test Run Status

Was this helpful?

Edit on GitHub
  1. CI Integration
  2. Moropo API

Test Runs

Last updated 3 months ago

Was this helpful?

This endpoint is used to create, and read the results of, test runs. API URL -

Available actions

  1. Create Test Run

  2. Check Test Run Status

Example - Triggering a Test Run

Note this request uses POST to inform the API that a test run is being created. This example is for a basic usage of the endpoint. The docs linked above provide a comprehensive specification of all possible overrides.

curl -X 'POST' \
  'https://api.moropo.com/testRuns' \
  -H 'accept: */*' \
  -H 'x-app-api-key: MOROPO_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
	"ciCdId": "SCHEDULED_TEST_RUN_ID"
}'

Where;

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

  • SCHEDULED_TEST_RUN_ID is the UUID of the scheduled test run you wish to create.

Expected Response

{
  "statusCode": 200,
  "body": "{
  \"message\":\"Success\",
  \"testRunInfo\":{
    \"id\":TEST_RUN_ID,
    \"buildId\":\"BUILD_ID\",
    \"devices\":[\"DEVICES\"],
    \"tests\":[\"TESTS\"],
    \"expoReleaseChannel\":\"EXPO_RELEASE_CHANNEL\",
    \"url\":\"TEST_RUN_URL"
    }
  }"
}

Example - Reading Test Run Status

This request uses GET to inform the API test run status is being requested

curl -X 'GET' \
  'https://api.test.moropo.com/testRuns/TEST_RUN_ID' \
  -H 'accept: */*' \
  -H 'x-app-api-key: MOROPO_API_KEY'

Where;

  • TEST_RUN_ID is the ID of the test you want to request the results for.

Expected Response

{
  "statusCode": 200,
  "body": "{
    \"complete\":true,
    \"passed\":true,
    \"message\":\"Tests passed\"
  }"
}

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

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