-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Add Storybook tests #137
Open
ptgott
wants to merge
1
commit into
main
Choose a base branch
from
paul.gottschling/17-storybook
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Add Storybook tests #137
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
Amplify deployment status
|
44cc6b3
to
e8b2a97
Compare
e8b2a97
to
a09ee70
Compare
a09ee70
to
65a3581
Compare
231d71f
to
87cf186
Compare
631b857
to
d935d2b
Compare
d935d2b
to
56d24cb
Compare
Prevent regressions in our custom components by adding Storybook testing. Copy Storybook tests from the archived `gravitational/docs` repo. Add a rough-and-ready Storybook configuration to enable tests to pass. One significant complication is that Docusaurus generates a Webpack configuration when building a docs site. There are Storybook frameworks and add-ons for Docusaurus that take advantage of Docusaurus's asset-loading logic, but none are currently being maintained. The quickest thing we can do is add a separate Webpack configuration that renders components in Storybook similarly (but not identically) to the Docusaurus site. A separate change can refine this approach by, for example: - Vendoring a Storybook Docusaurus framework - Migrating Storybook tests to `react-testing-library` Also add a step to the `Run tests` GitHub Actions job to run the Storybook tests.
56d24cb
to
aef9425
Compare
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.
Prevent regressions in our custom components by adding Storybook testing. Copy Storybook tests from the archived
gravitational/docs
repo. Add a rough-and-ready Storybook configuration to enable tests to pass.One significant complication is that Docusaurus generates a Webpack configuration when building a docs site. There are Storybook frameworks and add-ons for Docusaurus that take advantage of Docusaurus's asset-loading logic, but none are currently being maintained. The quickest thing we can do is add a separate Webpack configuration that renders components in Storybook similarly (but not identically) to the Docusaurus site.
A separate change can refine this approach by, for example:
react-testing-library