You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we have a growing project in NX, with a lot of features generated by nx.
Typically when we're running jest tests, we can run the texts through nx affected and only run tests relating to the affected areas of our code.
however with storybook the 'story' is a bit different, it appears to be an all or nothing approach.
When I'm running 'nx affected -t test-storybook' it outputs a junit file which either contains test results for 0 tests (if no code has been touched in the project), or results for every single test if even just one feature has been modified.
Is there a way to solve this? for me to configure nx to tell storybook to only scan for stories in affected areas?
The nx documentation on storybook seems to have no mention of using nx affected.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, we have a growing project in NX, with a lot of features generated by nx.
Typically when we're running jest tests, we can run the texts through nx affected and only run tests relating to the affected areas of our code.
however with storybook the 'story' is a bit different, it appears to be an all or nothing approach.
When I'm running 'nx affected -t test-storybook' it outputs a junit file which either contains test results for 0 tests (if no code has been touched in the project), or results for every single test if even just one feature has been modified.
Is there a way to solve this? for me to configure nx to tell storybook to only scan for stories in affected areas?
The nx documentation on storybook seems to have no mention of using nx affected.
Beta Was this translation helpful? Give feedback.
All reactions