30dcc19d1f
I think it is bad for these reasons when `tests/` contains a mix of functional and integration tests - Concepts is harder to understand, the documentation makes a good unit vs functional vs integration distinction, but when the integration tests are just two subdirs within `tests/` this is not clear. - Source filtering in the `flake.nix` is more complex. We need to filter out some of the dirs from `tests/`, rather than simply pick the dirs we want and take all of them. This is a good sign the structure of what we are trying to do is not matching the structure of the files. With this change we have a clean: ```shell-session $ git show 'HEAD:tests' tree HEAD:tests functional/ installer/ nixos/ ``` (cherry picked from commit 68c81c737571794f7246db53fb4774e94fcf4b7e)
34 lines
1,010 B
Bash
34 lines
1,010 B
Bash
# Golden test support
|
|
#
|
|
# Test that the output of the given test matches what is expected. If
|
|
# `_NIX_TEST_ACCEPT` is non-empty also update the expected output so
|
|
# that next time the test succeeds.
|
|
function diffAndAcceptInner() {
|
|
local -r testName=$1
|
|
local -r got="$2"
|
|
local -r expected="$3"
|
|
|
|
# Absence of expected file indicates empty output expected.
|
|
if test -e "$expected"; then
|
|
local -r expectedOrEmpty="$expected"
|
|
else
|
|
local -r expectedOrEmpty=lang/empty.exp
|
|
fi
|
|
|
|
# Diff so we get a nice message
|
|
if ! diff --unified "$got" "$expectedOrEmpty"; then
|
|
echo "FAIL: evaluation result of $testName not as expected"
|
|
badDiff=1
|
|
fi
|
|
|
|
# Update expected if `_NIX_TEST_ACCEPT` is non-empty.
|
|
if test -n "${_NIX_TEST_ACCEPT-}"; then
|
|
cp "$got" "$expected"
|
|
# Delete empty expected files to avoid bloating the repo with
|
|
# empty files.
|
|
if ! test -s "$expected"; then
|
|
rm "$expected"
|
|
fi
|
|
fi
|
|
}
|