Skip to content

2.13.0 Test Plan

Jump to bottom
Kevin O'Gorman edited this page Dec 3, 2025 · 7 revisions

2.13.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.12.9, tails admin and journalist workstation migration (journalist alerts enabled, SI https enabled)
    • server upgrade from 2.12.9, tails admin and journalist workstation migration
  • 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.12.10 (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

Basic Tails Testing

After updating to this release candidate:

  • The securedrop-admin command is available

2.13.0 release-specific changes

Add Clear-Site-Data header on logout response for Source Interface (#7660)

  • log in to the SI, submit a message, thenwith developer tools open and watching network activity, log out
  • verify that the /logout response includes the Clear-Site-Data header

Use separate prefix for session cookies in Source and Journalist Interface (#7662)

  • Verify (eg using web developer tools) that:
    • the prefix ss_ is used for the Source Interface session cookie
    • the prefix js_ is used for the Journalist Interface session cookie

Implement v2 Journalist API

  • verify that, after authentication via the v1 api, calls to the the v2 api under /api/v2 fail with a 404 error

Update admin tooling to be deployed as a Debian package instead of via git (#7606)

fresh install (ssh-over-tor, journalist alerts enabled, SI https enabled)

Perform a fresh install using the 2.13.0 securedrop docs:

migration from 2.12.10 tails admin and journalist workstation migration

On an existing 2.12.10 Admin Workstation:

  • Create a file `~/securedrop_bootstrap.env with contents:

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

  • cd ~/Persistent/securedrop and git checkout <RC tag under test>

  • run ./securedrop-admin setup, follow on-screen instructions, and verify that:

    • The package migration process starts and can be completed successfully
    • After the migration is complete, the securedrop-admin debian package has been installed
    • All required configuration files (GPG keys, https certs, Tor connection files, site-specific file) have been copied to ~/.config/securedrop-admin

  • reboot the workstation and verify that:

    • The securedrop-admin package is installed automatically
    • config files are still available at ~/.config/securedrop-admin
    • The Securedrop menu is available with all expected items (SSH, SI and JI access, no updater entry)
    • The command securedrop-admin sdconfig can be stepped through successfully and all values have their expected items
    • The command securedrop-admin localconfig completes successfully and SSH and SI/JI access still works
    • A backup can be taken via securedrop-admin backup, written to ~/.config/securedrop-admin
    • The backup can be restored via securedrop-admin restore <file>
    • The install playbook can be rerun successfully via securedrop-admin install

On an existing 2.12.10 Journalist Workstation:

  • Create a file `~/securedrop_bootstrap.env with contents:

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

  • cd ~/Persistent/securedrop and git checkout <RC tag under test>

  • run ./securedrop-admin setup, follow on-screen instructions, and verify that:

    • The package migration process starts and can be completed successfully
    • After the migration is complete, the securedrop-admin debian package has been installed
    • All required configuration files (JI and SI Tor connection files) have been copied to ~/.config/securedrop-admin

  • reboot the workstation and verify that:

    • The securedrop-admin package is installed automatically
    • config files are still available at ~/.config/securedrop-admin
    • The Securedrop menu is available with all expected items (SI and JI access, no updater entry)
    • The command securedrop-admin localconfig completes successfully and SSH and SI/JI access still works

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 2.13.0 following the migration process
  • After reboot, updater GUI no longer appears

Clone this wiki locally