Bug 564282 - API revision | question extensibility

- add single workable test among all the abstract ones to 'api.tests' bundle to make sure-fire go Signed-off-by: elena.parovyshnaya <[email protected]>
eclipse-passage · Jun 15, 2020 · 5f59c72 · 5f59c72
1 parent a520c7e
commit 5f59c72
Showing 1 changed file with 26 additions and 0 deletions.
diff --git a/...clipse.passage.seal.demo.tests/src/org/eclipse/passage/seal/demo/tests/TemporaryTest.java b/...clipse.passage.seal.demo.tests/src/org/eclipse/passage/seal/demo/tests/TemporaryTest.java
@@ -0,0 +1,26 @@
+package org.eclipse.passage.seal.demo.tests;
+
+import static org.junit.Assert.assertTrue;
+
+import org.junit.Test;
+
+public final class TemporaryTest {
+	/**
+	 * <p>
+	 * There only contract (meaning abstract) tests in this bundle. Nonetheless,
+	 * it's still recognized as 'tests' bundle. All the special treatments are
+	 * applied: sure-fire plug-in is applied. This one fails on a bundle where is
+	 * nothing to run.
+	 * </p>
+	 * 
+	 * <p>
+	 * Thus we add a single deadly stupid but workable test especially for sure-fire
+	 * to make it go.
+	 * </p>
+	 */
+	@Test
+	public void singleWorkableTestInABundleFullOfAbstractTest() {
+		assertTrue(System.currentTimeMillis() > 0);
+	}
+
+}