You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GeetaSarvadnya
changed the title
Incorrect response value when vpn usage days (30 days) distributed withing two months
Incorrect response value when vpn usage days (30 days) distributed within two months
Sep 5, 2022
GeetaSarvadnya
changed the title
Incorrect response value when vpn usage days (30 days) distributed within two months
Incorrect response value when Brave VPN usage days (30 days) distributed within two months
Sep 5, 2022
The VPN subscription is valid for one month and when I set the date beyond one month, the vpn gets disconnected (show up the paymnet subscription expiry messge) hence the VPN usage is not accounted from the date when it gets disconnected. If I move the dates ahead then VPN usage counts gets decreased as expected.
Issue is working as expected. Hence closing the issue
Description
Found while testing #23892
Incorrect response value when vpn usage days (30 days) distributed within two months
Steps to Reproduce
As Brave VPN user, how many different days did I enable the Brave VPN in the last 30 days?
Brave.VPN.DaysInMonthUsed
Brave.VPN.DaysInMonthUsed
response value is1
as expectedBrave.VPN.DaysInMonthUsed
response value is2
as expectedBrave.VPN.DaysInMonthUsed
response value is3
as expectedBrave.VPN.DaysInMonthUsed
response value is3
as expectedBrave.VPN.DaysInMonthUsed
response value is3
as expected3
for all the dates in step 13Actual result:
Incorrect response value when vpn usage days (30 days) distributed within two months
Expected result:
The reponse value should be calculated for Brave VPN usage for the last 30 days only irrespective of month overlap
Reproduces how often:
Easy
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
cc: @DJAndries @mattmcalister @brave/qa-team
The text was updated successfully, but these errors were encountered: