Skip to content
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

Wrong file name displayed in the terminal #6873

Closed
HRK44 opened this issue Aug 21, 2018 · 9 comments
Closed

Wrong file name displayed in the terminal #6873

HRK44 opened this issue Aug 21, 2018 · 9 comments
Labels

Comments

@HRK44
Copy link

HRK44 commented Aug 21, 2018

🐛 Bug Report

When a test fails, it will show the file name of the test with some wrong extension, I don't know if the error is actually from the filename value OR maybe some terminal visual artefacts.

screenshot from 2018-08-21 11-54-54

As you can see, there is the correct file toto.test.js but it's also showing toto.test.jss and sometimes it's showing toto.test.jsjs.

toto.test.jss doesn't exist and the correct file toto.test.js is just an empty file.

To Reproduce

Setup a good test and a wrong test (in 2 different files), then run the jest.

Expected behavior

The filename should be displayed correctly.

Run npx envinfo --preset jest

  System:
    OS: Linux 4.15 Ubuntu 18.04.1 LTS (Bionic Beaver)
    CPU: x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
  Binaries:
    Node: 10.9.0 - /usr/bin/node
    Yarn: 1.9.4 - /usr/bin/yarn
    npm: 6.2.0 - /usr/bin/npm
  npmPackages:
    jest: ^23.5.0 => 23.5.0
@thymikee
Copy link
Collaborator

Need a repro

@HRK44
Copy link
Author

HRK44 commented Aug 21, 2018

@thymikee I'm using https://github.com/xfumihiro/jest-puppeteer-example which is from the official jest doc

@thymikee
Copy link
Collaborator

This is a problem with a reporter – the second s is from the previous line which is not cleared entirely.

@HRK44
Copy link
Author

HRK44 commented Aug 21, 2018

@thymikee is this reporter actually part of jest?

@thymikee
Copy link
Collaborator

Yes, it's a default reporter. It sometimes breaks like this when there's some stdout/stderr output coming from your tests or code. I believe this should be fixed by #6871

@HRK44
Copy link
Author

HRK44 commented Aug 21, 2018

Ok thanks for the quick replies, hopefully this PR fixes it ! 💯

@github-actions
Copy link

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 github-actions bot added the Stale label Feb 25, 2022
@github-actions
Copy link

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
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants