2.14.0 Test Plan

2.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.

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.

Notes:

Environment

• Install target:
• Tails version:
• Test Scenario:
  • fresh install - server and tails
  • server upgrade from 2.130, tails admin and journalist workstation update
• SSH over Tor?:
• Tor PoW enabled?:
• Release candidate:
• General notes:

Basic Server Testing

• Testinfra tests are passing against production servers after installation:
  • run the following:

    cd Persistent/securedrop
    sudo apt install -y python3.13-venv
    python3 -m venv admin/.venv3 && source admin/.venv3/bin/activate
    torify pip install -r admin/requirements-testinfra.txt
    TEST_ENV=prod devops/scripts/run_prod_testinfra
    

  • verify that tests pass.
• 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.13.0 (workstation version) 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

(Optional after first pass) 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

2.14.0 release-specific changes

Update Source Interface warning banner to refer to modern mobile browsers (#7751)

• Open the SI in Tor Browser for Android (or fake it with a UA-changing web extension) and verify that the

Ensure KeePassXC is installed with securedrop-admin (#7762)

Note: you can override production settings in the securedrop-admin install script by creating a file ~/securedrop_bootstrap.env with contents:

APT_REPO_URL="https://apt-test.freedom.press"
APT_SIGNING_KEY_FILE="apt-test-signing-key.pub"

For upgrades, you'll need to edit the apt source config and add the test release key via apt-key add instead.

Fresh install (simulated Tails without keepassxc)

• before installing securedrop-admin, remove the keepassxc package: sudo apt remove keepassxc-minimal, then verify that it is reinstalled with the securedrop-admin package.
• verify that KeePassXC is still accessible via the Tails menu and SecureDrop menu.
• verify that the sample database can be found at /usr/share/securedrop-admin/keepassxc

Fresh install (current Tails)

• Install securedrop-admin and verify that the package installation completes successfully and KeePassXC is still available
• verify that KeePassXC is still accessible via the Tails menu and SecureDrop menu.
• verify that the sample database can be found at /usr/share/securedrop-admin/keepassxc

Upgrade (current Tails)

• Verify that securedrop-admin is upgraded on session start (this may take a few mins for background apt tasks)
• verify that KeePassXC is still accessible via the Tails menu and SecureDrop menu.
• verify that the sample database can be found at /usr/share/securedrop-admin/keepassxc

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.14.0
• A message can be successfully submitted

Tails

• securedrop-admin is available on session start
• If testing an upgrade, securedrop-admin is upgraded automatically to the current version.