@jasongorman I seriously dislike the terms unit and integration test. I wish I could come up with better terms for the handful of different test scenarios I regularly encounter. I think the existing terms are highly misleading

@jay_peper @jasongorman There are deterministic and non-deterministic tests, any other classifications are bound to be subjective.

@renewiersma I tend to differentiate tests by what kind of environment I feel I need to include (i.e. with SQL involved or a HTTP server/client)

@jay_peper Those would be non-deterministic tests.

@renewiersma they happen to be very deterministic (as in: succeeding 100% of the time)

@jay_peper Do they still pass when your internet connection is down?

@renewiersma of course

@jay_peper How does your code make a connection to a remote server or database when you have no internet connection?

@renewiersma there is no remote server. There are local servers (stood up by the tests or some test support)

@jay_peper I see. I still would call those tests non-deterministic, though. You have reduced the ways in which they could fail by hosting the remote instances locally, but in a production environment they might still fail, and the code calling those instances will still have to address the ways in which they could fail.

@renewiersma no. I'll add those fail scenarios as well. The tests are deterministic

@jay_peper Let's say you want to test a remote service timing out on a request, how would you set that up?