<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 30, 2013 at 2:40 PM, Kris Borchers <span dir="ltr"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Bruno and I have already started working on something like this for JS. I have a couple of comments inline which will illustrate why I think this should be separated by component and not one single aerogear-test-harness repo.<br>
<div class="im"><br>
On Jul 30, 2013, at 3:31 AM, Karel Piwko <<a href="mailto:kpiwko@redhat.com">kpiwko@redhat.com</a>> wrote:<br>
<br>
> Hi all,<br>
><br>
> there were already plenty of discussions about integration tests in Aerogear<br>
> [1-6]. As these are something most people want to execute in CI only and QE<br>
> wants to have better control over commits, I'd like to introduce new model that<br>
> I hope will improve current state:<br>
><br>
> * Integration tests are hosted in separate repository, e.g.<br>
> aerogear/aerogear-test-harness<br>
<br>
</div>+1 but would prefer that each component (JS, Android, iOS, etc.) have their own integration test repos<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> * Aerogear components do not contain integration tests<br>
<br>
</div>+1<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> * Aerogear components have .travis.yml modified to clone aerogear-test-harness<br>
> repository and execute appropriate component integration tests in CI after<br>
> each commit into component<br>
<br>
</div>This is the part where I think they need to be separate. I don't want to have to clone that entire repo including the tests and config for other components when I am testing JS.<br>
<div class="im">> * QE and devs have commit access to aerogear-test-harness repository<br>
<br>
</div>+1 to QE having access to all testing repos<br>
<div class="im">> * Aerogear-test-harness contains modules per integration test scenario, e.g.<br>
> a module for unified-push-server or a module for simple-push-server. Any<br>
> module can use different tools and/or language, whatever fits the test<br>
> scenario best way.<br>
<br>
</div>Again, this is solved by separate repos.<br></blockquote><div><br></div><div>+1</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">><br>
> Tolis already solved outstanding technical problems, either it is requirement to<br>
> depend on latest component state without polluting repository with local<br>
> installation, versioning or ability to make it importable to an IDE.<br>
><br>
> Let me know if you like it, we can proceed filling its content today.<br>
><br>
> Thanks,<br>
><br>
> Karel<br>
><br>
> [1] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-May/002471.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-May/002471.html</a><br>
> [2] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-July/003912.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-July/003912.html</a><br>
> [3] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-July/003944.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-July/003944.html</a><br>
> [4] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-July/003979.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-July/003979.html</a><br>
> [5] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-July/004127.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-July/004127.html</a><br>
> [6] <a href="http://lists.jboss.org/pipermail/aerogear-dev/2013-July/004096.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2013-July/004096.html</a><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>