0.14.0 Test Plan

QA plan

• NUC5s
• NUC7s
• Mac Minis
• 1U servers in SF

0.14.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. Feel free to edit this message to update the plan as appropriate.

If you have submitted a QA report already for a 0.14.0 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 0.14.0-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

• I can access both the source and journalist interfaces
• I can SSH into both machines over Tor
• AppArmor is loaded on app
  • 0 processes are running unconfined
• AppArmor is loaded on mon
  • 0 processes are running unconfined
• Both servers are running grsec kernels
• iptables rules loaded
• OSSEC emails begin to flow after install
• OSSEC emails are decrypted to correct key and I am able to decrypt them
• QA Matrix checks pass

Command Line User Generation

• Can successfully add admin user and login

Administration

• I have backed up and successfully restored the app server following the documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
• If doing upgrade testing, make a backup on 0.13.1 and restore this backup on 0.14.0
• "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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 codename 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

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 And Submissions" and the source and docs are deleted
• You can click on a document and successfully decrypt using application private key

Basic Tails Testing

Updater GUI

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

• The Updater GUI appears on boot
• Updating occurs without issue

0.14.0-specific changes

• Ensure there are no Font Awesome CSS assets loaded on the source interface (#4464)
• Ensure that the supported locales are exposed in the source interface metadata API (for a case with only supported en_US locale, and a case where multiple locales are supported) (#4467).
• Run through source interface Tor Browser 8.5 security settings - ensure instructions are accurate (#4462, #4494)
• Ensure you can set a journalist first name and last name via the CLI (#4425)
• Ensure you can successfully add a new account as an admin from the journalist interface(#4425)
• Ensure you can successfully change the name of an account that is not yours as an admin from the admin page (#4425)
• Ensure you can successfully change your own name as a non-admin from the account page (#4425)
• Ensure you can successfully change your own name to empty strings as a non-admin from the accounts page (#4425)
• Ensure you can export a tarball containing logs via securedrop-admin logs (#4497)
• Ensure that intel-microcode is installed (#4543).
• Ensure that grsec kernels version 4.4.182 are installed (#4543).
• Follow STR in https://github.com/freedomofpress/securedrop/issues/4490 to verify sessions expiring on /generate do not cause errors (#4496).

0.14.0-rc2 specific changes

• Installed version of securedrop-keyring should be 0.1.3
• securedrop-admin logs completes without issue in Tails
• Verify that the update process works when a release key is already in the GPG keychain in Tails, using the following commands in a terminal:

cd ~/Persistent/securedrop
gpg --recv-key "22245C81E3BAEB4138B36061310F561200F4AD77"   # use Tails' default keyserver
git checkout 0.14.0-rc2
./securedrop-admin update
git status    # should now be on 0.13.1 tag

• Verify that the update process works when a release key is already in the GPG keychain in Tails, using the following commands in a terminal:

gpg --delete-keys "22245C81E3BAEB4138B36061310F561200F4AD77"
git checkout 0.14.0-rc2
./securedrop-admin update
git status    # should now be on 0.13.1 tag

Preflight

• Ensure the builder image is up-to-date on release day

These tests should be performed the day of release prior to live debian packages on apt.freedom.press

Basic testing

• Install or upgrade occurs without error
• Source interface is available and version string indicates it is 0.14.0
• A message can be successfully submitted

Tails

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