Skip to content

0.12.0 Test plan

Jump to bottom
Erik Moeller edited this page Feb 19, 2019 · 12 revisions

QA plan

  • NUCs
  • Mac Minis
  • 1U servers in SF

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

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

0.12.0-specific changes

  • The operating system warning implemented in #4055 appears on Trusty if XENIAL_WARNING_DATE in the journalist app is set to the current date on the app server.
  • Keys generated for new sources no longer leak expiration dates, and will have a creation date of May 14, 2013. Verify this by inspecting the keyring on the application server after creation of a new source. (See #3994 for background.)
  • After enabling logging in the Apache config on the sources interfaces, a single submit-download-reply flow from source to journalist and back produces no errors in /var/log/apache2/*
  • There are no AppArmor denials in /var/log/kern.log (and no new warnings)
  • There are no new and unexpected logs in /var/ossec/logs/ossec.log and /var/ossec/logs/alerts/alerts.log
  • On a Trusty system that used cron-apt to install the latest packages, the OSSEC alerts point to securedrop.org documentation and do not say to use do-release-upgrade
  • Tor version installed on app and mon is 0.3.5.7 (on Xenial) or 0.3.4.9 (on Trusty)
  • grsec kernel version 4.4.167 is running

Lower priority:

  • API responses should no longer include the Set-Cookie and Vary: Cookie headers as described in #3876 and implemented in #3941
  • An API consumer should be able to set a reply UUID as described in #3957 and implemented in #3958
  • Creating a reply through the API should result in a response including the reply's filename as described in #4057 and implemented in #4052
  • Creating an auth token through the API should result in a response including the journalist's UUID as described in #4081 and implemented in #4088
  • Immediately fetching a source's public key after it was created should not return all source public keys, as described in #4005 and resolved in #4009 (note that this needs to be immediate, as in < 2 seconds)

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

Tails

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