Hello everyone,
On behalf of the TestNG Dev team,I am pleased to announce the availability of TestNG 7.8.0 org.testng:testng:7.8.0
TestNG 7.8.0 is now available in Maven Central.
Contributors who helped make TestNG become better in this release:
- Bruce Wen
- Dmytro Budym
- Joaquin Moreira
- Sergei Baranov
- Oliver Hughes
- Bob Shi
Special thanks go to:
- Julien Herr for helping out with all the code reviews
- To all the other contributors who made this release possible.
In this release, we spent time squashing some bugs (Please see below for a full list of issues that were fixed)
- Fixed: GITHUB-2906: Generate testng-results.xml per test suite
- New: GITHUB-2897: Not exception but warning if some (not all) of the given test names are not found in suite files.
- New: GITHUB-2907: Added assertListContains and assertListContainsObject methods to check if specific object present in List
- Fixed: GITHUB-2888: Skipped Tests with DataProvider appear as failed
- Fixed: GITHUB-2884: Discrepancies with DataProvider and Retry of failed tests
- Fixed: GITHUB-2879: Test listeners specified in parent testng.xml file are not included in testng-failed.xml file
- Fixed: GITHUB-2866: TestNG.xml doesn’t honour Parallel value of a clone
- Fixed: GITHUB-2875: JUnitReportReporter should capture the test case output at the test case level
- Fixed: GITHUB-2771: After upgrading to TestNG 7.5.0, setting ITestResult.status to FAILURE doesn’t fail the test anymore
- New: GITHUB-2862: Allow test classes to define “configfailurepolicy” at a per class level
- Fixed: GITHUB-2796: Option for onAfterClass to run after @AfterClass
- Fixed: GITHUB-2857: XmlTest index is not set for test suites invoked with YAML
- Fixed: GITHUB-2880: Before configuration and before invocation set ‘SKIP’ when beforeMethod is ‘skip’
- Fixed: GITHUB-2886: testng-results xml reports config skips from base classes as ignored