-
Type:
Story
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: Master
-
Component/s: Product Menu, Style Books
- Intro/Context:
The goal of this story is to allow the Designer to manage (create, update, delete) stylebooks and allow viewing the values of the defined tokens.
-
When a UX Designer navigate to the product menu
Then he/she can navigate and :
- View the style books
- Create a new one (via add button)
- Delete a Style Book (via 3 dots)
- Rename a Style Book (via 3 dots)
- Set Style Book as Default for both Private & Public (via 3 dots)
- Assumption they have the same Theme
- Change Thumbnail (via 3 dots)
-
When the UX Designer edits a style book
Then he/she can view all the values of the tokens with the categories:
- Colors
- Spacing
- etc.
- (see attached document)
-
Notes:
- This story should also have a versioning system as the base to allow auto-save, and publication to version.
- This could be validated during PM review.
- Editing Stylebook actions in the mock up are only for info. They will be implemented in next story.
Test Scenarios
Test Scenarios | Test Strategy | Kind of test | Is it covered by FrontEnd ? (JS-Unit) | Is it covered by BackEnd ? (unit or integration) | Could it be covered by POSHI? |
---|---|---|---|---|---|
Site Designer can create a style book | Critical | Manual | No | Yes | Yes |
Site Designer can rename a style book | High | Manual | No | Yes | Yes |
Site Designer can delete a style book | Critical | Manual | No | Yes | Yes |
Site Designer can set a style book as default | High | Manual | No | Yes | Yes |
Site Designer can change the thumbnail of a style book | High | Manual | No | Yes | Yes |
Site Designer can edit a style book | Critical | Manual | No | No | Yes |
The data of Style Books is immediately available to Live site when manage it in Staging site | Critical | Manual | No | No | Yes |
- relates
-
LPS-118752 LPS-116077 - Product QA | Test Automation Creation
-
- Closed
-