4.flake-parts/dev/tests
Robert Hensing f427ecf1a0 Repurpose moduleLocation impl for new errorLocation
The difference is that moduleLocation is "guaranteed" reliable data,
whereas errorLocation is the best choice for error messages in the core.

moduleLocation is suitable for the module key attribute.
errorLocation is best for the *ROOT* module _file attribute.

Initially I applied errorLocation in too many places. It is only needed
when the flake output attribute names are strict in it.
To avoid confusion, I'm not exposing errorLocation to the modules, until
we have a concrete use case for it.
2023-10-14 00:03:28 +02:00
..
eval-tests.nix Repurpose moduleLocation impl for new errorLocation 2023-10-14 00:03:28 +02:00
README.md Explain hci effect tests 2022-11-13 12:25:55 +01:00
template.nix Test the template 2022-11-13 12:19:55 +01:00

Running the tests

These tests can be run locally with the hci effect run command. This gives the tests access to a proper nix daemon and the network.

Designed for convenient deployments, it needs some information from git. You may use --no-token to disable this functionality if you're getting errors, or if you're asked to log in.

Example:

hci effect run --no-token default.effects.tests.template