-
Notifications
You must be signed in to change notification settings - Fork 701
2.12.10 Test Plan
Kevin O'Gorman edited this page Sep 22, 2025
·
1 revision
For both upgrades and fresh installs, here is a list of functionality that requires testing. You can use this for copy/pasting into your QA report.
This release is Tails-only, enabling the migration from Tails 6 to 7 - no server installs are required.
- Install target:
- Tails version:
- Test Scenario:
- Migration from Tails 6
- Fresh install on Tails 7
- SSH over Tor:
- Release candidate:
- General notes:
- On an admin workstation, check out the latest RC (
cd ~/Persistent/securedrop && git fetch && git checkout <latest RC tag>:- Confirm that
./securedrop-adminand its subcommands display an error that indicates the user has to run the tool on Tails 7
- Confirm that
- Check out
2.12.9:- Smoke test that
./securedrop-adminsubcommands work again (change is reversible)
- Smoke test that
- Check out the latest RC again.
- Back up the Persistent Volume (PV)
- Create a fresh Tails 7 stick and restore the PV to it
- Do a manual update via the following commands:
-
sudo apt update && ./securedrop-admin setup- confirm that the Tails 6 venv is destroyed and a Tails 7 version created -
./securedrop-admin tailsconfig- confirm that ssh targets, icons, and menu are created
-
- Confirm that
./securedrop-admin logscompletes successfully, capturing the expected logs - Verify that:
-
./securedrop-admin sdconfiglists the expected config settings - A rerun of
./securedrop-admin installcompletes successfully (may take time over Tor)
-
- reboot the admin workstation and verify that:
- The network hook runs successfully on network connection, and the ssh targets, JI/SI shortcuts, and SecureDrop menu are available.
- Submit via the source interface, create a journalist account, and reply via the journalist interface. Then, confirm that:
-
./securedrop-admin backupcompletes successfully
-
- Reply again, run
./securedrop-admin restore <backupname>and confirm that- the restore command completes successfully
- the second reply is not present.
- On an admin workstation, check out the latest RC and perform a production install, and verify that:
-
./securedrop-admin setupcompletes successfully, installing required apt packages and creating a virtualenv with updated dependencies listed above -
./securedrop-admin --force sdconfigcompletes successfully -
./securedrop-admin --force installcompletes successfully -
./securedrop-admin --force tailsconfigcompletes successfully with ssh targets, JI/SI shortcuts (reachable via GNOME search), and SecureDrop menu available. -
./securedrop-admin setup -t && ./securedrop-admin verifycompletes successfully
-
- reboot the admin workstation and verify that:
- The network hook runs successfully on network connection, and the ssh targets, JI/SI shortcuts, and SecureDrop menu are available.
- Submit via the source interface, create a journalist account, and reply via the journalist interface. Then, confirm that:
-
./securedrop-admin backupcompletes successfully
-
- Reply again, run
./securedrop-admin restore <backupname>and confirm that- the restore command completes successfully
- the second reply is not present.
- Confirm that
./securedrop-admin logscompletes successfully, capturing the expected logs
-
On a Tails 6 Admin Workstation:
- The updater GUI appears on boot
- The update successfully occurs to 2.12.10 ( but the updater returns an error when trying to run the
setupsubcommand) - After reboot, updater GUI no longer appears
-
securedrop-adminsubcommands prompt user to upgrade to Tails 7, and then exit.
-
On a Tails 7 Admin Workstation:
- After checking out 2.12.10,
sudo apt update && ./securedrop-admin setupcomplete successfully - Subsequent
securedrop-adminsubcommands give their expected responses, without a prompt to upgrade to Tails 7
- After checking out 2.12.10,