step.yml

#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/

title: |-
  Run tests using Marathon Cloud
summary: |
  Run all your automated tests in just 15 minutes, no matter how many tests you have
description: |
  With this step you can easily run your Android instrumentation and iOS tests. Marathon Cloud is designed to run all your automated tests in just 15 minutes, no matter how many tests you have.
website: https://marathonlabs.io
source_code_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud
support_url: https://github.com/MarathonLabs/bitrise-step-run-tests-using-marathon-cloud/issues

# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
project_type_tags:
  - ios
  - android

# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
  - test

# These properties define whether a Step is run in a given Workflow or not.
# You can find more information about this in the documentation here:
# https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/developing-a-new-step.html#setting-conditions-for-running-the-step
#
# is_always_run: false
# is_skippable: false
# run_if: ""

# Use the `deps` property to declare dependencies that you can fetch from an OS dependency manager.
# You can find more information about this in the documentation here:
# https://devcenter.bitrise.io/en/steps-and-workflows/developing-your-own-bitrise-step/developing-a-new-step.html#submodules-and-step-dependencies
#
deps:
  brew:
    - name: malinskiy/tap/marathon-cloud
#   apt_get:
#   - name: cmake

toolkit:
  bash:
    entry_file: step.sh

inputs:
  - application: ""
    opts:
      title: App File
      summary: The application binary path refers to the APK file for Android or the ZIP file for the iOS application.
      description: |
        Application binary path.  
        For an Android project: app APK file path.  
        For an iOS project: an ARM compatible Simulator build packaged in a ZIP archive.
      is_expand: true
      is_required: true
  - test_application: ""
    opts:
      title: Test App File
      summary: The test application binary path refers to the APK file for Android or the ZIP file for the iOS Test Runner app.
      description: |
        Test application binary path.  
        For an Android project: test app APK file path.  
        For an iOS project: an ARM compatible Simulator iOS Test Runner app packaged in a ZIP archive.
      is_expand: true
      is_required: true
  - platform: ""
    opts:
      title: Testing platform
      summary: Testing platform. `Android` or `iOS` only
      description: ""
      value_options:
        - "Android"
        - "iOS"
      is_expand: true
      is_required: true
  - api_key:
    opts:
      title: Marathon Cloud API key
      summary: API key for authenticating with Marathon Cloud
      description: |
        Have a look at [the tokens page](https://cloud.marathonlabs.io/tokens) in the dashboard to obtain your token.
      is_expand: true
      is_required: true
      is_sensitive: true
  - docker_image: marathonlabs/marathon-cloud:latest
    opts:
      title: Docker image to use for running marathon-cloud cli on Linux hosts
      summary: You can specify your own custom image with a Docker Registry proxy here
      description: ""
      is_required: false
  - os_version: ""
    opts:
      title: OS version
      summary: Android or iOS OS version
      description: ""
      is_expand: true
      is_required: false
  - run_name: ""
    opts:
      title: Name for run
      summary: Name for run, for example it could be description of commit
      description: ""
      is_expand: true
      is_required: false
  - link: ""
    opts:
      title: Optional link, for example it could be a link to source control commit or CI run
      summary: Optional link, for example it could be a link to source control commit or CI run
      description: ""
      is_expand: true
      is_required: false
  - system_image: ""
    opts:
      title: Runtime system image. Only for Android
      summary: Runtime system image. Possible values are `default` ,`google_apis`
      description: ""
      value_options:
        - "default"
        - "google_apis"
      is_expand: true
      is_required: false
  - isolated: false
    opts:
      title: Run each test using isolated execution
      summary: Run each test using isolated execution. Default is false
      description: ""
      value_options:
        - "true"
        - "false"
      is_expand: true
      is_required: false
  - ignore_test_failures: false
    opts:
      title: Ignore test failures
      summary: When tests fail and this option is true then cli will exit with code 0. By default, cli will exit with code 1 in case of test failures and 0 for passing tests
      description: ""
      value_options:
        - "true"
        - "false"
      is_expand: true
      is_required: false
  - output: ""
    opts:
      title: Output folder
      summary: Output folder for test run results
      description: ""
      is_expand: true
      is_required: false
  - filter_file: ""
    opts:
      title: Filter file
      summary: File containing test filters in YAML format, following the schema described at https://docs.marathonlabs.io/runner/configuration/filtering/#filtering-logic. For iOS see also https://docs.marathonlabs.io/runner/next/ios#test-plans.
      description: ""
      is_expand: true
      is_required: false
  - device: ""
    opts:
      title: Device type
      summary: Device type. For Android one of [phone, tv, watch]. For iOS one of [iPhone-15, iPhone-15-Pro, iPhone-15-Pro-Max]
      description: ""
      is_expand: true
      is_required: false
  - xcode_version: ""
    opts:
      title: Xcode version. Only for iOS
      summary: Xcode version. Only for iOS. Possible values are [15.2, 15.4]
      description: ""
      is_expand: true
      is_required: false
  - xctestplan_filter_file: ""
    opts:
      title: Test filters supplied as .xctestplan file. Only for iOS
      summary: Test filters supplied as .xctestplan file
      description: ""
      is_expand: true
      is_required: false
  - xctestplan_target_name: ""
    opts:
      title: Target name to use for test filtering in .xctestplan. Only for iOS
      summary: Target name to use for test filtering in .xctestplan
      description: ""
      is_expand: true
      is_required: false