Le Fre wrote:which feature do you think testng do not encourage good unit test?
Actually the main advantage I see in testng as for now is to be able to prepare database settings in a super class in a non-static @beforeclass annotated method and still be able to hack this preparation in the subclass.
Jeanne Boyarsky wrote:TestNG shines in the complex tests with dependencies arena. A situation I don't want to find myself in.
Cedric Beust wrote:Besides, when you embark on picking a testing framework, it's very likely that you will be using it to do both unit *and* functional testing. For the latter, dependencies can be useful, especially if you're using Selenium or doing some web testing. Check out the Selenium forums to understand how people use TestNG's dependencies to simplify their tests.
Cedric Beust wrote:Just because this feature exists doesn't mean you have to use it.
Cedric Beust wrote:Besides, when you embark on picking a testing framework, it's very likely that you will be using it to do both unit *and* functional testing.
Cedric Beust wrote:As for your 3), it does sound like a hack to me. You created a workaround for the fact that JUnit doesn't support @BeforeSuite and @AfterSuite. It doesn't scream "great design" to me :-)
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton