This repository has been archived by the owner on May 11, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 32
Regression Checks
DC edited this page Nov 3, 2013
·
1 revision
Here are some quick checks that will catch a lot of bugs.
Remember that the testing site, gpgmail.io auto updates has the latest commit on the master
branch. The main site, scramble.io auto updates to the latest commit on production
. We can do these checks on gpgmail.io before every push to production.
- Are your emails and contacts still there? Does everything look right? This step is especially important if there were DB migrations.
- Try using an existing username. Then, try new username but with a short password. Do the error messages look right?
- Finish creating a new account. You should have an empty Inbox, empty Sent, empty Contacts except for a single contact ("me").
- Send an unencrypted email (eg to your gmail address), then reply. Does the thread look right?
- Send an encrypted email to a different scramble server (eg from gpgmail.io to scramble.io), then reply.
- Send an encrypted email to yourself, then reply.
- Try a few of the keyboard shortcuts.
- Add a contact from the Contacts page.
- Go to an email thread, then add one of the addresses as a contact from there.
Together with unit tests, this will help us keep Scramble robust.