Add support for writing out new expected results files via env var #1438
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…_EXPECTED_RESULTS env var
atoulme
reviewed
Sep 9, 2024
samiura
approved these changes
Sep 9, 2024
jvoravong
changed the title
jvoravong
force-pushed
the
feature-update-expected-test-results
branch
5 times, most recently
from
77f0abe
to
b1fb4d4
Compare
jvoravong
force-pushed
the
feature-update-expected-test-results
branch
from
b1fb4d4
to
55c2e6d
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
functional_tests/resultsdirectory and in the golden file formatUPDATE_EXPECTED_RESULTSenv var to determine if new expected test results are generated, the env var should default to false.