Fix mistake as test files when run coverage issue.

[H1Gdev]

• Check testPathIgnorePatterns.
• Add tests.

Summary

Run coverage the following test environment.

package.json

{
  "jest": {
    "testPathIgnorePatterns": [
      "/node_modules/",
      "/src/"
    ],
  }
}

file tree

├── __tests__
│   └── component.spec.js
└── src
     ├── component.js
     └── spec.js

Expect:

• src/spec.js file is not a test file.

Actual:

• src/spec.js file is a test file.

Test plan

Above test result as expected.

--------------------|----------|----------|----------|----------|-------------------|
File                |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
--------------------|----------|----------|----------|----------|-------------------|
All files           |      100 |      100 |      100 |      100 |                   |
 src                |      100 |      100 |      100 |      100 |                   |
  component.js      |      100 |      100 |      100 |      100 |                   |
  spec.js           |      100 |      100 |      100 |      100 |                   |
--------------------|----------|----------|----------|----------|-------------------|

[thymikee]

there's the same check a bit further down this file: https://github.com/facebook/jest/blob/f38b0c9d17f92f3e0f144087db6264d585bcbeed/packages/jest-runtime/src/should_instrument.js#L79-L84

maybe we can just move it up to this place?

[SimenB]

@thymikee testPathIgnorePatterns vs coveragePathIgnorePatterns, no?

[thymikee]

🙈

[H1Gdev]

@thymikee
@SimenB

Thank you for your review.

I think that it is determined by testRegex, testMatch and testPathIgnorePatterns whether file is test file or not.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.