John Ericson 30dcc19d1f Put functional tests in tests/functional ... 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 68c81c7375)		2023-12-01 12:06:43 -05:00
..
build-built-drv.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
common.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
config.nix.in	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
dep-built-drv.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
eval-outputOf.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
local.mk	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
old-daemon-error-hack.nix	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
old-daemon-error-hack.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
recursive-mod-json.nix	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
recursive-mod-json.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
text-hashed-output.nix	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
text-hashed-output.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00