Repeato
  • Features
  • Pricing
  • Blog
  • About us
  • Get for free
  • Getting started
  • Running test batches
  • Reporting
  • Test exception handling
  • Test workspaces
  • Advanced testing techniques
  • JavaScript API
  • Virtual Test Devices
  • Share tests within the team
  • Continuous Integration Support

Frequently asked questions

Why Repeato?

What is Repeato? Why another UI testing tool?

Repeato is a mobile test automation tool which works based on computer vision and machine learning. This way the tester does not need to care about the underlying architecture of the app (IDs, layout structure) which simplifies the creation of tests.

Instead of writing code, tests can be recorded via a test recorder. For each click interaction, a visual fingerprint is generated which allows the test runner to find the UI element later on.

For each test run, a report can be generated which shows a visual step-by-step representation of the automated UI interactions.

 

How does Repeato work compared to other mobile app testing tools?

Repeato has a new approach to mobile UI testing and works fundamentally different then other UI testing frameworks:

Repeato 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 utilizing computer vision (openCV, tesseract) and machine learning (tensorflow).

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.

 

Does Repeato work with frameworks?

Yes, Repeato support a wide range of frameworks: Flutter, React Native, Xamarin, Unreal Engine and many more.

 

Is Repeato an alternative to Espresso?

Yes it is.

What is wrong with using Espresso for testing? Not much. There is one big issue though: It's very time consuming to create tests: finding the right view ID, mocking classes, creating idling resources or finding the right delays for you next step.

Espresso need to have a sophisticated understanding of how the UI is structured. In order to create asserts and click views, Espresso as well as most other testing frameworks 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)

 

Is Repeato an alternative to Gherkin and Appium?

Gherkin with Appium is not a bad idea. Especially if you want to tests on hundreds of different devices in parallel. It’s open source and there is tons of documentation out there.

However, the problem with traditional test automation is the complexity in terms of setup and communication:
The testers need the app to be built in a way that they can access the UI elements. Most often IDs are used for that. So before they can even start to automate things, the developer team needs to do a lot of work:

  1. Creating and documenting IDs, making sure IDs are unique
  2. Setting up the whole infrastructure to execute tests
  3. Educating the testers on how to automate things and sync tests with the team
BDD (or, Gherkin) adds another layer of abstraction, which is good for non-technical staff, but has it’s own downsides:
  • Natural language phrases (such as “When I click the login button”) need to be backed by code, which again has to be taken care of by developers.
  • Often, because the developers can’t foresee what the QAs want to automate, there is an ongoing back and forth about additional IDs or additional phrase definitions
  • An additional layer of abstraction also adds another point of failure and makes debugging harder.

To sum it up: Gherkin with Appium makes the QA team dependent on the developer team and puts even more responsibilities on them. And it takes a lot of communication between the teams. We have seen companies postpone their plans to introduce test automation because of that for years (not kidding).

So we suggest: Use both things in parallel. You will need lots of time to get a proper Appium automation working. But it might pay off in the long run!
Additionally use Repeato because some of the things you can do with it are not even possible with Appium (like checking content in native views like maps, generating batch run reports or pixel perfect assertions).

 

Testing with Repeato

Can I integrate Repeato into my continuous integration flow?

Yes you can. Repeato will run headless as a node.js application on pretty much every system.

 

Do you offer any device pools or does all the testing happen on customers local devices?

Only customers local devices. Emulators work too.

 

Can I use emulators or simulators instead of real devices?

Yes, with Repeato you can also use emulators or simulators instead of physical devices.

 

Does Repeato support real iOS devices?

Yes.

 

Can tests be replayed on other OSs (Android test on iOS for example)?

Unfortunately not yet. We are working on it though.

 

If I record a test on a device with 2:1 screen ratio, can I run it on 16:9?

Yes.

 

Can I modify test inputs without rerecording the test? (e.g. replace the recorded username with another one)

Yes, you can edit test steps easily.

 

Can you randomly generate input data for a test?

Yes, e.g. for registering new accounts you can generate random usernames or email addresses.

 

Can I record a test on one view of the app and replay it on another?

Yes, you can.

 

How can I sync my tests with my team?

Repeato allows you to create workspaces. Each workspace can live in its own directory which can be easily checked into a repository (either git or some other versioning software).  Learn how to get started.

Got more questions?

Get in touch!

Repeato

  • Home
  • Pricing
  • Blog
  • FAQ
  • About us

Documentation

  • Getting started
  • Test exception handling
  • Advanced testing techniques
  • JavaScript API
  • Release notes

Support

  • Contact
  • Documentation
  • Book a demo

Legal

  • Imprint
  • Terms & Conditions
  • Privacy policy
Repeato Reviews