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
{{ message }}
This repository was archived by the owner on Dec 8, 2024. It is now read-only.
E.g. Karma's preprocessor instruments file by file. In this case the instrumentation is done with absolute path. Whereas the cli allows instrumentation off directories which are enforced by code to be relative.
instrument.js:#204 relative: true
Merging these results with a middleware does not work. It is desired to expose the option relative to the cli.
The text was updated successfully, but these errors were encountered:
In an Meteor project called RTD we have a mix of instrumentation for acceptance tests and unit tests. The one uses Karma, which instruments the files file-by-file. This results into instrumentations having an absolute path. For the other method we use Istanbul directly by passing an directory. In this case all directories are relative.
If we merge these friends together in order to get a full coverage result for both tests, the results are not merged and each file is listed twice, since they're instrumented differently. (side-note: istanbul-middleware-port is used)
We fix this currently with preprocessing the report data using the following statement.
E.g. Karma's preprocessor instruments file by file. In this case the instrumentation is done with absolute path. Whereas the cli allows instrumentation off directories which are enforced by code to be relative.
Merging these results with a middleware does not work. It is desired to expose the option relative to the cli.
The text was updated successfully, but these errors were encountered: