Skip to content

2.9.0 Test Plan

Jump to bottom
Kevin O'Gorman edited this page Jun 13, 2024 · 4 revisions

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

Note that this release includes changes to the server configuration to enable Tor PoW - you should complete the relevant test plan section while performing the installation or upgrade.

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.8.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.9.0 release-specific changes

Tor PoW defense #7175

  • Install onionprobe on the admin workstation if not already present
Fresh install
  • when running ./securedrop-admin sdconfig, confirm that the option to enable PoW defense is available - choose to enable it
  • run ./securedrop-admin install and `./securedrop-admin tailsconfig and confirm:
    • both commands completed successfully
    • all Tor hidden services are available
    • onionprobe -e <si address> confirms that PoW is enabled for the source interface
Upgrade

  • after completing the upgrade procedure on the servers and admin workstation:

  • run ./securedrop-admin sdconfig and confirm that the option to enable PoW defense is available - choose to enable it

  • run ./securedrop-admin install and confirm:

    • all Tor hidden services are available
    • onionprobe -e <si address> confirms that PoW is enabled for the source interface

  • run ./securedrop-admin sdconfig again and disable PoW defense

  • run ./securedrop-admin install and confirm:

    • all Tor hidden services are available
    • onionprobe -e <SI address> confirms that PoW is not enabled for the source interface

Update release key expiry #7167

  • after installation or upgrade, verify that the key in /etc/apt/trusted.gpg.d/securedrop-keyring.gpg is the SecureDrop signing key with an expiry of 2027-05-24

API range request support #7160

  • set up a journalist user via the JI
  • install jq in Tails with sudo apt install jq
  • From a terminal, get an API token with a command like: curl -X POST -H "Content-Type: application/json" -d '{"username": "<journalist_name>", "passphrase": "<passphrase>", "one_time_code": "<code"}' http://<JI address>/api/v1/token
  • extract the token from the response and store it in an env var, e.g TOKEN=<token_string>
  • Get the submission and download URL for a file submission: 
    SUBMISSION_URL=$(curl -H "Authorization: Token $TOKEN" http://<JI address>/api/v1/sources | jq -r '.sources[-1].submissions_url')
DOWNLOAD_URL=$(curl -H "Authorization: Token $TOKEN" http://<JI address>$SUBMISSION_URL | jq -r '.submissions[0].download_url')
  • verify that you can download the full submission: curl -v -H "Authorization: Token $TOKEN" -o logo.png.gpg http://<JI_address>$DOWNLOAD_URL
  • verify that you can download the first 100 bytes of the submission: curl -v -H "Authorization: Token $TOKEN" -H "Range: bytes=0-99" -o logo.png.gpg.part-0-99 http://l<JI_address>$DOWNLOAD_URL
  • Verify that the first 100 bytes of the original submission has the same sha256 hash as the partial download.

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

Tails

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