You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We are currently facing issues with Storybook runner visual tests failing due to incomplete hydration. We’ve experimented with both the mask feature , waitForPageReady and the waitFor method using Promise.all and custom polling, but the results remain inconsistent. Additionally, we’ve noticed that sometimes the masked elements seem to shift, causing tests to fail.
Describe the solution you'd like
Given that the Playwright package is already used in the Storybook runner, we suggest integrating the .toPass or .toPoll method. This could help improve the reliability of our visual tests by providing more consistent and readable assertions.
ihsib
changed the title
[Feature request]: implement equivalent to Playwrigts .toPass or .poll
[Feature request]: implement equivalent to Playwright’s .toPass or .poll
Jan 22, 2025
Is your feature request related to a problem? Please describe.
We are currently facing issues with Storybook runner visual tests failing due to incomplete hydration. We’ve experimented with both the
mask
feature ,waitForPageReady
and thewaitFor
method using Promise.all and custom polling, but the results remain inconsistent. Additionally, we’ve noticed that sometimes the masked elements seem to shift, causing tests to fail.Describe the solution you'd like
Given that the Playwright package is already used in the Storybook runner, we suggest integrating the .toPass or .toPoll method. This could help improve the reliability of our visual tests by providing more consistent and readable assertions.
https://playwright.dev/docs/test-assertions#expecttopass
https://playwright.dev/docs/test-assertions#expectpoll
Describe alternatives you've considered
No response
Are you able to assist to bring the feature to reality?
no
Additional context
No response
The text was updated successfully, but these errors were encountered: