TestNG 5.13.1 is now available. The previous release was just three months ago, but as you can see below, a lot of fixes went into this new version. A big thanks to everyone who helped (hopefully credited below), and especially to Nalin Makar, who made some major contributions to TestNG these past months.
You can either download TestNG from the web site or from Maven:
org.testng testng 5.13.1 test
Here is the complete list of changes, please refer to the documentation for more details.
TestNG
- Added: -methods
- Added: -configfailurepolicy (Todd Quessenberry)
- Added: -methodselectors (Todd Quessenberry)
- Added: @NoInjection
- Added: <test preserve-order="true">
- Added: -testnames (command line) and testnames (ant)
- Added: New ant task tag: propertyset (Todd Wells)
- Added: ITestNGListenerFactory
- Added: Passing command line properties via the ant task and doc update (Todd Wells)
- Added: Hierarchical XmlSuites (Nalin Makar)
- Added: Reporter#clear()
- Fixed: NullPointerException when a suite produces no results (Cefn Hoile)
- Fixed: Identical configuration methods were not always invoked in the correct order in superclasses (Nalin Makar)
- Fixed: @DataProvider(parallel = true) was passing incorrect parameters with injection
- Fixed: Replaced @Test(sequential) with @Test(singleThreaded)
- Fixed: If inherited configuration methods had defined deps, they could be invoked in incorrect order (Nalin Makar)
- Fixed: Initialize all Suite/Test runners at beginning to catch configuration issues right at start (Nalin Makar)
- Fixed: Issue7: Issue86 Incorrect dates reported for configuration methods
- Fixed: Issue24: OOM errors in SuiteHTMLReporter (Nalin Makar)
- Fixed: Time outs specified in XML were not honored for <suite parallel=”tests”>
- Fixed: <suite> and <test> time outs were hardcoded, they now honor their time-out attribute
- Fixed: TestNG was hanging if no test methods were found
- Fixed: onTestSuccess() was called after @AfterMethod instead of after the test method (test: test.listener.ListenerTest)
- Fixed: XML test results contained skipfailedinvocationCounts instead of skipfailedinvocationcounts
- Fixed: Issue4 assertEquals for primitive arrays, Issue34 assertNull javadoc updated
- Fixed: Issue78 NPE with non-public class. Now throws TestNG exception
- Fixed: NPE with @Optional null parameters (Yves Dessertine)
- Fixed: TESTNG-387 TestNG not rerunning test method with the right data set from Data Provider (François Reynaud)
- Fixed: Show correct number of pass/failed numbers for tests using @DataProvider
- Fixed: Return correct method status and exception (if any) in InvokedMethodListener.afterInvocation()
- Fixed: Trivial fixes: TESTNG-241 (log message at Info), Issue2 (throw SAXException and not NPE for invalid testng xml)
- Fixed: Configuration methods couldn’t depend on an abstract method (Nalin Makar)
- Fixed: TestNG#setTestClasses was not resetting m_suites
- Fixed: Exceptions thrown by IInvokedMethodListeners were not caught (Nalin Makar)
- Fixed: @Listeners now works on base classes as well
- Fixed: Test priorities were not working properly in non-parallel mode
- Fixed: @Listeners wasn’t working properly with ITestListener
Eclipse
- Fixed: TESTNG-395 New wizard was creating classes called “NewTest”
- Fixed: TESTNG-397 Class level @Test was preventing groups from showing up in the launch configuration
Doc
- Updated Maven documentation (Brett Porter)
#1 by Christophe Vanfleteren on August 5, 2010 - 8:49 am
You’ve got a bad link to the downloads, I assume you mean http://testng.org/doc/download.html instead 🙂
Pingback: Pedro Newsletter 16.08.2010 « Pragmatic Programmer Issues – pietrowski.info
#2 by lei on August 25, 2010 - 9:38 pm
Hi ,I specified preserve-order=”true” in the tag, but it seems that TestNG does not run my classes in the same order I listed them.Why?Thanks in advance.
#3 by hlamik on September 24, 2010 - 12:30 am
The same for me – it looks that preserve-order=true doesn’t work at all. Sometimes when I have 2 classes – the second one also starts first. If I add one more class – it is OK. Adding one more class leads to run commands randomly.
Could someone help me? Thank you.
#4 by rina solomon on October 12, 2010 - 8:31 am
I run tests using ant, preserve-order=”true” doesn’t work for testng-5.14 as well. It’s very strange because when I run it in Eclipse the test flow saves its order as in testng.xml appears.
#5 by Miller on November 23, 2010 - 4:07 pm
I run testd with version 5.13.1 and not able to get preserve-order work as well. Did I miss something? Thanks,
#6 by aeren on February 10, 2011 - 2:49 am
I have the same problem with preserve-order. It doesn’t work. I have tried to run tests in many ways from eclipse, but it seems that testng don’t take into account preserve-order attribute at all.