This commit is contained in:
parent
284d9bdac7
commit
d1233db2f9
GPG Key ID:
19CE1EC1D9E0486D
119
docs
119
docs
|
|
@ -671,7 +671,7 @@ test set
|
|||
commits the changes made
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- user is logged in
|
||||
- expected result - a file at {file name} is created (from the scratch)
|
||||
- Post-conditions
|
||||
|
|
@ -687,7 +687,7 @@ test set
|
|||
message, branch and file name and commits the file
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- user is logged in
|
||||
- expected result - a file is uploaded
|
||||
- Post-conditions
|
||||
|
|
@ -747,7 +747,7 @@ test set
|
|||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- expected result - webhook is added
|
||||
- Post-conditions
|
||||
- close browser
|
||||
|
|
@ -760,7 +760,7 @@ test set
|
|||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- expected result - branch protection is set up
|
||||
- Post-conditions
|
||||
- close browser
|
||||
|
|
@ -773,7 +773,7 @@ test set
|
|||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- expected result - deploy key is added
|
||||
- Post-conditions
|
||||
- close browser
|
||||
|
|
@ -786,7 +786,7 @@ test set
|
|||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- expected result - pre-receive git hook is added
|
||||
- Post-conditions
|
||||
- close browser
|
||||
|
|
@ -795,11 +795,14 @@ test set
|
|||
|
||||
- id - 12
|
||||
- name - set repo as private
|
||||
-
|
||||
- user goes to the 'Explore' page, searches for a repo they own,
|
||||
selects it, clicks the repo 'Settings' button, checks the checkbox
|
||||
under 'Visibility' in 'Basic Settings' section
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- repo is currently publicly visible
|
||||
- expected result - repository is not visible to anyone beyond the owner and collaborators
|
||||
- Post-conditions
|
||||
- close browser
|
||||
|
|
@ -808,11 +811,16 @@ test set
|
|||
|
||||
- id - 13
|
||||
- name - enable repo external issue tracker
|
||||
-
|
||||
- user goes to the 'Explore' page, searches for a repo they own,
|
||||
selects it, clicks the repo 'Settings' button, scrolls down to
|
||||
the 'Advanced Settings' section, inputs URL into
|
||||
'External Issue Tracker URL' input, inputs issue tracker URL format
|
||||
into the 'External Issue Tracker URL format' input and via radio
|
||||
button selects whether the issue format is numeric or alphanumeric
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- user has write access to the repo
|
||||
- expected result - issue links route to external issue tracker seamlessly
|
||||
- Post-conditions
|
||||
- close browser
|
||||
|
|
@ -821,12 +829,97 @@ test set
|
|||
|
||||
- id - 14
|
||||
- name - disable repo wiki
|
||||
-
|
||||
- user goes to the 'Explore' page, searches for a repo they own,
|
||||
selects it, clicks the repo 'Settings' button, scrolls down to
|
||||
the 'Advanced Settings' section, unchecks the 'Enable Repository Wiki' checkbox
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has a write access to the repo
|
||||
- expected result - repo wiki is disabled (not shown)
|
||||
- user has write access to the repo
|
||||
- expected result - repo wiki is disabled
|
||||
- Post-conditions
|
||||
- close browser
|
||||
- execution - manual
|
||||
- execution time - variable
|
||||
|
||||
- id - 15
|
||||
- name - create an organization
|
||||
- user clicks on the tabbar dropdown to the left of the right-positioned
|
||||
user avatar dropdown, selects 'New Organization', inputs name, selects
|
||||
org visibility in a radio button selection, optionally grants the admins
|
||||
of the org permissions to manage access for other team members and hits
|
||||
the 'Create Organization' button
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- expected result - organisation is created
|
||||
- Post-conditions
|
||||
- close browser
|
||||
- execution - manual
|
||||
- execution time - variable
|
||||
|
||||
- id - 16
|
||||
- name - delete the org
|
||||
- user selects the org from the orgs 'Explore' page, selects
|
||||
the subject org, clicks on the cog icon next to the org avatar,
|
||||
selects the 'Delete Organization' tab on the left-hand side,
|
||||
confirm the intent with their password and hits the 'Confirm Deletion' button
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has admin access to the org
|
||||
- expected result - org is deleted
|
||||
- Post-conditions
|
||||
- close browser
|
||||
- execution - manual
|
||||
- execution time - variable
|
||||
|
||||
- id - 17
|
||||
- name - follow a user
|
||||
- user goes to the 'Explore' page, selects the 'Users' tab,
|
||||
searches for a user, selects a user to get to their profile page,
|
||||
clicks on the big green 'Follow' button to be a good follower
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has admin access to the org
|
||||
- expected result - we become one of the followers
|
||||
- Post-conditions
|
||||
- close browser
|
||||
- execution - manual
|
||||
- execution time - variable
|
||||
|
||||
- id - 18
|
||||
- name - add gpg key for the user
|
||||
- user clicks on the user avatar dropdown in the top right corner,
|
||||
selects 'Settings' to get to the user settings page, selects
|
||||
the 'SSH/GPG Keys' tab, clicks on 'Add Key' button under
|
||||
the 'Manage GPG Keys' section, copies a key from clipboard
|
||||
to the 'Content' input field and clicks on the green 'Add Key' button.
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has write access to the repo
|
||||
- expected result - gpg key is added
|
||||
- Post-conditions
|
||||
- close browser
|
||||
- execution - manual
|
||||
- execution time - variable
|
||||
|
||||
- id - 19
|
||||
- name - add ssh key for the user
|
||||
- user clicks on the user avatar dropdown in the top right corner,
|
||||
selects 'Settings' to get to the user settings page, selects
|
||||
the 'SSH/GPG Keys' tab, clicks on 'Add Key' button under
|
||||
the 'Manage SSH Keys' section, copies a key from clipboard
|
||||
to the 'Content' input field. Name is set automatically, although
|
||||
the user is able to set a custom name for the key.
|
||||
To finally add the key, user clicks on the green 'Add Key' button.
|
||||
- Pre-conditions
|
||||
- user registered (automated test09)
|
||||
- user is logged in
|
||||
- user has write access to the repo
|
||||
- expected result - ssh key is added
|
||||
- Post-conditions
|
||||
- close browser
|
||||
- execution - manual
|
||||
|
|
|
|||
Reference in New Issue