-
Notifications
You must be signed in to change notification settings - Fork 696
2.12.0 Test Plan
Cory Francis Myers edited this page Mar 5, 2025
·
5 revisions
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.
If you have submitted a QA report already for a release candidate with successful basic server testing and application acceptance testing sections, then you can skip these sections in subsequent reports, unless otherwise indicated by the Release Manager. This is to ensure that you focus your QA effort on the release-specific changes as well as changes since the previous release candidate.
- if testing an upgrade scenario, the initial 2.11.1 install should include
hias a supported locale, to facilitate testing its removal in 2.12.0
- Install target:
- Tails version:
- Test Scenario:
- Noble fresh install
- focal 2.11.1 upgrade to focal 2.12.0
- focal 2.11.1 upgrade to focal 2.12.0, auto-update to noble
- focal 2.11.1 upgrade to focal 2.12.0, triggered update to noble
- SSH over Tor?:
- Tor PoW enabled?:
- Release candidate:
- General notes:
- After installing the testinfra dependencies, all tests in
./securedrop-admin verifyare passing:- Install dependencies on Admin Workstation with
cd ~/Persistent/securedrop && ./securedrop-admin setup -t - Run tests with
./securedrop-admin verify(this will take a while) - Remove test dependencies:
rm -rf admin/.venv3/ && ./securedrop-admin setup
- Install dependencies on Admin Workstation with
- QA Matrix checks pass
- Can successfully add admin user and login
- I have backed up and successfully restored the app server following the backup documentation
- If doing upgrade testing, make a backup on 2.11.1 and restore this backup on this release candidate, verifying that the Redis password in /etc/redis/redis.conf changes
- "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent
- Can successfully add journalist account with HOTP authentication
- JS warning bar does not appear when using Security Slider high
- JS warning bar does appear when using Security Slider Low
- On generate page, refreshing page produces a new 7-word codename
- On submit page, empty submissions produce flashed message
- On submit page, short message submitted successfully
- On submit page, file greater than 500 MB produces "The connection was reset" in Tor Browser quickly before the entire file is uploaded
- On submit page, file less than 500 MB submitted successfully
- Nonexistent codename cannot log in
- Empty codename cannot log in
- Legitimate codename can log in
- Returning user can view journalist replies - need to log into journalist interface to test
- Can log in with 2FA tokens
- incorrect password cannot log in
- invalid 2fa token cannot log in
- 2fa immediate reuse cannot log in
- Journalist account with HOTP can log in
- Filter by codename works
- Starring and unstarring works
- Click select all selects all submissions
- Selecting all and clicking "Download" works
- You can submit a reply and a flashed message and new row appears
- You cannot submit an empty reply
- Clicking "Delete Source Account" and the source and docs are deleted
- You can click on a document and successfully decrypt using application private key
After updating to this release candidate and running securedrop-admin tailsconfig
- The Updater GUI appears on boot
- upgrade-only - verify that after upgrading an installation initially configured with
hias a locale,hiis no longer available in the dropdown - verify that
hiis not available as an option when stepping through./securedrop-admin sdconfig
Upgrade-only On both servers, when testing against RCs:
- Add the apt-test public key with
cat <keyfile> | apt-key add - - edit
/lib/systemd/system/securedrop-noble-migration-upgrade.serviceto add the lineEnvironment=EXTRA_APT_SOURCE="deb [trusted=yes] https://apt-test.freedom.press/ noble main"On the Admin Workstation: - Ensure the Admin Workstation securedrop code is updated to 2.12.0 (or the latest RC)
- Run
./securedrop-admin --force noble_migrationand verify that it completes successfully
Once the migration is complete:
- Verify that
./securedrop-admin verifypasses - Verify that acceptance tests above still pass
- Verify that OSSEC alerts are being received.
On the app server:
- Add the apt-test public key with
cat <keyfile> | apt-key add - - edit
/lib/systemd/system/securedrop-noble-migration-upgrade.serviceto add the lineEnvironment=EXTRA_APT_SOURCE="deb [trusted=yes] https://apt-test.freedom.press noble main" - verify
/etc/securedrop-noble-migration-state.jsonwas created with{"finished": None, "bucket": 1-5}. - edit
/usr/share/securedrop/noble-upgrade.json, to setapp.enabled = trueandapp.bucket = 5. - Verify that the
securedrop-noble-migration-upgradesystemdtimer starts within 3 minutes approx. - Verify that the server reboots and that
/etc/securedrop-noble-migration-state.jsonshows that the upgrade has finished the PendingUpdates stage. - Verify that the
securedrop-noble-migration-upgradesystemdtimer starts again within 3 minutes approx and apt updates begin. - Verify that the SI/JI are unreachable (apache is masked) during the upgrade process
- Verify that the system reboots again, and on reboot
/etc/securedrop-noble-migration-state.json,s stage should be Reboot. - Verify that the time triggers again and that the stage moves to Done soon after.
- Verify that the OS is now Noble via
cat /etc/os-release.
On the mon server:
- Add the apt-test public key with
cat <keyfile> | apt-key add - - edit
/lib/systemd/system/securedrop-noble-migration-upgrade.serviceto add the lineEnvironment=EXTRA_APT_SOURCE="deb [trusted=yes] https://apt-test.freedom.press noble main" - verify
/etc/securedrop-noble-migration-state.jsonwas created with{"finished": None, "bucket": 1-5}. - edit
/usr/share/securedrop/noble-upgrade.json, to setmon.enabled = trueandmon.bucket = 5. - Verify that the
securedrop-noble-migration-upgradesystemdtimer starts within 3 minutes approx. - Verify that the server reboots and that
/etc/securedrop-noble-migration-state.jsonshows that the upgrade has finished the PendingUpdates stage. - Verify that the
securedrop-noble-migration-upgradesystemdtimer starts again within 3 minutes approx and apt updates begin. - Verify that the system reboots again, and on reboot
/etc/securedrop-noble-migration-state.json,s stage should be Reboot. - Verify that the time triggers again and that the stage moves to Done soon after.
- Verify that the OS is now Noble via
cat /etc/os-release.
Once both servers are updated:
- Verify that
./securedrop-admin verifypasses - Verify that acceptance tests above still pass
- Verify that OSSEC alerts are being received.
- Install or upgrade occurs without error (from
apt-qa.freedom.pressper preflight procedure) - Source interface is available and version string indicates it is 2.12.0
- A message can be successfully submitted
- The updater GUI appears on boot
- The update successfully occurs to 2.12.0
- After reboot, updater GUI no longer appears