Added safety net preventing storybook Jest addon from throwing. #3023
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.
Added safety net preventing storybook Jest addon from throwing on unrecognized test results and forcing those results to be returned no matter their format.
Issue:
Storybook's Jest addon throws an Error when one of failed tests is a Jest snapshot and is not fully recognized by it.
What I did
Used enzyme-to-json to make better snapshots of React components in Jest when using Enzyme to render them. Failed tests would throw an exception in Storybook's Jest addon, because the addon could not fully recognize the format of the output.
How to test
reduce
cannot receive an object. This is due to one of reducers inside Storybook's Jest addon being unable to properly parse Jest's output and returning an object instead of an array for the next reducer.Is this testable with jest or storyshots?
Jest
Does this need a new example in the kitchen sink apps?
No
Does this need an update to the documentation?
No
If your answer is yes to any of these, please make sure to include it in your PR.