Refactor test structure

Tests are now in a 'test' sub-package, so it is clear that they are
indeed test code, not just disjoint parts of the main code

1 files changed, 0 insertions, 36 deletions

diff --git a/base/src/test/java/bjc/utils/data/BooleanToggleTest.java b/base/src/test/java/bjc/utils/data/BooleanToggleTest.java
deleted file mode 100644
index 66f44c0..0000000
--- a/base/src/test/java/bjc/utils/data/BooleanToggleTest.java
+++ /dev/null
@@ -1,36 +0,0 @@
-package bjc.utils.data;
-
-import static org.junit.Assert.assertEquals;
-
-import org.junit.Test;
-
-/**
- * Test for boolean toggles.
- * @author bjculkin
- *
- */
-public class BooleanToggleTest {
-
-	/**
-	 * Test that boolean toggles work right.
-	 */
-	@Test
-	public void test() {
-		BooleanToggle tog = new BooleanToggle();
-		
-		// Check initial value is false.
-		assertEquals(false, tog.peek());
-		// Check that 'get' returns the old value
-		assertEquals(false, tog.get());
-		// Check that 'get' swaps the value
-		assertEquals(true, tog.peek());
-		// Check that we can round-trip back.
-		assertEquals(true, tog.get());
-		assertEquals(false, tog.peek());
-		
-		tog.set(true);
-		
-		// Check set works
-		assertEquals(true, tog.peek());
-	}
-}