brave/qa-resources

Major Chromium bump specific checklist/items

Opened this issue · 3 comments

All items may not be applicable to both Desktop and Android, but we should add a section where we check specific items for major Chromium bumps (probably to full manual pass only).

Some ideas for this include:

  • context menus (various - text, links, URL bar, tab, etc)
  • settings comparison, especially:
    • check brave://settings/content -> make sure you click on Additional content settings and make sure there's nothing new in there (example: Auto-verify was added with C117)
    • check brave://settings/content -> make sure you click on Additional permissions and make sure there's nothing new in there
  • ref code check (per https://bravesoftware.slack.com/archives/C012NN4F6UU/p1695058849619809?thread_ts=1695056786.078529&cid=C012NN4F6UU) - not applicable for Linux
    • on desktop this means confirming promoCode file is created and listed in brave://local-state
    • on android, likely just confirming expected promoCode is listed on brave://local-state but need to confirm this

More to be added.

cc @kjozwiak as the above were his suggestions 👍🏻

Discussed on 11/27 with @kjozwiak.

Current thought is that this will not be part of the manual pass but either:

  • An addendum to the normal "Affected Areas" (provided by dev, these areas change with each major CR bump) that QA has to check each time
  • Or possibly a separate issue/checklist to be completed while the major CR bump is still being tested with Nightly prior to uplifting to the next channel

Looking to implement this with Chromium 121 testing in Jan 2024.

Another suggestion - manifest v2 check (#594).