Post History

> I'm actually mainly interested in testing foo()

Ok, so let's do that.

> I could make it public, but I really don't want to do that just so that the test class can access it

Java has 4 different access modes: `private`, default access, `protected`, and `public`. The typical solution is to use default access, and put your unit test into the same package. This pattern is common enough that Guava provides `@VisibleForTesting` to document why access has been relaxed.

Alternatively, you could move the `foo` method to a different class, so it can be invoked independently without cluttering the API of the class that uses it. 

> How to unittest method that involves contacting remote servers? 

Generally, by moving the code contacting remote servers into its own method, and mocking that method in tests. To inject the mock, one usually uses dependency injection.