You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2012/05/16 21:02:47 UTC
Git, my huge commit, etc.
Hopefully I haven't totally destabilized the world.
I've been working in a local branch moving TestNG code over to Spock.
It's beautiful. However, it is only half done and the command line
build may be affected.
Normally, I would have waited until it was complete, and done a single
big rebase/merge ... but I couldn't risk it on top of the move from
git+svn to pure svn.
In any case, in the future, it will be much easier to keep this kind
of thing in branches.
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Git, my huge commit, etc.
Posted by Howard Lewis Ship <hl...@gmail.com>.
This is still evolving.
If you code in Java, you should learn Spock for testing. If you write
Java web stuff, learn Geb. You will be happy.
That being said, I expect to set things up so that there are specific
packages for JUnit & Spock tests, and others for TestNG. TestNG
claims to be able to integrated JUnit tests and produce a combined
execution and report. I'll be testing that.
Junit + Geb do not have a couple of test lifecycle features that the
tapestry-core tests need.
On Thu, May 17, 2012 at 2:28 AM, Lance Java <la...@googlemail.com> wrote:
> Hi Howard, does this mean that all future test cases should be in
> groovy/spock?
>
> I think it's fair to say that everyone committing patches to Jira will have
> Java knowledge. Since a patch is more likely to be included if it has a test
> case, I think you are limiting your potential committers by requiring that
> test cases are written in spock/groovy.
>
> My 2p.
>
> Cheers,
> Lance.
>
> --
> View this message in context: http://tapestry.1045711.n5.nabble.com/Git-my-huge-commit-etc-tp5711062p5711296.html
> Sent from the Tapestry - Dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Git, my huge commit, etc.
Posted by Lance Java <la...@googlemail.com>.
Hi Howard, does this mean that all future test cases should be in
groovy/spock?
I think it's fair to say that everyone committing patches to Jira will have
Java knowledge. Since a patch is more likely to be included if it has a test
case, I think you are limiting your potential committers by requiring that
test cases are written in spock/groovy.
My 2p.
Cheers,
Lance.
--
View this message in context: http://tapestry.1045711.n5.nabble.com/Git-my-huge-commit-etc-tp5711062p5711296.html
Sent from the Tapestry - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org