feat: added manual test specs + updated .drone.yml accordingly
All checks were successful
continuous-integration/drone/push Build is passing

This commit is contained in:
surtur 2020-07-06 02:08:07 +02:00
parent 8f891b3280
commit 4b929e2d59
Signed by: wanderer
GPG Key ID: 19CE1EC1D9E0486D
4 changed files with 142 additions and 317 deletions

View File

@ -352,150 +352,6 @@ steps:
- test09
- test18
- name: test20
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test20
- robot -T -d results/${DRONE_STAGE_NAME}/test20 test20.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test21
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test21
- robot -T -d results/${DRONE_STAGE_NAME}/test21 test21.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test22
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test22
- robot -T -d results/${DRONE_STAGE_NAME}/test22 test22.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test23
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test23
- robot -T -d results/${DRONE_STAGE_NAME}/test23 test23.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test24
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test24
- robot -T -d results/${DRONE_STAGE_NAME}/test24 test24.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test25
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test25
- robot -T -d results/${DRONE_STAGE_NAME}/test25 test25.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test26
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test26
- robot -T -d results/${DRONE_STAGE_NAME}/test26 test26.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test27
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test27
- robot -T -d results/${DRONE_STAGE_NAME}/test27 test27.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test28
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/test28
- robot -T -d results/${DRONE_STAGE_NAME}/test28 test28.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: test29
pull: if-not-exists
image: immawanderer/alpine-rf:latest
@ -557,15 +413,6 @@ steps:
- test17
- test18
- test19
- test20
- test21
- test22
- test23
- test24
- test25
- test26
- test27
- test28
- test29
volumes:
@ -933,150 +780,6 @@ steps:
- m-test09
- m-test18
- name: m-test20
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test20
- robot -T -d results/${DRONE_STAGE_NAME}/m-test20 m-test20.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test21
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test21
- robot -T -d results/${DRONE_STAGE_NAME}/m-test21 m-test21.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test22
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test22
- robot -T -d results/${DRONE_STAGE_NAME}/m-test22 m-test22.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test23
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test23
- robot -T -d results/${DRONE_STAGE_NAME}/m-test23 m-test23.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test24
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test24
- robot -T -d results/${DRONE_STAGE_NAME}/m-test24 m-test24.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test25
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test25
- robot -T -d results/${DRONE_STAGE_NAME}/m-test25 m-test25.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test26
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test26
- robot -T -d results/${DRONE_STAGE_NAME}/m-test26 m-test26.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test27
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test27
- robot -T -d results/${DRONE_STAGE_NAME}/m-test27 m-test27.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test28
pull: if-not-exists
image: immawanderer/alpine-rf:latest
volumes:
- name: shm
path: /dev/shm
commands:
- mkdir -pv results/${DRONE_STAGE_NAME}/m-test28
- robot -T -d results/${DRONE_STAGE_NAME}/m-test28 m-test28.robot
when:
status:
- success
- failure
depends_on:
- reveal-env
- name: m-test29
pull: if-not-exists
image: immawanderer/alpine-rf:latest
@ -1139,15 +842,6 @@ steps:
- m-test17
- m-test18
- m-test19
- m-test20
- m-test21
- m-test22
- m-test23
- m-test24
- m-test25
- m-test26
- m-test27
- m-test28
- m-test29
volumes:

135
docs
View File

@ -605,3 +605,138 @@ test set
- 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 a 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 a 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

View File

@ -1,14 +1,10 @@
graph TD
A -->|test set| B(desktop)
A[rf tests] -->|test set| C(mobile)
A -->|test set| B(fa:fa-cog automated)
A[rf tests] -->|test set| C(fa:fa-wrench manual)
B --> |test set|D(fa:fa-cog automated)
B --> |test set|E(fa:fa-wrench manual)
C --> |test set|F(fa:fa-cog automated)
C --> |test set|G(fa:fa-wrench manual)
B --> |test set|D(fa:fa-desktop desktop)
B --> |test set|E(fa:fa-mobile mobile)
C --> |test|F(test00-19)
D --> |test|H(test00-19)
E --> |test|I(test20-29)
F --> |test|J(m-test00-19)
G --> |test|K(m-test20-29)
D --> |test|G(test00-19)
E --> |test|H(m-test00-19)

Binary file not shown.

Before

Width:  |  Height:  |  Size: 26 KiB

After

Width:  |  Height:  |  Size: 20 KiB