How to exclude

node_modules

in the testing coverage report? I tried with

sst test --coverage

showing the node_modules files also in the coverage report.

use

--collectCoverageFrom='!**/node_modules'

flag

It didn't work. Still showing the node_modules in the coverage report

weird, this is what I use with create-react-app. Not sure what the issue is.

it's showing only a few packages i.e @aws/cdk and construct. Refer the screenshot.

It maybe because of how the constructs are wired, let me think.

{   "compilerOptions": {     "target": "ES2018",     "module": "commonjs",     "lib": ["es2018"],     "declaration": true,     "strict": true,     "noImplicitAny": true,     "strictNullChecks": true,     "noImplicitThis": true,     "alwaysStrict": true,     "noUnusedLocals": false,     "noUnusedParameters": false,     "noImplicitReturns": true,     "noFallthroughCasesInSwitch": false,     "inlineSourceMap": true,     "inlineSources": true,     "experimentalDecorators": true,     "strictPropertyInitialization": false,     "typeRoots": ["./node_modules/@types"]   },   "include": ["lib","src"] }

add a exclude: [“node_modules”]

Okay. Let me try.

okay, no more ideas left. 😅

Ok. NP. I resolved this by including the lib and src folder 😂

oh yes, that would work, good workaround. 👏

Just wanted to chime in here. I haven’t done much with coverage reports before but should the

node_modules

be ignored automatically?

No, most tooling require a configuration which decides what is to be included and what is to be not.

Ah I see. The flag that you posted before

--collectCoverageFrom='!**/node_modules'

that works in CRA but not in SST?

Yep, sst test could accept that flag and pass it to jest internally.

We’ll create an issue for this @Frank ?

Should we pass all the options passed to

sst test

to jest?

Yes, that would be the best way to ensure minimal confusion and avoid additional documentation.

Makes sense! https://github.com/serverless-stack/serverless-stack/issues/681

Started to look into this and as far as I can tell the arguments are passed through. If you run

sst test --collectCoverageFrom='!**/node_modules' --showConfig

you can see that the

"collectCoverageFrom"

field shows the expected value

Oh so we do support it? I wonder what @Bhuvaneshwaran Rajendran’s issue was then?

@Jay Even though I use collectCoverageFrom='!**/node_modules' it still covers some of the node_modules which should not happen. Please refer to the screenshot.

@thdxr Just bringing this up. It seems like something is amiss with our Jest configs?

Need to dig into this more, this doesn't happen for me. We should probably talk more about if

sst test

is adding value