Delete unnecessary OpPriorityTest test

gselzer · ctrueden · commit 69a8f0516dd1 · 2019-09-22T16:54:43.000+02:00
This test was deleted for two reasons:
1) It is not future proof: it assumes that the Op within
MathOpCollection will always be the highest priority, which it might not
always be
2) Since the matcher now wraps up all returns into Ops (assuming there
  is a method to do so), the information that the test used to confirm
the origin of the Op can no longer be accessed.
diff --git a/src/test/java/org/scijava/ops/OpPriorityTest.java b/src/test/java/org/scijava/ops/OpPriorityTest.java
@@ -30,15 +30,12 @@
 package org.scijava.ops;
 import static org.junit.Assert.assertTrue;
 
-import java.util.function.BiFunction;
-
 import org.junit.Test;
 import org.scijava.core.Priority;
 import org.scijava.ops.core.Op;
 import org.scijava.ops.core.Source;
 import org.scijava.ops.types.Nil;
 import org.scijava.param.Parameter;
-import org.scijava.param.ValidityException;
 import org.scijava.plugin.Plugin;
 import org.scijava.struct.ItemIO;
 
@@ -62,23 +59,6 @@ public Number create() {
 		}
 	}
 	
-
-	Nil<Double> nilDouble = new Nil<Double>() {
-	};
-	
-	@Test
-	public void testOpCollection() throws ValidityException {
-		BiFunction<Double, Double, Double> divFunction = ops.findOp( //
-				"math.add", new Nil<BiFunction<Double, Double, Double>>() {
-				}, //
-				new Nil[] { nilDouble, nilDouble }, //
-				nilDouble//
-		);
-
-		// The found op is assumed to come from the MathOpCollection
-		assertTrue(divFunction.getClass().getName().contains("MathOpCollection$$Lambda"));
-	}
-	
 	@Test
 	public void testOpPriority() {
 
