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

PayJunctionv2: Fix billing address fields #3557

Closed
wants to merge 1 commit into from

Conversation

leila-alderman
Copy link
Contributor

@leila-alderman leila-alderman commented Feb 28, 2020

The billing address fields were recently added to the PayJunctionv2
gateway but were mapped to incorrect fields for the gateway.

This update corrects these fields to send the data in the correctly
named fields according to PayJunction's documentation.

In addition, new remote test assertions were added to ensure that the
gateway is correctly receiving and returning the billing address fields
in the response.

CE-437

Unit:
19 tests, 87 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions,
0 notifications
100% passed

Remote:
20 tests, 57 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions,
0 notifications
100% passed

All unit tests:
4464 tests, 71595 assertions, 0 failures, 0 errors, 0 pendings, 2
omissions, 0 notifications
100% passed

@leila-alderman leila-alderman requested a review from a team February 28, 2020 21:05
@leila-alderman leila-alderman force-pushed the CE-437_payjunction_billing_address branch from 1da3dee to 7e537a5 Compare February 28, 2020 21:17
Copy link
Contributor

@therufs therufs left a comment

Choose a reason for hiding this comment

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

Rubocop is slightly annoyed by an extra blank line, but otherwise LGTM 👍

@leila-alderman leila-alderman force-pushed the CE-437_payjunction_billing_address branch from 7e537a5 to f3f2fd2 Compare February 28, 2020 21:38
@leila-alderman
Copy link
Contributor Author

@therufs Thank you for the super speedy review! 🏆
I've appeased RuboCop now, although I believe it's too late on a Friday to get this change deployed out today, so I'll get this out first thing Monday.

The billing address fields were recently added to the PayJunctionv2
gateway but were mapped to incorrect fields for the gateway.

This update corrects these fields to send the data in the correctly
named fields according to [PayJunction's documentation](https://developer.payjunction.com/hc/en-us/articles/216477407-POST-transactions).

In addition, new remote test assertions were added to ensure that the
gateway is correctly receiving and returning the billing address fields
in the response.

CE-437

Unit:
19 tests, 87 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions,
0 notifications
100% passed

Remote:
20 tests, 63 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions,
0 notifications
100% passed

All unit tests:
4464 tests, 71595 assertions, 0 failures, 0 errors, 0 pendings, 2
omissions, 0 notifications
100% passed
@leila-alderman leila-alderman force-pushed the CE-437_payjunction_billing_address branch from f3f2fd2 to 65db5c4 Compare March 2, 2020 14:40
@leila-alderman leila-alderman deleted the CE-437_payjunction_billing_address branch March 2, 2020 14:41
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