Currently tests that exist in http-lib use functionality (such as security features) that rely on a running simulator to be active

'xcodebuild' by default runs the tests within the context of the simulator (aka as 'application tests') and always succeed. In contrast 'xctool' (used by travis) relies the tests to be explicitly set as 'application tests' for the emulator to startup.

To be correct, both in travis and since our tests are currently integration tests, we should convert our tests to application tests by explicitly adding an application target.

Details can be found on xctool issue tracker:
https://github.com/facebook/xctool/issues/454#issuecomment-65835905