Instrument spawned processes with ts-node #2911
-
|
Can Vitest instrument The use case is integration testing for CLI applications. I recently swapped from mocha-chai to Vitest and the coverage half-worked. vitest config: Result: Previously, those with 100% branch coverage had 100% coverage for other columns too. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 9 replies
-
Currently Vitest does not intercept But I'm not sure if it can "see" processes launched by |
Beta Was this translation helpful? Give feedback.
-
|
Currently there are no plans or on-going work to support intercepting Supporting
As you are testing a CLI application, maybe you could start the testing from a different module and not the CLI entrypoint? - spawnSync("ts-node-esm", [path.join(__dirname, "application.ts")]);
+ await import("application.ts") // Now vite-node will handle the transforms and include it in coverageIt really depends on the application code whether this is possible. But for now that's all that I can think of. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, thank you for the answer. Yes, I am testing a CLI application directly. I believe outside of spawing, this can work with enough mocking:
I have looked around in vitest's mocking system, I am not sure if there are possible, can you point me towards them if they are? The stub.stubEnv seems confusing, I am not what is the lifecycle (does it auto clean up?) Is there be a way to mock native Lastly, I would like to ask if I should create this as a feature request in GitHub's issue Thank you! |
Beta Was this translation helpful? Give feedback.
-
Sure, feel free to create issue for this. Then more people will easier find it and tell if they need it as well. I'm not sure how to answer to these other questions related to |
Beta Was this translation helpful? Give feedback.
-
|
@AriPerkkio did you end up create a issue for this? I've stumbled into this while trying to get coverage for web workers and would like to follow the discussion if there's any. |
Beta Was this translation helpful? Give feedback.
-
|
No, I don't think anyone ended up filing feature requests for this. |
Beta Was this translation helpful? Give feedback.
-
|
See #7064 |
Beta Was this translation helpful? Give feedback.
Currently Vitest does not intercept
require()calls thatts-nodehooks into. It should be possible to implement a require hook for Istanbul instrumentation so that code that is not run throughvite-nodecould be included in code coverage.But I'm not sure if it can "see" processes launched by
child_process.spawn. There's nothing about patchingchild_processhere: https://github.com/istanbuljs/istanbuljs/blob/fb8cb4bb99c9e5d36c8b011338d2ab5d3c72ff9c/packages/istanbul-lib-hook/lib/hook.js#L229-L236Could you provide small example of this so that I could test it?