Exactly. The annotations in InstrumentationTestRunner come from
android.test.suitebuilder.annotation. My understanding is that, while
they're public, they're not supported.
As a note, InstrumentationTestRunner and the Android unit/functional
test framework are based on JUnit 3, not JUnit 4.
On Jan 14, 3:09 pm, Diego Torres Milano <dtmil...@gmail.com> wrote:
> If you want to provide a different behavior for the test runner just
> create your own extending it:
>
> public class MyTestRunner extends
> android.test.InstrumentationTestRunner {
> // do wathever you want
>
> }
>
> To do whatever you want, use android.test.InstrumentationTestRunner
> source as a an inspiration.
>
> On Jan 13, 1:47 am, Aman Bhardwaj <myama...@gmail.com> wrote:
>
> > Hi,
> > I have some test cases with my own defined Annotations, but
> > InstrumenationTestRunner doesn't runs tests based on annotation.
> > However it works if I add annotations
> > from android.test.suitebuilder.annotation.
>
> > Is it only supposed to work with annotations
> > in android.test.suitebuilder.annotation.Smoke?
> > Any suggestions how to make it work with my own annotations.
>
> > Thanks,
> > ~Aman
>
> --
> Have you read my blog ?http://dtmilano.blogspot.com
> android junit tests ui linux cult thin clients
--
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
