Jest not able to find test specs in Windows 10

[nirkki]

Fresh project with 'vue init webpack just-testing' doesn't find the test files in Win 10
...
25 files checked.
testMatch: /tests//.js?(x),**/?(.)(spec|test).js?(x) - 1 match
testPathIgnorePatterns: \node_modules\ - 25 matches
Pattern: test/unit/specs - 0 matches

[LinusBorg]

@eddyerburgh Got an idea?

[eddyerburgh]

@nirkki can you try running:

npm run unit -- --no-watchman

I'm basing this off a stackoverflow answer.

[fedegar33]

Same issue on Windows 7. Tried to run npm run unit -- --no-watchman but the problem persists.

[nirkki]

Didn't help here either. I also found some notes that Jest has had some issues with Windows paths containing special chars - but my project doesn't have those.
jestjs/jest#4467

[nirkki]

Tried to troubleshoot this further: installing jest globally didn't make difference on 'npm run unit'
But it enabled me to run it from the command line - and here is the result

C:\test\jesting> jest --coverage
 PASS  test\unit\specs\HelloWorld.spec.js
  HelloWorld.vue
    √ should render correct contents (27ms)

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total
Snapshots:   0 total
Time:        1.403s
Ran all test suites.
-----------------|----------|----------|----------|----------|----------------|
File             |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
-----------------|----------|----------|----------|----------|----------------|
All files        |        0 |        0 |        0 |        0 |                |
 src             |        0 |        0 |        0 |        0 |                |
  App.vue        |        0 |        0 |        0 |        0 |... 19,20,21,22 |
 src/components  |        0 |        0 |        0 |        0 |                |
  HelloWorld.vue |        0 |        0 |        0 |        0 |... 39,40,41,42 |
-----------------|----------|----------|----------|----------|----------------|

But if I give a path the result is the same as running npm run unit

 C:\test\jesting> jest test/unit/specs --coverage
No tests found
In C:\test\jesting
  28 files checked.
  testMatch: **/__tests__/**/*.js?(x),**/?(*.)(spec|test).js?(x) - 1 match
  testPathIgnorePatterns: \\node_modules\\ - 28 matches
Pattern: test/unit/specs - 0 matches
----------|----------|----------|----------|----------|----------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
----------|----------|----------|----------|----------|----------------|
All files |  Unknown |  Unknown |  Unknown |  Unknown |                |
----------|----------|----------|----------|----------|----------------|

[eddyerburgh]

I'm not sure what to suggest. It looks like Jest has some long standing issues with Windows that I was unaware of.

All the issues I have looked at suggest that they won't be fixed by the maintainers any time soon 😕

[nirkki]

Too bad, I'll revert back to Karma-Mocha. At least feel more like home there. Thanks for help!

[eddyerburgh]

Sorry @nirkki . We'll probably move back to Karma and mocha as the default because of this issue

[eddyerburgh]

@nirkki Can you post the full path of your tests. Does it include parentheses, like C:\Program Files\tmp (x86)\project

I'm pretty sure it has to do with this issue — jestjs/jest#2381

[nirkki]

No paranthesis in the path C:\test\jesting

[Akryum]

Here is a working config for Windows 10:

{
  rootDir: "D:\\Mes documents\\GitHub\\livestorm-container\\livestorm-app",
  roots: ["<rootDir>/app/frontend"],
  moduleFileExtensions: [
    "coffee",
    "js",
    "json",
    "jsx",
    "ts",
    "vue",
    "sass",
    "scss",
    "styl",
    "css",
    "png",
    "svg",
    "gif",
    "jpeg",
    "jpg"
  ],
  moduleDirectories: [
    "app/frontend",
    "node_modules",
    "app/frontend",
    "app/frontend/packs",
    "app/frontend/common/js/",
    "app/frontend/common/vue",
    "app/frontend/common/vue/components",
    "app/frontend/api",
    "app/frontend/config",
    "config/locales-front",
    "public"
  ],
  moduleNameMapper: { "^@/(.*)$": "<rootDir>/app/frontend/$1" },
  transform: {
    "^.+.jsx?$": "<rootDir>/node_modules/babel-jest",
    ".*.(vue)$": "<rootDir>/node_modules/jest-vue"
  },
  mapCoverage: true,
  snapshotSerializers: ["<rootDir>/node_modules/jest-serializer-vue"],
  testPathIgnorePatterns: ["/node_modules/", "/vendors/"],
  setupFiles: ["<rootDir>/test/frontend/jest-setup"]
}

[robertmain]

Windows 10 user here chipping in. I find it works if I run npx jest but not npm run-script unit. To say I'm confused is an understatement.

Additionally, manually running the jest test/unit/specs --coverage command doesn't work. It seems to be interpreting the test/unit/specs as the pattern to search for unit test specs...which doesn't work for some reason. Remove that and it seems to at least find the test suites.

[eddyerburgh]

@robertmain could you change the script to this:

"unit": "jest test/unit --coverage",

And see if that solves your issue