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

Upgrade from C132 -> C133 on Android ARM x64 via 1.76.x - Nightly (Checking C133) #43476

Closed
22 of 25 tasks
LaurenWags opened this issue Jan 24, 2025 · 1 comment
Closed
22 of 25 tasks
Assignees
Labels
ARM Android ARM related issues OS/Android Fixes related to Android browser functionality QA Pass - Android ARM QA/Yes release-notes/exclude tests

Comments

@LaurenWags
Copy link
Member

LaurenWags commented Jan 24, 2025

As per process, QA runs through the following cases to ensure that the major chromium bump that's about to get merged into master doesn't regress the Nightly channel. Once the major chromium bump is merged into master, QA will run through a full manual pass on Windows & Android.

Startup & Components

  • Verify that Brave is only contacting *.brave.com endpoints on first launch using either Charles Proxy, Fiddler, Wireshark or LittleSnitch (or a similar application)
    • Verify that opening a NTP doesn't trigger any outbound connections related to widgets without user interaction
  • Restart the browser, load brave://components, wait for 8 mins and verify that no component shows any errors

Note: Always double check brave://components to make sure there's no errors/missing version numbers. We basically want to make sure that components are working as they regressed in C98 when we first merged into master.

Upgrade

  • Make sure that data from the last version appears in the new version OK
  • Ensure that brave://version lists the expected Brave & Chromium versions
  • With data from the last version, verify that:
    • Bookmarks on the bookmark toolbar and bookmark folders can be opened
    • Cookies are preserved
    • Installed extensions are retained and work correctly
    • Opened tabs can be reloaded
    • Stored passwords are preserved
    • Sync chain created in previous version is retained
    • Social media-blocking buttons changes are retained
    • Rewards
      • Wallet balance is retained
      • Auto-contribute list is retained
      • Both Tips and Monthly Contributions are retained
      • Wallet panel transactions list is retained
      • Changes to rewards settings are retained
      • Ensure that Auto Contribute is not being enabled when upgrading to a new version if AC was disabled
    • Ads
      • Both Estimated pending rewards & Ad notifications received this month are retained
      • Changes to ads settings are retained
      • Ensure that ads are not being enabled when upgrading to a new version if they were disabled
      • Ensure that ads are not disabled when upgrading to a new version if they were enabled
@LaurenWags LaurenWags added ARM Android ARM related issues OS/Android Fixes related to Android browser functionality QA/Yes release-notes/exclude tests labels Jan 24, 2025
@LaurenWags LaurenWags added this to the 1.76.x - Nightly milestone Jan 24, 2025
@Uni-verse Uni-verse self-assigned this Jan 24, 2025
@Uni-verse
Copy link
Contributor

Uni-verse commented Jan 24, 2025

Verified on Android ARM using version:

Brave	1.76.34 Chromium: 133.0.6943.27 (Official Build) canary (64-bit) 
Revision	225d5f135d10df8b1b0c53b22934da5aae14cf28
OS	Android 14; Build/UP1A.231005.007; 34; REL

@Uni-verse Uni-verse added the QA/In-Progress Indicates that QA is currently in progress for that particular issue label Jan 24, 2025
@Uni-verse Uni-verse added QA Pass - Android ARM and removed QA/In-Progress Indicates that QA is currently in progress for that particular issue labels Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARM Android ARM related issues OS/Android Fixes related to Android browser functionality QA Pass - Android ARM QA/Yes release-notes/exclude tests
Projects
None yet
Development

No branches or pull requests

2 participants