Confusing escaping behaviours on Windows

Do you want to request a feature or report a bug? Bug What is the current behavior? There’s a different behaviour in escaping the path separator on Windows when the pattern is specified via CLI parameter vs. when it’s inserted via the pattern prompt (pressing “p”) If I run on the command prompt something like yarn jest folder\file --watchAll then Jest would fail with

No tests found
[...]
Pattern: folder\file - 0 matches

but then if press p and enter the exact same pattern folder\file, Jest would find the correct file(s) and run correctly. I know that the correct CLI pattern should be folder\\file but seeing the same input give different outputs is confusing.

Run npx envinfo --preset jest in your project directory and paste the results here

System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-3635QM CPU @ 2.40GHz
  Binaries:
    Node: 8.9.4
    Yarn: 1.5.1
    npm: 5.6.0
  npmPackages:
    jest:
      wanted: ^22.4.3
      installed: 22.4.3

[rickhanlonii]

@jarvinenio all you!

[github-actions[bot]]

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.