Moving src files doesn't bust the Jest cache #3705

adityavohra7 · 2017-05-31T23:07:02Z

Do you want to request a feature or report a bug?

Bug report.

What is the current behavior?

Moving a source file doesn't seem to bust the Jest cache. This causes the default coverage reporter to report missing coverage on the moved file in the new location, and report full coverage on the moved file in the old location.

If the current behavior is a bug, please provide the steps to reproduce and either a repl.it demo through https://repl.it/languages/jest or a minimal repository on GitHub that we can yarn install and yarn test.

Here is my src dir structure:

$ tree src/
src/
├── components
│   └── Example
│       └── README.md
├── foo
│   └── index.js
└── scss
    └── index.scss

4 directories, 3 files

Running jest before moving index.js:

$ ./node_modules/.bin/jest --config jest.config.js
 PASS  tests/components/example.test.js
  ExampleComponent
    ✓ renders all the right stuff (15ms)
    ✓ passes a snapshot test (8ms)

Test Suites: 1 passed, 1 total
Tests:       2 passed, 2 total
Snapshots:   1 passed, 1 total
Time:        1.598s, estimated 2s
Ran all test suites.
----------|----------|----------|----------|----------|----------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
----------|----------|----------|----------|----------|----------------|
All files |      100 |      100 |      100 |      100 |                |
 index.js |      100 |      100 |      100 |      100 |                |
----------|----------|----------|----------|----------|----------------|

Moving index.js:

$ mv src/foo/index.js src/components/Example/
$ tree src/
src/
├── components
│   └── Example
│       ├── index.js
│       └── README.md
└── scss
    └── index.scss

3 directories, 3 files

Rerunning Jest after moving index.js (and updating the import statement in the test):

 $ ./node_modules/.bin/jest --config jest.config.js
 PASS  tests/components/example.test.js
  ExampleComponent
    ✓ renders all the right stuff (15ms)
    ✓ passes a snapshot test (8ms)

Test Suites: 1 passed, 1 total
Tests:       2 passed, 2 total
Snapshots:   1 passed, 1 total
Time:        1.628s, estimated 2s
Ran all test suites.
--------------------|----------|----------|----------|----------|----------------|
File                |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
--------------------|----------|----------|----------|----------|----------------|
All files           |     4.76 |        0 |       20 |       20 |                |
 components/Example |        0 |        0 |        0 |        0 |                |
  index.js          |        0 |        0 |        0 |        0 |        1,3,5,6 |
 foo                |      100 |      100 |      100 |      100 |                |
  index.js          |      100 |      100 |      100 |      100 |                |
--------------------|----------|----------|----------|----------|----------------|
Jest: Coverage for statements (4.76%) does not meet global threshold (100%)
Jest: Coverage for branches (0%) does not meet global threshold (100%)
Jest: Coverage for lines (20%) does not meet global threshold (100%)
Jest: Coverage for functions (20%) does not meet global threshold (100%)

What is the expected behavior?

Jest should detect that I've moved the file. Running Jest with --no-cache "fixes" this (coverage is as expected). Rerunning without --no-cache causes the issue again (cache isn't cleared?). Editing the moved file however fixes the problem.

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

Jest config:

module.exports = {
  collectCoverage: true,

  collectCoverageFrom: [
    'src/**/*.js'
  ],

  coverageThreshold: {
    global: {
      branches: 100,
      functions: 100,
      lines: 100,
      statements: 100
    }
  },

  snapshotSerializers: [
    'enzyme-to-json/serializer'
  ]
};

Version details:

$ ./node_modules/.bin/jest --version
v20.0.4

$ node --version
v5.11.0

$ npm --version
3.8.6

$ uname -a
Linux dev36-devc 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016 x86_64 GNU/Linux

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

ulrik59 · 2017-06-14T10:07:33Z

I have the same problem. I have to run all my tests with --no-cache to get the real coverage...

nerfologist · 2017-06-29T12:51:53Z

Also experiencing this issue.

Also, as a workaround, it would be nice to have more info on how to flush the cache manually in case this happens (--no-cache ignores it, but it doesn't reset it).

ljharb · 2017-06-29T23:49:39Z

I'm seeing this same problem, and I can't figure out how to clear the cache - only --no-cache works.

nerfologist · 2017-06-30T07:34:07Z

Hi @ljharb , I spent a lot of time trying to figure out where the cache files were created, in my configuration (Mac Os X Sierra, react-scripts 1.0.7 for create-react-app 1.3.1) I found the cache files in the /private/var/folders/zj/112vf5bj0js_hx6l9ntz3w780000gn/T/jest_dxdirectory.

Hope this info can be useful to you if you want to clear them out:

✔  09:31 {ruby-2.4.0} {node v8.1.2} [/private/var/folders/zj/112vf5bj0js_hx6l9ntz3w780000gn/T/jest_dx]
✎  $ tree .
.
├── haste-map-6baae784957a7b05d31a1cb3f11cd62f-db0bbdff794026d6fe1c81c15eb00f76
├── haste-map-972935e3c872cc2710b886add2b47c99-9d19e3ac6c85c10f406f2d517029338b
└── haste-map-d9a696895ec6b2ddc29d4b43f785986b-ef8320c62d38fbedac43da58d7b811b3

0 directories, 3 files

In order to locate them on your machine, I'd issue a
find /private/var/folders -type f -name haste-map-\* 2>/dev/null

thymikee · 2017-06-30T07:47:41Z

@nerfologist you can jest --showConfig, search for "cacheDirectory" key and just remove that folder if you want to purge the cache completely for some reason

ljharb · 2017-06-30T15:11:49Z

Thanks, that helps. jest really needs a clear cache command :-/

michaelgmcd · 2017-06-30T21:41:36Z

Having this issue as well. I have two files with paths app/controllers/index.js and app/stages/index.js and they both have unit tests. For some reason, the coverage report says that app/stages/index.js is never covered. Even if I only run the app/stages/index.js test, app/controllers/index.js has 100% coverage and the stages file has 0%

Removing the cache and running jest does not work, but running jest --no-cache works as expected and says that both files are properly covered.

nerfologist · 2017-07-03T13:27:56Z

Workaround npm script to zap jest cache (requires rimraf and jq, not windows-portable), based on @thymikee's suggestion :

// package.json
{
  "scripts": {
    "test:clearCache": "rimraf $(./node_modules/jest/bin/jest.js --showConfig | jq '.config.cacheDirectory')"
  }
}

@thymikee

This explanation by @thymikee worked like a charm! #3705 (comment)

@thymikee

This explanation by @thymikee worked like a charm! #3705 (comment)

@thymikee

This explanation by @thymikee worked like a charm! jestjs#3705 (comment)

stipsan · 2017-09-06T11:12:55Z

Hey guys,

Hopefully you won't need a clear cache command anymore after this is released: #4432

cpojer · 2017-09-06T11:37:39Z

Ah nice! Closing this task.

tabrindle · 2017-10-11T18:42:14Z

In case cache clearing is needed in the future, as of 21.3.0, there is a new cli option --clearCache

#4430

AndrewRayCode · 2017-12-17T02:25:23Z

Not sure if this is the same ticket, but I had jest watch report that a test file was completely passing,even after editing that specific test file, and even after re-running all tests with a, and even when running a single test not in watch mode, even though it was actually failing. Finding and removing the cache directory made me see actual test results.

I've been moving a few files so not sure if related, but sure is scary to know that the tests I'm running have no guarantee to be accurate!

Berkmann18 · 2019-04-13T09:16:26Z

jest --clearCache and jest --no-cache doesn't seem to help in making sure that jest stops looking for an old filename (both the test suite and tested file were renamed from labelClass to findCategory).

Cannot find module '../findCategory' from 'labelClass.js'
 > 1 | import {findBestCategory} from '../findCategory'

And it worked well before renaming both files.
Also, whenever I try to re-run failed tests (on yarn) it says "No failed test found"...
EDIT: Renaming he ../findCategory to ../labelClass _then running jest --clearCache then yarn test (while keeping the new module name, i.e findCategory.js) makes it work.

moodseller · 2019-08-14T13:31:29Z

Having a similar issue, running jest as it is works fine, however if I want to add a --watch to it, it keeps giving me an error of Could not locate module even though it locates without the --watch and my application runs without any issues.

Could not locate module @lib/token/token mapped as:
    /Users/privateUser/Documents/api/lib/token/token.
Please check your configuration for these entries:
    {
      "moduleNameMapper": {
        "/@lib\/(.*)/": "/Users/privateUser/Documents/api/lib/$1"
      },
      "resolver": null
    }

moduleNameMapper: {
		'@lib/(.*)': '<rootDir>/lib/$1'
	},

Nowhere in my project do I have such an import as it was an old one and it was modified to @lib/token.

SimenB · 2019-09-04T08:55:39Z

Please open new issues, with reproductions, rather than commenting on old closed ones

SergeyKatugin · 2019-11-18T07:28:51Z

Having same problem. My solution was remove coverage folder from project. And restart

crisu83 · 2020-05-27T13:01:18Z

Workaround npm script to zap jest cache (requires rimraf and jq, not windows-portable), based on @thymikee's suggestion :
// package.json
{
  "scripts": {
    "test:clearCache": "rimraf $(./node_modules/jest/bin/jest.js --showConfig | jq '.config.cacheDirectory')"
  }
}

Alternatively you can also use grep if you don't have jq available in your environment.

// package.json
{
  "scripts": {
    "test:clearCache": "rimraf $(./node_modules/.bin/jest --showConfig | grep -o '\"cacheDirectory\": \"[^\"]*' | grep -o '[^\"]*$')"
  }
}

github-actions · 2021-05-11T08:06:13Z

This issue 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.

nerfologist mentioned this issue Jun 29, 2017

Allow specifying jest's cacheDirectory facebook/create-react-app#2687

Closed

vjeux added a commit that referenced this issue Aug 9, 2017

Explain how to clear the cache

986c613

This explanation by @thymikee worked like a charm! #3705 (comment)

vjeux mentioned this issue Aug 9, 2017

Explain how to clear the cache #4232

Merged

cpojer pushed a commit that referenced this issue Aug 9, 2017

Explain how to clear the cache (#4232)

9aceeb6

This explanation by @thymikee worked like a charm! #3705 (comment)

tushardhole pushed a commit to tushardhole/jest that referenced this issue Aug 21, 2017

Explain how to clear the cache (jestjs#4232)

28551b9

This explanation by @thymikee worked like a charm! jestjs#3705 (comment)

tabrindle mentioned this issue Sep 5, 2017

add clearCache cli command #4430

Merged

cpojer closed this as completed Sep 6, 2017

thymikee mentioned this issue Oct 19, 2017

Jest watching mode seems to unexpectedly cache sources facebook/react#11283

Closed

jamesvclements mentioned this issue Nov 7, 2017

23 add redux bartop-io/bartop#39

Merged

thymikee mentioned this issue Nov 14, 2017

Using ng5 new locale feature thymikee/jest-preset-angular#92

Closed

github-actions bot locked as resolved and limited conversation to collaborators May 11, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Moving src files doesn't bust the Jest cache #3705

Moving src files doesn't bust the Jest cache #3705

adityavohra7 commented May 31, 2017 •

edited

Loading

ulrik59 commented Jun 14, 2017 •

edited

Loading

nerfologist commented Jun 29, 2017

ljharb commented Jun 29, 2017

nerfologist commented Jun 30, 2017

thymikee commented Jun 30, 2017

ljharb commented Jun 30, 2017

michaelgmcd commented Jun 30, 2017

nerfologist commented Jul 3, 2017 •

edited

Loading

stipsan commented Sep 6, 2017

cpojer commented Sep 6, 2017

tabrindle commented Oct 11, 2017

AndrewRayCode commented Dec 17, 2017 •

edited

Loading

Berkmann18 commented Apr 13, 2019 •

edited

Loading

moodseller commented Aug 14, 2019 •

edited

Loading

SimenB commented Sep 4, 2019

SergeyKatugin commented Nov 18, 2019

crisu83 commented May 27, 2020

github-actions bot commented May 11, 2021

Moving src files doesn't bust the Jest cache #3705

Moving src files doesn't bust the Jest cache #3705

Comments

adityavohra7 commented May 31, 2017 • edited Loading

ulrik59 commented Jun 14, 2017 • edited Loading

nerfologist commented Jun 29, 2017

ljharb commented Jun 29, 2017

nerfologist commented Jun 30, 2017

thymikee commented Jun 30, 2017

ljharb commented Jun 30, 2017

michaelgmcd commented Jun 30, 2017

nerfologist commented Jul 3, 2017 • edited Loading

stipsan commented Sep 6, 2017

cpojer commented Sep 6, 2017

tabrindle commented Oct 11, 2017

AndrewRayCode commented Dec 17, 2017 • edited Loading

Berkmann18 commented Apr 13, 2019 • edited Loading

moodseller commented Aug 14, 2019 • edited Loading

SimenB commented Sep 4, 2019

SergeyKatugin commented Nov 18, 2019

crisu83 commented May 27, 2020

github-actions bot commented May 11, 2021

adityavohra7 commented May 31, 2017 •

edited

Loading

ulrik59 commented Jun 14, 2017 •

edited

Loading

nerfologist commented Jul 3, 2017 •

edited

Loading

AndrewRayCode commented Dec 17, 2017 •

edited

Loading

Berkmann18 commented Apr 13, 2019 •

edited

Loading

moodseller commented Aug 14, 2019 •

edited

Loading