Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Combine multiple TestOnly stories into a single one with multiple components to reduce snapshot count #7919

Open
benelan opened this issue Oct 2, 2023 · 0 comments
Open

Combine multiple TestOnly stories into a single one with multiple components to reduce snapshot count #7919

benelan opened this issue Oct 2, 2023 · 0 comments
Labels
0 - new New issues that need assignment. p - high Issue should be addressed in the current milestone, impacts component or core functionality testing Issues related to automated or manual testing.

Comments

@benelan
Copy link
Member

benelan commented Oct 2, 2023

Test type

chromatic

Which Component(s)

all

Unstable Tests

No response

Test error, if applicable

No response

PR skipped, if applicable

No response

Additional Info

We should do a pass through our component TestOnly stories looking for ways we can combine multiple stories into a single one, with the goal of reducing our snapshot count. A couple ideas are:

  • If there are three stories, one for each scale, we can create a single story that contains three components with the different scales
  • We can combine stories that are testing different locales into a single locals_TestOnly story with multiple components
  • Other places where different iterations of the same prop are tested in separate stories can be combined into a single story with multiple components

came up in #7915 (comment)
@benelan benelan added testing Issues related to automated or manual testing. p - high Issue should be addressed in the current milestone, impacts component or core functionality 0 - new New issues that need assignment. labels Oct 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
0 - new New issues that need assignment. p - high Issue should be addressed in the current milestone, impacts component or core functionality testing Issues related to automated or manual testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@benelan