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
Here is a setup that I am using:
I have an angular app that I instrument using nyc instrument --in-place command.
Then, I build a dev build npm run build:dev and serve it via http-server
I then run a set of tests using cypress after following the guide for cypress to understand and use the instrumentation (https://docs.cypress.io/guides/tooling/code-coverage).
After tests complete I recieve .nyc_output and coverage folders (inside cypress folder), which indicates cypress actually uses the instrumentation correctly, but code inside is instrumented, which makes it unreadable for human.
(while application is located in ./main/app, tests are located in ./main/tests)
Here is a setup that I am using:
I have an angular app that I instrument using
nyc instrument --in-place
command.Then, I build a dev build
npm run build:dev
and serve it viahttp-server
I then run a set of tests using cypress after following the guide for cypress to understand and use the instrumentation (https://docs.cypress.io/guides/tooling/code-coverage).
After tests complete I recieve
.nyc_output
andcoverage
folders (inside cypress folder), which indicates cypress actually uses the instrumentation correctly, but code inside is instrumented, which makes it unreadable for human.(while application is located in
./main/app
, tests are located in./main/tests
).nycrc
file:webpack-config.js
file (one that is used in cypress):Expected Behavior
Inside the
lcov' or
html` report, I recieve raw application code which allows me to check which functions/methods are used inside the components.Observed Behavior
Inside the
lcov
orhtml
report, I recieve instrumented code instead of raw, image belowTroubleshooting steps
cache: false
in my nyc configtypescript
anddecorators
toparser-plugins
.nyc-output
file to "main" application folder (main/app
) and generating new report usingnyc report --reporter=html
Environment Information
The text was updated successfully, but these errors were encountered: