The issue I have with robolectric is that it doesn\'t make real HttpRequests.
Could I replace the HttpClient implementation of robolectric using a real one actually
Basically you don't. Robolectric is a test framework and this is how it designed to work, what you asked is not what we do with Robolectric.
I am sure you have came cross this blog taking about using Robolectric test HTTP requests. Actually the title "How to test HTTP requests" is not quite accurate IMO. I would rather call it "How to mock HTTP requests", as stated in this blog, the best place to use Robolectric mock http request is where you don't really want to bother real network calls to remote server maybe during Project development/testing phase.
Suppose I have a main activity connect to my bank account for some operation, the submit button should post my input info to remote server update my account info, then based on different responses bring me to several different activities. I have written all code smoothly, HttpClient, form with submit button, new intent to next activity, etc. all nice and clean. Right, how can I test when click submit button, the proper activity is opened based on those different response, without either need change my Activity source code or use real network call to screw my real bank account. The answer is Robolectric mock http request. The key point of using Robolectric in this case is not for testing real http request, instead, it is used for fooling my httpClient code and test other part of my application code like UI stuff. Ultimately, the real network test should be perform on emulator or a real device at some stage when your deployment come to a final stable state.
Another advantage claimed by Robolectirc team is you don't need start instrumentation test on emulator or device, which is inefficient and slow down application development/test life cycle.