Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release SecureDrop 0.10.0 #3849

Closed
24 tasks done
redshiftzero opened this issue Oct 5, 2018 · 11 comments
Closed
24 tasks done

Release SecureDrop 0.10.0 #3849

redshiftzero opened this issue Oct 5, 2018 · 11 comments
Milestone
0.10.0

Comments

@redshiftzero
Copy link
Contributor

redshiftzero commented Oct 5, 2018 •
edited
Loading

This is a tracking issue for the upcoming release of SecureDrop 0.10.0 - tasks may get added or modified.

Feature freeze: October 9, 2018
String freeze: October 16, 2018
Pre-release announcement: October 16, 2018
Release date: October 23, 2018

SecureDrop maintainers and testers: As you QA 0.10.0, please report back your testing results as comments on this ticket. File GitHub issues for any problems found, tag them "QA: Release", and associate them with the 0.10.0 milestone for tracking (or ask a maintainer to do so).

Test debian packages will be posted on https://apt-test.freedom.press signed with the test key. An Ansible playbook testing the upgrade path is here.

Prepare release candidate (0.10.0~rc1)

  • Prepare 0.10.0-rc1 release changelog - @redshiftzero
  • Branch off 0.10.0~rc1 into release/0.10.0 - @redshiftzero
  • [skipped] Build debs (including new Tor package) and put up 0.10.0~rc1 on test apt server

We merged in two important fixes prior to building debs for rc1 so stopped here

Prepare release candidate (0.10.0~rc2)

Prepare release candidate (0.10.0~rc3)

  • Prepare 0.10.0-rc3 release changelog - @redshiftzero
  • Prepare test plan for 0.10.0~rc3 - @emkll
  • Push 0.10.0-rc3 tag - @redshiftzero
  • Build debs and put up 0.10.0~rc3 on test apt server - @emkll

Prepare release candidate (0.10.0~rc4)

[we will add checklists for rc5 release candidates and later as we proceed through the release process]

Test plan to be posted during business hours Pacific time on Wednesday, October 10th.

QA Matrix for 0.10.0

Test Plan for 0.10.0

After each test, please update the QA matrix and post details for Basic Server Testing, Application Acceptance Testing and 0.10.0-specific testing below in comments to this ticket.

Final release

  • Ensure builder in release branch is updated and/or update builder image - @emkll or @msheiny
  • Merge final translations - @kushaldas
  • Push signed tag - @redshiftzero
  • Build final Debian packages for 0.10.0 - @conorsch
  • Upload Debian packages (including new linux-image, linux-firmware, and tor packages) to apt test - @conorsch
  • Pre-Flight: Test install and upgrade of 0.10.0 works w/ prod repo debs, test updater logic in Tails - @zenmonkeykstop
  • Write and send release announcement - @eloquence
  • Publish blog post about 0.10.0 Debian package release and instructions for admins - @eloquence

Post release

  • Merge changelog (i.e. rc commits) back to develop - @redshiftzero
  • Bump version on develop in prep for 0.11.0 release - @redshiftzero
@redshiftzero redshiftzero added this to the 0.10.0 milestone Oct 5, 2018
@eloquence eloquence mentioned this issue Oct 5, 2018
Closed
@zenmonkeykstop
Copy link
Contributor

Note to self (and others wishing to test upgrade path on HW) - ansible playbook to set instance up to use apt-test. instead of apt. is here:
https://gist.github.com/conorsch/e7556624df59b2a0f8b81f7c0c4f9b7d

@zenmonkeykstop
Copy link
Contributor

zenmonkeykstop commented Oct 16, 2018 •
edited
Loading

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

Environment

  • Install target: prod VMs
  • Tails version: 3.9.1
  • Test Scenario: Clean install
  • SSH over Tor: enabled
  • Release candidate: 0.10.0~rc2
  • General Notes: OSSEC emails not checked for VMs, will test on HW

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
  • AppArmor is loaded on mon
  • Both servers are running grsec kernels
  • iptables rules loaded
  • OSSEC emails begin to flow after install NOT TESTED
  • OSSEC emails are decrypted to correct key and I am able to decrypt them NOT TESTED

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 all" works There is no Download all
Individual source page
  • You can submit a reply and a flashed message and new row appears
  • You cannot submit an empty reply
  • Clicking "Delete collection" and the source and docs are deleted it's Delete Source And Submissions
  • You can click on a document and successfully decrypt using application private key NOT TESTED`

Basic Tails Testing

Updater GUI

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

  • The Updater GUI appears on boot FAILED ~/Persistent/securedrop not mounted on boot in Tails VM
  • Updating occurs without issue FAILED

0.10.0-specific changes

Preflight

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 0.10.0
  • After reboot, updater GUI no longer appears

@zenmonkeykstop
Copy link
Contributor

zenmonkeykstop commented Oct 17, 2018 •
edited
Loading

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

Environment

  • Install target: 2014 Mac Mini
  • Tails version: 3.9.1
  • Test Scenario: clean install
  • SSH over Tor: enabled
  • Release candidate: 0.10.0-rc2
  • 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
  • AppArmor is loaded on mon
  • 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

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 after ensuring there were no staged changes

0.10.0-specific changes

Preflight

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 0.10.0
  • After reboot, updater GUI no longer appears

This was referenced Oct 17, 2018
Closed
Closed
@emkll
Copy link
Contributor

emkll commented Oct 17, 2018 •
edited
Loading

0.10.0 QA Checklist (Completed)

Environment

  • Install target: Intel NUC5PYH
  • Tails version: 3.9
  • Test Scenario: clean install
  • SSH over Tor: disabled
  • Release candidate: 0.10.0-rc2

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
  • AppArmor is loaded on mon
  • 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

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 after ensuring there were no staged changes

0.10.0-specific changes

@robzim
Copy link

robzim commented Oct 17, 2018 via email

@zenmonkeykstop
Copy link
Contributor

@robzim 🤞

@zenmonkeykstop
Copy link
Contributor

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

Environment

  • Install target: 2014 Mac Minis
  • Tails version: 3.9.1
  • Test Scenario: 0.9.1->0.10.0 upgrade
  • SSH over Tor: enabled
  • Release candidate: 0.10.0~rc2
  • General notes: app and mon downgraded to 3.14.79 before upgrade

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
  • AppArmor is loaded on mon
  • 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

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.10.0-specific changes

Preflight

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 0.10.0
  • After reboot, updater GUI no longer appears

@zenmonkeykstop
Copy link
Contributor

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

Environment

  • Install target: Intel NUCs
  • Tails version: 3.9.1
  • Test Scenario: upgrade from 0.9.1
  • SSH over Tor: enabled
  • Release candidate: 0.10.0~rc3
  • 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
  • AppArmor is loaded on mon
  • 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

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.10.0-specific changes

0.10.0-rc3-specific changes

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 0.10.0
  • After reboot, updater GUI no longer appears

@conorsch
Copy link
Contributor

0.10.0 QA Checklist

Performed a limited upgrade test on two (2) 1U form-factor servers, specifically to confirm upgrade to latest kernel from rolled back kernel (3.14.79-grsec). Testing was a success. Did not perform the general application testing steps, since those are well covered already by the reports above.

Environment

  • Install target: Dell PowerEdge R620 (for app), HP ProLiant DL385 G7 (for mon)
  • Tails version: 3.9.1
  • Test Scenario: upgrade from 0.9.1
  • SSH over Tor: enabled
  • Release candidate: 0.10.0~rc3
  • 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
  • AppArmor is loaded on mon
  • 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

Relevant terminal output

For validating kernel -> downgrade -> upgrade process. Manually activated virtualenv, then ran through a few steps for informative output. Confirming the latest kernels are running on 0.9.1:

(.venv) amnesia@amnesia:~/Persistent/securedrop/install_files/ansible-base$ ansible all -a 'uname -r'
app | SUCCESS | rc=0 >>
4.4.144-grsec

mon | SUCCESS | rc=0 >>
4.4.144-grsec

Display hardware type for each server, to aid debugging if problems arise:

(.venv) amnesia@amnesia:~/Persistent/securedrop/install_files/ansible-base$ ansible all -m setup -a filter=ansible_product_name -b
app | SUCCESS => {
    "ansible_facts": {
        "ansible_product_name": "PowerEdge R620"
    }, 
    "changed": false
}
mon | SUCCESS => {
    "ansible_facts": {
        "ansible_product_name": "ProLiant DL385 G7"
    }, 
    "changed": false
}

Followed the docs and manually rolled back both servers to 3.14.79-grsec. Worked:

(.venv) amnesia@amnesia:~/Persistent/securedrop/install_files/ansible-base$ sleep 300 && ansible all -a 'uname -r'
app | SUCCESS | rc=0 >>
3.14.79-grsec

mon | SUCCESS | rc=0 >>
3.14.79-grsec

Ran QA playbook, cron-apt command, then rebooted via CLI to test the kernel update procedure.

(.venv) amnesia@amnesia:~/Persistent/securedrop/install_files/ansible-base$ ansible all -a 'uname -r'
app | SUCCESS | rc=0 >>
4.4.144-grsec

mon | SUCCESS | rc=0 >>
4.4.144-grsec

Success!

@emkll
Copy link
Contributor

emkll commented Oct 23, 2018 •
edited
Loading

0.10.0-rc4 (Completed)

Environment

  • Install target: NUC 5PYH
  • Tails version: 3.9
  • Test Scenario: Upgrade from 0.9.1
  • SSH over Tor: Yes
  • Release candidate: rc4
  • General notes: Downgraded kernels to 3.14 prior to updating using /etc/default/grub

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
  • AppArmor is loaded on mon
  • 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

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.10.0-specific changes

0.10.0-rc3-specific changes

0.10.0-rc4-specific changes

@zenmonkeykstop
Copy link
Contributor

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

Environment

  • Install target: 2014 Mac Mini
  • Tails version: 3.9.1
  • Test Scenario: upgrade from 0.9.1
  • SSH over Tor: enabled
  • Release candidate: 0.10.0-rc4
  • 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
  • AppArmor is loaded on mon
  • 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

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.10.0-specific changes

0.10.0-rc3-specific changes

0.10.0-rc4-specific changes

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

Tails

  • The updater GUI appears on boot
  • The update successfully occurs to 0.10.0
  • After reboot, updater GUI no longer appears

@redshiftzero redshiftzero mentioned this issue Oct 23, 2018
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.10.0
Development

No branches or pull requests
5 participants
@conorsch @zenmonkeykstop @redshiftzero @robzim @emkll