Implemented Refund, Void, and Capture methods plus added testing #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
March 1, 2017 17:29
…for them. Still need to finish creating the tests.
…apture functionality and created tests for it as well.
…correct type code that beanstream uses. This commit also has an integration test class added for testing actual transactions with beanstream.
|
@aperdomo The output from travis-ci is a little vague. Could you shine some light on why the checks are failing for this PR? Thanks! |
|
So...I must have been blind when I looked at the output from the CI before. I guess I was just looking at the red text at the bottom. :) |
2 similar comments
aperdomo
approved these changes
Mar 7, 2017
|
@aperdomo |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This request contains implementations of the Refund, Void, and Capture requests. I also added testing for those requests as well as an integration test class for testing the functionality while it is actually interacting with Beanstream.