Improve golden file checking #1053
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently when I have a typo in the golden file path,
expectGolden
creates a new file, which makes the test pass.Locally I can notice the new file if I run
git status
, but if I'm not careful and rely on CI, because the tests pass, I can merge the PR.Update
expectGolden
to only create (or update if already exists) a golden file when the env variablePROTOC_UPDATE_GOLDENS
is set.Without the env variable it expects the file to exist, with the right contents. So typos now cause test failures as expected.