---

name: testing description: Test changes using module-graph and build commands

Testing

Critical Requirement

After making changes you MUST ALWAYS evaluate and test your changes.

Finding Affected Configurations

Use the module-graph script to determine which hosts and homes are affected by your changes:

Copy./flake/dev/scripts/module-graph.nu

This outputs JSON showing which configurations use each file:

Copy{
  "file": "modules/nixos/services/tailscale.nix",
  "hosts": ["nixdev", "nixmi", "nixcloud"],
  "homes": []
}

Minimum Test Requirements

Based on the module-graph output, you must test at least one of each type affected:

Test Commands

Test a host configuration

Copynix build .#nixosConfigurations.<hostname>.config.system.build.toplevel

Test a home configuration

Copynix build .#homeConfigurations."<user>@<host>".activationPackage

Run full flake check

Copynix flake check --override-input devenv-root "file+file://$PWD/.devenv/root"

Testing Workflow Example

1. Make changes to modules/nixos/services/tailscale.nix

2. Run module-graph to find affected configs:

   Copy./flake/dev/scripts/module-graph.nu | jq '.[] | select(.file | contains("tailscale"))'
   

3. Pick one affected host and build:

   Copynix build .#nixosConfigurations.nixdev.config.system.build.toplevel
   

4. If the change also affects homes, build one:

   Copynix build .#homeConfigurations."racci@nixmi".activationPackage
   

5. Format your changes:

   Copynix fmt modules/nixos/services/tailscale.nix