Gmail and Slack integration

Oct 13, 2025 by pynkocean.com 74 views

Introduction

As we continue to push the boundaries of innovation in the world of web browsers, it's essential to ensure that our latest release, 1.76.x, meets the highest standards of quality and performance. In this manual test run, we'll be putting our Android ARM version through a series of rigorous tests to identify any potential issues and ensure a seamless user experience.

Installer

The installer is a critical component of our browser, and we need to ensure that it's functioning correctly. Here are the key points to check:

Verify installer size: The installer should be close to the size of the last release, indicating that we've optimized our code and reduced unnecessary bloat.
Check Brave version: We need to verify that the Brave version displayed in the About section is exactly as expected, ensuring that our versioning system is accurate and up-to-date.

Custom Tabs

Custom tabs are a game-changer in the world of web browsing, allowing users to access their favorite websites with ease. Here are the key points to check:

Gmail and Slack integration: We need to ensure that Brave handles links from Gmail and Slack correctly, providing a seamless experience for users.
Chrome browser compatibility: We need to verify that Brave works as custom tabs provide with the Chrome browser, ensuring that our integration is smooth and hassle-free.
Sync enabled/disabled: We need to ensure that custom tabs work even with sync enabled or disabled, providing users with flexibility and control.

Settings and Bottom Bar

The settings and bottom bar are essential components of our browser, and we need to ensure that they're functioning correctly. Here are the key points to check:

Default settings retention: We need to verify that changing default settings are retained and don't cause the browser to crash, ensuring that users can customize their experience without any issues.
Bottom bar buttons: We need to verify that the bottom bar buttons (Home/Bookmark/Search/Tabs) work as expected, providing users with easy access to their favorite features.

Rewards

Rewards are a key feature of our browser, allowing users to earn cryptocurrency for browsing the web. Here are the key points to check:

Join Rewards on a fresh profile: We need to verify that users can successfully join Rewards on a fresh profile, ensuring that the onboarding process is smooth and hassle-free.

Upgrade

Upgrading to a new version of our browser can be a complex process, and we need to ensure that data from the last version is preserved correctly. Here are the key points to check:

Data preservation: We need to ensure that data from the last version appears in the new version OK, including bookmarks, cookies, per-site shield settings, and more.
Version information: We need to verify that brave://version lists the expected Brave and Chromium versions, ensuring that our versioning system is accurate and up-to-date.
Setting changes preservation: We need to ensure that setting changes are preserved, including default search engine, shield settings, homepage, and more.
Top Tiles preservation: We need to verify that Top Tiles under the New Tab Page are preserved, ensuring that users can access their favorite websites with ease.
Home screen shortcuts preservation: We need to ensure that Home screen shortcuts are preserved, providing users with easy access to their favorite websites.
Rewards preservation: We need to verify that Rewards are preserved, including BAT balance, auto-contribute list, tips, monthly contributions, and more.
Ads preservation: We need to ensure that ads are preserved, including estimated pending rewards, ad notifications received this month, and more.
Ads settings preservation: We need to verify that ads settings are preserved, ensuring that users can customize their experience without any issues.

Conclusion

Q: What is the purpose of the manual test run on Android ARM for 1.76.x - Release #3?

A: The purpose of the manual test run is to ensure that our latest release, 1.76.x, meets the highest standards of quality and performance on Android ARM devices. We want to identify any potential issues and ensure a seamless user experience.

Q: What are the key areas that will be tested during the manual test run?

A: The key areas that will be tested during the manual test run include:

Installer
Custom tabs
Settings and bottom bar
Rewards
Upgrade

Q: What specific tests will be performed on the installer?

A: The following tests will be performed on the installer:

Verify installer size
Check Brave version

Q: What specific tests will be performed on custom tabs?

A: The following tests will be performed on custom tabs:

Verify that Brave handles links from Gmail and Slack correctly
Verify that Brave works as custom tabs provide with the Chrome browser
Verify that custom tabs work even with sync enabled or disabled

Q: What specific tests will be performed on settings and bottom bar?

A: The following tests will be performed on settings and bottom bar:

Verify that changing default settings are retained and don't cause the browser to crash
Verify that bottom bar buttons (Home/Bookmark/Search/Tabs) work as expected

Q: What specific tests will be performed on rewards?

A: The following tests will be performed on rewards:

Verify that users can successfully join Rewards on a fresh profile

Q: What specific tests will be performed on upgrade?

A: The following tests will be performed on upgrade:

Verify that data from the last version appears in the new version OK
Verify that setting changes are preserved
Verify that Top Tiles under the New Tab Page are preserved
Verify that Home screen shortcuts are preserved
Verify that Rewards are preserved
Verify that ads are preserved
Verify that ads settings are preserved

Q: What is the expected outcome of the manual test run?

A: The expected outcome of the manual test run is to identify any potential issues and ensure a seamless user experience. We want to ensure that our browser provides a high-quality experience for our users.

Q: How will the results of the manual test run be used?

A: The results of the manual test run will be used to identify areas for improvement and to prioritize bug fixes and feature enhancements. We will use the results to ensure that our browser meets the highest standards of quality and performance.

Q: When will the results of the manual test run be available?

A: The results of the manual test run will be available shortly after the completion of the test run. We will provide a detailed report of the results, including any issues that were identified and the steps that will be taken to address them.