geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Kashyap" <>
Subject Re: Testsuite ready for action !
Date Tue, 21 Nov 2006 21:19:11 GMT
I don't know a whole lot of pros and cons of TestNG since I began
using it recently myself.

JUnit 3.8 didn't have a per-suite-once execution like TestNG
(@BeforeSuite and @AfterSuite) did. So we began using it.

JUnit 4.0 now does (@BeforeClass and @AfterClass) but yet it is highly
restrictive. The @BeforeClass has to be a public void static method
with no arguments. In our console-testsuite scenario, that wasn't of
much help to me.

I was told that there are other such nifty features but I'll let
someone more knowledgeable answer that.


On 11/21/06, Jacek Laskowski <> wrote:
> On 11/21/06, Prasad Kashyap <> wrote:
> > Issue #2 is now fixed. All the tests in console-testsuites and
> > deployment-testsuites now run and pass successfully. They continue to
> > use TestNG. So these testsuites will serve as a good example for
> > others wanting to use TestNG.
> Will you be willing to tell us (me, particularly) what the pros and
> cons of using TestNG are? In other words, shall we abandon junit for
> testng completely because testng is what Geronimo, OpenEJB should be
> using due to its better architecture, etc.? I'd like to give it a shot
> in openejb and see how it could improve its bits.
> Jacek
> --
> Jacek Laskowski

View raw message