The these switches don't address the wander off problem when you need a 3rd party Activity to make a selection and return a result. Switching apps (pct-appswitch) and injecting any event (pct-anyevent) don't accomplish the goal of selecting and returning a result. It gets worse when the 3rd party package contains many interlinked Activities where the monkey can get lost since there is no way to restrict a 3rd party Activity by Activity name. Switch allowed-package-name only restricts by package.
Note: The contradiction isn't lost on me. On one hand I'm asking for the Monkey to use the 3rd party Activity so my calling Activity is forced to handle the range of possible results and on the other hand I dislike that the monkey spends significant time within the 3rd party Activity (which could be necessary to find all possible result values). That said, I'm ok with the current options. It just takes more monkeys (or more time) to get the job done. On Feb 13, 11:49 am, Brian Conrad <[email protected]> wrote: > Mark Murphy wrote: > >> 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. > > I used the --pct-appswitch --pct-anyevent switches which I used to > rein in Monkey's wandering off. I finally got it through a large > number of events without it getting hung up on stuff that wasn't mine. > > >> 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. -- 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.
