Update P3A rewards enabled question to measure ads

Description

Recently we added Brave.Rewards.EnabledDuration but there isn’t really a good definition of “Rewards Enabled”. We used to have a settings toggle for rewards overall, but it’s been removed and currently we look at a combination of ads and autocontribute opt-in settings.

@miyayes asked me to alter the measurement to just report how long ads were enabled. This is the more relevant question.

[Miyayes]

Thanks @rillian, I think we should rename the question just to avoid confusion (unless it introduces a lot of wrinkles).

[kjozwiak]

Verification PASSED on Samsung S10+ running Android 12 using the following build(s):

Brave | 1.38.106 Chromium: 101.0.4951.41 (Official Build) (32-bit)
--- | ---
Revision | 93c720db8323b3ec10d056025ab95c23a31997c9-refs/branch-heads/4951@{#904}
OS | Android 12; Build/SP1A.210812.016

Went through the STR/Cases outlined via https://github.com/brave/brave-core/pull/12371 & https://github.com/brave/brave-browser/issues/21030#issuecomment-1092057586.

Clean profile

Case 1: Ads was never ON_Brave.Rewards.AdsEnabledDuration=0_PASSED

• Verified that when rewards is NOT enabled, the metrics Brave.Rewards.AdsEnabledDuration response value is 0

Case 2: Ads is still ON_Brave.Rewards.AdsEnabledDuration=1_PASSED

• Verified that when rewards is enabled, the metrics Brave.Rewards.AdsEnabledDuration response value is 1

Case 3: Ads was enabled less than three hours in past_Brave.Rewards.AdsEnabledDuration=2_PASSED

Case 1_enable and disable Ads in a minute

• Clean profile 1.38x
• Enable rewards and disable Ads switch
• Open brave://local-state file
• Ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 2 as Ads is disabled within three hours

Case 2_disable Ads in < 3 hours

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system time ahead by 2 hours
• Relaunch the browser
• Disable the Ads switch
• Open brave://local-state file
• Ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 2 as Ads is disabled within three hours

Case 3_disable Ads exactly at 3 hours:

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system time ahead by exact 3 hours
• Relaunch the browser
• Disable the Ads switch
• Open brave://local-state file
• Ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 3 as Ads is disabled exact at 3 hours

Case 4_disable Ads after 3 hours:

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system time ahead by 3 hours 2 mins 0 secs
• Relaunch the browser
• Disable the Ads switch
• Open brave://local-state file
• Ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 3 as Ads is disabled after 3 hours

Case 4: Ads was enabled less than three days in past_Brave.Rewards.AdsEnabledDuration=3_PASSED

Case 1: disable ads in < 3days

1. Clean profile 1.38.x
2. Enable rewards and close the browser
3. Set the system date ahead by 1 or 2 days (<3days)
4. Relaunch the browser
5. Disable ads switch
6. Open brave://local-state
7. Brave.Rewards.AdsEnabledDuration response value is 3 as Ads is disabled within 3days

Case 2: disable ads exactly on the 3rd day

1. Clean profile 1.38.x
2. Enable rewards and close the browser
3. Set the system date ahead by 3days
4. Relaunch the browser
5. Disable Ads switch
6. Open brave://local-state
7. Ensured that the Brave.Rewards.AdsEnabledDuration response value is 4 as Ads is disabled on the 3rd day

Case 3: disable ads after 3days

1. Clean profile 1.38.x
2. Enable rewards and close the browser
3. Set the system date ahead by 3 days 2 mins 00 seconds
4. Relaunch the browser
5. Disable Ads switch
6. Open brave://local-state
7. Ensured that the Brave.Rewards.AdsEnabledDuration response value is 4 as Ads is disabled after 3days

Case 5: Ads was enabled less than three weeks in past_Brave.Rewards.AdsEnabledDuration=4_PASSED

Case 1: disable ads in < three weeks

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system time ahead by 3=>days & <=20days
• Relaunch browser
• Disable Ads switch
• Open brave://local-state file
• Ensured that the Brave.Rewards.AdsEnabledDuration response value is 4 as Ads is disabled within 3 weeks

Case 2: disable ads exactly on the 3rd week (21st day)

• Clean profile 1.38.x (Apr 11th)
• Enable rewards and close the browser
• Set the system time ahead by 21days (May 2nd)
• Relaunch browser
• Disable Ads switch
• Open brave://local-state file
• Ensured that the Brave.Rewards.AdsEnabledDuration response value is 5 as Ads is disabled on the 3rd week

Case 6: Ads was enabled less than three months in past_Brave.Rewards.AdsEnabledDuration=5_PASSED

Case 1: Passed

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system date 21=>days <=89
• Relaunch the browser
• Disable Ads switch
• Open brave://local-state file
• Ensured that the Brave.Rewards.AdsEnabledDuration response value is 5 as Ads is disabled within 3 months

Case 2: - Passed

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system date ahead by 90 days
• Relaunch the browser
• Disable Ads switch
• Open brave://local-state file
• Ensured that the Brave.Rewards.AdsEnabledDuration response value is 5 as expected (Discussed with @DJAndries: 30.44 days as a “month” (that’s the average length of a month) multiply that by three and we get 91.32, so 90 days would not trigger a value of 6)

Case 7: Ads was enabled more than three months in past_Brave.Rewards.AdsEnabledDuration=6_PASSED

• Clean profile 1.38.x
• Enable rewards and close the browser
• Set the system date ahead by 91 days (greater than 3 months)
• Relaunch the browser
• Disable Ads switch
• Open brave://local-state file
• Ensured that the Brave.Rewards.AdsEnabledDuration response value is 6

Case 8: Reset rewards_Brave.Rewards.AdsEnabledDuration=0_PASSED

• Clean profile 1.38.x
• Enable rewards
• Open brave://local-state file
• Ensured Brave.Rewards.AdsEnabledDuration response value is 1 as expected
• Reset the rewards via Manage Brave Rewards
• Reload the brave://local-state file and brave://rewards page
• Restart the browser
• Ensured that the Brave.Rewards.AdsEnabledDuration response value is 0 as expected

Upgrade profile

Case 1: Enable Rewards and upgrade the profile_PASSED

• Install 1.37.x beta build and enabled rewards and upgraded the profile to 1.38.x and ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 1 as expected
• Disable Ads switch in 1.38.x upgraded profile and ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 2 as expected

Case 2: Enable Rewards and disable Ad switch and then upgrade the profile_PASSED

• Install 1.37.x beta build and enabled rewards and disable Ads switch and upgraded the profile to 1.38.x and ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 0 as expected

Case 3: Enable Rewards and disable AC switch and then upgrade the profile_PASSED

• Install 1.37.x beta build and enabled rewards and disable rewards AC switch and upgraded the profile to 1.38.x and ensured that the metrics Brave.Rewards.AdsEnabledDuration response value is 1 as expected

Case 4: Enable Rewards and disable Ads and AC switches manually and then upgrade the profile_PASSED

- Install `1.37.x beta` build and enable rewards disable Ads and AC switches and upgraded the profile to `1.38.x` and ensured that the metrics `Brave.Rewards.AdsEnabledDuration` response value is `0` as expected

Case 5: Enable Rewards and reset rewards and then upgrade the profile_PASSED

- Install `1.37.x beta` build and enable rewards and reset rewards and upgraded the profile to `1.38.x` and ensured that the metrics `Brave.Rewards.AdsEnabledDuration` response value is `0` as expected