Replies: 1 comment 1 reply
-
i would really like to fix this. it annoys me as well. My current way of handling it is: delete all verified files, run all the tests, do a bulk accept of all changes. This is clunky. The problem is i havnt figured out a way to achieve this. Any ideas? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am still getting comfortable with using Verify and the related workflow. One thing that does annoy me is when I refactor my tests, e.g. change their name, add parameters, or rename types, all verified files gets stranded. If its a straight up refactor, the content of the old and new verified files should be the same, so GIT can usually detect this as a rename.
However, if I have many tests in the same folder, it can be a bit tedious to go find the verified files that are no longer relevant and delete those. Is there a way for Verify to automatically detect these scenarios and do the clean up for me? Or is there another pattern I should be using, e.g. store verified files in subfolders matching the name of the test?
This is a bigger issue when using
theory
/data driven tests, which I do quite a bit, where there can be many verified files per test.Beta Was this translation helpful? Give feedback.
All reactions