2.8.0 Test Plan

2.8.0 QA Checklist

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.

Note that this release includes an update to support Tails 6 for the admin tools. As such, there are a number of potential scenarios to test:

• Upgrading to 2.8.0, staying on Tails 5
• Upgrading to 2.8.0, moving to Tails 6 (this will require a second USB stick)
• A fresh install on Tails 6 (fresh installs on Tails 5 will still work but are not going to be supported. New users should be using Tails 6 from the start)

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.

Environment

• Install target:
• Tails version:
• Test Scenario:
• SSH over Tor:
• Release candidate:
• General notes:

Basic Server Testing

• After installing the testinfra dependencies, all tests in ./securedrop-admin verify are 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
• QA Matrix checks pass

Command Line User Generation

• Can successfully add admin user and login

(Optional) Administration

• I have backed up and successfully restored the app server following the backup documentation
• If doing upgrade testing, make a backup on 2.7.0 and restore this backup on this release candidate
• "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

(Optional) Application Acceptance Testing

Source Interface

Landing page base cases

• JS warning bar does not appear when using Security Slider high
• JS warning bar does appear when using Security Slider Low

First submission base cases

• 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

Returning source base cases

• 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

Journalist Interface

Login base cases

• 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

Index base cases

• Filter by codename works
• Starring and unstarring works
• Click select all selects all submissions
• Selecting all and clicking "Download" works

Individual source page

• 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

Basic Tails Testing

After updating to this release candidate and running securedrop-admin tailsconfig

• The Updater GUI appears on boot

2.8.0 release-specific changes

Update to 5.15.148 kernel (https://github.com/freedomofpress/securedrop/issues/7113)

• Kernel-specific checks in QA matrix pass on instance hardware.

Tails 6 support (https://github.com/freedomofpress/securedrop/pull/7116)

Upgrade #1 - updating to 2.8.0 on Tails 5

• On a Tails 5 admin workstation with an existing install of 2.7.0, simulate a GUI update with the following commands:
  • git fetch && git checkout <latest RC tag> completes
  • ./securedrop-admin setup completes
  • ./securedrop-admin --force tailsconfig completes
• Verify that ssh targets, desktop icons, and SecureDrop menu are still available and working.
• Confirm that ./securedrop-admin logs completes successfully, capturing the expected logs
• Verify that:
  • ./securedrop-admin --force sdconfig lists the expected config settings
  • A rerun of ./securedrop-admin --force install completes 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, desktop icons, and SecureDrop menu are available.
• Create a new source account via the SI and make a submission. Then, confirm that:
  • ./securedrop-admin backup completes successfully
  • in the JI, the first source is present.
• Create a second source account via the SI and make a submission, then run ./securedrop-admin restore <backupname> and confirm that
  • the restore command completes successfully
  • in the JI, the first source is present but the second source is not.

Upgrade #2 - updating to Tails 6, updating to 2.8.0

• Create a fresh Tails 6 stick and restore the PV from your Tails 5 admin workstation to it, using these instructions
• Perform a manual update:
  • git fetch && git checkout <latest RC tag> (simulating ./securedrop-admin update)
  • ./securedrop-admin setup - confirm that the tails 5 venv is destroyed and a tails 6 version created
  • ./securedrop-admin --force tailsconfig - confirm that ssh targets, icons, and menu are created
• Confirm that ./securedrop-admin logs completes successfully, capturing the expected logs
• Verify that:
  • ./securedrop-admin --force sdconfig lists the expected config settings
  • A rerun of ./securedrop-admin --force install completes successfully
• reboot the admin workstation and verify that:
  • The network hook runs successfully on network connection, and the ssh targets and SecureDrop menu are available.
• Create a new source account via the SI and make a submission. Then, confirm that:
  • ./securedrop-admin backup completes successfully
  • in the JI, the first source is present.
• Create a second source account via the SI and make a submission, then run ./securedrop-admin restore <backupname> and confirm that
  • the restore command completes successfully
  • in the JI, the first source is present but the second source is not.

Fresh install (Tails 6)

• Set up a Tails 6 workstation using the latest RC tag and verify that:
  • ./securedrop-admin setup completes successfully, installing required apt packages and creating a virtualenv with updated dependencies listed above
  • ./securedrop-admin --force sdconfig completes successfully
  • ./securedrop-admin --force install completes successfully
  • ./securedrop-admin --force tailsconfig completes successfully with ssh targets, desktop icons, and SecureDrop menu available.
• reboot the admin workstation and verify that:
  • The network hook runs successfully on network connection, and the ssh targets, desktop icons, and SecureDrop menu are available.
• Create a new source account via the SI and make a submission. Then, confirm that:
  • ./securedrop-admin backup completes successfully
  • in the JI, the first source is present.
• Create a second source account via the SI and make a submission, then run ./securedrop-admin restore <backupname> and confirm that
  • the restore command completes successfully
  • in the JI, the first source is present but the second source is not.

Preflight testing

Basic testing

• Install or upgrade occurs without error (from apt-qa.freedom.press per preflight procedure)
• Source interface is available and version string indicates it is 2.8.0
• A message can be successfully submitted

Tails 5

• The updater GUI appears on boot
• The update successfully occurs to 2.8.0
• After reboot, updater GUI no longer appears

Tails 6

• Manual install of 2.8.0 is successful
• After reboot, updater GUI does not appear