Skip to content

2.11.0 Test Plan

Jump to bottom
Kevin O'Gorman edited this page Dec 11, 2024 · 4 revisions

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

Environment

  • Install target:
  • Tails version:
  • Test Scenario:
  • SSH over Tor?:
  • Tor PoW enabled?:
  • 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.10.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

(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.11.0 release-specific changes

Noble prep (misc PRs)

  • Verify that ufw and haveged are not installed on either server
  • Verify that sdssh user group exists containing SD admin acccount, and that the ssh group is empty, on both servers

Check script and banner (#7334, #7363, 7348)

  • After installation and reboot, verify that a file /etc/securedrop-noble-migration.json has been created on the application server
  • Install the ufw package on the application server and run sudo /usr/bin/securedrop-noble-migration-check - verify that the ufw value in the json file is now False
  • Run sudo systemctl start securedrop-remove-packages and then run sudo /usr/bin/securedrop-noble-migration-check again - verify that the ufw value in the json file is now False
  • Edit the json file and ensure at least one value is false; then run sudo systemctl restart apache2 to restart the JI
  • Log into the JI and verify that a banner is displayed with the Noble readiness warning message
  • Edit the json file again, flipping all values to True and restart the JI with sudo systemctl restart apache2
  • Log into the JI and verify that the banner is not displayed
  • In /var/www/securedrop/server_os.py, set FOCAL_ENDOFLIFE to a past date; and restart the JI with sudo systemctl restart apache2
  • Log into the JI and verify that a banner is displayed with the Focal EOL warning message
  • In /var/www/securedrop/server_os.py, reset FOCAL_ENDOFLIFE to its original value; and restart the JI with sudo systemctl restart apache2

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 2.11.0
  • After reboot, updater GUI no longer appears
Clone this wiki locally