Talk:TestNG

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Java Low‑importance

	This article is within the scope of WikiProject Java, a collaborative effort to improve the coverage of Java on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.JavaWikipedia:WikiProject JavaTemplate:WikiProject JavaJava articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

This reads like an ad for TestNG and not an unbiased encyclopedia style article. 146.115.38.3 (talk) 18:33, 11 September 2013 (UTC)[reply]

TestNG is not only for unit testing. It's generic enough as to permit other type of tests (like functional tests). — Preceding unsigned comment added by 50.161.102.33 (talk) 21:21, 25 January 2014 (UTC)[reply]

I agree with 146.115.38.3 on the tone of this article. At the moment, I'm wondering in particular about these sentences:

"In JUnit 4, the @BeforeClass and @AfterClass methods have to be declared as static. TestNG does not have this constraint."

Note that @BeforeClass/@AfterClass are the JUnit 4 equivalents of the JUnit 5 @BeforeAll/@AfterAll. I plan to edit this article to bring up more up to the times with JUnit 5. This does seem to be a constraint, strictly speaking, of JUnit. However, it doesn't make much logical sense to have non-static @BeforeAll/@AfterAll methods. I've never had a practical case where this would be any consideration. Thoughts on this? A248 (talk) 00:56, 6 February 2021 (UTC)[reply]