The migrating from JUnit section tries to facilitate a migration with minimal code changes while still keeping the old test code. IMO, that may work in the short run, but since the integration tests have become messy, I'd advice against trying to preserve old code, but look at it from a fresh perspective, and do it right.
On Thu, Dec 15, 2011 at 11:01 PM, Nirmal Fernando <[email protected]> wrote: > May be it's worth reading on "migrating from Junit section" (there's > an Eclipse plugin) [1] and an user experience on migration [2], if you > haven't referred to them yet. > > [1] http://testng.org/doc/migrating.html > [2] > http://www.opengamma.com/blog/2011/04/04/converting-opengamma-junit-testng > > On Wed, Dec 14, 2011 at 6:12 PM, Nuwan Wimalasekara <[email protected]> > wrote: > > +1. TestNG has test parameterization and multi threading test > execution. > > these features also can be used. > > > > Thanks > > NuwanW > > > > On Tue, Dec 13, 2011 at 7:56 PM, Afkham Azeez <[email protected]> wrote: > >> > >> Folks, > >> I was playing around a bit with TestNG > >> (http://testng.org/doc/documentation-main.html#introduction) & it > seems to > >> be the way to go for the type of integration testing we are doing. This > may > >> involve major changes at the platform testing level but will be worth > the > >> investment. > >> > >> Here are some articles that compare TestNG with JUnit4. We are using > JUnit > >> 3. > >> > >> http://www.mkyong.com/unittest/junit-4-vs-testng-comparison/ > >> http://nelz.net/2010/10/06/testng-vs-junit4/ > >> > >> I had a chat with Krishantha & he too agrees that TestNG is more > suitable > >> for the type of test automation we do. Does anybody have any concerns > >> regarding this move? > >> > >> -- > >> Afkham Azeez > >> Director of Architecture; WSO2, Inc.; http://wso2.com > >> Member; Apache Software Foundation; http://www.apache.org/ > >> > >> email: [email protected] cell: +94 77 3320919 > >> blog: http://blog.afkham.org > >> twitter: http://twitter.com/afkham_azeez > >> linked-in: http://lk.linkedin.com/in/afkhamazeez > >> > >> Lean . Enterprise . Middleware > >> > >> > >> _______________________________________________ > >> Architecture mailing list > >> [email protected] > >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >> > > > > > > _______________________________________________ > > Carbon-dev mailing list > > [email protected] > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > -- > > regards, > Nirmal > > Software Engineer, WSO2 Inc. > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
