We use TestNG suits to run our automated tests. There are test steps that sould pass normally but sometimes they are expected to throw an exception. Consider the "Delete 2nd" test in the following suite.\[code\]...<test name="Delete 1st" preserve-order="true"> <classes> <class name="myBrick"> <methods> <include name="delete"> <parameter name="handle" value="http://stackoverflow.com/questions/15620931/42" /> </include> </methods> </class> </classes></test><test name="Delete 2nd" preserve-order="true"> <classes> <class name="myBrick"> <methods> <include name="delete"> <parameter name="handle" value="http://stackoverflow.com/questions/15620931/42" /> </include> </methods> </class> </classes></test>...\[/code\]The same test method should try to do the same for the second time -- but of course it is going to throw an exception this time. It would not be nice to write another version of \[code\]delete()\[/code\] test method just to specify a test annotation containing the \[code\]@ExpectedExceptions\[/code\] annotation... Is there any elegant way to control this test behavior from the testng.xml suite file?