There is a new way to mark tests as failing

And by "new" I mean 15 years old.

Part of eclipse-cdt#115

core/org.eclipse.cdt.ui.tests/ui/org/eclipse/cdt/ui/tests/refactoring/rename/RenameRegressionTests.java

@@ -17,15 +17,13 @@
 import java.io.StringWriter;
 
 import org.eclipse.cdt.core.dom.ast.IBinding;
-import org.eclipse.cdt.core.tests.FailingTester;
 import org.eclipse.core.resources.IFile;
 import org.eclipse.ltk.core.refactoring.Change;
 import org.eclipse.ltk.core.refactoring.RefactoringStatus;
 import org.eclipse.ltk.core.refactoring.participants.RenameArguments;
 
 import junit.framework.AssertionFailedError;
 import junit.framework.Test;
-import junit.framework.TestSuite;
 
 public class RenameRegressionTests extends RenameTestBase {
 	public RenameRegressionTests() {
@@ -37,20 +35,7 @@ public RenameRegressionTests(String name) {
 	}
 
 	public static Test suite() {
-		return suite(true);
-	}
-
-	public static Test suite(boolean cleanup) {
-		TestSuite innerSuite = new TestSuite(RenameRegressionTests.class);
-		innerSuite.addTest(new FailingTester(new RenameRegressionTests("_testMethod_35_72726"), 72726));
-
-		TestSuite suite = new TestSuite("RenameRegressionTests");
-		suite.addTest(innerSuite);
-
-		if (cleanup)
-			suite.addTest(new RenameRegressionTests("cleanupProject"));
-
-		return suite;
+		return suite(RenameRegressionTests.class, "_");
 	}
 
 	public void testSimpleRename() throws Exception {

core/org.eclipse.cdt.ui.tests/ui/org/eclipse/cdt/ui/tests/refactoring/rename/RenameTestBase.java

@@ -30,7 +30,7 @@
 /**
  * @author markus.schorn@windriver.com
  */
-public class RenameTestBase extends RefactoringTests {
+public abstract class RenameTestBase extends RefactoringTests {
 	private static final IProgressMonitor NPM = new NullProgressMonitor();
 
 	protected RenameTestBase(String name) {