confusa

For each release (starting with v0.4), a set of tests will be performed before the final release is tagged. The list should be formatted as a test-matrix (use the numbering to make the table more compact), and only when everything is green should a new release be tagged and released.

Normal operations for each type of user (NREN-admin, Subscriber-admin, subscriber-subadmin, user)

1. User:

1. Create new certificate (CSR paste, CSR upload, browser signing)
2. Listing of certificates (are all ordered and valid certs listed, can they be inspected etc.)
3. Download and mail reception of certificates
4. Revoke certificate

2. NREN-Admin:

1. Mass revoke
2. Settings (need sublevels on this)
3. Manage admins
4. Manage Subscribers
5. Map

3. Subscriber Admin:

1. RI, upload cert
2. RI, list certs
3. Manage admins
4. Revoke certs
5. Map

4. Notification logic

1. Does the new-cert mail work as expected
2. Content of notification mail (the template) work properly
3. Severe warnings sent via email to operations
4. Help-info for subscribers displayed properly to users

5. Robotic Interface

1. library works as expected
2. Correct list of issued certificates are returned
3. Revocation works

6. Nagios and self-diagnosis:

1. Testcases cover everything (include list of nagios-tests performed)
2. Reset severe warnings

7. Does installation work seamlessly?

1. Are all config options and DB tables covered in the installation scripts?
2. If possible, test to deploy an instance of the new Confusa version from scratch, for instance in a Virtual machine.

8. Are all pages displayed as inteded? (including all subpages, substates etc). Test for supported browsers to catch xhtml-oddities.

1. User is not authenticated
2. User is authenticated.