68c81c7375
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/ ```
31 lines
659 B
Bash
31 lines
659 B
Bash
source ./common.sh
|
|
|
|
requireGit
|
|
|
|
flake1Dir=$TEST_ROOT/flake1
|
|
flake2Dir=$TEST_ROOT/flake2
|
|
|
|
createGitRepo $flake1Dir
|
|
cat > $flake1Dir/flake.nix <<EOF
|
|
{
|
|
outputs = { self }: { x = import ./x.nix; };
|
|
}
|
|
EOF
|
|
echo 123 > $flake1Dir/x.nix
|
|
git -C $flake1Dir add flake.nix x.nix
|
|
git -C $flake1Dir commit -m Initial
|
|
|
|
createGitRepo $flake2Dir
|
|
cat > $flake2Dir/flake.nix <<EOF
|
|
{
|
|
outputs = { self, flake1 }: { x = flake1.x; };
|
|
}
|
|
EOF
|
|
git -C $flake2Dir add flake.nix
|
|
|
|
[[ $(nix eval --json $flake2Dir#x --override-input flake1 $TEST_ROOT/flake1) = 123 ]]
|
|
|
|
echo 456 > $flake1Dir/x.nix
|
|
|
|
[[ $(nix eval --json $flake2Dir#x --override-input flake1 $TEST_ROOT/flake1) = 456 ]]
|