Yann Braga

Hey there! I wanted to thank you for using @storybook/testing-react! `@storybook/testing-react` has been promoted to a first-class Storybook functionality in Storybook 7. This means that you no longer need this...

Hey @puppybits! Feel free to open a PR and we can do experimentations to get it over the finish line. These are possible places to take a look at: https://github.com/storybookjs/test-runner/blob/future/playwright/custom-environment.js#L13...

Adding another use case from #109: > It would be very useful to have teardown() hook similar to setup() so we can run code after all stories are tested. >...

Hey @ild0tt0re thanks a lot for reporting this issue! This is definitely a use case I didn't think about. For scenarios like these, you can always work around them by...

Hey there! Thanks for opening this issue. Could you please create or share a minimal reproduction to take a look at? Thanks!

Hey @kasperpeulen you have recently experienced with merging Storybook and non-Storybook tests in a single jest config. Do you have any ideas to help here?

Maybe we can tackle this with [module augmentation](https://www.typescriptlang.org/docs/handbook/declaration-merging.html#module-augmentation) indeed, here's a quick sketch: ```ts // ./storybook/typings.d.ts import { ToolbarAnnotation } from '@storybook/addon-toolbars'; declare module '@storybook/core/types' { export interface ArgTypes extends...

The test runner by default will turn stories files defined in your `main.js` into tests, regardless if they are broken or not, which is different than how Chromatic accesses the...

I'll be closing this issue as it seems to be solved in Storybook 7, but feel free to reopen it in case you are still experiencing it in Storybook 7!

@SocketSecurity ignore-all