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 <r...@acm.org> 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 android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
