Use import static org.testng.Assert.*
Don't use the JUnit stuff. Just migrate the Junit stuff. Putting an import static will fix the compilation errors. On Mon, Jan 2, 2012 at 12:01 PM, Subash Chaturanga <sub...@wso2.com> wrote: > Hi Azeez, > > When migrating to TestNG from JUnit, there are slight changes in the APIs > (in Assertions). I have already started re-factoring most of them. > But I just saw that there is an alternative JUnit compatible > testng.AssertJUnit class. Which one is preferred ? > (As we're completely moving away from JUnit, I thought of using the pure > org.testng.Assert class and re-factor our tests accordingly). > > WDYT ? > > Thanks > /subash > -- > > Subash Chaturanga > Software Engineer > WSO2 Inc. http://wso2.com > > email - sub...@wso2.com > phone - 077 2225922 > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **az...@wso2.com* <az...@wso2.com>* 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 Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
