Initial test run of Jest source code in VS Code on Windows fails due to snapshots missing color tags

[urig]

🐛 Bug Report

When Jest performs its initial test run in VS Code on Windows, a large number of snapshot tests fail because the Received snapshot is missing color tags (ex: <red>)

To Reproduce

1. In Windows 10, follow the steps in the Contributing Guide
   
2. Open Jest in VS Code (v1.29.1)
3. Switch to the Output window to view test results as the run progresses.

Actual behavior

A large number of snapshot tests FAIL. From a cursory glance, the cause of the failure is the lack of color tags in the Received snapshots. For example:

FAIL packages/jest-config/src/__tests__/normalize.test.js (10.679s)

  ● rootDir › throws if the options is missing a rootDir property

    expect(value).toMatchSnapshot()

    Received value does not match stored snapshot "rootDir throws if the options is missing a rootDir property 1".

    - Snapshot
    + Received

    - "<red><bold><bold>● <bold>Validation Error</>:</>
    - <red></>
    - <red>  Configuration option <bold>rootDir</> must be specified.</>
    - <red></>
    - <red>  <bold>Configuration Documentation:</></>
    - <red>  https://jestjs.io/docs/configuration.html</>
    - <red></>"
    + "● Validation Error:
    + 
    +   Configuration option rootDir must be specified.
    + 
    +   Configuration Documentation:
    +   https://jestjs.io/docs/configuration.html
    + "

      at Object.toThrowErrorMatchingSnapshot (packages/jest-config/src/__tests__/normalize.test.js:96:8)

Expected behavior

Snapshot tests are expected to PASS.

Link to repl or repo (highly encouraged)

https://github.com/urig/jest/

Run npx envinfo --preset jest

Paste the results here:

  System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
  Binaries:
    Yarn: 1.12.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD

Notes

Note: I think the lack of color tags in the Received snapshots is not surprising given that the command used to run the tests is shown to include the --no-color switch:

$ node ./packages/jest-cli/bin/jest.js --json --useStderr --outputFile C:\Users\urig\AppData\Local\Temp/jest_runner.json --no-color

The question is - Why does the command include this switch?

[SimenB]

no-color should just affect the output you see, not the test results jest itself sees from running its own integration tests.

That said, we do have issues with colors disappearing on CI, not sure how to debug it?

[github-actions]

This issue is stale because it has been open for 1 year with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity. Please open a new issue if the issue is still relevant, linking to this one.

[github-actions]

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.