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 68c81c737571794f7246db53fb4774e94fcf4b7e)		2023-12-01 12:06:43 -05:00
..
clean.mk
common-test.sh	Put functional tests in tests/functional	2023-12-01 12:06:43 -05:00
cxx-big-literal.mk	Dedup some markdown -> C++ big literal stuff in build system	2023-05-15 10:38:11 -04:00
debug-test.sh	Harden tests' bash	2023-03-08 10:26:30 -05:00
disable-tests.mk
functions.mk
install.mk
lib.mk	Introduce notion of a test group, use for CA tests	2023-07-18 09:31:13 -04:00
libraries.mk	fix: build aarch64-darwin	2023-03-18 17:53:45 -04:00
patterns.mk	Enable -Werror=switch-enum	2023-04-03 18:45:20 +02:00
precompiled-headers.mk
programs.mk
run-test.sh	Remove "unexpected EOF" retry hack	2023-03-15 10:59:10 +01:00
templates.mk
tests.mk	Introduce notion of a test group, use for CA tests	2023-07-18 09:31:13 -04:00
tracing.mk