Re: [android-developers] test cases are in a different package

2012-02-19 Thread Ray Tayek
At 11:56 AM 2/18/2012, you wrote: At 10:43 AM 2/18/2012, you wrote: ... That's not true. You want the unit tests (it's important to distinguish what kind of test we're discussing!) in the same package as the classes they test. yes. ... Put the test code in its own source tree, duh. / |

Re: [android-developers] test cases are in a different package

2012-02-18 Thread Ray Tayek
At 10:43 AM 2/18/2012, you wrote: ... That's not true. You want the unit tests (it's important to distinguish what kind of test we're discussing!) in the same package as the classes they test. yes. ... Put the test code in its own source tree, duh. / | | src/ | |--- test/ my

Re: [android-developers] test cases are in a different package

2012-02-18 Thread Lew
hongbosb wrote: > > If test cases are put in the same package, then release version will > contain test project. This isn't customer want to see. > That's not true. You want the unit tests (it's important to distinguish what kind of test we're discussing!) in the same package as the classes the

Re: [android-developers] test cases are in a different package

2012-02-18 Thread fei ji
> > If test cases are put in the same package, then release version will > contain test project. > who is going to do that? the test cases are in a separate project? In android, test project is usually put in a directory called tests under the tested project. If it is a sub-project of the under t

Re: [android-developers] test cases are in a different package

2012-02-17 Thread Ray Tayek
At 03:06 PM 2/17/2012, you wrote: If test cases are put in the same package, then release version will contain test project. who is going to do that? the test cases are in a separate project? And you should only test public interface. i disagree. i usually test non-public classes and metho

Re: [android-developers] test cases are in a different package

2012-02-17 Thread fei ji
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

[android-developers] test cases are in a different package

2012-02-17 Thread Ray Tayek
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