Comments on: AbstractTransactionalSpringContextTests meets TestNG http://blog.centuryminds.com/2006/12/abstracttransactionalspringcontexttests-meets-testng/ Mon, 21 May 2012 01:03:08 +0000 http://wordpress.org/?v=2.6.2 By: Rubén Barroso http://blog.centuryminds.com/2006/12/abstracttransactionalspringcontexttests-meets-testng/#comment-184 Rubén Barroso Tue, 27 Feb 2007 14:55:12 +0000 http://blog.centuryminds.com/2006/12/12/abstracttransactionalspringcontexttests-meets-testng/#comment-184 Glad to hear that, Hani! I'll check them out and see how they can fit to our needs. Thanks very much Glad to hear that, Hani! I’ll check them out and see how they can fit to our needs. Thanks very much

]]> By: Hani Suleiman http://blog.centuryminds.com/2006/12/abstracttransactionalspringcontexttests-meets-testng/#comment-183 Hani Suleiman Tue, 27 Feb 2007 13:03:29 +0000 http://blog.centuryminds.com/2006/12/12/abstracttransactionalspringcontexttests-meets-testng/#comment-183 Hi there, All of the spring test heirarchy exists in testng, in the org.testng.spring package! Unfortunately there are no builds for this, so if you grab the source andgo to the spring directory, run ant, you'll end up with a jar file that has classes matching all of the names of the ones that Spring ships, without any JUnit dependencies. You can even do stuff like annotate test methods with @Transactional if you want. Hi there,

All of the spring test heirarchy exists in testng, in the org.testng.spring package! Unfortunately there are no builds for this, so if you grab the source andgo to the spring directory, run ant, you’ll end up with a jar file that has classes matching all of the names of the ones that Spring ships, without any JUnit dependencies.

You can even do stuff like annotate test methods with @Transactional if you want.

]]> By: GojiraDeMonstah http://blog.centuryminds.com/2006/12/abstracttransactionalspringcontexttests-meets-testng/#comment-182 GojiraDeMonstah Wed, 21 Feb 2007 19:32:39 +0000 http://blog.centuryminds.com/2006/12/12/abstracttransactionalspringcontexttests-meets-testng/#comment-182 The JUnit dependency is unfortunate, but I think the solution as a whole is fantastic. I just googled on combining TestNG and Spring on a whim and found this article - it's *exactly* what I needed. The nice goodies the testNG Eclipse plugin gives you with the heavy duty IOC and transaction management from Spring - it is the best of both worlds. Nice work Rubén! The JUnit dependency is unfortunate, but I think the solution as a whole is fantastic. I just googled on combining TestNG and Spring on a whim and found this article - it’s *exactly* what I needed. The nice goodies the testNG Eclipse plugin gives you with the heavy duty IOC and transaction management from Spring - it is the best of both worlds.

Nice work Rubén!

]]> By: Rubén Barroso http://blog.centuryminds.com/2006/12/abstracttransactionalspringcontexttests-meets-testng/#comment-181 Rubén Barroso Mon, 29 Jan 2007 19:44:14 +0000 http://blog.centuryminds.com/2006/12/12/abstracttransactionalspringcontexttests-meets-testng/#comment-181 Nico, thanks for your comments. In relation to the issue with the JUnit dependency, I think you´re right. As you say, it would be great to count on such features in Spring. In fact, Hani/Cédric told us there are some classes in the new Spring release (2.0) to cope with that, but after taking a peek at it, as of that time those classes didn´t use the annotations facility, but the commons´ javadoc tags. Anyway, the actual point to take into account is the one you state: to get rid of the JUnit dependency whenever you want to use TestNG. Let´s see if we come along with this in the sort term :) Nico, thanks for your comments. In relation to the issue with the JUnit dependency, I think you´re right. As you say, it would be great to count on such features in Spring. In fact, Hani/Cédric told us there are some classes in the new Spring release (2.0) to cope with that, but after taking a peek at it, as of that time those classes didn´t use the annotations facility, but the commons´ javadoc tags.
Anyway, the actual point to take into account is the one you state: to get rid of the JUnit dependency whenever you want to use TestNG. Let´s see if we come along with this in the sort term :)

]]> By: nico http://blog.centuryminds.com/2006/12/abstracttransactionalspringcontexttests-meets-testng/#comment-185 nico Thu, 18 Jan 2007 13:45:37 +0000 http://blog.centuryminds.com/2006/12/12/abstracttransactionalspringcontexttests-meets-testng/#comment-185 First drawback i see is that this way of joining spring and testNG, keeps in your system the dependency with JUnit framework... which as you 're trying to use testNG is quite undesireable. Possible solution is to replicate spring mock test classes eliminating its dependency on junit, although the best solution would be that spring fellows put some classes right out-of-the-box which 've no dependency on junit.., and then subclass them to add the junit dependency. First drawback i see is that this way of joining spring and testNG, keeps in your system the dependency with JUnit framework… which as you ‘re trying to use testNG is quite undesireable.

Possible solution is to replicate spring mock test classes eliminating its dependency on junit, although the best solution would be that spring fellows put some classes right out-of-the-box which ‘ve no dependency on junit.., and then subclass them to add the junit dependency.

]]>