Adds FAQ explaining why tests show as new #616
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@deandre is this meant just for E2E tests or storybook too? If both, could you also include an example of story name changing inside a stories file. |
|
@winkerVSbecks the scope of this particular FAQ is E2E tests. it can probably be expanded later to include a CSF example. i've made changes to specify "test" rather than "story" throughout, to avoid confusion. edit: story names are addressed to an extent by https://www.chromatic.com/docs/faq/why-are-storybook-and-chromatic-story-names-different/ |
deandre
changed the title
winkerVSbecks
approved these changes
Jan 15, 2025
|
Awesome, thank you |
winkerVSbecks
deleted the
deandre/sup-246-faq-why-do-tests-show-as-new-in-builds
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Explain why E2E tests would show as new in builds.