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

On 03/01/2013 09:23 AM, Matthias Wessendorf wrote: > On Fri, Mar 1, 2013 at 3:16 PM, Summers Pittman <supittma(a)redhat.com&gt; wrote: >> On 03/01/2013 07:16 AM, Matthias Wessendorf wrote: >>> On Fri, Mar 1, 2013 at 12:59 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: >>>> On Mar 1, 2013, at 12:38 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: >>>> >>>>> On Fri, Mar 1, 2013 at 2:02 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>>>> On 28/02/2013, at 20:07, Summers Pittman <supittma(a)redhat.com&gt; 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. >>> Not sure about the details, BUT... you misread. >>> >>> Unit tests belong to the library. I am -1000 on having a 'unit test' >>> only broject. >>> >>> Integration tests are different, they _should_ be separated >> Integration tests also test on the underlying platform (IE the Android >> device). > of course :) never said anything against that :) > But... running them from an emulator, against a REAL server, is a > start for an integration test suite. > >> The unit tests for AG Android can stay with the project, > ok > >> but the number of tests in the project will go way down. > So you remove them ? Not sure I get that... (half) sentence; The project, aerogear-android will have fewer tests because only the unit ("pure java") tests will stay in it. Tests which use the integration server or the emulator (say anything with Loaders) will go in the ag-and-test project.

> >>> -M >>> >>>>> 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(a)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(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>> >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev