-
Notifications
You must be signed in to change notification settings - Fork 49
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
Implement logging for the security code component #492
Conversation
43fd866
to
3484a8f
Compare
The base branch was changed.
e5ac3e0
to
b10261c
Compare
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.
LGTM
Validated logs. LGTM |
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.
logs looks good. Nice work
These two assertions have never been true when called independently. They were being asserted as true because the SturLogManager's static queue array was being populated by CardValidatorTests and was never being flushed. So, whenever the CheckoutTests are run altogether, tests were passing, but, whenever they are called separately, they were failing.
c8d8b62
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
* Implement logging for the security code component * Fix logging issue * Fix unit tests These two assertions have never been true when called independently. They were being asserted as true because the StubLogManager's static queue array was being populated by CardValidatorTests and was never being flushed. So, whenever the CheckoutTests are run altogether, tests were passing, but, whenever they are called separately, they were failing.
Issue
JIRA-2169
Proposed changes
Log the token requested and response events for the newly introduced security code component
Test Steps
If there's any functionality change, please list a step by step guide of how to verify the changes, and/or upload a screen recording for any visible changes.
Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Token requested success log is here
Token response success log is here
Server error log is here