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

Cybersource: add processor response message #4293

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dsmcclain
Copy link
Contributor

Cybersource: adds constant for mapping processorResponse to processor error codes.

Note: there is no remote test coverage for the processor response mapping because Cybersource sandbox does not return processorResponse error codes (not that I can find, at least).

Second Note: submitted as a draft PR awaiting further information from Cybersource on whether these processor response messages can be trusted. Do not merge until further notice.

CE-2271

Unit:
5046 tests, 74997 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Rubocop:
728 files inspected, no offenses detected

Remote:
101 tests, 512 assertions, 7 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
93.0693% passed

The following tests are failing on master for reasons unrelated to this change:

test_successful_validate_pinless_debit_card
test_successful_tax_calculation
test_successful_pinless_debit_card_purchase
test_successful_authorization_and_failed_capture
 test_successful_asynchronous_adjust
test_successful_3ds_validate_purchase_request
test_successful_3ds_validate_authorize_request

Cybersource: adds constant for mapping `processorResponse` to processor error codes.

CE-2271

Unit:
5046 tests, 74997 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Rubocop:
728 files inspected, no offenses detected

Remote:
101 tests, 512 assertions, 7 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
93.0693% passed
@curiousepic
Copy link
Contributor

Marking this "of interest" before a cleanup of stale PRs

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.

None yet

2 participants