1.1.0 Test plan
mickael e edited this page Oct 17, 2019
·
6 revisions
- NUC5s
- NUC7s
- Mac Minis
- 1U servers in SF
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.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 1.1.0-specific changes as well as changes since the previous release candidate.
- Install target:
- Tails version (3.16 or 4.0 upgraded or 4.0 clean install):
- Test Scenario:
- SSH over Tor:
- Onion service version:
- Release candidate:
- General notes:
- 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
- Can successfully add admin user and login
- 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 1.0.0 and restore this backup on 1.1.0
- "Send Test OSSEC Alert" button in the journalist triggers an OSSEC alert and an email is sent.
- JS warning bar does not appear when using Security Slider high
- JS warning bar does appear when using Security Slider Low
- 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
- 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
- Can log in with 2FA tokens
- incorrect password cannot log in
- invalid 2fa token cannot log in
- 2fa immediate reuse cannot log in
- Filter by codename works
- Starring and unstarring works
- Click select all selects all submissions
- Selecting all and clicking "Download" works
- 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
After updating to this release candidate and running securedrop-admin tailsconfig
- The Updater GUI appears on boot
- Updating occurs without issue
- Tor version running is 0.4.1.6
- Running
manage.pyin/var/www/securedrop/returns a correct and ordered list of options
- cron-apt update was successful (if upgrade scenario)
Please remember to indicate whether you are using Tails 3.16 or Tails 4.0 in your test report, and indicate if you performed an upgrade of your admin workstation.
- ./securedrop-admin setup works as expected
- ./securedrop-admin sdconfig works as expected
- ./securedrop-admin install works as expected
- ./securedrop-admin tailsconfig works as expected
- ./securedrop-admin backup works as expected
- ./securedrop-admin restore works as expected
- Desktop icon is functional for Source and Journalist interfaces
- A spinning cursor is displayed when Source or Journalist icons are double-clicked
- Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
- ./securedrop-admin setup works as expected
- ./securedrop-admin sdconfig works as expected
- ./securedrop-admin install works as expected
- ./securedrop-admin tailsconfig works as expected
- ./securedrop-admin backup works as expected
- ./securedrop-admin restore works as expected
- Desktop icon is functional for Source and Journalist interfaces
- Reboot with no tails admin password (but persistence enabled) : Updater appears, when Update now is clicked a modal dialog displayed prompting user to reboot and set an admin password
- Upgrade case: Keepass database can be used/migrated in the new version of Keepass in Tails 4
- There are no new apparmor, ossec or other errors/messages in syslog or apache logs relevant to the new updated libraries
- (TBD, not yet merged) Czech and Slovak are displayed on the interface if enabled in SDCONFIG
We want to ensure the virtualenv transition when upgrading from Tails 3.x to Tails 4.x is handled by ./securedrop-admin
- Test plan from 4914 completes successfully
- 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
- Install or upgrade occurs without error
- Source interface is available and version string indicates it is 1.1.0
- A message can be successfully submitted
- The updater GUI appears on boot
- The update successfully occurs to 1.1.0
- After reboot, updater GUI no longer appears