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/ ```
18 lines
369 B
Bash
18 lines
369 B
Bash
source ./common.sh
|
|
|
|
flake1Dir=$TEST_ROOT/flake1
|
|
|
|
mkdir -p $flake1Dir
|
|
cat > $flake1Dir/flake.nix <<EOF
|
|
{
|
|
outputs = { self }: {
|
|
x = 1;
|
|
packages.$system.x = 2;
|
|
};
|
|
}
|
|
EOF
|
|
|
|
[ "$(nix eval --impure --json $flake1Dir#.x)" -eq 1 ]
|
|
[ "$(nix eval --impure --json $flake1Dir#x)" -eq 2 ]
|
|
[ "$(nix eval --impure --json $flake1Dir#.packages.$system.x)" -eq 2 ]
|