Test harness

[kenwest]

I'm getting bored testing this extension (wonderful as it is). Here are some thoughts on testing ...

• A PHP program to invoke the payment processor for
  • one-off contributions
  • recurring contributions
  • running the batch job
  • simulating 'advance the date' with some SQL that: finds the recurring contributions generated by the test; ad sets their 'next payment date' to 'today'
  • assuming emails are being directed to a mail.log file, reading that file and grepping for meaningful strings like amount, etc.

Thoughts?

[eileenmcnaughton]

It's possible to add unit tests using Civix - I did it a while back on a different module but there was some teething.

When I've been testing on sites I've been hacking a short-circuit into some functions so they don't actually contact eway- I was thinking about having a setting to put the site into 'eway offline test mode' so that all payments do this - & probably a hook kicks in defaulting the credit card details to save entering them

[kenwest]

Eileen, when I test I take a copy of my production system and then set the eWAY payment processor so the live-payment settings are the same as the test-payment settings. I then run the eWAY job manually to process any payments from production (they fail because they don't use the test token value),

There's a risk I might one day inadvertently process live transactions, but I'm also testing the payment processor all the way.

[eileenmcnaughton]

hmm - I'm not quite sure what you are saying - are you advocating this approach or telling me the short-comings of it?

The patch in the PR allows you to set the whole site into dev mode - which allows testing of ;everything but the interaction with eway - which is one part of the testing required when working with this (but obviously only one part)

[kenwest]

Eileen, I'm not sure what I'm saying either ;-) It happens with age.

[eileenmcnaughton]

or too many hours in front of a screen