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. On Friday, May 6, 2011 10:49:45 PM UTC-7, Mark Murphy (a Commons Guy) wrote: > > On Fri, May 6, 2011 at 9:43 PM, avi <avina...@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: Fix the bug > > Step #4: Ensure that the test case you wrote in step #2 now passes > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 3.4 Available! > > -- 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
