Skip to content

Commit

Permalink
docs(storybook): remove design system directory
Browse files Browse the repository at this point in the history
  • Loading branch information
Jamie Thompson committed Sep 29, 2021
1 parent 19f0590 commit 8c04a43
Show file tree
Hide file tree
Showing 164 changed files with 522 additions and 522 deletions.
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -2870,7 +2870,7 @@ cell paddings should depend on FlatTable size prop
* **select:** Experimental Select component has been removed, please use our new Select component `import { Select, Option } from "carbon-react/lib/components/select"`
* **select-async:** SelectAsync component has been removed, please use our new Select component `import { Select, Option } from "carbon-react/lib/components/select"`
Also check an example of how to provide data fetching functionality
https://carbon.sage.com/?path=/docs/design-system-select--with-is-loading-prop
https://carbon.sage.com/?path=/docs/select--with-is-loading-prop
* **date:** Date component no longer supports classic theme
* **textbox:** Textbox no longer supports classic theme
* **textarea:** Textarea input no longer supports classic theme
Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ Your branch should meet the following criteria:
1. The code follows our existing coding conventions.
1. It has detailed commit messages and squashed commits. PRs with commit messages like 'WIP' and 'addressed comments', or long lists of commits will likely require amending."
1. The code does not introduce unnecessary dependencies (no jQuery!).
1. Storybook is updated to include `Design System` and `Test` examples.
1. Storybook is updated to include examples.
1. Theme support is provided.
1. Typescript `d.ts` files are provided or updated.

Expand Down
Original file line number Diff line number Diff line change
@@ -1,46 +1,46 @@
Feature: Accessibility tests - Design System folder
Feature: Accessibility tests - Continued
I want to check that all components have no violations

@accessibility
Scenario Outline: Design System Accordion component <story> page closed state
When I open "Design System Accordion" component page "<story>"
Scenario Outline: Accordion component <story> page closed state
When I open "Accordion" component page "<story>"
Then "Accordion <story> page" component has no accessibility violations
Examples:
| story |
| default story |
| with dynamic content |

@accessibility
Scenario: Design System Accordion component primary page opened state
Given I open "Design System Accordion" component page "default story"
When I expand Design System accordionRow via click
Scenario: Accordion component primary page opened state
Given I open "Accordion" component page "default story"
When I expand default accordionRow via click
Then "Accordion default page" component has no accessibility violations

@accessibility
Scenario Outline: Design System <component> default story page
Scenario Outline: <component> default story page
When I open "Test <component>" component page "default"
Then "<component>" component has no accessibility violations
Examples:
| component |
| Anchornavigation |

@accessibility
Scenario: Design System DuellingPicklist component default story page
When I open "Design System DuellingPicklist Test" component page "default"
Scenario: DuellingPicklist component default story page
When I open "DuellingPicklist Test" component page "default"
Then "DuellingPicklist" component has no accessibility violations

@accessibility
Scenario Outline: Design System Numeral Date component <story> story page
When I open "Design System Numeral Date Test" component page "<story>"
Scenario Outline: Numeral Date component <story> story page
When I open "Numeral Date Test" component page "<story>"
Then "Numeral Date <story>" component has no accessibility violations
Examples:
| story |
| default |
| validations |

@accessibility
Scenario Outline: Design System Button component <story> page
When I open "Design System Button" component page "<story>"
Scenario Outline: Button component <story> page
When I open "Button" component page "<story>"
Then "Button <story> page" component has no accessibility violations
Examples:
| story |
Expand All @@ -65,8 +65,8 @@ Feature: Accessibility tests - Design System folder
| dashed icon |

@accessibility
Scenario Outline: Design System Button Bar component <story> page
When I open "Design System Button Bar" component page "<story>"
Scenario Outline: Button Bar component <story> page
When I open "Button Bar" component page "<story>"
Then "Button Bar <story> page" component has no accessibility violations
Examples:
| story |
Expand All @@ -77,38 +77,38 @@ Feature: Accessibility tests - Design System folder
| full width |

@accessibility
Scenario: Design System Button component as a sibling story page
When I open "Design System Button Test" component page "as a sibling"
Scenario: Button component as a sibling story page
When I open "Button Test" component page "as a sibling"
Then "button" component has no accessibility violations

@accessibility
Scenario Outline: Design System <component> component visual page
When I open "Design System <component> Test" component page "visual"
Scenario Outline: <component> component visual page
When I open "<component> Test" component page "visual"
Then "<component>" component has no accessibility violations
Examples:
| component |
| Drawer |
| Grid |

@accessibility
Scenario: Design System Form component with both errors and warnings summary page
When I open "Design System Form" component page "with both errors and warnings summary"
Scenario: Form component with both errors and warnings summary page
When I open "Form" component page "with both errors and warnings summary"
Then "Form" component has no accessibility violations

@accessibility
Scenario: Design System Numeral Date component validations page
When I open "Design System Numeral Date Test" component page "validations"
Scenario: Numeral Date component validations page
When I open "Numeral Date Test" component page "validations"
Then "Numeral Date" component has no accessibility violations

@accessibility
Scenario: Design System Popover Container component default page
Given I open "Design System Popover Container" component page "default story"
Scenario: Popover Container component default page
Given I open "Popover Container" component page "default story"
When I open popover container
Then "Popover Container" component has no accessibility violations

@accessibility
Scenario Outline: Design System <component> component default page
When I open "Design System <component>" component page "default story"
Scenario Outline: <component> component default page
When I open "<component>" component page "default story"
Then "<component>" component has no accessibility violations
Examples:
| component |
Expand Down Expand Up @@ -138,17 +138,17 @@ Feature: Accessibility tests - Design System folder
| Tile Select |

@accessibility
Scenario Outline: Design System Text Editor component <story> page
When I open "Design System Text Editor" component page "<story>"
Scenario Outline: Text Editor component <story> page
When I open "Text Editor" component page "<story>"
Then "Text Editor component <story> page" component has no accessibility violations
Examples:
| story |
| with content |
| with optional buttons |

@accessibility
Scenario Outline: Design System Select component <story> page
When I open "Design System Select" component page "<story>"
Scenario Outline: Select component <story> page
When I open "Select" component page "<story>"
Then "Select" component has no accessibility violations
Examples:
| story |
Expand All @@ -157,60 +157,60 @@ Feature: Accessibility tests - Design System folder
| transparent |

@accessibility
Scenario: Design System Select component default story page
Given I open "Design System Select" component page "default story"
Scenario: Select component default story page
Given I open "Select" component page "default story"
When I click on default Select input
Then "Select" component has no accessibility violations

@accessibility
Scenario Outline: Design System Filterable Select component <story> page
When I open "Design System Select filterable" component page "<story>"
Scenario Outline: Filterable Select component <story> page
When I open "Select filterable" component page "<story>"
Then "Select" component has no accessibility violations
Examples:
| story |
| disabled |
| readOnly |

@accessibility
Scenario: Design System Note component inline controls page
When I open "Design System Note" component page "with inline controls"
Scenario: Note component inline controls page
When I open "Note" component page "with inline controls"
Then "Note inline controls" component has no accessibility violations

@accessibility
Scenario Outline: Design System Menu component <story> page
When I open "Design System Menu" component page "<story>"
Scenario Outline: Menu component <story> page
When I open "Menu" component page "<story>"
Then "Menu <story>" component has no accessibility violations
Examples:
| story |
| default story |
| dark theme |

@accessibility
Scenario Outline: Design System Navigation Bar component <story> page
When I open "Design System Navigation Bar" component page "<story>"
Scenario Outline: Navigation Bar component <story> page
When I open "Navigation Bar" component page "<story>"
Then "Navigation Bar <story>" component has no accessibility violations
Examples:
| story |
| default story |
| dark theme |

@accessibility
Scenario Outline: Design System Tile component <story> page
When I open "Design System Tile" component page "<story>"
Scenario Outline: Tile component <story> page
When I open "Tile" component page "<story>"
Then "Tile <story>" component has no accessibility violations
Examples:
| story |
| default story |
| with definition list default |

@accessibility
Scenario: Design System Toast component visual story page
When I open "Design System Toast Test" component page "visual"
Scenario: Toast component visual story page
When I open "Toast Test" component page "visual"
Then "Toast" component has no accessibility violations

@accessibility
Scenario Outline: Design System Card component <story> page
When I open "Design System Card" component page "<story>"
Scenario Outline: Card component <story> page
When I open "Card" component page "<story>"
Then "Card <story>" component has no accessibility violations
Examples:
| story |
Expand All @@ -220,8 +220,8 @@ Feature: Accessibility tests - Design System folder
| more examples of card footer |

@accessibility
Scenario Outline: Design System Pill component <story> page
When I open "Design System Pill" component page "<story>"
Scenario Outline: Pill component <story> page
When I open "Pill" component page "<story>"
Then "Pill <story> story" component has no accessibility violations
Examples:
| story |
Expand All @@ -230,13 +230,13 @@ Feature: Accessibility tests - Design System folder
| tag |

@accessibility
Scenario: Design System Tooltip component default story page
When I open "Design System Tooltip Test" component page "default"
Then "Design System Tooltip Test default" component has no accessibility violations
Scenario: Tooltip component default story page
When I open "Tooltip Test" component page "default"
Then "Tooltip Test default" component has no accessibility violations

@accessibility
Scenario Outline: Design System <component> validations boolean story page
When I open "Design System <component>" component page "validations boolean"
Scenario Outline: <component> validations boolean story page
When I open "<component>" component page "validations boolean"
Then "<component>" component has no accessibility violations
Examples:
| component |
Expand All @@ -248,8 +248,8 @@ Feature: Accessibility tests - Design System folder
| fieldset |

@accessibility
Scenario Outline: Design System <component> validations string story page
When I open "Design System <component>" component page "validations string component"
Scenario Outline: <component> validations string story page
When I open "<component>" component page "validations string component"
Then "<component>" component has no accessibility violations
Examples:
| component |
Expand All @@ -261,8 +261,8 @@ Feature: Accessibility tests - Design System folder
| fieldset |

@accessibility
Scenario Outline: Design System <component> validations string label story page
When I open "Design System <component>" component page "validations string label"
Scenario Outline: <component> validations string label story page
When I open "<component>" component page "validations string label"
Then "<component>" component has no accessibility violations
Examples:
| component |
Expand All @@ -275,13 +275,13 @@ Feature: Accessibility tests - Design System folder

@accessibility
Scenario: Image component default story
When I open "Design System Image" component page "default story"
When I open "Image" component page "default story"
Then "Image default story" component has no accessibility violations

@accessibility
Scenario Outline: Design System checkbox component <story> story
When I open "Design System checkbox validations" component page "<story>"
Then "Design System checkbox <story> story" component has no accessibility violations
Scenario Outline: checkbox component <story> story
When I open "checkbox validations" component page "<story>"
Then "checkbox <story> story" component has no accessibility violations
Examples:
| story |
| group checkbox boolean validation |
Expand All @@ -290,24 +290,24 @@ Feature: Accessibility tests - Design System folder
| single checkbox string validation |

@accessibility
Scenario: Design System checkbox with asterisk
When I open "Design System checkbox validations" component page "required"
Then "Design System checkbox with asterisk" component has no accessibility violations
Scenario: checkbox with asterisk
When I open "checkbox validations" component page "required"
Then "checkbox with asterisk" component has no accessibility violations

@accessibility
Scenario Outline: Design System switch component <story> story
When I open "Design System switch" component page "<story>"
Then "Design System switch <story> story" component has no accessibility violations
Scenario Outline: switch component <story> story
When I open "switch" component page "<story>"
Then "switch <story> story" component has no accessibility violations
Examples:
| story |
| single switch boolean validation |
| single switch string validation |
| single switch string validation validation on label |

@accessibility
Scenario Outline: Design System Radiobutton component with <story> story
When I open "Design System Radiobutton" component page "<story>"
Then "Design System Radiobutton with <story> story" component has no accessibility violations
Scenario Outline: Radiobutton component with <story> story
When I open "Radiobutton" component page "<story>"
Then "Radiobutton with <story> story" component has no accessibility violations
Examples:
| story |
| with legend and labels |
Expand Down
14 changes: 7 additions & 7 deletions cypress/features/regression/designSystem/accordion.feature
Original file line number Diff line number Diff line change
@@ -1,26 +1,26 @@
Feature: Design System Accordion component
I want to test Design System Accordion component
Feature: Accordion component
I want to test Accordion component

@positive
Scenario: I expand accordion using click
Given I open "Design System Accordion" component page "default story"
When I expand Design System accordionRow via click
Given I open "Accordion" component page "default story"
When I expand default accordionRow via click
Then accordionRow is expanded

@positive
Scenario: I expand accordion using Enter key
Given I open "Design System Accordion" component page "default story"
Given I open "Accordion" component page "default story"
When I expand accordionRow using "Enter" key
Then accordionRow is expanded

@positive
Scenario: Verify border outline color on focus
Given I open "Design System Accordion" component page "default story"
Given I open "Accordion" component page "default story"
When I focus first accordionRow
Then accordionRow has golden border outline

@positive
Scenario: Open accordion by clicking on validation icon
Given I open "Design System Accordion" component page "validation icon"
Given I open "Accordion" component page "validation icon"
When I click on first validation icon
Then accordionRow is expanded
Loading

0 comments on commit 8c04a43

Please sign in to comment.