-
Notifications
You must be signed in to change notification settings - Fork 701
2.12.2 Test Plan
Kevin O'Gorman edited this page Apr 16, 2025
·
3 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.
- Install target:
- Tails version:
- Test Scenario:
- Noble fresh install
- Noble 2.12.1 upgrade to Noble 2.12.2
- focal 2.12.1 upgrade to focal 2.12.2, auto-update to noble
- focal 2.12.1 upgrade to focal 2.12.2, 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.12.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
- After installation is complete, edit
/etc/securedrop-noble-migration-state.jsonon app to be in bucket 1, and reboot servers - Verify that an attempted migration is not triggered
- After upgrade is complete, edit
/etc/securedrop-noble-migration-state.jsonon app to be in bucket 1, and reboot servers - Verify that an attempted migration is not triggered
On the app server:
- After upgrade is complete, edit
/etc/securedrop-noble-migration-state.jsonon to be in bucket 5, and reboot server - Verify that an attempted migration is not triggered
- edit securedrop-noble-migration-upgrade.service to set
Environment=EXTRA_APT_SOURCE="deb [trusted=yes] https://apt-test.freedom.press noble main" systemctl daemon-reload- edit
/etc/securedrop-noble-migration-state.jsonto be in bucket 1, and wait up to 3 minutes - Verify that an attempted migration is triggered and completes successfully
On the mon server:
- After upgrade is complete, edit
/etc/securedrop-noble-migration-state.jsonon to be in bucket 5, and reboot server - Verify that an attempted migration is not triggered
- edit securedrop-noble-migration-upgrade.service to set
Environment=EXTRA_APT_SOURCE="deb [trusted=yes] https://apt-test.freedom.press noble main" systemctl daemon-reload- edit
/etc/securedrop-noble-migration-state.jsonto be in bucket 1, and wait up to 3 minutes - Verify that the migration check is triggered (
journalctl -efor similar) and the migration does not proceed
- After upgrade is complete, edit
/etc/securedrop-noble-migration-state.jsonon app to be in bucket 5, and reboot servers - Verify that an attempted migration is not triggered
- Verify that a migration triggered by
./securedrop-admin noble_migrationon the admin workstation completes successfully.
- Run through
./securedrop-admin sdconfig, copying in a valid gpg fingerprint and one or more newlines when prompted for the submission key fingerprint - verify that validation succeeds
- 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