Create a search configuration and make the test pass

We can now create a searchable configuration and use the controller inside the activity to make the test pass.
All Android related boilerplate is confined inside the activity while the controller encapsulates the logic behind it.
We can remove boilerplate duplication (savedInstanceState, findViewById, Intent navigation) using annotations or injecting helpers, depending on our need.
We can start using these tools when our domain is more defined.
Add test fixtures to the real Github service

Our integration tests are green, but we are running those tests against a mock server.
In order to test that our predictions are correct and that the apis are stable, we can exercise our code against the live service.
This step can be taken in parallel with the development of the rest of the application code.
Since we are exploring another boundary, the api service, we wrap the implementation details with our own interface, the GithubApi.
We pick Retrofit as a REST framework for its ability to run both on Android and on JVM.
Rewrite Service injection using multiple levels

This small refactoring allow us to easily swap one service for another, while keeping our IT run in mock mode.
Add Travis configuration