On Tue, Jan 8, 2013 at 12:47 PM, Edison Su <edison...@citrix.com> wrote: > > >> -----Original Message----- >> From: Alex Huang [mailto:alex.hu...@citrix.com] >> Sent: Tuesday, January 08, 2013 6:18 AM >> To: cloudstack-dev@incubator.apache.org >> Subject: RE: [Discuss] Integration test >> >> > On 13/1/8 上午7:33, "Edison Su" <edison...@citrix.com> wrote: >> > >> > >BTW, the current junit test case can be transformed into testNG test >> > >case in eclipse automatically. So if we decide to switch to testNG >> > >for both unit test and integration test, it's doable with minimal >> > >effort. But, I do like junit, which is just so simple to use, and the >> > >integration with Spring is much better than testNG. Anyway, better to >> > >just use one test framework for all if possible. >> >> I think it's fine to use more than one framework. I don't see why we should >> limit how people do their now unit tests for example. > > OK, both junit and testNG test cases can be executed by maven, even they are > in the same maven project, so it's possible to mix junit and testNG in one > project, people can choose whatever they want: > http://confluence.highsource.org/display/~lexi/How+to+run+both+JUnit+and+TestNG+with+maven-surefire-plugin >
Thanks for checking into that Edison! >> >> However, I do believe that integration testing is something that community >> provides for community so integration testing itself should go on a single >> framework. >> >> --Alex >
