Ask HN: Is it time for a new Storybook?

Re:Ask HN: Is it time for a new Storybook? by lmiller1990 on Saturday November 19, 2022 @05:33PM (#33675530)

I think a single tool to solve design + testing would be great. Cypress does Component Testing now, and you can use it in a Storybook-esque fashion, but it doesn't export to a static site for documentation, and instead of using knobs/plugins, you automate with the Cypress API. It's missing some of the design touches of Storybook, though.

Storybook is good for design, but the testing integration is definitely lacking. Having to maintain <test suite in Jest> alongside <design suite> feels like a lot of code.

[ Parent | on HN ]

Re:Ask HN: Is it time for a new Storybook? by samhuk on Saturday November 19, 2022 @05:46PM (#33675679)

Thanks for your feedback. I agree on most of your points.

I feel like Cypress moving into the component testing arena was an interesting move.

[ Parent | on HN ]

Re:Ask HN: Is it time for a new Storybook? by chantastic on Monday November 21, 2022 @01:41AM (#33689572)

lmiller1990, have you experimented much with @storybook/test-runner?

I've found it pretty capable for doubling my stories as Jest tests. For those using testing-library for component testing, it even acts like a GUI for those tests.

If you're interested, I threw together a little walkthru that show some of the ways I'm using it with Jest: https://github.com/chantastic/vite-react-jest-testing-librar...

[ Parent | on HN ]