-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 Chromium 115 to Chromium 116. #30747
Comments
Verification PASSED on
Changing shield settings works correctly_PASSEDClean profileRestart browser and verify updated shield settings retainedCase 1: Browser restart retain the updated site specific shield settings_PASSEDTrackers & ads blocking Case 1:
Case 2:
Case 3:
Block fingerprinting Case 1:
Case 2:
Case 3:
Block cookies Case 1:
Case 2:
Case 3:
Case 2: Browser restart retain the updated global shield settings_PASSEDTrackers & ads blocking Case 1:
Case 2:
Case 3:
Fingerprint blocking Case 1:
Case 2:
Case 3:
Cookies blocking Case 1:
Case 2:
Case 3:
Site shield settings in Private windowCase 1: Per site shiled settings are propagated to private windows_PASSED
Case 2: Updated global shiled settings are propagated to Private windows_PASSED
Case 3: Verify that updated per site shield settings in Private window are NOT propagated to Normal window_PASSED
Verify disable per site shield settings propagated to all the tabsCase 1: Disable local shield settings for a site A_PASSED
Case 2: Disable global shield settings for a site A_PASSED
Case 3: Turn OFF the per site shield switch_PASSED
Verify disable per site shield settings propagated to all the windowsCase 1: Disable local shield settings for a site A in window 1_PASSED
Case 2: Disable global shield settings for a site A_ in windows 1_PASSED
Case 3: Turn OFF the per site shield switch_PASSED
Verify change per site shield settings propagated to all the tabsCase 1: Change local shield settings for a site A_PASSED
Case 2: Changed global shield settings for a site A_PASSED
Verify change per site shield settings propagated to all the windowsCase 1: Change local shield settings for a site A_PASSED
Case 2: Changed global shield settings for a site A_PASSED
Upgrade profileCase 1: Install 1.56.x CR 115 and upgrade it to 1.58.x CR 116 - PASSEDCase 1.1: Default shield settings upgrade - PASSED
Case 1.2: Update the default shield settings and then upgrade - PASSED
Case 1.3: Update the global default shield settings and then upgrade - PASSED
Case 1.4: Turn OFF the shield for a few sites and then upgrade - PASSED
Case 1.5: Block scripts and then upgrade - PASSED
Case 1.6: Block HTTPS upgrade and then upgrade - PASSED
All items a present and work as expected in the ☰ menu_PASSEDSigning into Google sites works_PASSED
Brave Side Panel looks/works correctly_PASSED
Clear browsing data for time span works_PASSEDBasic_Last hour_PASSEDCase 1:
Before:
After:
Case 2:
Advanced_All time_PASSEDCase 1: All time
Advanced_Last 7 days_PASSED
Advanced_Last 4 weeks_PASSED
On exit_PASSED
Before:
After:
Omnibox suggestions are shown when enabled_PASSED
Settings comparison
Components updater Translate page works -
Brave startup calls
- Confirmed that only brave domains are listed in the Charles when the nightly build is launched with a clean profile
- Confirmed no calls to google, gstatic, etc domains when the nightly build is launched with a clean profile
|
Verified on
Bottom toolbar
Downloads
Sync
Top toolbar
|
The above requires |
Tests below verified with 1.57.42, remaining testing to be completed via #32168 (comment) with updated version.
Changing shield settings works correctly - PASSEDClean profileRestart browser and verify updated shield settings retainedCase 1: Browser restart retain the updated site specific shield settings - PASSEDTrackers & ads blocking Case 1:
Case 2:
Case 3:
Block fingerprinting Case 1:
Case 2:
Case 3:
Block cookies Case 1:
Case 2:
Case 3:
Case 2: Browser restart retain the updated global shield settings - PASSEDTrackers & ads blocking Case 1:
Case 2:
Case 3:
Fingerprint blocking Case 1:
Case 2:
Case 3:
Cookies blocking Case 1:
Case 2:
Case 3:
Site shield settings in Private windowCase 3: Verify that updated per site shield settings in Private window are NOT propagated to Normal window - PASSED
Upgrade profileCase 1: Install 1.56.x CR 115 and upgrade it to 1.57.x CR 116 - PASSEDCase 1.1: Default shield settings upgrade - PASSED
Case 1.2: Update the default shield settings and then upgrade - PASSED
Case 1.3: Update the global default shield settings and then upgrade - PASSED
Case 1.4: Turn OFF the shield for a few sites and then upgrade - PASSED
Case 1.5: Block scripts and then upgrade - PASSED
Case 1.6: Block HTTPS upgrade and then upgrade - PASSED
All items a present and work as expected in the ☰ menu - PASSED
Translate page - PASSED
Signing into Google sites works - PASSEDCase 1 - PASSED
Case 2 - PASSED
Linux specific password checks - PASSEDFollowed tests from https://gist.github.com/fmarier/224729615bd5e887b9ac29236288f7a1. Case 1 - Saving a password directly - PASSEDReference https://gist.github.com/fmarier/224729615bd5e887b9ac29236288f7a1#saving-a-password-in-a-new-profile.
Now, pick a website for which you'll save the password in Brave. I used https://www.libravatar.org/. Now let's save the password in a new profile of Brave Release pre-req: install
Case 2 - Looking at the password database directly - PASSEDContinuing from case 1, confirm that the password was saved in an encrypted way:
![]()
Per https://gist.github.com/fmarier/224729615bd5e887b9ac29236288f7a1#looking-at-the-password-database-directly, since we see that "v11", it means that Brave was able to connect to gnome-keyring using gnome-libsecret since that's the only secure storage wallet available by default in Ubuntu. Note - I "redacted" username and the unnecessary part of the password_value. Case 3 - Opening an old password database using a new version of Brave - PASSED
![]()
![]()
If you can see the password in 1.57.x, that means that 1.57.x, using gnome-libsecret, can continue to read passwords that were saved in gnome-keyring (using the old library in Release 1.56.x with Chromium 115). |
Verification
|
brave://settings/shields |
sfgate.com , defaults |
---|---|
![]() |
![]() |
Disabled
brave://settings/shields |
sfgate.com , Allow all trackers & ads |
---|---|
![]() |
![]() |
Block scripts - PASSED
Default (Off/Disabled)
brave://settings/shields |
blizzard.com , defaults |
---|---|
![]() |
![]() |
Block scripts
, ON
brave://settings/shields |
blizzard.com , Scripted blocked |
---|---|
![]() |
![]() |
Block fingerprinting - PASSED
Block cookies - PASSED
Upgraded profile - PASSED
Install 1.56.x CR 115 and upgrade it to 1.57.x CR 116 - PASSED
Case 1.1: Default shield settings upgrade - PASSED
1. Clean profile 1.56.x
2. Open a few websites
4. Upgrade the profile to 1.57.x CR 116
5. Confirmed profile is upgraded to 1.57.x CR 116
6. Confirmed default shield settings are retained
Case 1.2: Update the default shield settings and then upgrade - PASSED
1. Clean profile 1.56.x
2. Open a few websites
3. Edit the site-specific shield settings
5. Upgrade the profile to 1.57.x CR 116
6. Confirmed profile is upgraded to 1.57.x CR 116
7. Confirmed that updated shield settings are retained after the upgrade
Case 1.3: Update the global default shield settings and then upgrade - PASSED
1. Clean profile 1.56.x
2. Open a few websites
3. Edit the global shield settings via brave://settings/shields
5. Upgrade the profile to 1.57.x CR 116
6. Confirmed profile is upgraded to 1.57.x CR 116
7. Confirmed that updated global shield settings are retained after the upgrade
Case 1.4: Turn OFF the shield for a few sites and then upgrade - PASSED
1. Clean profile 1.56.x
2. Open a few websites
3. Turn OFF the shield for a few sites via panel
4. Upgrade the profile to 1.57.x CR 116
6. Confirmed profile is upgraded to 1.57.x CR 116
7. Confirmed that shield settings are retained after the upgrade
Case 1.5: Block scripts and then upgrade - PASSED
1. Clean profile 1.56.x
2. Open a few websites
3. Block scripts for any of the sites via Panel or via brave://settings/shields
5. Upgrade the profile to 1.57.x CR 116
6. Confirmed profile is upgraded to 1.57.x CR 116
7. Confirmed that script block settings are retained after the upgrade
Case 1.6: Block HTTPS upgrade and then upgrade - PASSED
1. Clean profile 1.56.x
2. Open a few websites
3. Block HTTPS upgrade via Panel or via brave://settings/shields
5. Upgrade the profile to 1.57.x CR 116
6. Confirmed profile is upgraded to 1.57.x CR 116
7. Confirmed that block HTTPS upgrade settings are retained after the upgrade
All items are present and work as expected in the ☰ menu - PASSED

Note: encountered the menu-item string changes from Chromium 116 mentioned here: https://bravesoftware.slack.com/archives/CU5UXM3EC/p1690561214082359?thread_ts=1690227069.794059&cid=CU5UXM3EC
Translate page works - PASSED
- confirmed I could translate from
Ukranian
toEnglish
onhttps://www.pravda.com.ua/
- confirmed I could translate from
Spanish
toEnglish
onesmas.com
- confirmed I could translate from
Spanish
toEnglish
and then toAfrikaans
, onesmas.com
example | example | example | example | example | example |
---|---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Signing into Google sites works - PASSED
- confirmed
Allow use of third-party cookies for legacy Google Sign-In
was enabled viabrave://settings/socialBlocking
- confirmed I could log in to
expensify.com
usingSAML
, with the above pref enabled - toggled
Allow use of third-party cookies for legacy Google Sign-In
toOFF
- confirmed I could NOT log in to
expensify
with the above pref disabled
example | example | example | example |
---|---|---|---|
![]() |
![]() |
![]() |
![]() |
Brave Side Panel looks/works correctly - PASSED
- Confirmed that sidebar is NOT shown by default
- Confirmed that Reading list icon is added to the sidebar menu
- Confirmed that reading list panel is shown when user click on the Reading list icon in the sidebar menu
- Confirmed that user can add the list of websites to the reading list by clicking on the +Add current tab
- Confirmed that user can add the list of websites to the reading list by right clicking on the tab and choose the option Add tab to the reading list
- Confirmed that reading list panel can be hidden by clicking on the Reading list icon in the sidebar menu
- Confirmed that reading list icon is shown in the URL bar, next to wallet icon
- Confirmed that user can enable/disable the reading list by clicking on the reading list icon (shown in the URL bar)
- Confirmed that reading list is shown in all the window types (Normal, PT, TOR, and Guest window)
- Websites can't be added to reading list in Guest, encountered Unable to add a site to reading list in Guest window as
Add to current tab
option is not getting activated #24930 - Confirmed that sites can be segregated to Read and Unread list
- Confirmed that sites can be deleted from the reading list
- Confirmed that tooltip is shown correctly for each menu item in sidebar
- Confirmed that click on each sidepanel button Brave Talk, wallet, Bookmarks and Reading list works as expected
Clear browsing data for time span works - PASSED
Basic - last hour - PASSED
- install
1.57.42
- launched Brave
- browsed a few sites
- logged in to a few sites
- clicked on
Brave
->Clear Browsing Data...
- unchecked
Cookies and other site data
- clicked
Clear data
- confirmed
brave://history
was empty - confirmed I was still signed in to
gmail.com
- returned to
brave://settings/clearBrowserData
- checked
Cookies and other site data
- clicked
Clear data
- confirmed I was no longer signed in
- confirmed
brave://history
was cleared
example | example | example | example | example |
---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
Advanced - all time - PASSED
- install
1.57.42
- launched Brave
- browsed a few sites
- logged in to a few sites
- clicked on
Brave
->Clear Browsing Data...
- clicked on the
Advanced
tab - selected
All time
fromTime range
- clicked
Clear data
- confirmed I was no longer signed in
- confirmed
brave://history
was cleared
example | example | example | example | example |
---|---|---|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
Advanced - last 7 days - PASSED
Advanced - last 4 weeks - PASSED
Omnibox suggestions are shown when enabled - PASSED
- confirmed default of no search suggestions when typing
san mateo weather
(and assorted searches) in the URL bar - confirmed
Improve search suggestions
is set toOFF
inbrave://settings/search
- toggled
Improve search suggestions
toON
- typed
san mateo weather
again - confirmed I saw search-autocomplete suggestions in the URL bar
- confirmed
Improve search suggestions
, when enabled, has no effect in bothPrivate
andPrivate w/Tor
windows
Improve search suggestions , OFF |
Improve search suggestions , ON |
---|---|
![]() |
![]() |
Improve search suggestions , ON |
Private window |
Private w/Tor window |
Guest window |
---|---|---|---|
![]() |
![]() |
![]() |
![]() |
Note: encountered the menu-item string changes from Chromium 116 mentioned here: https://bravesoftware.slack.com/archives/CU5UXM3EC/p1690561214082359?thread_ts=1690227069.794059&cid=CU5UXM3EC
Installation and upgrade work (upgrade 1.56.x -> 1.57.x and 1.57.x to 1.57.x) - PENDING
1.56.x
-> 1.57.x
- PASSED
Done as part of the Shields
-profile upgrade work, see above
1.57.42
-> 1.57.44
- PENDING
Update from 1.57.42
to 1.57.44
Labelling as |
Upgrade from Chromium 115 to Chromium 116
https://chromium.googlesource.com/chromium/src/+log/115.0.5790.98..116.0.5845.42/?pretty=fuller&n=10000
QA tests:
This is a major Chromium version bump, please do full passes.
Desktop Affected areas:
MacOS:
Installation and upgrade work (upgrade 1.56.x -> 1.57.x and 1.57.x to 1.57.x)
Linux:
iOS Affected areas:
N/A
Android Affected areas:
The text was updated successfully, but these errors were encountered: