That’s really great feedback. We’d be interested to know how many events you’d find most beneficial so we can work out how much time to allot to each individual test run. It’s something we’ve been debating internally, so let us know what you think so we can test the system.

We sure have put a lot into the UI. Our frontend dev has done some really innovative stuff with D3 and HTML5 Canvas (working on a blog all about it). We’ve heard from a few Devs that the ability to download results is a feature they’d like to see. We’re looking to implement that really soon.

Appreciate your feedback!

Any chance you will be allowing more flexibility in the tests that can be run? For example my app is large enough that I seem to fail to install on many of your devices – so allowing the install timeout to be longer would probably help a lot. Additionally just 1500 events passed via the Monkey is nothing – it only ever gets to exercise a tiny fraction on my app – perhaps you could allow “off peak” users to specify an increased number of events to be dispatched?

Finally you’ve put a lot of effort in to the UI for displaying results, and for casual usage that’s great, but I really want to be able to download all the results and look at them offline (or rather for my own scripts to process them offline!) Any chance you could add a “download a zip file of all results”?

Keep up the good work