Skip to content

2.3.1 Test Plan

Jump to bottom
Kevin O'Gorman edited this page Apr 8, 2022 · 2 revisions

2.3.1 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 2.3.1 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

Administration

  • I have backed up and successfully restored the app server following the backup documentation
  • If doing upgrade testing, make a backup on 2.3.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

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
  • Updating to 2.3.0 is successful

2.3.1 release-specific changes

  • #6377 allow GET and POST methods for /generate

    • Visit the SI and verify that:
      • you can navigate normally to /generate via the GET STARTED link
      • if you reload the /generate page, it asks to resubmit POST data, and generates a new codemame
      • if you choose another language in the dropdown the /gnerate page reloads without prompting for the POST resubmit and generates a new codename

  • in Tor Browser with the security level set to safest, visit the SI via a tor2web proxy, and click GET STARTED

    • Confirm that the /generate page is not displayed and the tor2web warning page is displayed instead.

  • #6390 Remove trustdb checks in python-gnupg GPG commands

    • Log on to the application server with ssh app and use loaddata.py to add between 10k and 20k sources.
    • As the www-data user on the application server, run while true; do grep "g[p]g2"<<<$(ps axwww); sleep 1; done. While this script is running:
      • Add a new user in the SI and confirm that the page render does not time out, and that gpg2 commands complete quickly (~3sec max) and include the --no-auto-check-trustdb option
      • Submit a message and confirm that the page render does not time out, and that gpg2 commands complete quickly and include the --no-auto-check-trustdb option
      • Log into the JI and reply to the source, confirming that the page render does not time out, and that gpg2 commands complete quickly and include the --no-auto-check-trustdb option
      • Log into the SI as the original source and confirm that the reply is visible, the page renders without timouts, and gpg2 commands complete quickly with the option as per above
      • In the JI, download and decrypt the source's message, confirming that it can be successfully decrypted.
      • In the JI, delete the source account and confirm that deletion is successful, and that gpg2 commands complete quickly and include the --no-auto-check-trustdb option

Preflight testing

Basic testing

  • Install or upgrade occurs without error
  • Source interface is available and version string indicates it is 2.3.1
  • A message can be successfully submitted

Tails

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