playwright-story-tests

To run Playwright tests against Storybook stories, you mount the story's iframe URL and execute the story's play function to validate UI behavior, ARIA roles, and IndexedDB state. This ensures consistent end-to-end UI behavior.

Yes, you can validate IndexedDB state during Storybook story tests. The testing mechanism accesses real-browser IDB contents within the iframe to ensure accurate data persistence and UI state validation.

The best way to automate E2E testing for Storybook stories is coordinating Playwright to mount id-based iframe URLs and validate post-condition UI and data, integrated directly into the bun run check workflow.

Yes, the Playwright Storybook testing workflow enforces metadata consistency. It validates the id-based iframe URL contract rendering to ensure accurate UI behavior and correct IndexedDB contents across story-level tests.

You integrate Storybook Playwright tests by running bun run check, which executes all story-level and story-URL tests to gate changes and ensure disciplined test-contract workflow compliance.

Playwright provides real-browser IDB access and validates the id-based iframe URL contract, ensuring post-condition UI and data accuracy that other category-level testing tools might not achieve within Storybook iframes.