Hoping to use this plugin in conjunction with the @stencil/playwright adapter for E2E testing1.
In Playwright, we use the Stencil adapter's page.goto() method to load the Story's iframe content directly and then make assertions against it. However, we run into occasional flakiness where the story has not rendered by the time the assertions run. I see the adapter adds logic to the goto() method to wait for the appload event to trigger before finishing. However, debugging this event, the story is not attached to the DOM by the time the event is triggered.
Would it be appropriate for the Stencil storybook plugin to defer the appload event until after the story is rendered and hydrated?
Hoping to use this plugin in conjunction with the
@stencil/playwrightadapter for E2E testing1.In Playwright, we use the Stencil adapter's
page.goto()method to load the Story's iframe content directly and then make assertions against it. However, we run into occasional flakiness where the story has not rendered by the time the assertions run. I see the adapter adds logic to thegoto()method to wait for theapploadevent to trigger before finishing. However, debugging this event, the story is not attached to the DOM by the time the event is triggered.Would it be appropriate for the Stencil storybook plugin to defer the
apploadevent until after the story is rendered and hydrated?Footnotes
https://stenciljs.com/docs/testing/playwright/e2e-testing ↩