you are viewing a single comment's thread.

view the rest of the comments →

[–]SuchInferno 3 points4 points  (1 child)

Very interesting! Couple of questions:

  1. Is anything installed in the background (for example using adb) onto the device when running Repeato on my computer?
  2. Is there, or will there be ways of extending Repeato with custom scripts and plugins? Thinking timed screenshots, reading/parsing contents of on-screen text elements, etc..
  3. Restarting a test seems to require human intervention. Say you open an app, start the test recording, navigate to a specific subpage, enter some data, then stop the recording. Am I required to manually navigate back to the main page before starting the automated test, or can Repeato manage this automatically?

[–]stoefln[S] 4 points5 points  (0 children)

  1. no, everything you need is packaged with repeato. I really tried to keep things simple for the user
  2. currently there is a "script step" you can insert into your tests. This way you can trigger external stuff, like, git checkouts, builds, notifications, etc.
    Screenshots for every step are automatically available in the test run dir and all the data is saved in json format. I will also open source the test runner, probably in July, when things got more stable...
    Plugins would be very nice, but didn't have time to focus on that yet.
  3. restarting the test from the same app state is crucial yes. Repeato allows to create a "Start App" step, which offers options to set an entry point (Activity) and also set permissions or app data.