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

Missing snapshot summary #15

Closed
SimenB opened this issue Jul 26, 2019 · 3 comments
Closed

Missing snapshot summary #15

SimenB opened this issue Jul 26, 2019 · 3 comments

Comments

@SimenB
Copy link
Collaborator

SimenB commented Jul 26, 2019

Made debugging jestjs/jest#8665 confusing as we only saw the exit status but no errors. Temporarily using the default reporter had this output:
image

@SimenB
Copy link
Collaborator Author

SimenB commented Dec 4, 2020

Solved by #23 I believe?

@SimenB SimenB closed this as completed Dec 4, 2020
@NickHeiner
Copy link

This seems be causing a lot of problems for people with jestjs/jest#9324. It might be good to make showPaths default to true.

@NickHeiner
Copy link

NickHeiner commented Sep 2, 2021

Also, I don't think #23 universally solves it. I observed an issue where Jest exited with status code 1 because a snapshot was obsolete, but it wasn't related to the file I was running the test for:

 PASS   lint  packages/darwin/src/components/AcessibilityText/index.js
  ✓ ESLint (843 ms)

Snapshot Summary
 › 5 snapshot files obsolete from 5 test suites. To remove them all, re-run jest with `-u`.
   ↳   • servers/tvui-nodequark/src/routes/videos/stubsFocusedTall/__functional__/__snapshots__/route.js.snap

Therefore, when I did console.log(testResult); in onTestResult, I didn't see anything about this snapshot, which is not surprising, because it's for a different file.

I'm not sure what Jest API should be used to figure out if unrelated snapshots are going to cause a non-0 status code exit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants