Re: Payment_Process2
| From: | Daniel O'Connor | Date: | Tue, 24 Feb 2009 07:02:13 +0000 |
| Subject: | Re: Payment_Process2 | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-51555@lists.php.net to get a copy of this message | ||
I've just chucked in the work to date into CVS (Payment_Process2) and put in
a quick request for a shiny new package - Christian has set that all up
(cheers!)
Phillippe, I take it you'd like to be a lead on this package too?
Everyone else:
I've now got it to the point where I can write unit test coverage of the
drivers themselves. That unfortunately means ripping out Net_Curl and
HTTP_Request *first* then writing the unit tests with mocked out data.
Since it will take me a long long while to get each and every driver fully
mocked out, if any of use are able to send sanitized production data of
successes, failures, and other responses for any drivers you are using in
production; that would be awesome and time saving.
You can see an example with
http://cvs.php.net/viewvc.cgi/pear/Payment_Process2/tests/data/
- just plain
old HTML is fine for most drivers.
Next items on my list of TODOs:
- Rip out CURL for HTTP_Request2 in all drivers
- Mock out all drivers
- Unit test coverage - all result classes
- Refactoring - get all result classes to define an interface
- Documentation: How to migrate
- Implement ANZ driver (and get it cleared)