This repository has been archived on 2022-05-04. You can view files and clone it, but cannot push or open issues or pull requests.
tso-sw/docs
surtur 9eda65d667
All checks were successful
continuous-integration/drone/push Build is passing
continuous-integration/drone/tag Build is passing
chore: finalised the docs
2020-07-13 11:40:03 +02:00

961 lines
32 KiB
Plaintext

# vim:fileencoding=utf-8:ff=unix:ft=conf:foldmethod=marker:noexpandtab
# the code is available at https://git.dotya.ml/wanderer/tso-sw
test set
desktop - Testing a webpage with desktop browser
test case
- id - 01
- name - open page and maximize
- opens the specified webpage and maximizes the browser window
- expected result - webpage is successfully loaded and browser is maximized (screenshot proof)
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 02
- name - attempt login without creds
- opens the specified webpage and attempts to log in with no
credentials (at all), which should (obviously) fail
- expected result - webpage is loaded, login page displayed and login fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 03
- name - open page, click Explore button and sort by "Most stars"
- opens the specified webpage, clicks on a button to browse
repositories, clicks on a dropdown, selects an option
- expected result - repositories page should be ordered by "Most stars"
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 04
- name - attempt login without password
- opens the specified webpage, clicks on a tabbar button to get to
login page, inputs a username and clicks on a 'Sign In' button
- expected result - login fails, error message is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 05
- name - attempt login without username
- opens the specified webpage, clicks on a tabbar button to get to
login page, inputs a password and clicks on a 'Sign In' button
- expected result - login fails, error message is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 06
- name - attempt login with bogus creds
- opens the specified webpage, clicks on a tabbar button to get to
login page, inputs a bogus username and bogus password and clicks
on a 'Sign In' button
- expected result - login fails, error message is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 07
- name - attempt to register short password
- opens the specified webpage, clicks on a tabbar button to get to
login page, clicks on a 'Need to register' link, inputs a username,
email and a *short* password (this Gitea instance has got a password
length requirement), retypes it for confirmation and clicks on
the 'Register Account' button
- expected result - account registration fails, error message is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 08
- name - attempt to register weak password
- opens the specified webpage, clicks on a tabbar button to get to
login page, clicks on a 'Need to register' link, inputs a username,
email and a password that is now long enough but *weak* (this
Gitea instance has also got a password 'strength' requirement),
retypes it for confirmation and clicks on the 'Register Account'
button
- expected result - account registration fails, error message is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 09
- name - attempt to register (semi-)legit password
- opens the specified webpage, clicks on a tabbar button to get to
login page, clicks on a 'Need to register' link, inputs a username,
an email and a semi-legitimate password (while technically compliant
with requirements of this Gitea instance, it could be better;
however, for testing purposes will do), retypes it for confirmation
and clicks on the 'Register Account' button
- expected result - account registration is successful, user Dashboard page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 10
- name - log in to an account using username
- opens the specified webpage, clicks on a tabbar button to get to
login page, inputs username and password, hits Enter, logs in
- Pre-conditions
- user registered (test09)
- expected result - user login is successful, user Dashboard page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 11
- name - log in to an account using email
- opens the specified webpage, clicks on a tabbar button to get to
login page, inputs email and password, hits Enter, logs in
- Pre-conditions
- user registered (test09)
- expected result - user login is successful, user Dashboard page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 12
- name - show Milestones page
- robot user logs in using username and password,
clicks on a tabbar button to get to the Milestones page
- Pre-conditions
- user registered (test09)
- expected result - Milestones page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 13
- name - show Pull Requests page
- robot user logs in using username and password,
clicks on a tabbar button to get to the Pull Requests page
- Pre-conditions
- user registered (test09)
- expected result - Pull Requests page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 14
- name - show Issues page
- robot user logs in using username and password,
clicks on a tabbar button to get to the Issues page
- Pre-conditions
- user registered (test09)
- expected result - Issues page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 15
- name - show user profile page
- robot user logs in using username and password,
clicks on a tabbar user menu button, selects Profile entry
to get to the user profile page
- Pre-conditions
- user registered (test09)
- expected result - user profile page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 16
- name - star wanderer's dotfiles repo
- robot user logs in using username and password,
clicks on Explore tabbar button, searches for dotfiles repo,
selects the one by 'wanderer' and stars it
- Pre-conditions
- user registered (test09)
- expected result - wanderer's dotfiles repo is starred by robot user
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 17
- name - unstar wanderer's dotfiles repo
- robot user logs in using username and password,
clicks on Explore tabbar button, searches for dotfiles repo,
selects the one by 'wanderer' and unstars it
- Pre-conditions
- user registered (test09)
- wanderer's repo is starred by the robot user
- expected result - wanderer's dotfiles repo is not starred by robot user
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 18
- name - create a mirror of a repository
- robot user logs in using username and password,
creates a mirror of the BLAKE3 repository
- Pre-conditions
- user registered (test09)
- expected result - local mirror of BLAKE3 is created
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 19
- name - delete a migrated repo
- robot user logs in using username and password,
deletes a previously created mirror repository
- Pre-conditions
- user registered (test09)
- mirror created (test18)
- expected result - mirror repo is deleted
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 00
- name - delete test user account
- robot user logs in, goes to account settings and deletes the account
- Pre-conditions
- user registered (test09)
- expected result - user account is deleted
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
test set
mobile - Testing a webpage with (emulated) mobile browser
test case
- id - 01
- name - open homepage (mobile)
- opens the specified webpage
- expected result - webpage is loaded
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 02
- name - attempt login without creds (mobile)
- attempts login without creds
- expected result - login fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 03
- name - sort repos by "Most stars" (mobile)
- opens the specified webpage, clicks on the burger menu, then
clicks on the Explore button to browse through repositories,
clicks on a dropdown and selects an option to sort repos by
most stars
- expected result - repositories page should be ordered by "Most stars"
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 04
- name - attempt login without password (mobile)
- attempts login using only username (no password)
- expected result - login fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 05
- name - attempt login without username (mobile)
- attempts login using only password (no username)
- expected result - login fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 06
- name - attempt login with bogus creds (mobile)
- robot attempts login using bogus creds
- expected result - login fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 07
- name - attempt to register short password (mobile)
- robot attempts to register an account using a short password
- expected result - registration fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 08
- name - attempt to register weak password (mobile)
- robot attempts to register an account using a weak password
- expected result - registration fails
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 09
- name - attempt to register (semi-)legit password (mobile)
- opens the specified webpage, clicks on burger menu, selects
'Log In' to get to login page, taps on a 'Need to register' link,
inputs a username, an email and a semi-legitimate password
retypes it for confirmation and clicks on 'Register Account'
- expected result - account registration is successful, user Dashboard page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 10
- name - log in to an account using username (mobile)
- opens the specified webpage, taps on the "burger menu", selects
'Sign In', inputs username and password, taps on 'Sign In' button
- Pre-conditions
- user registered (test09)
- expected result - user login is successful, user Dashboard page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 11
- name - log in to an account using email (mobile)
- opens the specified webpage, taps on the "burger menu", selects
'Sign In', inputs email and password, taps on 'Sign In' button
- Pre-conditions
- user registered (test09)
- expected result - user login is successful, user Dashboard page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 12
- name - show Milestones page (mobile)
- robot user signs in, taps on the burger menu, selects
'Milestones'
- Pre-conditions
- user registered (test09)
- expected result - user's 'Milestones' page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 13
- name - show Pull Requests page (mobile)
- robot user signs in, taps on the burger menu, selects
'Pull Requests'
- Pre-conditions
- user registered (test09)
- expected result - user's 'Pull Requests' page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 14
- name - show Issues page (mobile)
- robot user signs in, taps on the burger menu, selects 'Issues'
- Pre-conditions
- user registered (test09)
- expected result - user's 'Issues' page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 15
- name - show user profile page (mobile)
- robot user signs in, taps on the burger menu, taps on a dropdown
to have user menu shown, selects 'Profile'
- Pre-conditions
- user registered (test09)
- expected result - user profile page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 16
- name - star wanderer's repo (mobile)
- robot user logs in, taps on the burger menu, selects Explore
button, searches for dotfiles repo, selects the one by 'wanderer'
and stars it
- Pre-conditions
- user registered (test09)
- expected result - user profile page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 17
- name - unstar wanderer's repo (mobile)
- robot user logs in, taps on the burger menu, selects Explore
button, searches for dotfiles repo, selects the one by 'wanderer'
and unstars it
- Pre-conditions
- user registered (test09)
- expected result - user profile page is shown
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 18
- name - create a mirror of a repository (mobile)
- robot user logs in using username and password,
creates a mirror of the BLAKE3 repository
- Pre-conditions
- user registered (test09)
- expected result - local mirror of BLAKE3 is created
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 19
- name - delete a migrated repo (mobile)
- robot user logs in using username and password,
deletes a previously created mirror repository
- Pre-conditions
- user registered (test09)
- mirror created (m-test18)
- expected result - mirror repo is deleted
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
- id - 00
- name - delete test user account (mobile)
- robot user logs in, goes to account settings and deletes the account
- Pre-conditions
- user registered (test09)
- expected result - user account is deleted
- steps:
see test{{tc_id}}.robot
- Post-conditions
- close browser
- execution - automatic (robotframework)
- execution time - variable, see test results
- author - ...
- date - see test results
test set
manual
- id - 00
- name - add a collaborator (mobile)
- user goes to the 'Explore' page, searches for their favourite repo
and selects it, taps on the repo 'Settings' button, taps on
'Collaborators', inputs the username of a collaborator, taps
on 'Add Collaborator' button and selects the collaborators access
level using the provided dropdown on the next screen (Read, Write, Admin)
- Pre-conditions
- user registered (automated test09)
- user has write access to a repo
- collaborator has an account
- user is logged in
- expected result - collaborator is added
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 01
- name - open a new issue (mobile)
- user goes to the 'Explore' page, searches for a favourite repo,
taps on the repo name, taps on the 'Issues' (if available) tab in the repo (next
to the 'Code' tab, that is selected by default), taps on
the'New Issue' button, inputs the issue title, describes the issue
into the description input box, if possible selects an assignee, if available
adds issue badges of choice, if available sets a milestone,
if applicable specifies branch or tag, previews the issue, optionally
uploads a file via provided drag-and-drop and finally taps
on the 'Create Issue' button
- Pre-conditions
- user registered (automated test09)
- user is logged in
- expected result - new issue is open
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 02
- name - create a milestone (mobile)
- user goes to the 'Explore' page, searches for a favourite repo,
taps on the repo name, taps on the 'Issues' tab in the repo,
taps on the 'Milestones' button (right next to the 'Labels'
button), taps on 'New Milestone', inputs milestone title and
description, optionally also due date and taps on 'Create Milestone'
- Pre-conditions
- user registered (automated test09)
- user is logged in
- expected result - milestone is created
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 03
- name - create a file using webui (mobile)
- user goes to the 'Explore' page, searches for a repo they own,
taps on the repo name, then taps on 'New File', inputs file name
to the filename input box, inputs content to the file body input,
sets off to commit a change, inputs a commit message and finally
commits the changes made
- Pre-conditions
- user registered (automated test09)
- 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
- close browser
- execution - manual
- execution time - variable
- id - 04
- name - upload a file using webui (mobile)
- user goes to the 'Explore' page, searches for a repo they own,
taps on the repo name, then taps on 'Upload File', selects the
file from the filesystem or uses drag-and-drop, inputs commit
message, branch and file name and commits the file
- Pre-conditions
- user registered (automated test09)
- user has write access to the repo
- user is logged in
- expected result - a file is uploaded
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 05
- name - edit a file using webui (mobile)
- user goes to the 'Explore' page, searches for a repo they own,
taps on the repo name, then taps on the file they wish to edit,
taps on the 'Edit file' icon in the file header ribbon, makes
changes, inputs commit message and finally commits the changes
to the repo once they're done
- Pre-conditions
- user registered (automated test09)
- user is logged in
- expected result - edited file is commited to the repo
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 06
- name - set user email visibility to hidden (mobile)
- user taps on the burger menu, then taps on their avatar to show
a dropdown, taps on 'Settings', in the 'Profile' section checks
the 'Hide Email Address' checkbox, if unchecked
- Pre-conditions
- user registered (automated test09)
- user is logged in
- expected result - user email is hidden from other users
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 07
- name - change user avatar (mobile)
- user taps on the burger menu, then taps on their avatar to show
a dropdown, taps on 'Settings', in the 'Profile' section scrolls down,
selects 'Use Custom Avatar' radio button and after tapping on 'Browse'
button selects a custom avatar from the filesystem and finally
taps 'Update Avatar' button.
- Pre-conditions
- user registered (automated test09)
- user is logged in
- expected result - user email is hidden from other users
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 08
- name - add webhook
- user searches for their favourite repo, clicks on 'Settings',
move to the 'Webhooks' tab, clicks on 'Add Webhook', selects
'Discord', inputs webhook URL into 'Target URL', optionally
renames the webhook or specifies a path to the custom icon,
specifies trigger events and branches that are relevant (wildcards allowed),
checks the 'Active' checkbox and clicks on 'Add Webhook' button to save all.
- Pre-conditions
- user registered (automated test09)
- user is logged in
- user has write access to the repo
- expected result - webhook is added
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 09
- name - set protected branch
- user finds their favourite repo, clicks on repo 'Settings', goes
to the 'Branches' tab, selects one from the dropdown, checks the 'Enable Branch Protection'
checkbox, selects the desired protection options such as commit
signing requirement, blocked merges when PRs are outdated
(behind the base) etc., and clicks on 'Update Settings' to save all.
- Pre-conditions
- user registered (automated test09)
- user is logged in
- user has write access to the repo
- expected result - branch protection is set up
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 10
- name - add deploy key
- user finds their favourite repo, clicks on repo 'Settings', goes
to the 'Deploy Keys' tab, clicks on 'Add Deploy Key' button,
pastes copied pubkey from the clipboard to the 'Content' field,
optionally renames the key (as its name is derived automatically from the key),
decides whether or not to allow write access and saves by clicking
on the big green 'Add Deploy Key' button right under the 'Content' field
- Pre-conditions
- user registered (automated test09)
- user is logged in
- user has write access to the repo
- expected result - deploy key is added
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- id - 11
- name - update a pre-receive git hook
- user finds their favourite repo, clicks on repo 'Settings', goes
to the 'Git Hooks' tab, clicks on the edit icon of the 'pre-receive' row,
inputs the desired content into the 'Hook Content' field and saves it
by clicking on 'Update Hook'
- Pre-conditions
- user registered (automated test09)
- user is logged in
- user has write access to the repo
- expected result - pre-receive git hook is added
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- 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 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
- execution - manual
- execution time - variable
- 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 write access to the repo
- expected result - issue links route to external issue tracker seamlessly
- Post-conditions
- close browser
- execution - manual
- execution time - variable
- 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 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
- execution time - variable