Make integration tests work with any set of user credentials

[interfax]

Make integration tests work with any set of user credentials

[jdpearce]

That would be one way to do it, yes. Assuming there are faxes already existing. I can't recall if I left any Thread.Sleeps in the tests - these were my way of trying to create outbound faxes from scratch and work with those so we didn't have to rely on anything being present, but there are some methods (such as those on inbound faxes) which can't be tested that way and the delay between faxes being accepted/sent by the API and things like images being available wasn't known or discovered at the time.

[cbetta]

The more I think about it, the more I am not sure if these kind of tests make sense. Ideally the tests should only test if the SDK passes the right arguments to the API, and if it parses the API responses correctly when they return. The actual API call returning what is expected is out of scope.

Now obviously there's a few ways to solve this. In Ruby we'd use something like VCR to record responses for certain apI calls: https://github.com/vcr/vcr. This ensures that a) if the request changes the VCR will fail and warn the user that the request changed, and b) it ensures that the responses are parsed as if a real API call was made, without actually doing so.

But to be honest, we didn't do these kind of tests in any of the other SDK, so as it stands I am happy to scrap/mock them out.