Skip to content

2.6.0 Test Plan

Jump to bottom
Kevin O'Gorman edited this page Jun 13, 2023 · 2 revisions

2.6.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:
  • 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.5.2 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.6.0 release-specific changes

  • #6657 - switch to argon2id hashes

    • Upgrade only Before upgrading, create a journalist or admin account
    • Upgrade only After upgrading, verify that existing journalist accounts can still log in
    • Verify that new journalist accounts can log in
    • In the application db, verify that all journalist account password hashes start with '$argon2id$...'

  • #6681 - remove i18n globals

    • in SI, locale switcher works as expected
    • In JI, locale switcher works as expected

  • #6738 - add descriptive titles

    • SI pages have descriptive titles based on the pages' main headers
    • JI pages have descriptive titles based on the pages' main headers

  • #6768 - update CSP policy

    • In the SI, the Cross-Origin-Resource-Policy header is set with value same-origin
    • In the JI, the Cross-Origin-Resource-Policy header is set with value same-origin

  • #6826 - remove stale pending sources

    • On the app server, generate more than 100 pending sources using eg:

      sudo -u www-data bash
cd /var/www/securedrop/
./loaddata.py --source-count 110 --files-per-source 0 --messages-per-source 0 --replies-per-source 0

    • Trigger the removal service with sudo systemctl start securedrop-remove-pending-sources.service

    • Verify that only 100 pending sources remain in the database

  • #6712 - add a Gnome shell extension

    • Fresh install only After running ./securedrop-admin tailsconfig, verify that:

      • The playbook message directs you to reboot
      • After rebooting, a SecureDrop menu is available in the top menubar including options to access the SI and JI, SSH to servers, access the Persistent directory, and start KeePassXC
      • after setting up a Journalist Workstation and rebooting, the same menu and options are available with the exception of the SSH options.

    • Upgrade only Upgrade the Tails Workstation to the latest RC by running the following commands in a terminal:

      cd Persistent/securedrop
git checkout 2.6.0-rcN   # Where N is latest version
./securedrop-admin setup
./securedrop-admin tailsconfig

    • verify that:

      • The tailsconfig playbook message directs you to reboot
      • After rebooting, a SecureDrop menu is available in the top menubar including options to access the SI and JI, SSH to servers, access the Persistent directory, and start KeePassXC
      • after setting up a Journalist Workstation and rebooting, the same menu and options are available with the exception of the SSH options.

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

Tails

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