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.

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

Final Testing of AWS Gogs #171

Closed
36 of 37 tasks
jag3773 opened this issue May 4, 2017 · 3 comments
Closed
36 of 37 tasks

Final Testing of AWS Gogs #171

jag3773 opened this issue May 4, 2017 · 3 comments
Assignees
Labels

Comments

@jag3773
Copy link
Contributor

jag3773 commented May 4, 2017

Run (manually) through items in:

https://github.com/unfoldingWord-dev/gogs/wiki/Items-for-Acceptance-Testing

Putting items here and will check those that pass, or make a note for those that don't:

  • Avatars persist across updates - FAILS, see comment below
  • "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, private repos
  • Options available if logged in: explore
  • Access to private repos is restricted
  • License file is created in new repos as LICENSE.md with correct CC BY-SA text
  • Scrub tool functions for a repo
  • 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)
  • Able to delete a user
  • 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 cancel registration - all info and repos deleted
  • Create public repos
  • Edit file formats: .txt, .md, .usfm, .json, .yml/yaml
  • Watch/unwatch
  • Star/unstar
  • Download zip, gz, individual file, from branch/tag/commit
  • Clone and push to repo
    • Over SSH
    • Over HTTPS
@richmahn richmahn self-assigned this May 5, 2017
@richmahn
Copy link
Member

richmahn commented May 7, 2017

For the first one, that avatars persist across migration/upgrade, I found a migration that was added is making everyone's avatar the same. I couldn't figure out a quick fix, other than when we run gitea the first time to do the migrations, to rename /mnt/git/gogs-avatars to something else, run gitea and then put the gogs-avatars directory back.

go-gitea/gitea#1234

@richmahn
Copy link
Member

richmahn commented May 10, 2017

There's a fix I added to the update-gogs-db-after-first-run.sql to make sure avatars are carried over. Uncomment the AVATAR_DIR line in the app.ini line after the first run of the gitea binary.

@richmahn
Copy link
Member

I don't see a way for a user to cancel registration (unverified account), and once verified, if they want to delete their account, but have repos, they have to delete their repos first, so deleting an account doesn't delete repos for them.

@jag3773 jag3773 added this to the WST Sprint #24 milestone May 11, 2017
@jag3773 jag3773 closed this as completed May 11, 2017
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants