The way storyshots currently works prevents it from showing feedback during runs. Only after every story has been run, is there any feedback.
This is disturbing especially for large storybooks, as the process seems to hang, and gives the impression is broken.
It would be much nicer is all stories are run individually.
This has a couple of other improvements as well: The stories can be sharded over multiple CPU's, individual stories can be re-run and failures are detected faster.
The idea is to overhaul storyshots to not wrap ALL stories, but instead run story-files directly in jest, and provide a storybook facade for it's api's.
This would remove a lot of complexity for us as well, as most options can be deprecated.