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

"Ad notifications received" should show Ads viewed between the 1st of the month and the 4th of the following month #2132

Merged
merged 1 commit into from
Apr 2, 2019

Conversation

tmancey
Copy link
Collaborator

@tmancey tmancey commented Apr 1, 2019

fixes brave/brave-browser#3958

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security) on
    • Windows
    • macOS
    • Linux
  • Verified that all lint errors/warnings are resolved (npm run lint)
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.
  • Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

If the day of the month is less than 5 then "Ad notifications received" stats should include ads viewed between 1st of the previous month (at midnight) and the 4th of the current month (23:59:59). If the day of the month is 5 or higher then "Ad notifications received" stats should include ads viewed from the 1st of the month up until now.

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

emerick
emerick previously approved these changes Apr 1, 2019
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

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

LGTM, one really minor comment that could be nothing.


exploded.hour = 0;
exploded.minute = 0;
exploded.second = 0;
Copy link
Contributor

Choose a reason for hiding this comment

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

exploded.millisecond will probably have garbage in it if you don't explicitly zero it out, though not sure if it strictly matters here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

good catch will fix just incase a user redeems a token before 1 second passes as this redemption would not be shown in this edge case 👍

… the month and the 4th of the following month
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

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

LGTM

@bsclifton
Copy link
Member

@tmancey can we get some tests for this? Looks like that was missed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants