These tests use NO CODE | component testing in Storybook

[@asilurian]

This. Changes. Everything! :D Really excited to use this

[@chantastic]

heck yeah! me too :)

[@gokhankoc3507]

I have been using interactions for a while at work and love them. Now I believe there needs to be further documentation for testing strategies, patterns and examples. For example, to be able to test actions (they will be automatically jest.fn() mocks), they need to be defined in argTypes. It took hours for me to figure that out. Is there any way I can contribute?

[@chantastic]

have you had a chance to look at the test-runner documentation? there are a number of recipes there. a number of our posts and videos are just resurfacing the documentation there github.com/storybookjs/test-runner#setting-up-code-coverage

[@chantastic]

and yeah! we're always open to contributions. the test-runner docs (linked in the other comment) are the best place to make contributions. this particular package is under a lot of active development

[@xardass4209]

When run test runner in cli, storybook 8.5.3 I got message: An error occurred in the following story, most likely because of a navigation. I noticed this when there is more than one story in stories.ts/tsx file. Is there any solution or setting for this case?

[@dominicnguyen5465]

Haha "Stabbing your components with a blindfold on" ❤

[@SithLordBishop]

does this work with vitest?

[@chromaticui]

sadly no

[@jamesgarcia1538]

This is amazing! Thanks for sharing :)

[@chantastic]

Thanks for the encouragement James!

[@kabburebh]

These tests can show the coverage in sonar as well?

[@chromaticui]

We have a doc that covers integration with Istanbul. None for sonar yet. But the Istanbul docs may provide some general guidance storybook.js.org/docs/react/writing-tests/test-coverage

[@xennialmusic]

I'm in the Storybook Discord channel and I can't find the testing channel you speak of at the end of the video.

[@chromaticui]

discord.com/channels/486522875931656193/691505730125168682

[@justingiovanetti]

“With no test code”? You showed the test code.

[@sebastianthomas1901]

"Get free tests with just two lines!". Proceeds to write tests. So sick of these hype men talking nonsense and selling lies

[@Thr0nSK]

Any idea why I'm getting a type error `TS2339: Property 'toHaveStyle' does not exist on type 'JestMatchers '.` with the `toHaveStyle` method?

[@chromaticui]

stackoverflow.com/questions/38324949/error-ts2339-property-x-does-not-exist-on-type-y

[@Thr0nSK]

@@chromaticui Sorry but I'm not sure how this helps. I shouldn't need to extend the type, should I? I saw that other people had problems with this as well and solved it by adding @types/testing-library__jest-dom but it doesn't seem to help in my case.

[@eduardoalvarez4457]

In case someone just came from the documentation using TypeScript and get errors everywhere, remember to rename your story from component.stories.ts to component.stories.tsx (notice the x at the end) as the decorator is JSX and its required for the TypeScript compiler to be valid.