-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WSL] Test report corruption #4353
Comments
This sounds plausible. You can see the same issue when using "Git Bash" under Windows. The fix would live in |
IMO we should consume log-symbols here; we already use it (elsewhere). |
Hello I tried to reproduce this issue. And I found some reason. My operating system
In conclusion, when running node, if it is executed with double quotes like This was not solved using Using |
Hello |
changing the output is a breaking change. I expect it to land in mocha v9. will take a look at the PR before then |
I'm working on Windows/WSL 2.0 and can't confirm this rendering issue anymore. We aren't going to pursue this issue any further. Trying to handle rendering deficiencies of individuell shells is out of Mocha's scope. |
Prerequisites
faq
labelnode node_modules/.bin/mocha --version
(Local) andmocha --version
(Global). We recommend that you not install Mocha globally.Description
The checkmark and ex symbols used by mocha, don't render well in many Windows shell environments. For example, in Windows Subsystem for Linux, they show up as the missing Unicode question mark glyph.
Steps to Reproduce
Use mocha in WSL.
Expected behavior: The report renders successfully.
Actual behavior: Special characters are mangled.
Reproduces how often: 100%
Versions
The output of
mocha --version
andnode node_modules/.bin/mocha --version
: 6.2.0The output of
node --version
: 8.16.0Your operating system
Your shell (e.g., bash, zsh, PowerShell, cmd): zsh inside Ubuntu inside WSL inside Windows 10.
Additional Information
Recommended to detect WSL, and use plain ASCII characters in this case. The number of Windows shell environments that don't support Unicode characters well, far outnumbers the Windows shell environments that do.
The text was updated successfully, but these errors were encountered: