Skip to content
This repository has been archived by the owner on Nov 21, 2022. It is now read-only.

Document Usage Scenarios #113

Merged
merged 1 commit into from
Jun 2, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions documentation/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
# Opt Out Documentation

## Usage Scenarios and Requirements

Usage Scenarios are meant to explain click by click interaction. They do reference the exact inputs, and need to be changed when the UI changes. They are organised in to a table that represents the list of tasks that users will go through. There are 3 types of action to help explain the expected behaviour:

- Action - A user interaction
- Reaction - The way the software reacts to the user action
- Insight - What the user learns or recognises as a result of their action or the software reaction

There is also a space to link a task to a requirement. This should be done for any requirements listed in the scenario but it's not so important to link to every requirement that's relevant defined in other scenarios.

### Linking to Tests

One place where writing user scenarios comes in handy is that these are the exact things that need to be tested using end 2 end testing. The id of the scenario can be referenced in the test title. Like so:

```
describe('[US-002] - Hide misogynist tweets, () => {...});
```

The tasks themselves can be referenced in the test title, like so:

```
it('[T-01] - Open Extension', () => {...});
```
15 changes: 15 additions & 0 deletions documentation/usage_scenarios/001_open_extension_toolbar.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# 001 Open Extension from Toolbar

## Requirements

| ID | Description |
| ---- | ------------------------------------------------------------------- |
| R-01 | The user can open the extension by clicking the icon in the toolbar |

## Usage Scenario

| Task | Action Type | Description | REQ ID |
| ---- | ----------- | ----------------------------------------------------------------------------------------- | ------ |
| T-01 | Action | User clicks Opt Out logo | R-01 |
| T-02 | Reaction | The extension popup opens | |
| T-03 | Insight | The user is aware the popup is open and that they can change the settings with the inputs | |
16 changes: 16 additions & 0 deletions documentation/usage_scenarios/002_hide_misogynist_tweets.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# 002 Hide Misogynist Tweets

## Requirements

| ID | Description |
| ---- | --------------------------------------------------------------------------------- |
| R-01 | Tweets can be hidden or modified in the twitter timeline if they contain misogyny |

## Usage Scenario

| Task | Action Type | Description | REQ ID |
| ---- | ----------- | --------------------------------------------------------------------------------------- | ------ |
| T-01 | Action | US-001 - Open extension | |
| T-02 | Action | User clicks on slider and drags the input to the "hide all" position | |
| T-03 | Reaction | The style of misogynist tweets in the timeline is changed to the selected display style | R-01 |
| T-04 | Insight | The user is aware the tweets in the timeline that are hidden were misogynist | |
16 changes: 16 additions & 0 deletions documentation/usage_scenarios/004_change_display_hidden.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# 002 Hide Misogynist Tweets

## Requirements

| ID | Description |
| ---- | --------------------------------------------------------------------------------- |
| R-01 | Tweets can be hidden or modified in the twitter timeline if they contain misogyny |

## Usage Scenario

| Task | Action Type | Description | REQ ID |
| ---- | ----------- | --------------------------------------------------------------------------------------- | ------ |
| T-01 | Action | US-001 - Open extension | |
| T-02 | Action | User clicks on slider and drags the input to the "hide all" position | |
| T-03 | Reaction | The style of misogynist tweets in the timeline is changed to the selected display style | R-01 |
| T-04 | Insight | The user is aware the tweets in the timeline that are hidden were misogynist | |
Empty file.