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
The image below shows an excerpt of a coverage report displayed by the jenkins CI cobertura plugin for a project that is mostly implemented in C++, but which has a component written in TypeScript running in node that is tested with jest using the istanbul cobertura coverage reporter. In the picture "sparrow" is the name of a component written in C++. The "src", "src.controller", "src.db", etc packages are all from the node subproject. My issue is that these packages don't have the subproject name prefixed.
I pass a projectRoot config property to jest which istanbul-reports/lib/cobertura/index.js uses for filepaths, but not for package names. This is what is generated:
The problem is the package attribute name="src" it should be name="sub-project.src" to be consistent with the projectRoot and match the path in the class filename="sub-project/src/app.ts" attribute.
The text was updated successfully, but these errors were encountered:
The image below shows an excerpt of a coverage report displayed by the jenkins CI cobertura plugin for a project that is mostly implemented in C++, but which has a component written in TypeScript running in node that is tested with jest using the istanbul cobertura coverage reporter. In the picture "sparrow" is the name of a component written in C++. The "src", "src.controller", "src.db", etc packages are all from the node subproject. My issue is that these packages don't have the subproject name prefixed.
I pass a projectRoot config property to jest which istanbul-reports/lib/cobertura/index.js uses for filepaths, but not for package names. This is what is generated:
The problem is the package attribute
name="src"
it should bename="sub-project.src"
to be consistent with the projectRoot and match the path in theclass filename="sub-project/src/app.ts"
attribute.The text was updated successfully, but these errors were encountered: