@justinplouffe I always focus on the remote tests first; the basic rule is: no remote test should raise an exception, since any failure we can anticipate and trigger in a remote test should be encapsulated in a failed `Response`.

In the case of the unit tests like `test_failed_authorize`, I'd expect the same: it should mirror the remote test result of passing a badly formatted credit card number on to the gateway, which in turn should turn into a failed `Response`.

Basically exceptions should bubble up for any kind of case we can't anticipate in the remote tests.