Mark Murphy wrote:
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.
No, I meant the switch that tells the Monkey to stay within your own app,
skipping any events that lead elsewhere.
If you are talking about -p you can even get Monkey to run an app
without that switch. Here are the switches:
usage: monkey [-p ALLOWED_PACKAGE [-p ALLOWED_PACKAGE] ...]
[-c MAIN_CATEGORY [-c MAIN_CATEGORY] ...]
[--ignore-crashes] [--ignore-timeouts]
[--ignore-security-exceptions] [--monitor-native-crashes]
[--kill-process-after-error] [--hprof]
[--pct-touch PERCENT] [--pct-motion PERCENT]
[--pct-trackball PERCENT] [--pct-syskeys PERCENT]
[--pct-nav PERCENT] [--pct-majornav PERCENT]
[--pct-appswitch PERCENT] [--pct-flip PERCENT]
[--pct-anyevent PERCENT]
[--wait-dbg] [--dbg-no-events] [-f scriptfile]
[--port port]
[-s SEED] [-v [-v] ...] [--throttle MILLISEC]
COUNT
And here:
http://developer.android.com/guide/developing/tools/monkey.html
As usual there is NOT enough information to understand how this stuff is
supposed to work (blog article might be welcome by many developers). I
think some folks have walked the source which I haven't yet but really
don't want to spend time on that over creating new apps. Also -v seems
to need the number IMMEDIATELY following i.e. -v1 . The -c option is
VERY unclear in the documentation. Anyone know what an actual command
line using should look like?
What I'm saying is I got more satisfactory results when I put the
percentages at 10 for the switches I mentioned. My app got through all
25,000 events.
--
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.
