Originally posted by Pradip Bhat:
Like you said if there are 1000 records and 850th record cause the test to fail does, TestNg print the offending record or just would say that test fail ? Thanks
Originally posted by Pradip Bhat:
If we are doing TTD wouldn't there be many broken tests because the features are still not implemented.
Originally posted by Prad Bhat:
How do I use TestNg for integration testing ? Is there any guideline on this ?
Originally posted by Pradip Bhat:
With reference to this interview of C�dric Beust
http://www.artima.com/lejava/articles/testng.html
I have question regarding dataProvider on whether we really need it ?
How is writing
different from
Originally posted by Jeanne Boyarsky:
Not yet. I understand that explanation for @BeforeClass - if the classwide setup fails, it doesn't make sense to do anything in that class.
@BeforeMethod is just for one test method though, right? So why would one method's setup pertain to the entire class? For that matter, why is it invoked "before all the methods of the class"? It's method specific.
Suppose I have the following test method in JUnit:
Converting it to TestNG, I would have:
In the JUnit example, I expect all other tests in the class to run because the setup that failed was inside a particular test. Why would the TestNG example work differently? If I had something that affected the whole class, it would go in @BeforeClass, no?
Originally posted by Swosti Dipan Pal:
How the new generation testing id different from the current approach of Junit and Load/Regression testing ?
What are the advantages of using these approaches ?
Who are the audiences for these testing ?
Originally posted by Jeanne Boyarsky:
My last question of the week:
On page 112 of "Next Generation Java Testing - TestNG and Advanced Concepts", it says that if @BeforeMethod fails, all test methods in the test class are skipped. Why does TestNG skip all the methods rather than just the one method the @BeforeMethod goes with?
Originally posted by Jeanne Boyarsky:
I'm curious what the authors (or anyone else with experience in TestNG) consider to be the most important few features in TestNG that is not in JUnit 4.0. Most articles, just hash through the differences between TestNG and JUnit 3.8.
From reading the book, the concurrency testing support seems useful if you are working on a threaded application.
If test groups are your answer, what do you consider the second most important feature that is not in JUnit 4.0? (because groups have been well discussed this week)