259e328de8
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. Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io> |
||
---|---|---|
.. | ||
clean.mk | ||
common-test.sh | ||
cxx-big-literal.mk | ||
debug-test.sh | ||
disable-tests.mk | ||
functions.mk | ||
install.mk | ||
lib.mk | ||
libraries.mk | ||
patterns.mk | ||
precompiled-headers.mk | ||
programs.mk | ||
run-test.sh | ||
templates.mk | ||
tests.mk | ||
tracing.mk |