<div dir="ltr">Hi,<div><br></div><div>thanks for putting some test work together.</div><div><br></div><div style>Looking at <a href="https://gist.github.com/kpiwko/5612949">https://gist.github.com/kpiwko/5612949</a>, this reminds me of what I have called "integration tests" in previous projects. This is great and indeed needed! </div>
<div style>--> that way you can _really_ tell if something is broken, since executed against a real (separated) server, and not against something that is mocked.</div><div style><br></div><div style><br></div><div style>
However, not sure I really like having a new "tests" folder at "root" level of the project;</div><div style>Instead, I'd prefer a separate PushEE-integration-tests project, which does the same.</div>
<div style><br></div><div style>For me, tests inside of the project should be more mock/unit/BDD kinda tests. Integration tests should be on their own repo, IMO <br></div><div style><br></div><div style>Once, we have an "official" AG-PushEE repo, do you think having these "integration" in an isolated repo makes sense?</div>
<div style><br></div><div style><br></div><div style>-Matthias</div><div style><br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 20, 2013 at 6:21 PM, Karel Piwko <span dir="ltr"><<a href="mailto:kpiwko@redhat.com" target="_blank">kpiwko@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All,<br>
<br>
I've just sent a PR for PushEE testing [1]. The idea is to write tests covering<br>
specification and simply execute those against a real running server instance.<br>
More details at [2].<br>
<br>
I have evaluated multiple API approaches, described here[3], Groovy and Spock<br>
seems to be the best to me.<br>
<br>
Any comments/suggestions/objections very welcomed. My plan is to start covering<br>
specs we have so far and run it on a CI server.<br>
<br>
Thanks,<br>
<br>
Karel<br>
<br>
[1] <a href="https://github.com/matzew/pushee/pull/6/" target="_blank">https://github.com/matzew/pushee/pull/6/</a><br>
[2] <a href="https://github.com/kpiwko/pushee/blob/tests/tests/readme.txt" target="_blank">https://github.com/kpiwko/pushee/blob/tests/tests/readme.txt</a><br>
[3] <a href="https://gist.github.com/kpiwko/5612949" target="_blank">https://gist.github.com/kpiwko/5612949</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>
</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>