Stack traces can be interactively shown in the HTML reports
Link to testng.xml in the reports
Ant task: support for JVM, workingDir, timeout
New structure for reports, suites go in their individual directory
@Test(suiteName) and @Test(testName)
The stack traces in reports do not include TestNG frames (system property testng.exception) see: http://groups.google.com/group/testng-dev/browse_thread/thread/9f4d46ade10b0fda)
Exit with error when no methods are run (see: http://groups.google.com/group/testng-dev/browse_thread/thread/3c26e8a5658f22ac)
List of methods in alphabetical order
Class-scoped annotations were not recognized when inherited
Deprecated @Configuration and introduced @BeforeSuite/Test/Class/TestMethod
Deprecated @ExpectedExceptions and moved it into @Test
expectedExceptions to @Test, deprecated @ExpectedExceptions
New annotations: @BeforeSuite, @BeforeTest, etc...
Was returning an exit code of 0 if a cyclic graph was detected
Interface org.testng.ITest so that tests can declare a name
Fixed: The Text reporter was reporting the square of the actual number of methods
Bug reported by Eran about dependencies with an afterClass method
IHookCallBack now receives the ITestResult in its run() method
Name of suite for command line can be set with -Dtestng.suite.name=xxx
TestNGAntTask was hardcoding m_haltOnFSP to true
Passing a null parameter caused an NPE in the reports
"listener" to the ant task (and documentation)
if patch-testng-sourcedir.properties is found in the classpath with a property "sourcedir" containing a ; separated list of directories, this list will override -sourcedir.
↑返回目录
前一篇:
OpenJPA 已经可以通过 Apache Incubator 下载
后一篇:
Compass 1.0 发布