Marathon

General

Category
Free
Tag
Testing Tools
License
Apache License, Version 2.0
Registered
Feb 25, 2019
Favorites
0
Link
https://github.com/Malinskiy/marathon
See also
Bee
Spoon
Atmosphere Framework
EletricSpock
Magneto

Additional

Language
Kotlin
Version
0.10.0 (Mar 12, 2024)
Created
Apr 13, 2018
Updated
Apr 12, 2024
Owner
Anton Malinskiy (Malinskiy)
Contributors
Iñaki Villar (cdsap)
Mike Penz (mikepenz)
Anton Malinskiy (Malinskiy)
Sergii Pechenizkyi (plastiv)
Ivan Balaksha (tagantroy)
Nick Chameyev (lukaville)
Trevor Jones (trevjonez)
Konstantin Aksenov (Vacxe)
David Santiago Turiño (nimeacuerdo)
Alexander Blinov (xanderblinov)
Alexey Bykov (NoNews)
Roland Moers (CooperRS)
Martin Brandtner (mabae)
Boris Osipov (BorisOsipov)
dependabot[bot]
Yurii Panforov (memega)
Zoey Juan (zoey-juan)
Tieru
Show all (44)44
Activity
Badge
Generate
Download
Source code

Advertisement

Releases   |   Documentation   

Marathon is a project that helps execute tests in the shortest time possible. Specifically it helps with stability of test execution adjusting for flakiness in the environment and in the tests and also achieves best performance using high parallelization

TL;DR

Marathon is a fast, platform-independent test runner focused on performance and stability. It offers easy to use platform implementations for Android and iOS as well as an API for use with custom hardware farms and more techstacks.

Marathon implements multiple key concepts of test execution such as test batching, device pools, test sharding, test sorting, preventive retries as well as post-factum retries. By default, most of these are set to conservative defaults but custom configurations are encouraged for those who want to optimize performance and/or stability.

Marathon's primary focus is on full control over the balance between stability of test execution, testing performance and cost.

For more information see the documentation

Overview

Performance

Marathon takes into account two key aspects of test execution:

  • The duration of the test
  • The probability of the test passing

Test run can only finish as quickly as possible if we plan the execution of tests with regard to the expected duration of the test. On the other hand, we need to address the flakiness of the environment and of the test itself. One key indicator of flakiness is the probability of the test passing.

Marathon takes a number of steps to ensure that each test run is as balanced as possible:

  • The flakiness strategy queues up preventive retries for tests which are expected to fail during the test run according to the current real-time statistical data
  • The sorting strategy forces long tests to be executed first so that if an unexpected retry attempt occurs it doesn't affect the test run significantly (e.g. at the end of execution)
  • If all else fail we revert back to post-factum retries, but we try to limit their impact on the run with retry quotas

Configuration

Create a basic Marathonfile in the root of your project with the following content:

Android:

name: "My application"
outputDir: "build/reports/marathon"
vendorConfiguration:
  type: "Android"
  applicationApk: "dist/app-debug.apk"
  testApplicationApk: "dist/app-debug-androidTest.apk"

iOS:

name: "My application"
outputDir: "derived-data/Marathon"
vendorConfiguration:
  type: "iOS"
  bundle:
    application: "sample.app"
    testApplication: "sampleUITests.xctest"
    testType: xcuitest

Vendor section describes platform specific details.

Since iOS doesn't have any way to discover remote execution devices you have to provide your simulators using the Marathondevices file:

workers:
  - transport:
      type: local
    devices:
      - type: simulator
        udid: "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
      - type: simulatorProfile
        deviceType: com.apple.CoreSimulator.SimDeviceType.iPhone-13-mini

This Marathondevices file specifies a list of macOS instances and simulators for use. Marathon can use pre-provisioned simulators, but it can also provision new ones if needed.

Example above uses the local instance where marathon is executed, but you can connect many more instance via SSH.

ℹ️ The instance where you run marathon is not limited to macOS: if you're using remote macOS instances then you can easily start your marathon run from Linux for example.

You can find more information on providing devices in the workers documentation

The file structure for testing should look something like this:

Android:

foo@bar $ tree .  
.
├── Marathonfile
├── dist
│   ├── app-debug.apk
│   ├── app-debug-androidTest.apk

iOS:

foo@bar $ tree .  
.
├── Marathondevices
├── Marathonfile
├── build
│   ├── my.app
│   ├── my.xctest

Execution

Start the test runner in the root of your project

$ marathon 
XXX [main] INFO com.malinskiy.marathon.cli.ApplicationView - Starting marathon
XXX [main] INFO com.malinskiy.marathon.cli.config.ConfigFactory - Checking Marathonfile config
...

Requirements

Marathon requires Java Runtime Environment 8 or higher.

Move even faster with Marathon Cloud

Marathon Cloud is a scalable testing-as-a-service product designed and developed by us, the creators of Marathon. It's got all the cloud testing infrastructure you need to run any number of tests in less than 15 minutes, whether you're a startup or a large enterprise.

Learn more

Contributing

See contributing docs

License

Marathon codebase is GPL 2.0 LICENSE with following optional components under specific licenses: