Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Manual test run on OS X for 0.20.x Hotfix 1 #12980

Closed
43 tasks done
kjozwiak opened this issue Feb 1, 2018 · 1 comment
Closed
43 tasks done

Manual test run on OS X for 0.20.x Hotfix 1 #12980

kjozwiak opened this issue Feb 1, 2018 · 1 comment

Comments

@kjozwiak
Copy link
Member

kjozwiak commented Feb 1, 2018

Per release specialty tests

Installer

  • Check that installer is close to the size of last release.
  • Check signature: If OS Run spctl --assess --verbose /Applications/Brave.app/ and make sure it returns accepted. If Windows right click on the installer exe and go to Properties, go to the Digital Signatures tab and double click on the signature. Make sure it says "The digital signature is OK" in the popup window.
  • Check Brave, muon, and libchromiumcontent version in about:brave and make sure it is EXACTLY as expected.

Data

  • Make sure that data from the last version appears in the new version OK.
  • With data from the last version, test that
    • cookies are preserved
    • pinned tabs can be opened
    • pinned tabs can be unpinned
    • unpinned tabs can be re-pinned
    • opened tabs can be reloaded
    • bookmarks on the bookmark toolbar can be opened
    • bookmarks in the bookmark folder toolbar can be opened

Keyboard Shortcuts

  • Open a new tab: Command + t (macOS) || Ctrl + t (Win/Linux)
  • Open a new private tab: Command + Shift + p (macOS) || Ctrl + Shift + p (Win/Linux)
  • Reopen the latest closed tab: Command + Shift + t (macOS) || Ctrl + Shift + t (Win/Linux)
  • Jump to the next tab: Command + Option + -> (macOS) || Ctrl + PgDn (Win/Linux)
  • Jump to the previous tab: Command + Option + <- (macOS) || Ctrl + PgUp (Win/Linux)
  • Jump to the next tab: Ctrl + Tab (macOS/Win/Linux)
  • Jump to the previous tab: Ctrl + Shift + Tab (macOS/Win/Linux)

Tabs, Pinning and Tear off tabs

  • Test that tabs are pinnable
  • Test that tabs are unpinnable
  • Test that tabs are draggable to same tabset
  • Test that tabs are draggable to alternate tabset
  • Test that tabs can be teared off into a new window
  • Test that you are able to reattach a tab that is teared off into a new window
  • Test that tab pages can be closed
  • Test that tab pages can be muted
  • Test that tabs can be cloned

Content tests

  • Make sure that Command + Click (Control + Click on Windows, Control + Click on Ubuntu) on a link opens a new tab but does NOT switch to it. Click on it and make sure it is already loaded.

Session storage

Do not forget to make a backup of your entire ~/Library/Application\ Support/Brave folder.

  • Temporarily move away your ~/Library/Application\ Support/Brave/session-store-1 and test that clean session storage works. (%appdata%\Brave in Windows, ./config/brave in Ubuntu)
  • Test that windows and tabs restore when closed, including active tab.
  • Test that the current active tab loads URL when restoring session
  • Test that non-active tabs are being lazy loaded when restoring session
  • Test that hovering over lazy loaded tabs after a session restore correctly loads the tab
  • Test that clicking/making a lazy loaded tab active after a session restore correctly loads the tab
  • Test that pinned tabs are not being lazy loaded after session restore
  • Test that about: pages are not being lazy loaded after session restore
  • Move away your entire ~/Library/Application\ Support/Brave folder (%appdata%\Brave in Windows, ./config/brave in Ubuntu)

Cookie and Cache

  • Make a backup of your profile, turn on all clearing in preferences and shut down. Make sure when you bring the browser back up everything is gone that is specified.
  • Go to http://samy.pl/evercookie/ and set an evercookie. Check that going to prefs, clearing site data and cache, and going back to the Evercookie site does not remember the old evercookie value.

Update tests

  • Test that updating using BRAVE_UPDATE_VERSION=0.8.3 env variable works correctly.
  • Test that using BRAVE_ENABLE_PREVIEW_UPDATES=TRUE env variable works and prompts for preview build updates.
@LaurenWags
Copy link
Member

Tests were as expected.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants