Skip to content

0.13.0 Test plan

Jump to bottom
Kevin O'Gorman edited this page May 21, 2019 · 8 revisions

QA plan

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

0.13.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.13.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.13.0-specific changes as well as changes since the previous release candidate.

Note: if you are testing an upgrade scenario, you should create several sources and submit a large number of files of varying sizes up to the 500MB limit before performing the upgrade. A large dataset is required in order to test the long-running database migration task implemented in #4134.

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 (#4211)
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.13.0-specific changes

  • The message to sources that have been flagged for reply has been updated as implemented in #4428. Verify this by changing line 201 in /var/www/securedrop/source_app/main.py from if entropy_avail >= 2400: to if entropy_avail >= 2400 and False:, restarting Apache, creating a source, flagging the source in the Journalist Interface, and logging back in as the source.
  • When a user attempts to log in twice on the source interface, a single 500 error is returned and the user is logged out, as per #4391. Verify this by opening a browser tab and visiting /generate, then opening a second tab and logging in or creating a new codename via /create, then returning to the first tab and attempting to log in.
  • The sha256 checksum of a given encrypted submission or reply is returned as the ETag header value in API download responses, as per #4314:
    • Upgrade Only: BEFORE upgrade, run the QA loader (https://docs.securedrop.org/en/release-0.12.2/development/database_migrations.html#release-testing-migrations) and also upload a few very large files (~100 MB+). Following the postinst migration task, the checksum field in the submissions and replies tables is populated with the sha256 hash of the corresponding files. Verify this by checking the Application Servers sqlite database and comparing values.
    • After a submission has been uploaded and the checksum field has been asynchronously updated, the ETag header value in the response to an API request for a file contains the sha256 hash of the file. Verify this by comparing the ETag value of a response to the value in the database
    • Immediately after a large submission has been uploaded, before the checksum field has been updated, the Etag header value in the response to an API request for a file contains the sha256 hash of the file. Verify this by comparing the ETag value of a response to the sha256 hash of the encrypted submission.

(API-specific):

  • API responses to /api/v1/sources include the GPG fingerprint for sources' reply keys in their respective key objects, as implemented in #4436.
  • Calling /api/v1/logout invalidates the user's current authorization token, causing subsequent calls using the same token to fail, as implemented in #4349.
  • After the time set in TOKEN_EXPIRATION_MINS in securedrop/journalist_app/api.py, an unused authorization token is invalidated, causing subsequent calls to fail, as implemented in #4349. Verify this by setting TOKEN_EXPIRATION_MINS to a low value, restarting Apache, creating an auth token, and waiting for the timeout before using it in a call
  • API calls using the HTTP DELETE method to the /api/v1/sources/$UUID endpoint successfully delete the source with uuid $UUID, along with all related files, as implemented in #4023.

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

Tails

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