The main thing we use monkey for is automated testing for statistical tracking of stability and performance. That is, for a particular build there is a lab that runs multiple monkeys on the build and collects statistics on how many events they were able to perform before failing and what kinds of failures they had. This is aggregated together to get the overall stability of the platform and the most common kinds of failures that are impacting stability. Performing continuous monkey runs allows this information to be aggregated over time to detect if problems are being introduced or stability is being improved.
For application unit test, the instrumentation facility is the intended mechanism. This allows you to have much more control within your own application, and because it is running within that app you can avoid much of the impact of other things going on across the rest of the system. On Fri, May 13, 2011 at 8:08 PM, B Lyon <[email protected]> wrote: > When I first read about the monkey runner, I thought I could use it > for all kinds of stuff, but after learning a little more I'm not sure > you would want to use it for controlled tests (like regression checks, > functional tests). Maybe great to throw a bunch of random stuff at > your app (and it's fun to watch it go), and it might do something that > hits a bug you might never have found cause of the bizarre sequence it > went through, but not sure about how much you can do with it. I kind > of hope I'm wrong, so someone correct me if I am not giving the monkey > its due. > > On Fri, May 13, 2011 at 4:01 PM, Dianne Hackborn <[email protected]> > wrote: > > Again, monkeys are NOT deterministic. > > > > On Fri, May 13, 2011 at 7:52 PM, avi <[email protected]> wrote: > >> > >> Hi Diego, > >> > >> Thank you for your post..I tried the exact same steps..Running monkey > >> with verbose option and post processed the file to replay Monkey...but > >> there was slight deviation from the original run..If you have tried > >> it, could you please share your solution with me? > >> > >> Thanks again > >> > >> On May 8, 10:52 pm, Diego Torres Milano <[email protected]> wrote: > >> > I haven't tried this but it seems possible. > >> > > >> > Step #1: Increase monkey verbosity (-v -v -v) > >> > > >> > Step #2: Run the script and collect the output > >> > > >> > Step #3: Parse the output to regenerate a monkey script (optionally > >> > you can modify monkey to spit a valid monkey script) > >> > > >> > Step #4: Run the script > >> > > >> > On May 7, 2:20 pm, Bob Kerns <[email protected]> wrote: > >> > > >> > > True enough, but the difficulty generally comes between step #1 and > >> > > step #2, > >> > > in this sort of scenario of a rare, hard-to-reproduce crash. > >> > > >> > > Often you have to figure out everything you need to know to do step > #3 > >> > > (fix > >> > > the bug) before you can do step #2. > >> > > >> > > Even so, do it in this order. Write the test case before fixing it, > so > >> > > you > >> > > can do step #4 -- verify that you fixed it. > >> > > >> > -- > >> > Have you read my blog ?http://dtmilano.blogspot.com > >> > android junit tests ui linux cult thin clients > >> > >> -- > >> You received this message because you are subscribed to the Google > >> Groups "Android Developers" group. > >> To post to this group, send email to > [email protected] > >> To unsubscribe from this group, send email to > >> [email protected] > >> For more options, visit this group at > >> http://groups.google.com/group/android-developers?hl=en > > > > > > > > -- > > Dianne Hackborn > > Android framework engineer > > [email protected] > > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see > and > > answer them. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > > http://groups.google.com/group/android-developers?hl=en > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
