On Thu, Apr 14, 2011 at 9:51 AM, Ulrich Stärk <[email protected]> wrote:
> IMO we are making the build and test process even more complex than it is > today: We have Gradle and > Maven builds, we have tests written in Groovy and tests written in Java and > now we want to have > both, tests using Spock and tests using TestNG. Well, Spock makes tests shorter and more readable. All java-based testing libs feel clumsy after you learned Spock. By using Gradle, Grovvy-based tests and Spock we are making the build process easier, not more complex. > At one point we will loose track of what's happening > where. KISS! > C'mon Uli, I don't see a reason for loosing track. What are your concerns? Is it Groovy? > > So -1 from me unless there is something that we desperately need and that > can only be done with > Spock and not with TestNG. > Well, I could also ask you why would you need Tapestry if you could use plain Servlets and JSPs for building web applications. > > Uli > > On 14.04.2011 00:33, Igor Drobiazko wrote: > > Today I attended Peter Niederwieser's talk on Spock. Spock is just great > and > > beats all the existing Java-based testing frameworks easily. > > > > Since Spock is already used in plastic, I would like to propose to use in > in > > other tapestry module a well. Since it is impossible to migrate the > existing > > tests to Spock, we could write new tests with Spock. The only issue I see > is > > that Spock is run by JUnit while Tapestry's tests are based on TestNG. We > > would need to come up with two test runs: one for TestNG, the other for > > JUnit. We also would need to merge the cobertura coverage. > > > > Any ideas? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Best regards, Igor Drobiazko http://tapestry5.de
