You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running a lesser-known testing framework (called Alsatian) with nyc and ts-node, there should be an option to cover all files, despite the absence of a require definition in the config.
Observed Behavior
Coverage seems correct, in terms of individual files, but the results don't include files not directly imported by the tests. My understanding of "all": true that I've gleaned from issues and docs scattered about is that it won't actually include all files without a require. If I try to require ts-node/register with nyc (again, despite it seeming to work, coverage-wise, without that), then all desired files are included, but coverage becomes nonsense, highlighting random byte ranges.
Bonus Points! Code (or Repository) that Reproduces Issue
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
When running a lesser-known testing framework (called Alsatian) with nyc and ts-node, there should be an option to cover all files, despite the absence of a
require
definition in the config.Observed Behavior
Coverage seems correct, in terms of individual files, but the results don't include files not directly imported by the tests. My understanding of
"all": true
that I've gleaned from issues and docs scattered about is that it won't actually include all files without arequire
. If I try to requirets-node/register
with nyc (again, despite it seeming to work, coverage-wise, without that), then all desired files are included, but coverage becomes nonsense, highlighting random byte ranges.Bonus Points! Code (or Repository) that Reproduces Issue
package.json
and runner.tsForensic Information
Operating System: the operating system you observed the issue on.
Windows 10, Powershell
Environment Information: information about your project's environment, see instructions below:
sh -c 'node --version; npm --version; npm ls' > output.txt
gist of output.txt
The text was updated successfully, but these errors were encountered: