Skip to content

1.0.0 Test Plan

Jump to bottom
Kushal Das edited this page Sep 3, 2019 · 9 revisions

QA plan

  • NUC5s
  • NUC7s
  • Mac Minis
  • 1U servers in SF

1.0.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. Feel free to edit this message to update the plan as appropriate.

If you have submitted a QA report already for a 1.0.0 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 1.0.0-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

  • I can access both the source and journalist interfaces
  • I can SSH into both machines over Tor
  • AppArmor is loaded on app
    • 0 processes are running unconfined
  • AppArmor is loaded on mon
    • 0 processes are running unconfined
  • Both servers are running grsec kernels
  • iptables rules loaded
  • OSSEC emails begin to flow after install
  • OSSEC emails are decrypted to correct key and I am able to decrypt them
  • 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 documentation here: https://docs.securedrop.org/en/latest/backup_and_restore.html
  • If doing upgrade testing, make a backup on 0.13.1 and restore this backup on 0.14.0
  • "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.

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 codename 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
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 And Submissions" and the source and docs are deleted
  • You can click on a document and successfully decrypt using application private key

Basic Tails Testing

Updater GUI

After updating to this release candidate and running securedrop-admin tailsconfig

  • The Updater GUI appears on boot
  • Updating occurs without issue

1.0.0-specific changes

From a 0.14.0 install:

  • rerun ./securedrop-admin sdconfig to enable v2 and v3 onion services, and then do ./securedrop-admin install, check if the source and journalist desktop shortcuts has working v3 onion address. Also, check that the old v2 addresses are also working ssh over lan

  • rerun ./securedrop-admin sdconfig to enable only v3 onion services, and then do ./securedrop-admin install, check if the source and journalist desktop shortcuts has working v3 onion address. (#4708, $4677) ssh over lan

  • rerun ./securedrop-admin sdconfig to enable v2 and v3 onion services, and then do ./securedrop-admin install, check if the source and journalist desktop shortcuts has working v3 onion address. Also, check that the old v2 addresses are also working ssh over Tor

  • rerun ./securedrop-admin sdconfig to enable only v3 onion services, and then do ./securedrop-admin install, check if the source and journalist desktop shortcuts has working v3 onion address. (#4708, $4677) ssh over Tor

  • If the system has https enabled, when one enables v3 onion service via sdcofnig, it should show an warning to the user

  • Check that both app and mon servers are running 0.4.x services to Tor (#4658).

  • Login as a journalist, and via another admin account reset the password of the journalist, this should invalidate the journalist session, and the journalist must relogin (#4679)

TODO: Have to add test steps for source deletion and old submission deletion

Preflight

  • Ensure the builder image is up-to-date on release day

These tests should be performed the day of release prior to live debian packages on apt.freedom.press

Basic testing

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

Tails

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