<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 16, 2013 at 5:18 PM, Douglas Campos <span dir="ltr"><<a href="mailto:qmx@qmx.me" target="_blank">qmx@qmx.me</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks Karel for the well balanced email.<br>
<br>
This discussion will never reach an agreement, </blockquote><div><br></div><div>yes</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">because it's a biased<br>
discussion, and we do have personal preferences involved - I for one<br>
can't stand Groovy.<br>
<br>
And that's the reason I strongly advocate for keeping it to Java - this<br>
is a Groovy vs Java, while it should've been X vs Java - Scala specs2,<br>
RSpec (via JRuby), Jasmine or Mocha (via DynJS or Rhino) - Heck, even<br>
Clojure would be easier to work than Java.<br></blockquote><div><br></div><div><br></div><div>"easier" is also personal taste (I can't read the encrypted nature of Clojure) :-)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Unless we have a broad discussion over all those languages (which<br>
honestly I don't think we have time for that) we should stick to the<br>
lowest common denominator, which is (unfortunately) Java.<br></blockquote><div><br></div><div>This is also true.</div><div><br></div><div>I guess, not sure, it would make sense to "focus" or concentrate on Java, for now ? </div>
<div><br></div><div>I am not really sure, what's the "best" (ha ha) option on this. However, I think we do need a decision here...</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
fwiw, I can see the value of s/Groovy/dynamic JVM lang for tests/ - any<br>
of them would fit the bill - what I can't let go is the partiality of<br>
the debate.<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Jul 16, 2013 at 01:03:43PM +0200, Karel Piwko wrote:<br>
> Hi,<br>
><br>
> let me summarize the discussion from previous threads:<br>
><br>
> What were testing requirements?<br>
> * Do not mock<br>
> * Cover both backend and frontend testing at the same time<br>
> * Control test env from tests/Maven, so it runs on both CI and local machine<br>
> without any setup required<br>
> => Those 3 requirements limited us to use Arquillian<br>
> * Cover unified push server specifications in readable way<br>
><br>
> Why Groovy instead of Java?<br>
> + Better support for JSON<br>
> + Spock provides very nice BDD support<br>
> + Still supports anything Java would do<br>
><br>
> What problems we faced with Groovy?<br>
> - Needs specific compiler - solved, configured for tests only<br>
> - Needs support in IDE - Intellij - ootb, Eclipse and NetBeans have<br>
> plugins<br>
> - Needs to be deployed in test deployment - not addressed now, prolongs test<br>
> execution by few seconds per deployment<br>
><br>
> What are currently raised concerns?<br>
> - Different language for development and testing<br>
> - Raises bar for newcomers willing to write tests<br>
><br>
> Thank you for additional advantages, concerns or proving some of those are not<br>
> valid.<br>
><br>
> Karel<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>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
qmx<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<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>