You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 7, 2020. It is now read-only.
FWIW I personally would not use the interactive CLI. I would want to be able to simply update all snapshots. The workflow I'm thinking I would use is something like:
start from a clean version control revision
update all snapshots with CLI tool
use my version control diffing tools to see which tests have changed and how
use my version control tools to discard changes to files that I don't want.
commit
Another note about this is that it would be nicer in this paradigm for the files containing the test output to be only the result of the test. I'm kind of curious about that design decision btw. It seems to me that it would be simpler to encode the full rust module path to the test snapshot in the file path that holds the snapshot content. So for instance the file path to the test example in your blog post would change like:
use my version control tools to discard changes to files that I don't want.
My personal experience is that development tools are nicest to use when they minimize their assumptions about other tools in the environment. That said it's not like I have a lot of time for this at the moment!
It seems to me that it would be simpler to encode the full rust module path to the test snapshot in the file path that holds the snapshot content.
I believe this was an outcome of being in a rush and considering this experimental. PRs very welcome!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This CLI should:
UPDATE_SNAPSHOTS
env var setThe text was updated successfully, but these errors were encountered: