-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
add filename for obsolete snapshot file #8665
add filename for obsolete snapshot file #8665
Conversation
…new property filesRemovedList
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thanks! Will need to figure out why CI fails, but the code LGTM
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CI is happy now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Test result property naming getting awkward but I guess we'll have to live with that as anything else is too breaking
🎉 |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Summary
When a snapshot exists that's completely redundant because there's no test file that generates it, jest will report it found a obsolete snapshot:
Especially on a CI this can be not particularity useful, as there is no information on what's actually gone wrong, and the user cannot run
-u
on CI.Test plan
I have added e2e test called
snapshot-unknown
. This demonstrated the output or the cli reporter when there are 2 unknown snapshots. It should look like this:This addresses:
#5005 (comment)