Replies: 1 comment
-
According to the call about what benefits could the storybook brings to design systems and testing components. We decided to focus on these aspects:
For the first step, I'm going to integrate the interactor inspector to show the matched interactors for the current story, allow execute actions for these ones, show element's props, and highlight elements. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the last brainstorm session for the H1 2021, we decided it is nice to have this feature for the BigTest. I still don't have enough context about the project, so I'd like to discuss this feature's details. How do you see it should be?
So how I see it.
It should be a third-party addon that reuses the interactors inspector #873 to show information about matched interactors and provide a place to play around with the interactor's actions.
Storybook allows reusing stories in unit tests. We could try to show tests and provide the ability to run them right in Storybook.
We might allow the user to record actions sequence for the actions editor or test cases. But I think it's not so important for now.
Beta Was this translation helpful? Give feedback.
All reactions