2.1.0 Test Plan

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

If you are testing the upgrade scenario, you should create source and journalist accounts before performing the upgrade - some test cases require existing accounts.

In order to test #5988 you will need to enable HTTPS on the source interface. To do so using self-signed certs:

Use the command cd ~/Persistent/securedrop && make self-signed-https-certs on the Admin Workstation to generate the necessary files
Choose the appropriate options while running ./securedrop-admin sdconfig
Accept the self-signed cert when prompted with the HTTPS warning in Tor Browser.

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

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly