Items for Acceptance Testing

Here is a in-progress list of items that we should ensure we are testing for:

Regression Tests

* [ ] Avatars persist across updates

• "Code" is renamed as "Files" in top left tab of repo, with a font awesome file icon
• Options not available if not logged in: explore
• Options available if logged in: explore
• Logged out users not able to view private repos
• Access to private repos is restricted
• CC BY-SA box checked by default on new repo creation
• License file is created in new repos as LICENSE.md with correct CC BY-SA text
• Google Analytics code present
• Webhook(s) are trigged on push and/or web editor commit
• TOC yaml files link to the correct places within the repo
• Create private repo option disabled for regular users (unless user is an admin)
• Admin is able to delete a user
• Preview tab in the repo home page for viewing on Door43

* [ ] Hashtag feature * [ ] Hashtagged items appear as links on pages * [ ] /hashtag tab and location appear on 'ubn' and 'ubc' repos * [ ] Disambiguation pages work

Acceptance Tests

• Any user can fork from any public repo
• Any user can create a PR for any public repo
• Emails are sent to appropriate parties on appropriate actions
  • When someone is assigned an issue, they are emailed
  • Comments on issues send emails to parties included on that issue (owner, assignee, commentors get emails)
  • New user registration sends email to user
• Web editor works
• Battery of tests against API
  • Create repo
  • Get repo
  • Delete repo
  • Get list of all repos
  • Get list of repos for user
  • Check that "username" is in output of repo list
• Log in, log out.
• Register new user
• User can delete account - all info and repos deleted
• Create public repos
• Watch/unwatch
• Star/unstar
• Download zip, gz, individual file, from branch/tag/commit
• Clone and push to repo
  • Over SSH
  • Over HTTPS

Items checked above are being tested against production via https://github.com/unfoldingWord-dev/nagios_plugins/blob/master/gogs_acceptance_test.sh, or by the integration test suite.

Manual Tests on Upgrades

• Verify emails are actually sent