Cybersource: add processor response message #4293
Draft
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.
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: