-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove Pending Request Spec: Api Admin update payment state expectations. #4149
Conversation
This seems like a fine change as it reflects what the system currently does. Do you mind amending your commit message to follow our conventions? |
534ed40
to
56b97ac
Compare
Thanks, happy to... better? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep. Looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
For some reason, the spec suite is not starting here. I suspect it's because you created the solidus project in your own CircleCi workspace, which prevents the main CI to run, can you please check? |
@jcowhigjr oh interesting, maybe it was just a temporary CircleCI issue. Can you try to force-push that branch so that it should retrigger the build, thanks in advance! |
56b97ac
to
2448eda
Compare
Looks like it is working now. |
Edited your comment only to fix the image. |
Remove the pending/skipped spec that was previously throwing a stack level too deep error. Add a few more expectations to describe 422 payment.states to confirm the bug is gone.
2448eda
to
778524e
Compare
Removes Pending spec: payment.reload after the request raises 'stack level too deep'
Adds expectation for payment.reload.state.
These states could lead to discussion about what the correctness of these expectations.
Description
Motivation:
As newcomer to the codebase, a pending spec is typically a decent place to start.
I could not reproduce the behavior for the skipped expectation.
I was not sure of the expected states... so added them for discussion purposes.
Checklist: