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

Implement logging for the security code component #492

Merged
merged 3 commits into from
Nov 2, 2023

Conversation

okhan-okbay-cko
Copy link
Contributor

@okhan-okbay-cko okhan-okbay-cko commented Nov 1, 2023

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.

For instance:

  1. Go to the main screen
  2. Tap on Security Code Component button
  3. Verify the relevant logs are being uploaded.

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.

  • Reviewers assigned
  • I have performed a self-review of my code and manual testing
  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if applicable)

Token requested success log is here

Token response success log is here

Server error log is here

@okhan-okbay-cko okhan-okbay-cko force-pushed the feature/cvv-component-tokenisation branch from 43fd866 to 3484a8f Compare November 2, 2023 13:01
Base automatically changed from feature/cvv-component-tokenisation to develop November 2, 2023 13:34
@okhan-okbay-cko okhan-okbay-cko dismissed deepesh-vasthimal-cko’s stale review November 2, 2023 13:34

The base branch was changed.

@okhan-okbay-cko okhan-okbay-cko force-pushed the feature/cvv-component-logging branch from e5ac3e0 to b10261c Compare November 2, 2023 13:59
Copy link

@chintan-soni-cko chintan-soni-cko left a comment

Choose a reason for hiding this comment

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

LGTM

@patrick-hoban-cko
Copy link
Contributor

Validated logs. LGTM

Copy link
Contributor

@deepesh-vasthimal-cko deepesh-vasthimal-cko left a 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.
Copy link

sonarqubecloud bot commented Nov 2, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@okhan-okbay-cko okhan-okbay-cko merged commit 2f9d5c6 into develop Nov 2, 2023
8 checks passed
@okhan-okbay-cko okhan-okbay-cko deleted the feature/cvv-component-logging branch November 2, 2023 17:05
okhan-okbay-cko added a commit that referenced this pull request Nov 3, 2023
* 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants