setMockHttpResponse actually allows an array of mock file paths, useful if your gateway actually makes multiple requests as part of a single method as you can mock them all (i.e. the purchase method of coatesap/omnipay-realex makes a request to check 3dsecure enrolment then a further auth request if the customer isn't enrolled.
setMockHttpResponse actually allows an array of mock file paths, useful if your gateway actually makes multiple requests as part of a single method as you can mock them all (i.e. the purchase method of coatesap/omnipay-realex makes a request to check 3dsecure enrolment then a further auth request if the customer isn't enrolled.