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/ ```
30 lines
849 B
Bash
30 lines
849 B
Bash
source ../common.sh
|
||
|
||
clearStore
|
||
rm -rf $TEST_HOME/.cache $TEST_HOME/.config $TEST_HOME/.local
|
||
cp ../shell-hello.nix ../config.nix $TEST_HOME
|
||
cd $TEST_HOME
|
||
|
||
cat <<EOF > flake.nix
|
||
{
|
||
outputs = {self}: {
|
||
packages.$system.pkgAsPkg = (import ./shell-hello.nix).hello;
|
||
packages.$system.appAsApp = self.packages.$system.appAsApp;
|
||
|
||
apps.$system.pkgAsApp = self.packages.$system.pkgAsPkg;
|
||
apps.$system.appAsApp = {
|
||
type = "app";
|
||
program = "\${(import ./shell-hello.nix).hello}/bin/hello";
|
||
};
|
||
};
|
||
}
|
||
EOF
|
||
nix run --no-write-lock-file .#appAsApp
|
||
nix run --no-write-lock-file .#pkgAsPkg
|
||
|
||
! nix run --no-write-lock-file .#pkgAsApp || fail "'nix run' shouldn’t accept an 'app' defined under 'packages'"
|
||
! nix run --no-write-lock-file .#appAsPkg || fail "elements of 'apps' should be of type 'app'"
|
||
|
||
clearStore
|
||
|