Have a changeable default contribution amount for new installs (until user locks value)

[bsclifton]

Test plan

Should be ran via npm run watch / npm start since editing code is involved

Test Case 1

Make sure default is change-able

1. Fresh install of Brave / profile
2. Preferences > Payments, enable payments
3. Default contribution amount should be lowest amount available (currently 5.0 BAT)
4. Close Brave and open js/constants/appConfig.js
5. Change payments.defaultContributionAmount to 10
6. Re-launch Brave and see default amount updated to 10

Test Case 2

Make sure value doesn't change once it's set

1. Fresh install of Brave / profile
2. Preferences > Payments, enable payments
3. Default contribution amount should be lowest amount available (currently 5.0 BAT)
4. Change the monthly budget to another value (example: 17.5 BAT)
5. Close Brave and open js/constants/appConfig.js
6. Change payments.defaultContributionAmount to 10
7. Re-launch Brave and see contribution amount remain 17.5

Test Case 3

Make sure value doesn't change once funds are added

1. Fresh install of Brave / profile
2. Launch using LEDGER_ENVIRONMENT=staging (see here for more info on flags)
3. Preferences > Payments, enable payments
4. Default contribution amount should be lowest amount available (currently 5.0 BAT)
5. Use the Uphold Sandbox account and transfer BAT to the address shown in Brave
6. Once the funds show in Brave, exit the browser
7. Open js/constants/appConfig.js and change payments.defaultContributionAmount to 10
8. Re-launch Brave and see contribution amount remain 5.0

Description

For completely new installs, the default amount should be easily changeable. The value it has should come from a config and would be considered "floating" until the user takes an action to "lock it in"

• Manually choosing a value
• Funding wallet
• Accepting a grant (via user growth pool)

In those cases, the value that is set gets "locked in" and can only be changed by the user.

Existing installs are not affected by this change. They already have their values locked in.

[mrose17]

@bsclifton - i suggest that the default contribution be the smallest amount available, not hardwired to "5BAT"...

[bsclifton]

@mrose17 title updated

[srirambv]

All 3 test cases worked on Windows

[kjozwiak]

@LaurenWags and myself ran through these cases once again with 0.19.134 which included the following change:

• changing default from 5.0 BAT to 7.5 BAT