> Better control would be useful though. Sometimes the monkey will spend > an enormous amount of time in Activities that are not from my app > (when launched from my app). All I want the activity to do is perform > some operation and return but it just hangs out there testing someone > else's code.
There's a flag to control that. I'm on a 6-hour-delayed flight sitting in Atlanta typing this on a Droid, so I don't have the SDK docs in front of me right now to note what the switch is. > > On Feb 11, 4:37 am, Brian Conrad <[email protected]> wrote: >> Does anyone find Monkey all that useful? I it finds an error it dumps a >> ton of information which would probably only be understood by an Android >> systems engineer. Where's the documentation for all those dumps? >> Almost every time (as others have found) it has NOTHING to do with my >> application. Monkey doesn't seem to handle applications that launch >> intents very well. It still can get hung up on a dialog and think the >> app has died when it hasn't. Someone once said that perusing the Monkey >> code the ignore timeouts as just a stub and not implemented. Just for a >> test I ran it on the Api Demos and it failed only after 10 events. >> >> - Brian > > -- > You received this message because you are subscribed to the Google Groups > "Android Discuss" 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-discuss?hl=en. > > -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
