mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 10:18:54 +00:00
Whenever changing a URL we care about, we add an entry in `website/redirects.js` to avoid breaking links to the old page. Most search engines reindex these after 1 year, but other websites and places won't, so we should generally keep them indefinitely since they don't cost us much to keep around.
3.9 KiB
3.9 KiB
Intended Behavior
A less exhaustive version of Manual Testing
Smoke test checklist (Ubuntu)
Keep this synchronized with the Linux GUI docs in /website/src/app/kb/client-apps/linux-gui-client
Best performed on a clean VM
- Run
scripts/firezone-client-gui-install.sh - Expect "Reboot to finish..." message
- Run the Firezone GUI
- Expect an error saying that you are not a member of the group
firezone-client - Reboot
- Expect
groupsto include "firezone-client" - Run the Firezone GUI
- Expect the "Welcome to Firezone." screen
- Open the Settings window and change to staging if needed
- Click "Sign in"
- Expect a browser to open
- Sign in
- Expect Firefox to show "Allow this site to open the link with Firezone?" modal
- Check "Always..." and click "Open link"
- Expect a keyring dialog to pop up
- Enter 'password' for testing purposes
- Expect "Firezone connected" notification
- Browse to
https://ifconfig.net - Expect to see the gateway's IP and location
- Quit Firezone
- Refresh the page
- Expect to see your own IP and location
- Reboot
- Run the Firezone GUI
- Expect a keyring dialog to pop up
- Enter 'password' to unlock the stored token
- Expect "Firezone connected" notification
- Check the IP again, expect the gateway's IP
- Sign out of Firezone without quitting
- Check the IP again, expect your own IP (Checks for regressions in https://github.com/firezone/firezone/pull/5828)
- Export the logs
- Expect the zip file to start with
firezone_logs_ - Expect
zipinfoto show a single directory in the root of the zip, to prevent zip bombing - Expect two subdirectories in the zip, "connlib", and "app", with 3 and 2 files respectively, totalling 5 files
Smoke test checklist (Windows)
Keep this synchronized with the Windows GUI docs in /website/src/app/kb/client-apps/windows-gui-client
x86_64 only, see issue #2992. Best performed on a clean VM.
- Run the MSI installer and ensure "Launch Firezone" is checked at the end
- Expect the "Welcome to Firezone." screen
- Right-click on the Windows taskbar and configure it to show the Firezone icon
- Open the Settings window and change to staging if needed
- Click "Sign in"
- Expect a browser to open
- Sign in
- Expect the browser to show "This site is trying to open Firezone." modal
- Check "Always allow..." and click "Open"
- Expect "Firezone connected" notification
- Browse to
https://ifconfig.net - Expect to see the gateway's IP and location
- Quit Firezone
- Refresh the page
- Expect to see your own IP and location
- Reboot
- Browse to
https://ifconfig.net(For issue #4899) - Expect to see your own IP and location
- Run the Firezone GUI
- Expect "Firezone connected" notification
- Check the IP again, expect the gateway's IP
- Sign out of Firezone without quitting
- Check the IP again, expect your own IP (Checks for regressions in https://github.com/firezone/firezone/pull/5828)
- Export the logs
- Expect the zip file to start with
firezone_logs_ - Expect the zip to contain a single directory in the root of the zip, to prevent zip bombing
- Expect two subdirectories in the zip, "connlib", and "app", with 2 files each, totalling 4 files
Upgrade checklist (Linux)
- Close the Firezone GUI
- Run
scripts/firezone-client-gui-install.sh $NEW_DEB - Run the Firezone GUI
Upgrade checklist (Windows)
- Close the Firezone GUI
- Run the new MSI
- Run the Firezone GUI
Un-install checklist (Linux)
- Close the Firezone GUI
- Run
sudo apt-get remove firezone-client-gui
Un-install checklist (Windows)
- Quit the Firezone GUI
- Go to "Add or Remove Programs"
- Search for Firezone and click "Uninstall"
Settings tab
- Pressing Enter on a text field immediately saves and applies the settings
- Log level changes take effect on the next app start
- Auth base URL and API URL changes take effect on the next sign-in
Refs: