[aerogear-dev] [Android] Android project structure for final

[Kris Borchers]

On Mar 1, 2013, at 12:38 AM, Matthias Wessendorf <matzew at apache.org> wrote:

> On Fri, Mar 1, 2013 at 2:02 AM, Douglas Campos <qmx at qmx.me> wrote:
>> 
>> On 28/02/2013, at 20:07, Summers Pittman <supittma at redhat.com> wrote:
>> 
>>> aerogear-android-tests: This will house all of the Aerogear tests for
>>> Android.
>> 
>> You mean moving all the tests? Can't this be only for integration tests, and the unit tests stay on the aerogear-android project?
> 
> I'd also prefer to have the unit tests for each of the libs
> (aerogear-android + aerogear-android-support) being in there.

I can see one reason to have the unit tests in a separate project. I assume both aerogear-android and aerogear-android-support would have pretty much identical tests since their functionality should be the same, right? It would be a pain to have to maintain multiple sets of the same tests across projects.
> 
> Only integration tests should be a totally independent project,
> consuming the other libs (aerogear-android + aerogear-android-support)
> and having tests against em.
> 
> -M
> 
> 
>> 
>> -- qmx
>> 
>> 
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> 
> 
> -- 
> Matthias Wessendorf
> 
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev