Some cts info here: http://source.android.com/compatibility/cts-development.html. I would do:
cd $ANDROID_BUILD_TOP m -j<cpu-count> cts cts-tradefed run singleCommand cts --plan CTS There are options to run a specific test package, but as you can see in my notes about testing bouncycastle provider upgrades in external/bouncycastle/README.android, the tests for this stuff are scattered all over the place. -bri On Fri, Feb 22, 2013 at 8:11 AM, Joe Droider <droidvi...@gmail.com> wrote: > Thanks Brian. Lets say we take aosp code and port it back to 4.0.1. > > Is there any way to verify just this part of code using CTS? > > Please bear with my ignorance. How does one invoke CTS testing once platform > build is complete? > Can it be tweaked to do this testing one specific sdk packages (say > javax.security for example)? > > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Android Security Discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to android-security-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to > android-security-discuss@googlegroups.com. > Visit this group at > http://groups.google.com/group/android-security-discuss?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-security-discuss+unsubscr...@googlegroups.com. To post to this group, send email to android-security-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/android-security-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.