<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 16, 2013 at 3:52 PM, Summers Pittman <span dir="ltr"><<a href="mailto:supittma@redhat.com" target="_blank">supittma@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="im">
<div>On 07/16/2013 07:09 AM, Matthias
Wessendorf wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Karel,
<div><br>
</div>
<div>thanks for starting the thread and summarizing all the
facts/statements from the previous discussion!</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Jul 16, 2013 at 1:03 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,<br>
<br>
let me summarize the discussion from previous threads:<br>
<br>
What were testing requirements?<br>
* Do not mock<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
* 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>
</blockquote>
</div>
</div>
</div>
</blockquote></div>
Not really, if you are using Maven as your project format then the
IDEs really don't have to do any work. The latest NetBeans has not
craptacular Groovy out of the box as well. <br><div class="im">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- 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>
</blockquote>
</div>
</div>
</div>
</blockquote></div>
Why is this a concern? <br><div class="im">
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- Raises bar for newcomers willing to write tests<br>
</blockquote>
</div>
</div>
</div>
</blockquote></div>
Other than ending a FooTest in .groovy or .java how does it actually
raise the bar?</div></blockquote><div><br></div><div>true</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
<div class="im"><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>that's the 'concerns' I share as well: it a little
burden on getting back contributions, since the source of
the server is java.</div>
<div><br>
</div>
<div><br>
</div>
<div>Also, what would happen if others decide let's add Ruby
and also Perl for some sort of tests? That would mean a
language nightmare, IMO :) <br>
</div>
</div>
</div>
</div>
</blockquote></div>
We reject the PR. </div></blockquote><div><br></div><div>:-)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">
Groovy is a much "easier" language than Java.
Sure it will allow people to write some particularly hellish code,
but we just punt those PRs.<br>
<br>
Punting the PR is also the answer for what happens if someone adds
Ruby or Perl.<div class="im"><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thank you for additional advantages, concerns or proving
some of those are not<br>
valid.<br>
</blockquote>
</div>
</div>
</div>
</blockquote></div>
Pros of Groovy:<br>
* Built in examples of how to call the code from a Groovy based
application. <br>
* It gives us a carrot to hang in front of community members who
might not want to write Java or who want to stretch their polyglot
legs.<br>
<br>
Cons of Groovy:<br>
* Language is slippery. Lots of ways to do something which could be
quite abstract or opaque.<br>
* If we use indy then we are committing to Java 7+<br>
* It does require us to make some annoying trade offs w.r.t
simplicty of our build.<br>
* One more point of failure in a build<div class="im"><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Karel<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
aerogear-dev mailing list
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></pre>
</blockquote>
<br>
</div></div>
<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></div>