-
Notifications
You must be signed in to change notification settings - Fork 682
Jest for nuclide-test-runner #214
Comments
A test runner for Jest is something I'd like to add. The test runner interface currently expects JSON output (current JSON shape is in TestSuiteModel.js:19), which Jest/Jasmine do not bundle yet. jestjs/jest#513 is open to integrate with Arcanist, the CLI for Phabricator which also consumes JSON output for unit testing. It's possible for a test runner to simply write unstructured output to the buffer, but it would offer little more than typing |
Thanks for replying, yes being able to run npm test via a button in Nuclide would be a useful first step. |
Based on jestjs/jest@5413b7b, I'm not against contributing but I've no idea what to do. |
I'm attempting to create one here: |
While discussing with @cpojer, he mentioned @kentaromiura is the right person to approach with this request. Along with the test runner, it would also be great to have code coverage support as jest supports it natively. There are some packages available, but has some usability issues. It would be great to have something similar to flow coverage, where it highlights when click the percentage status on bottom. Also great to have a tree view of coverage, may be in a panel. thanks for your work on this. https://github.com/taskworld/atom-lcov |
Any new informations concerning this issue ? |
|
Not currently. |
Since this isn't something Nuclide is supporting or planning to support, what are most people using to debug jest tests on Atom? |
@captbaritone does oss nuclide come with a debugger? in this case running jest with |
This issue was a 2017 goal for Jest. Let's make up a featureset that would be representative of the sophisticated nature of both Nuclide and Jest and see if the community, myself included, can tackle this. VSCode has a Jest runner, I can't live with that. |
Since Jest is another Facebook project, can I expect that we will see a Jest nuclide-test-runner?
The text was updated successfully, but these errors were encountered: