summaryrefslogtreecommitdiff
path: root/scripts/test/generate_lld_tests.py
diff options
context:
space:
mode:
authorNathan Froyd <froydnj@gmail.com>2018-03-19 17:02:40 -0400
committerAlon Zakai <alonzakai@gmail.com>2018-03-19 14:02:40 -0700
commit267e4b55f8c2f598ea5ea44d5df88d83bfb3ebac (patch)
tree8c2aaad800cbdaf9f92f28ec9c7d480e906342b0 /scripts/test/generate_lld_tests.py
parent9c9b78db2e6ce178cc0c546d59aacaa4c72c001b (diff)
downloadbinaryen-267e4b55f8c2f598ea5ea44d5df88d83bfb3ebac.tar.gz
binaryen-267e4b55f8c2f598ea5ea44d5df88d83bfb3ebac.tar.bz2
binaryen-267e4b55f8c2f598ea5ea44d5df88d83bfb3ebac.zip
include the filename in erroneous diff output where possible (#1452)
Failing test cases often start out with: ``` incorrect output, diff: --- expected +++ actual ``` which makes it difficult to figure out where the expected output might live. That information can be derived from examining the tests, of course, but it'd be much nicer if it were provided in the diff to see straightaway. We do this by introducing a new check, one which takes a filename of expected output, which then enables us to display the failing file, e.g.: ``` incorrect output, diff: --- /home/froydnj/src/binaryen.git/test/passes/code-folding.txt +++ actual ``` which is arguably nicer. Having this new check also enables reducing some boilerplate `open(...).read()` calls in various places. There are still a few places using `fail_if_not_identical`, usually because `.strip()` is used on the expected output.
Diffstat (limited to 'scripts/test/generate_lld_tests.py')
0 files changed, 0 insertions, 0 deletions