When I remove the setContext() from a test, for example test_code_callbacks(),
```
	public void test_code_callbacks() {
		Router router = new Router();

		router.map("callback", new Router.RouterCallback() {
			@Override
			public void run(Map<String, String> params) {
				RouterTest.this._called = true;
			}
		});

		router.open("callback");

		Assert.assertTrue(this._called);
	}

```

I see the following stacktrace when I run the test - it shows up for almost all unit tests when I don't have the setContext() there.
```
com.usepropeller.routable.Router$ContextNotProvided: You need to supply a context for Router com.usepropeller.routable.Router@40cfaee0
at com.usepropeller.routable.Router.open(Router.java:255)
at com.usepropeller.routable.Router.open(Router.java:244)
at com.usepropeller.routable.Router.open(Router.java:226)
at com.usepropeller.routable.android.tests.RouterTest.test_code_callbacks(RouterTest.java:93)
at java.lang.reflect.Method.invokeNative(Native Method)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:190)
at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:175)
at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:555)
at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1661)
```

BTW since this test doesn't explicitly invoke any activities, this can probably exist as a regular (non-AndroidTestCase) JUnit test in the library project itself, which would let you inject mock objects and such. Of course, it's stilla  good idea to have on-device unit tests, especially for testing the propagation of intents into an activity and making sure the activity spins up fragments, etc. I'll prototype this separation in a branch and let you know how it goes