Jest snapshot updating not working: "Replace them" button doing nothing

[danawoodman]

Environment

1. node -v: v14.1.0

2. npm -v: 6.14.4 (we use yarn: 1.22.4)

3. npm ls jest or npm ls react-scripts (if you haven’t ejected): jest@26.6.3

4. your vscode-jest settings if customized:

   • jest.pathToJest? empty/default
   • jest.pathToConfig? empty/default
   • anything else that you think might be relevant? not really; running jest on the command line works as does hitting u to update. Only other thing I can think is I'm using multiple projects in my Jest config.

5. Operating system: macOs Catalina 10.15.7 (19H15)

Prerequisite

• are you able to run jest test from command line? yes
• how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest) we use nps to run tests but jest on its own works too

Steps to Reproduce

I'm not sure how to repro. I installed extension, added the config (below) as recommended and ran my tests. The snapshots are out of date and I see a message to update them but clicking does not update them.

    {
      "type": "node",
      "name": "vscode-jest-tests",
      "request": "launch",
      "program": "${workspaceFolder}/node_modules/jest/bin/jest",
      "args": ["--runInBand"],
      "cwd": "${workspaceFolder}",
      "console": "integratedTerminal",
      "internalConsoleOptions": "neverOpen",
      "disableOptimisticBPs": true
    },

Relevant Debug Info

Not sure what else I can provide to be helpful.

Expected Behavior

Should update snapshots

Actual Behavior

Not updating snapshots

[connectdotz]

hmmm... a few things to check...

• when you click on the "Replace" button, the extension should spawn a process with --updateSnapshot flag... can you turn on the debug mode then open the developer console to see if the command line contains the flag.
• if it does, and your subsequent run still showing failed snapshot, then either jest is not able to update the snapshots for some reason, or there is some bug in the extension... can you verify this on your terminal: run jest with the --updateSnapshot, does it update the snapshots?
• If the answers to both questions above are "yes" then it could be a bug in the extension for your use case... it would probably need a sample project to further investigate...