If test cases are put in the same package, then release version will contain test project. This isn't customer want to see. And you should only test public interface. Because other module can only use the method declared public. If you insist on testing method other than pubic, you can consider to use the reflection of java to test even private method. But it violate common sense of TDD. 在 2012-2-18 上午6:21，"Ray Tayek" <[email protected]>写道：
> having the test cases in a different package make it hard to test methods > and classes with protected or the default visibility. > > is there some reason why the test cases are put into a separate package? > > placing them in the same package seems to work ok. > > am going to run into trouble by doing this? > > thanks > > --- > co-chair http://ocjug.org/ > > -- > 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<[email protected]> > To unsubscribe from this group, send email to > android-developers+**[email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/**group/android-developers?hl=en<http://groups.google.com/group/android-developers?hl=en> -- You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en
