interesting to hear that it's being used to such a degree. It does
give me some comfort just to have something bang at the app in case it
hits a silly thing I might not have caught. btw, the monkey seems to
be particularly fascinated with the ringer volume, for some reason.
At least when I run
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,
Again, monkeys are NOT deterministic.
On Fri, May 13, 2011 at 7:52 PM, avi avinanku...@gmail.com 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
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
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
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,
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
You are experiencing different crashes because you have fixed the bugs
causing the other ones. Right?
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe
Sorry, I meant I am getting different crashes on the same build
(without any fix)...The crash that I am looking at happens only 1 out
of 10 times and it happens after running Monkey for several hours (~8
hours)..So, I would like to replay the monkey run which caused the
crash and check if my fix
If you give the same seed, you will have the same sequence of events
executed.
However it is pretty unavoidable that the results will be non-deterministic.
There is just too much asynchronous stuff, things running in the background
that can impact behavior, etc.
On Fri, May 6, 2011 at 2:57 PM,
Thank you Dianne for your response. So, what is Google's recommended
process for fixing issues caused by monkey runs?
On May 6, 4:24 pm, Dianne Hackborn hack...@android.com wrote:
If you give the same seed, you will have the same sequence of events
executed.
However it is pretty unavoidable
On Fri, May 6, 2011 at 9:43 PM, avi avinanku...@gmail.com wrote:
Thank you Dianne for your response. So, what is Google's recommended
process for fixing issues caused by monkey runs?
Step #1: Use the monkey to generate a crash
Step #2: Write the test case that reproduces the crash
Step #3:
12 matches
Mail list logo
