+ Send us feedback and get 10% off

  • Test Batch Composer
  • Exporting Test Results
  • Up to 5 Tests
  • ...and more

Repeato Android

€50 / month

+ Cancel subscription anytime

  • Test Batch Composer
  • Exporting Test Results
  • Unlimited Android Tests
  • ...and more


Price upon request

+ Cancel subscription anytime

  • All Features of Professional Plan
  • Team Support
  • Continuous Integration
  • ...and more
Contact us

Plan Details



Repeato Android

€50/ month


€120/ month


Price upon request

Monthly Testing Minutesunlimitedunlimitedunlimitedunlimited
Maximum Android Tests*

* When reaching the limit, it's possible to delete tests to free up "available tests"
Maximum iOS Tests*

* When reaching the limit, it's possible to delete tests to free up "available tests"
Seats (Workstations)1111
Price for Additional Seat€50 / month€50 / month€50 / month€50 / month
Test Batch Composer
Text Assertions
Pixel Perfect Assertions
ADB Commands
JavaScript Commands
Test Batch Reporting (ETA Q3/2021)
Test sharing between workstations
Test versioning
Workspaces (work environments)
Contiuous Integration Support
Priority Support via Email & Slack

Are you working for an NGO?

If you are working for a NGO, contact us and get repeato professional for free!

[contact-form-7 404 "Not Found"]

Frequently asked

Can I upgrade from one package to another?

Yes you can. Anytime - just send us an email.

Can I downgrade from one package to another?

Yes you can. Anytime - just send us an email.

Why another UI testing tool?

There are dozens of UI testing tools out there. Espresso, Robotium, Appium, you name it. But they all lack one thing: Simplicity.

How is repeato different from other testing tools?

Repeato does not rely on the underlying structure of a UI for testing. Instead it uses computer vision and machine learning algorithms for handling the matching which is needed for doing asserts.

A real alternative to Espresso

Tired of trying to find the right view ID, mocking classes, creating idling resources or finding the right delays for your test automation? This is how repeato does things differently:

Common UI Testing Frameworks need to have a sophisticated understanding of how the UI is structured. In order to create asserts and click views, the testing framework needs a unique reference to the respective view in the view hierarchy (layout). Usually a manually set ID or the "layout path" is used as a unique reference and the developers needs to reference that ID when they  write test automation code.
This approach comes with a lot of complexity which needs to be handled by the developer:

  1. Looking up view IDs
  2. Making sure that those are unique (IDs can reoccur in different places in the hierarchy)
  3. When layouts are refactored IDs often change, this breaks the tests, which need to be fixed
  4. Creating idling resources for asynchronous code
  5. Making sure view lookups and clicks are not executed before view is fully visible (problematic with view animations and fragment transitions)
  6. Installing additional framework components for handling automation outside of the app context (notifications, switching to other app)

Repeato does things differently. It operates fully on pixel data and does not care about the underlying structure of the UI. It basically sees what a tester would see by utilising computer vision (open CV) and machine learning (tensor flow).
Asserts are created by defining pixel regions, which can later be found again by the computer vision algorithm. Even when your design or device aspect rations change slightly.