Tests are not found out of the box #1686

lmiller1990 · 2018-06-27T12:40:14Z

Version

3.0.0-rc.3

Reproduction link

https://would-not-be-useful.com could not find a good way to do this - I think it must be related to some other setting.

Steps to reproduce

vue create test_app -> choose babel and jest

yarn unit:test
yarn run v1.7.0
$ vue-cli-service test:unit
No tests found
In /Users/lachlanmiller/javascript/vue/qiita_post
  10 files checked.
  testMatch: /Users/lachlanmiller/javascript/vue/qiita_post/(tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx)) - 0 matches
  testPathIgnorePatterns: /node_modules/ - 10 matches
Pattern:  - 0 matches
 ERROR  jest exited with code 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

What is expected?

It runs HelloWorld.spec.js

What is actually happening?

It does not find the test

MacOS 10.13.2 High Sierra
Happening on another machine (not sure of the macOS version for it, but it's high sierra). I can check the version tomorrow. I tried using both npm and yarn, and jest directly.

I tried both with jest config in package.json and standalone.

Also I cannot specify either:

yarn test:unit --  --runTestsByPath tests/unit/HelloWorld.spec.js

> vue-cli-service test:unit "--runTestsByPath" "tests/unit/HelloWorld.spec.js"

No tests found
No files found in /Users/lachlanmiller/javascript/vue/qiita_post.
Make sure Jest's configuration does not exclude this directory.
To set up Jest, make sure a package.json file exists.
Jest Documentation: facebook.github.io/jest/docs/configuration.html
Files: "tests/unit/HelloWorld.spec.js"

HOWEVER git cloning a project scaffolded on another PC works somehow.

Other projects on my machine are using jest no problem. Not sure what's going on. Any ideas?

The text was updated successfully, but these errors were encountered:

allochi · 2018-06-27T13:36:02Z

Hi, the same happened to me on MacOS 10.13.4 High Sierra, I removed the enclosing round brackets in jest.config.js and it works. basically, this works:

testMatch: [
    "<rootDir>/tests/unit/**/*.spec.(js|jsx|ts|tsx)|<rootDir>/**/__tests__/*.(js|jsx|ts|tsx)"
]

renyuanz · 2018-06-27T15:21:14Z

@allochi not working neither, but I'm on Windows 10
Exactly the same problem as described as @lmiller1990

lmiller1990 · 2018-06-28T01:06:54Z

Both my machines are 10.13.2 and confirmed the bug is the same.

@allochi thanks, that works for me. Are the other brackets necessary? If not, could they be removed (not sure if that would impact other systems).

Edit, looks like jest could be the culprit (see #1691 )

hajarrashidi · 2018-06-28T07:49:38Z

Allochi solution on mac works. but not in windows.

allochi · 2018-06-28T08:34:39Z

testMatch is an array, so I guess the following should work too (it did for me):

testMatch: [
    "<rootDir>/tests/unit/**/*.spec.(js|jsx|ts|tsx)",
    "<rootDir>/**/__tests__/*.(js|jsx|ts|tsx)"
]

It runs any test in the project's /tests/unit/ directory or any test in the project as long as it's in a __tests__ directory.

allochi · 2018-06-28T08:36:15Z

If you plan to have all your tests in /tests/unit/, just use:

testMatch: [
    "<rootDir>/tests/unit/**/*.spec.(js|jsx|ts|tsx)"
]

hajarrashidi · 2018-06-28T13:27:41Z

Not working /:

rdsn · 2018-06-29T09:00:45Z

The issue on windows seems to be caused by the fact that jest v23 uses micromatch v3.1.10, while jest v22 used micromatch v2.3.11.

let micromatch = require('micromatch');

let path = 'D:\\app\\tests\\unit\\HelloWorld.spec.js';
let glob= 'D:/app/(tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx))';

console.log(micromatch([path], glob));

// with micromatch@2.3.11 logs
// [ 'D:/app/tests/unit/HelloWorld.spec.js' ]

// with micromatch@3.1.10 logs
// []

lmiller1990 · 2018-06-29T09:03:54Z

I think the best solution would be to downgrade to jest 22, until the bug is addressed there.

mildc055ee · 2018-07-02T12:09:29Z

hello, I have same problem on windows 10, however, I can run test correctly in the following way

remove testMatch block
add transformIgnorePatterns like below

    "transformIgnorePatterns": [
      "node_modules/"
    ],

andreydos · 2018-07-02T13:22:21Z

On Ubuntu I have the same problem, I just add an additional path to

testMatch: [
    "<rootDir>/(tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx))",
    "<rootDir>/tests/unit/*.spec.(js|jsx|ts|tsx)"  // match test specs directly in "unit" directory  
  ]

coldino · 2018-07-02T23:31:41Z

On Windows the listed workarounds don't seem to work.

Although not idea, I found this combination means I can run tests again:

    "moduleFileExtensions": [ "ts", "js" ],
    "testMatch": [ ]

abbyjeet · 2018-07-10T06:04:56Z

@mildc055ee 's solution worked for me in Windows 10

mario-d-s · 2018-07-11T09:45:42Z

This issue is not fixed on Windows with #1756 😞. I just re-ran vue invoke unit-jest, adjusted the regex based on what was committed, and the generated HelloWorld.spec.js is still not found...

Akryum · 2018-07-11T09:51:08Z

Try this one: 96778b2#diff-29994942bb568c5548a12d8103751233R34

mario-d-s · 2018-07-11T11:12:23Z

@Akryum that one does work!

By the way I've just regenerated a project with vue-cli and strangely enough, now the test just works. I don't know what's changed. My CLI version is still 3.0.0-rc.3.

kevinhofmaenner · 2018-07-17T19:19:23Z

@mario-d-s

I scaffolded a vue-cli 3 app about ~2 weeks ago and my jest.config.js file looked like this:

module.exports = {
  moduleFileExtensions: ["js", "jsx", "json", "vue"],
  transform: {
    "^.+\\.vue$": "vue-jest",
    ".+\\.(css|styl|less|sass|scss|png|jpg|ttf|woff|woff2)$":
      "jest-transform-stub",
    "^.+\\.jsx?$": "babel-jest"
  },
  moduleNameMapper: {
    "^@/(.*)$": "<rootDir>/src/$1"
  },
  snapshotSerializers: ["jest-serializer-vue"],
  testMatch: [
    "<rootDir>/(tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx))"
  ]
};

When I scaffolded a new app today, jest.config.js now looks like

module.exports = {
  moduleFileExtensions: ["js", "jsx", "json", "vue"],
  transform: {
    "^.+\\.vue$": "vue-jest",
    ".+\\.(css|styl|less|sass|scss|png|jpg|ttf|woff|woff2)$":
      "jest-transform-stub",
    "^.+\\.jsx?$": "babel-jest"
  },
  moduleNameMapper: {
    "^@/(.*)$": "<rootDir>/src/$1"
  },
  snapshotSerializers: ["jest-serializer-vue"],
  testMatch: [
    "**/tests/unit/**/*.spec.(js|jsx|ts|tsx)|**/__tests__/*.(js|jsx|ts|tsx)"
  ]
};

Note the difference between the testMatch array.

mario-d-s · 2018-07-17T20:23:08Z

@kevinhofmaenner that is what vue-cli-plugin-unit-jest 3.0.0-rc.5 does. Can you check the version?

kevinhofmaenner · 2018-07-18T12:48:45Z

@mario-d-s - correct, the sample app I spun up yesterday was using 3.0.0-rc.5

onexdata · 2019-02-12T16:13:31Z

For people having this issue, the latest version of Jest doesn't like the <rootdir> in testMatch. This happened in Jest 23/24, so if you built your jest.config.js file in and older version of Jest, then upgraded to Jest latest, you will have this issue.

Use something like this instead:

'testMatch': [
  '**/?(*.)(spec).js?(x)',
  '**/?(*.)(test).js?(x)'
],

Breaking changes like this would be nice if Jest warned you that the devs decided to implement a breaking change, instead of just giving cryptic errors when the developer does nothing wrong.

Stuff like this makes all Jest 22 and previous source code that includes a jest.config.js file broken, for example. How is this good for the community?

ghost · 2019-12-13T06:34:21Z

@onexdata Really it would be nice if the documentation would cover this somehow. I tried ./test/*.js, test/*.js, but only **/test/*.js worked. I wonder why processing a simple glob pattern is so hard. This should be a core feature that works flawlessly instead of a barely supported and documented thing...

edit:
Lol, I thought we are in a jest issue. :-)

mohsenuss91 · 2020-04-16T09:01:11Z

<rootDir>/tests/unit/**/*.spec.(js|jsx|ts|tsx)|<rootDir>/**/__tests__/*.(js|jsx|ts|tsx)

@allochi I try it now I've got this :

  ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import { shallowMount } from '@vue/test-utils';
                                                                                             ^^^^^^

    SyntaxError: Cannot use import statement outside a module

lmiller1990 mentioned this issue Jun 28, 2018

No tests found when running npm run test:unit #1691

Closed

Akryum added bug scope: unit-jest needs team repro We acknowledged your report and will soon try to reproduce it priority: now labels Jun 28, 2018

tony19 mentioned this issue Jun 28, 2018

No tests found after installing buefy #1694

Closed

LinusBorg mentioned this issue Jul 2, 2018

Adjust documentation for using @vue/babel-preset-app in a non vue-cli environment #1725

Closed

savander mentioned this issue Jul 2, 2018

Test are not working properly with jest after micromatch update. VougeJS/Vouge#7

Closed

darkodemic mentioned this issue Jul 4, 2018

Fix issue with Jest configuration regex not matching template. #1756

Merged

Akryum closed this as completed in #1756 Jul 4, 2018

This was referenced Jul 6, 2018

jest.config.js > testMatch pattern is not working on windows 10 machine #1777

Closed

@vue/cli-plugin-unit-jest test configuration broken #1795

Closed

Akryum mentioned this issue Jul 10, 2018

Can't find and run generated unit tests #1804

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tests are not found out of the box #1686

Tests are not found out of the box #1686

lmiller1990 commented Jun 27, 2018 •

edited

Loading

allochi commented Jun 27, 2018 •

edited

Loading

renyuanz commented Jun 27, 2018

lmiller1990 commented Jun 28, 2018 •

edited

Loading

hajarrashidi commented Jun 28, 2018

allochi commented Jun 28, 2018 •

edited

Loading

allochi commented Jun 28, 2018

hajarrashidi commented Jun 28, 2018

rdsn commented Jun 29, 2018

lmiller1990 commented Jun 29, 2018

mildc055ee commented Jul 2, 2018

andreydos commented Jul 2, 2018 •

edited

Loading

coldino commented Jul 2, 2018

abbyjeet commented Jul 10, 2018

mario-d-s commented Jul 11, 2018

Akryum commented Jul 11, 2018

mario-d-s commented Jul 11, 2018

kevinhofmaenner commented Jul 17, 2018

mario-d-s commented Jul 17, 2018

kevinhofmaenner commented Jul 18, 2018

onexdata commented Feb 12, 2019 •

edited

Loading

ghost commented Dec 13, 2019 •

edited by ghost

Loading

mohsenuss91 commented Apr 16, 2020

Tests are not found out of the box #1686

Tests are not found out of the box #1686

Comments

lmiller1990 commented Jun 27, 2018 • edited Loading

Version

Reproduction link

Steps to reproduce

What is expected?

What is actually happening?

allochi commented Jun 27, 2018 • edited Loading

renyuanz commented Jun 27, 2018

lmiller1990 commented Jun 28, 2018 • edited Loading

hajarrashidi commented Jun 28, 2018

allochi commented Jun 28, 2018 • edited Loading

allochi commented Jun 28, 2018

hajarrashidi commented Jun 28, 2018

rdsn commented Jun 29, 2018

lmiller1990 commented Jun 29, 2018

mildc055ee commented Jul 2, 2018

andreydos commented Jul 2, 2018 • edited Loading

coldino commented Jul 2, 2018

abbyjeet commented Jul 10, 2018

mario-d-s commented Jul 11, 2018

Akryum commented Jul 11, 2018

mario-d-s commented Jul 11, 2018

kevinhofmaenner commented Jul 17, 2018

mario-d-s commented Jul 17, 2018

kevinhofmaenner commented Jul 18, 2018

onexdata commented Feb 12, 2019 • edited Loading

ghost commented Dec 13, 2019 • edited by ghost Loading

mohsenuss91 commented Apr 16, 2020

lmiller1990 commented Jun 27, 2018 •

edited

Loading

allochi commented Jun 27, 2018 •

edited

Loading

lmiller1990 commented Jun 28, 2018 •

edited

Loading

allochi commented Jun 28, 2018 •

edited

Loading

andreydos commented Jul 2, 2018 •

edited

Loading

onexdata commented Feb 12, 2019 •

edited

Loading

ghost commented Dec 13, 2019 •

edited by ghost

Loading