-
Notifications
You must be signed in to change notification settings - Fork 14
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
Failed to save coverage (for TypesScript) #79
Comments
Hello, I'm not sure the coverage is working on Windows. Last time I checked it wasn't with I did not test with Typescript neither. As you can see in the logs, there is no file that has been instrumented on the client side : If I get some time, I will try with your repository. |
Updated issue. Had a workaround, see commit. Essentially, revert to |
Maybe the babel instanbul package is not compatible with the meteor typescript package. |
Added dummy server test (with empty test body) in
Then tried renaming Tried again with |
Sorry, but that's not what I'm expecting. Are you sure you added the |
Here's the output dump with
|
Ok there is no clue about what is failing... If you run it in watch mode + coverage verbose, then open the test app (localhost:3000). Then if you do the same with the react app from my example repository, do you see the code instrumented ? I hope you get what I mean... ;) |
After starting test in watch mode. Server console output stops at:
When viewing source, all except 2 bundle scripts are in Interestingly, the server tests only shows in serve console output but not in browser. |
As there is no plan to officially support Meteor + Typescript + babel together (see this), the current version of meteor-coverage does not receive any coverage information about your source app. That's why my library is active but there is no coverage to export. |
Looks good! Will do more extensive tests over next few weeks and report back. |
So far testing on another project works for both TS and JS files. So the |
Everything have been published ! If you encounter any problem, feels free to open again this issue or create another one ! ;) |
I have the same issue as TC even not on typescript:
i do my call with |
@Gobliins the fix for me was to never use relative paths, always replace './' with |
Unable to save report even though tests completed.
Codebase.
Commit:
906dead1e336493ec1cde8653678d68f38bd9de3
Expected Behavior
Coverage report generated.
Possible Solution
Using
lmieulet:[email protected]
is a partial fix. But static assets will not be generated or are 0 bytes. Furthermore, the packages MUST be in .meteor/packages in the following order: meteortesting:[email protected], jquery, lmieulet:[email protected].Steps to Reproduce (for bugs)
However, renaming
Info.test.js
toInfo.tests.js
will render HTML coverage results with onlyInfo.tests.js
.Context
Your Environment
The text was updated successfully, but these errors were encountered: