Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BPoint: Hook up merchant_reference and CRN fields #3249

Conversation

curiousepic
Copy link
Contributor

These fields were already implemented in the request structure but did
not actually get anything passed to them from options.

Unit:
18 tests, 59 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Remote: No current test credentials, fairly confident the changes are
safe given that the fields are already present in requests, just without
a value.

These fields were already implemented in the request structure but did
not actually get anything passed to them from options.

Unit:
18 tests, 59 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Remote: No current test credentials, fairly confident the changes are
safe given that the fields are already present in requests, just without
a value.
@curiousepic curiousepic requested a review from a team June 19, 2019 18:39
Copy link
Member

@jknipp jknipp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀

@gateway.authorize(@amount, @credit_card, @options.merge({ crn1: 'ref' }))
end.check_request do |endpoint, data, headers|
assert_match(%r(<MerchantReference>1</MerchantReference>)m, data)
assert_match(%r(<CRN1>ref</CRN1>)m, data)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm assuming it was a deliberate decision to test a minimum number of fields here, as it's good enough testing.

whitby3001 pushed a commit to whitby3001/active_merchant that referenced this pull request Sep 3, 2019
These fields were already implemented in the request structure but did
not actually get anything passed to them from options.

Closes activemerchant#3249

Unit:
18 tests, 59 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Remote: No current test credentials, fairly confident the changes are
safe given that the fields are already present in requests, just without
a value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants