Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Running jest in own process, connect via IPC & stream results via websockets #32

Merged
merged 3 commits into from
Mar 9, 2017

Conversation

ndelangen
Copy link
Collaborator

No description provided.

@mthuret
Copy link
Owner

mthuret commented Mar 9, 2017

Thanks @ndelangen. I really need to find some time to take a look at this because it sounds super great :)

@mthuret mthuret merged commit aaad7ca into mthuret:jest-test-files Mar 9, 2017
@ndelangen
Copy link
Collaborator Author

It incomplete though :)

@gunnx
Copy link

gunnx commented Jun 26, 2017

Hi,
Is this still waiting for review? I wondered if it was affected by the upgrade to StoryBook 2
Thanks

@mthuret
Copy link
Owner

mthuret commented Jun 26, 2017

It's still on a branch for a POC. It was put on hold as @ndelangen is handling more core storybook development and I don't have that much time to dedicate to this project as for now. Any take over or improvement are welcome though :)

@dan-kez
Copy link

dan-kez commented Oct 2, 2017

This would also be very useful for react native testing. Running the tests in a separate process allows us to more easily use react-native-mock/mock for better enzyme testing without mucking around with the rendered view.

I'm not entirely sure where help would be best applied but I would love to see this come to fruition!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants