nix-super/tests/ca/local.mk

ca-tests := \
  $(d)/build-with-garbage-path.sh \
  $(d)/build.sh \
  $(d)/concurrent-builds.sh \
  $(d)/derivation-json.sh \
  $(d)/duplicate-realisation-in-closure.sh \
  $(d)/gc.sh \
  $(d)/import-derivation.sh \
  $(d)/new-build-cmd.sh \
  $(d)/nix-copy.sh \
  $(d)/nix-run.sh \
  $(d)/nix-shell.sh \
  $(d)/post-hook.sh \
  $(d)/recursive.sh \
  $(d)/repl.sh \
  $(d)/selfref-gc.sh \
  $(d)/signatures.sh \
  $(d)/substitute.sh \
  $(d)/why-depends.sh

install-tests-groups += ca

clean-files += \
  $(d)/config.nix

test-deps += \
  tests/ca/config.nix
Introduce notion of a test group, use for CA tests Grouping our tests should make it easier to understand the intent than one long poorly-arranged list. It also is convenient for running just the tests for a specific component when working on that component. We need at least one test group so this isn't dead code; I decided to collect the tests for the `ca-derivations` and `dynamic-derivations` experimental features in groups. Do ```bash make ca.test-group -jN ``` and ```bash make dyn-drv.test-group -jN ``` to try running just them. I originally did this as part of #8397 for being able to just the local overlay store alone. I am PRing it separately now so we can separate general infra from new features. 2023-07-10 05:24:51 +03:00			`ca-tests := \`
			`$(d)/build-with-garbage-path.sh \`
			`$(d)/build.sh \`
			`$(d)/concurrent-builds.sh \`
			`$(d)/derivation-json.sh \`
			`$(d)/duplicate-realisation-in-closure.sh \`
			`$(d)/gc.sh \`
			`$(d)/import-derivation.sh \`
			`$(d)/new-build-cmd.sh \`
			`$(d)/nix-copy.sh \`
			`$(d)/nix-run.sh \`
			`$(d)/nix-shell.sh \`
			`$(d)/post-hook.sh \`
			`$(d)/recursive.sh \`
			`$(d)/repl.sh \`
			`$(d)/selfref-gc.sh \`
			`$(d)/signatures.sh \`
			`$(d)/substitute.sh \`
			`$(d)/why-depends.sh`

			`install-tests-groups += ca`

			`clean-files += \`
			`$(d)/config.nix`

			`test-deps += \`
			`tests/ca/config.nix`