Comments on: TestNG 5.6 and Junit 4.4 : which framework you will choose for unit testing? http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/ The future belongs to those who believe in the beauty of their dreams. Fri, 04 Jul 2008 16:41:42 +0000 http://wordpress.org/?v=MU By: Links for 7th March http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10924 Links for 7th March Fri, 07 Mar 2008 23:39:43 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10924 [...] Which Unit Test Framework will you use - here [...] [...] Which Unit Test Framework will you use - here [...]

]]> By: openBlog » TestNG and JUnit http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10912 openBlog » TestNG and JUnit Wed, 05 Mar 2008 05:07:14 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10912 [...] and JUnit are 2 of the most popular testing frameworks in the market at the moment. I found this article comparing both frameworks interesting and would like to share with all of you. On top of that, I would like to mention a nice [...] [...] and JUnit are 2 of the most popular testing frameworks in the market at the moment. I found this article comparing both frameworks interesting and would like to share with all of you. On top of that, I would like to mention a nice [...]

]]> By: Lijin http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10903 Lijin Tue, 04 Mar 2008 04:25:39 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10903 @Eric @Hayato Thanks for the info friends @Eric @Hayato
Thanks for the info friends

]]> By: Lijin http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10902 Lijin Tue, 04 Mar 2008 04:25:04 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10902 @Alex Thank you very much Alex for giving your Precious Time for us. @Alex
Thank you very much Alex for giving your Precious Time for us.

]]> By: Hayato Ijuin http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10899 Hayato Ijuin Tue, 04 Mar 2008 01:28:39 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10899 Eclipse allows to run failed tests only or last test only for JUnit. I don't know if it's a Eclipse's peculiarity or a JUnit feature, though. Eclipse allows to run failed tests only or last test only for JUnit. I don’t know if it’s a Eclipse’s peculiarity or a JUnit feature, though.

]]> By: Alex the_mindstorm Popescu http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10898 Alex the_mindstorm Popescu Mon, 03 Mar 2008 21:37:45 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10898 Just a couple of things: 1/ @ExpectedExceptions is deprecated for a long time. Instead you should be using @Test(expectedExceptions= { /* class list */ }) 2/ TestNG has introduced the notion of skipped tests. These are neither failures, nor passed, but rather tests that were supposed to run but due to some "dependency" error (being a configuration failure or a test dependency failure) they were not run. This will lead to cleaner reports. 3/ You can use Hamcrest support for literate assertions. JUnit support is limited in this direction too, so finally you'll have to use Hamcrest. bests, ./alex -- .w( the_mindstorm )p. TestNG co-founder EclipseTestNG Creator Just a couple of things:

1/ @ExpectedExceptions is deprecated for a long time. Instead you should be using @Test(expectedExceptions= { /* class list */ })

2/ TestNG has introduced the notion of skipped tests. These are neither failures, nor passed, but rather tests that were supposed to run but due to some “dependency” error (being a configuration failure or a test dependency failure) they were not run. This will lead to cleaner reports.

3/ You can use Hamcrest support for literate assertions. JUnit support is limited in this direction too, so finally you’ll have to use Hamcrest.

bests,

./alex
–
.w( the_mindstorm )p.
TestNG co-founder
EclipseTestNG Creator

]]> By: Eric Jablow http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10897 Eric Jablow Mon, 03 Mar 2008 15:11:08 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10897 I've seen but never used Log4Unit, hosted at http://www.openfuture.de/Log4Unit/. I’ve seen but never used Log4Unit, hosted at http://www.openfuture.de/Log4Unit/.

]]> By: Lijin http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10893 Lijin Mon, 03 Mar 2008 05:16:24 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10893 Thanks Cedric. Thanks for the Info. Thanks Cedric. Thanks for the Info.

]]> By: Cedric http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10876 Cedric Fri, 29 Feb 2008 20:43:25 +0000 http://lijinjoseji.wordpress.com/2008/02/29/testng-56-and-junit-44-which-framework-you-will-choose-for-unit-testing/#comment-10876 FYI, Ignore is supported in TestNG with @Test(enabled=false). And also by excluding groups that your method belongs to. FYI, Ignore is supported in TestNG with @Test(enabled=false). And also by excluding groups that your method belongs to.

]]>