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. At one point we will loose track of what's happening where. KISS!
So -1 from me unless there is something that we desperately need and that can only be done with Spock and not with TestNG. 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]
