Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Storyshot, run individual tests
See original GitHub issueThis #6331 addresses the issue. I think it should have some priority since you can’t develop and run only one test for your story. All the tests will run. This implies a big problem if, for example, you are editing a single component and want to “update” the shot for that component with jest -u, all the conflicting components will be accepted. Ideally, one should update an isolated component, update the shot, and the go through all the conflicts modifying accordingly their context.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:38
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We’re hitting this problem on a pretty large project where we’re hoping to transition to storyshots. Having to run our entire test suite to update a single snapshot is painful. . . so 🙏 and ➕➕
Using hooks as a pre-commit or pre-push should ideally test only the staged files but because of this problem, it runs tests across all the stories and if any non-related tests are breaking the developer are stuck from pushing their changes upstream. Please consider this feature. 🙏