John Ericson 735a672e1f 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-09 23:08:03 -04:00
..
common.sh	Make tests/dyn-drv test dir	2023-04-19 18:49:50 -04:00
config.nix.in	Make tests/dyn-drv test dir	2023-04-19 18:49:50 -04:00
local.mk	Introduce notion of a test group, use for CA tests	2023-07-09 23:08:03 -04:00
recursive-mod-json.nix	Rename a few things in new tests	2023-05-08 08:01:58 -04:00
recursive-mod-json.sh	Add a more interesting test	2023-04-19 20:36:33 -04:00
text-hashed-output.nix	Rename a few things in new tests	2023-05-08 08:01:58 -04:00
text-hashed-output.sh	Rename a few things in new tests	2023-05-08 08:01:58 -04:00