Release SecureDrop 0.6.0 #3061

redshiftzero · 2018-02-22T23:08:22Z

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

Feature freeze: February 27, 2018
String freeze: March 6, 2018
Release date: March 13, 2018

SecureDrop maintainers and testers: As you QA 0.6, 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.6 milestone for tracking.

Test debian packages are 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.6~rc2)

Branch release/0.6 off master - @redshiftzero
0.6-rc1 was created but we did not build test debs as we needed to bump the kernels (Bumps securedrop-grsec metapackage to 4.4.115 #3077)
Prepare 0.6-rc2 tag - @redshiftzero
Build debs and put up 0.6~rc2 on test apt server - @conorsch

QA (0.6~rc2)

Test upgrade from 0.5.2 works on prod w/ test repo debs
Test fresh install (not upgrade) of 0.6 works on prod w/ test repo debs

Prepare next release candidate (0.6~rc3)

Prepare 0.6-rc3 tag - @redshiftzero
Build debs and put up 0.6~rc3 on test apt server - @conorsch

QA (0.6~rc3)

Test upgrade from 0.5.2 works on prod w/ test repo debs
Test fresh install (not upgrade) of 0.6 works on prod w/ test repo debs

Prepare next release candidate (0.6~rc4)

Prepare 0.6-rc4 tag - @redshiftzero
Build debs and put up 0.6~rc4 on test apt server - @conorsch

QA (0.6~rc4)

Test upgrade from 0.5.2 works on prod w/ test repo debs
Test fresh install (not upgrade) of 0.6 works on prod w/ test repo debs

Prepare final release candidate (0.6~rc5)

Prepare 0.6-rc5 tag - @redshiftzero
Build debs and put up 0.6~rc5 on test apt server - @conorsch

Final release

Push signed tag
Build final Debian packages for 0.6
Pre-Flight: Test install (not upgrade) of 0.6 works w/ prod repo debs
Publish blog post about 0.6 Debian package release and instructions for admins

Post-release

Merge release changes into master branch
Merge release changes into development branch

The text was updated successfully, but these errors were encountered:

ghost · 2018-02-24T12:06:36Z

It would be great to have detailed Q/A scripts that volunteers with a lot of good will but experience with SecureDrop could run manually. Do we have that already ?

redshiftzero · 2018-02-28T18:39:42Z

For getting setup with prod VMs for testing, this is the best documentation we have, and this post by @kushaldas is useful (version numbers will need bumping). In terms of QA scripts the most detailed generic (for any release) testing script we have is the following - it covers basic server testing and application acceptance testing:

A. Tests from the Admin Tails Drive

You should be able to access the source and journalist interfaces

Open up Tor browser and try it out on both interfaces

You should be able to SSH into app and mon over Tor

ssh app
ssh mon

OSSEC should start up

Execution steps:
- Check your email
Expected behavior:
- Check that OSSEC alerts were received
- Verify that you can decrypt the message

Check that both servers are running grsec kernels

Preconditions: You SSH into each server.
Execution steps:
- Run uname -a
Expected output:
- -grsec is in the kernel name

Verify AppArmor is loaded

Preconditions: You SSH into both servers.
Execution steps:
- Run sudo aa-status
Expected output:
- apparmor module is loaded appears in the output

Check iptables rules are set up

Preconditions: You SSH into each server.
Execution steps:
- Run sudo iptables-save
Expected output:
- iptables rules are printed to stdout
- The iptables output is dozens of lines, not just the default ACCEPT chains

B. Test Cases For Command Line User Creation

You can create a administrator from the command line.

Precondition: You are SSHed into app
Execution steps are described here.
Expected behavior:
- You are able to login using the account made at the command line
- Admin panel is available in journalist web interface

C. Test Cases for Source Interface

Precondition: You have used Tor Browser to navigate to the source interface.

Landing Page Base Cases

When the Tor Browser Security slider is at its lowest setting, a purple bar appears along the top of the application indicating that one should turn the security slider to high.
When the Tor Browser Security slider is at its highest setting, this bar does not appear.

First Submission Base Cases

Precondition: You have clicked “Submit Documents” on the home page.

On the generate page, clicking refresh changes the codename. 7 words appear before and after changing the codename.
On the submission page, clicking “Submit” with no documents or messages written generates an error message.
On the submission page, typing a message “test” and clicking “Submit” generates a “Success!” flashed message.
On the submission page, attempt to upload a file greater than 500 MB. This should not work and a “The Connection Was Reset” page should appear.
On the submission page, attempting to upload a file less than 500 MB results in a green success flashed message.

Returning Source Base Cases

Precondition: You have clicked “Check for a response” on the home page.

Entering an empty codename results in a “Sorry that is not a recognized codename” flashed message.
Entering a legitimate codename results in a source being able to successfully login.
On the submission page, journalist responses appear (one will need to be logged in).

D. Test Cases for Journalist Interface

Precondition: You have used Tor Browser to navigate to the journalist interface.

Login Base Cases

Username “test1” can successfully log in with their 2FA tokens.
If user “test1” uses an incorrect password, they get a “Login failed. Please wait for a new two-factor token before logging in again.” flashed message.
If “test1” tries to use an invalid 2FA token, they get a “Login failed. Please wait for a new two-factor token before logging in again.” flashed message.
If “test1” tries to use the same 2FA token, they get a “Login failed. Please wait for a new two-factor token before logging in again.” flashed message.

Index Base Cases

Precondition: You have used Tor Browser to navigate to the journalist interface and are logged in.

Filter by codename on index successfully filters
Click “select all” selects all submissions.
Selecting “Download All” results in all submissions being downloaded.
Starring a source successfully stars a source.
Unstarring a source successfully unstars a source.

Source Page Base Cases

Precondition: You have used Tor Browser to navigate to the journalist interface, logged in, and clicked on a given source.

You are able to type “Response” and hit “Submit” and get a “Thanks! Your reply has been stored” flashed message. A new row should appear ending in -reply.gpg.
You are able to click a document and download it. You can successfully decrypt the document using the submission private key.
You are able to submit an empty response and get a flashed message indicating that text needs to be entered.
Clicking “Delete collection” results in all documents being deleted for the given source.

Checklist

You can use this for copy/pasting into your QA report

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

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

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
You can click on a document and successfully decrypt using application private key

redshiftzero · 2018-02-28T18:49:48Z

redshiftzero · 2018-03-01T04:05:30Z

Fresh install `0.6~rc2` in prod VMs

0.6~rc2 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

ghost · 2018-03-01T11:02:06Z

There are commits to merge back to develop from yesterday's action.

$ git --no-pager  log --oneline --cherry-mark --right-only origin/develop...origin/release/0.6
+ 658088bb SecureDrop 0.6~rc2
+ e29bdd74 Merge pull request #3077 from freedomofpress/bump-grsec-metapackage-to-4.4-kernels
+ ab2a05e0 Updates config tests for new kernel image version
+ eb88a67b Updates docs for new kernel image version
+ a9c9643b Bumps securedrop-grsec metapackage to 4.4.115
+ 898690ed SecureDrop 0.6~rc1

Proposed at #3061

ghost · 2018-03-01T11:07:52Z

I see we are creating 0.6 packages and tags. Could we please switch to using 0.6.0 instead? So we have a uniform naming scheme.

msheiny · 2018-03-01T16:08:33Z

So I thought this was important ... but I just performed an upgrade and confirmed that the old 3.14.79-grsec kernel was still in the boot menu. This is important so if any instances have issues they can roll back temporarily.

msheiny · 2018-03-01T18:10:30Z

Upgrade install `0.6~rc2` in prod VMs

0.6~rc2 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

emkll · 2018-03-01T18:26:15Z

Fresh install `0.6~rc2` in prod VMs

Everything looks good in clean install, will be testing upgrade path in VMs next.

0.6~rc2 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

Other:

ls /boot does not contain any non-grsec kernls

kushaldas · 2018-03-01T18:55:00Z

Update from '0.5.2' to `0.6~rc2` in prod VMs

0.6~rc2 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

ghost · 2018-03-02T14:44:32Z

Only cherry-picks in the release/0.6 as shown by the = sign which indicates the commits that are both in develop and release/0.6 and have the same patch-id.

$ git --no-pager  log  --no-merges --oneline --cherry-mark --right-only origin/develop...origin/release/0.6
= 4ec882bb Monitor only hostname in /var/lib/tor/services
= 1b67299b journalist: kindly ask to check the mail

emkll · 2018-03-02T14:47:11Z

Upgrade from `0.5.2` to `0.6~rc2` on physical install

0.6~rc2 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

Getting some unecessary OSSEC emails (which appear unrelated to this release):



OSSEC HIDS Notification.
2018 Mar 02 04:11:18

Received From: (app) 10.20.2.2->/var/log/syslog
Rule: 100003 fired (level 7) -> "A cron-apt warning was detected"
Portion of the log(s):

Mar  2 04:11:16 app cron-apt: W: Duplicate sources.list entry https://tor-apt.freedom.press/ trusty/main amd64 Packages (/var/lib/apt/lists/tor-apt.freedom.press_dists_trusty_main_binary-amd64_Packages)



 --END OF NOTIFICATION



OSSEC HIDS Notification.
2018 Mar 02 04:11:18

Received From: (app) 10.20.2.2->/var/log/syslog
Rule: 100003 fired (level 7) -> "A cron-apt warning was detected"
Portion of the log(s):

Mar  2 04:11:16 app cron-apt: W: Duplicate sources.list entry https://tor-apt.freedom.press/ trusty/main i386 Packages (/var/lib/apt/lists/tor-apt.freedom.press_dists_trusty_main_binary-i386_Packages)



 --END OF NOTIFICATION

redshiftzero · 2018-03-03T04:10:40Z

Upgrade 0.5.2 -> `0.6-rc3` in prod VMs

0.6~rc3 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

kushaldas · 2018-03-12T18:08:47Z

Upgrade 0.6-rc3 -> `0.6-rc4` in prod VMs

0.6~rc4 specific testing

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

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 collection" and the source and docs are deleted
You can click on a document and successfully decrypt using application private key

emkll · 2018-03-13T14:15:38Z

I have tested the kernel metapackage changes as part of 0.6-rc5

Classic upgrade scenario (pre-Feb 16) 0.5.2 -> 0.6:

[x] Kernel 3.14.79-grsec is installed
[x] Kernel 4.4.115-grsec is installed
[x] Kernel 4.4.115-grsec boots by default

Alternate upgrade scenario (SD instance installed after Feb 16) 0.5.2 -> 0.6:

[x] Kernel 3.14.79-grsec is installed
[x] Kernel 4.4.115-grsec is installed
[x] Kernel 4.4.115-grsec boots by default
❗ linux 4.4.0-116-generic is installed, but does not boot by default (4.4.115>4.4.0)

eloquence · 2018-03-16T21:23:48Z

SecureDrop 0.6 went out as planned on March 13, closing. :)

redshiftzero added this to the 0.6 milestone Feb 22, 2018

ghost mentioned this issue Mar 1, 2018

merge back 0.6 into develop 2018-03-01 #3083

Merged

redshiftzero changed the title ~~Release SecureDrop 0.6~~ Release SecureDrop 0.6.0 Mar 1, 2018

eloquence closed this as completed Mar 16, 2018

emkll mentioned this issue Apr 25, 2018

Release SecureDrop 0.7.0 #3307

Closed

21 tasks

redshiftzero mentioned this issue May 15, 2018

[QA] Tails GUI updater reporting new versions #3426

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Release SecureDrop 0.6.0 #3061

Release SecureDrop 0.6.0 #3061

redshiftzero commented Feb 22, 2018 •

edited

Loading

ghost commented Feb 24, 2018

redshiftzero commented Feb 28, 2018 •

edited

Loading

redshiftzero commented Feb 28, 2018

redshiftzero commented Mar 1, 2018

ghost commented Mar 1, 2018

ghost commented Mar 1, 2018

msheiny commented Mar 1, 2018

msheiny commented Mar 1, 2018 •

edited

Loading

emkll commented Mar 1, 2018 •

edited

Loading

kushaldas commented Mar 1, 2018

ghost commented Mar 2, 2018 •

edited by ghost

Loading

emkll commented Mar 2, 2018 •

edited

Loading

redshiftzero commented Mar 3, 2018

kushaldas commented Mar 12, 2018

emkll commented Mar 13, 2018 •

edited

Loading

eloquence commented Mar 16, 2018

Release SecureDrop 0.6.0 #3061

Release SecureDrop 0.6.0 #3061

Comments

redshiftzero commented Feb 22, 2018 • edited Loading

Prepare release candidate (0.6~rc2)

QA (0.6~rc2)

Prepare next release candidate (0.6~rc3)

QA (0.6~rc3)

Prepare next release candidate (0.6~rc4)

QA (0.6~rc4)

Prepare final release candidate (0.6~rc5)

Final release

Post-release

ghost commented Feb 24, 2018

redshiftzero commented Feb 28, 2018 • edited Loading

A. Tests from the Admin Tails Drive

B. Test Cases For Command Line User Creation

C. Test Cases for Source Interface

Landing Page Base Cases

First Submission Base Cases

Returning Source Base Cases

D. Test Cases for Journalist Interface

Login Base Cases

Index Base Cases

Source Page Base Cases

Checklist

Basic Server Testing

Command Line User Generation

Application Acceptance Testing

Source Interface

Landing page base cases

First submission base cases

Returning source base cases

Journalist Interface

Login base cases

Index base cases

Individual source page

redshiftzero commented Feb 28, 2018

redshiftzero commented Mar 1, 2018

Fresh install 0.6~rc2 in prod VMs

0.6~rc2 specific testing

Basic Server Testing

Command Line User Generation

Application Acceptance Testing

Source Interface

Landing page base cases

First submission base cases

Returning source base cases

Journalist Interface

Login base cases

Index base cases

Individual source page

ghost commented Mar 1, 2018

ghost commented Mar 1, 2018

msheiny commented Mar 1, 2018

msheiny commented Mar 1, 2018 • edited Loading

Upgrade install 0.6~rc2 in prod VMs

0.6~rc2 specific testing

Basic Server Testing

Command Line User Generation

Application Acceptance Testing

Source Interface

Landing page base cases

First submission base cases

Returning source base cases

Journalist Interface

Login base cases

Index base cases

Individual source page

emkll commented Mar 1, 2018 • edited Loading

Fresh install 0.6~rc2 in prod VMs

0.6~rc2 specific testing

Basic Server Testing

Command Line User Generation

Application Acceptance Testing

Source Interface

Landing page base cases

First submission base cases

Returning source base cases

Journalist Interface

redshiftzero commented Feb 22, 2018 •

edited

Loading

redshiftzero commented Feb 28, 2018 •

edited

Loading

Fresh install `0.6~rc2` in prod VMs

msheiny commented Mar 1, 2018 •

edited

Loading

Upgrade install `0.6~rc2` in prod VMs

emkll commented Mar 1, 2018 •

edited

Loading

Fresh install `0.6~rc2` in prod VMs

Update from '0.5.2' to `0.6~rc2` in prod VMs

ghost commented Mar 2, 2018 •

edited by ghost

Loading

emkll commented Mar 2, 2018 •

edited

Loading

Upgrade from `0.5.2` to `0.6~rc2` on physical install

Upgrade 0.5.2 -> `0.6-rc3` in prod VMs

Upgrade 0.6-rc3 -> `0.6-rc4` in prod VMs

emkll commented Mar 13, 2018 •

edited

Loading