b3aa38702b
check if directory has a default.nix and use directory name as key Co-authored-by: Timothy DeHerrera <tim.deh@pm.me> |
||
|---|---|---|
| .. | ||
| testPathsToImportedAttrs | ||
| default.nix | ||
| lib.nix | ||
| README.md | ||
Testing
Testing is always an important aspect of any software development project, and NixOS offers some incredibly powerful tools to write tests for your configuration, and, optionally, run them in CI.
Lib Tests
You can easily write tests for your own library functions in the
tests/lib.nix file and they will be run on every nix flake check or
during a CI run.
Unit Tests
Unit tests are can be created from regular derivations, and they can do almost anything you can imagine. By convention, it is best to test your packages during their check phase. All packages and their tests will be built during CI.
Integration Tests
You can write integration tests for one or more NixOS VMs that can, optionally, be networked together, and yes, it's as awesome as it sounds!
Be sure to use the mkTest function, in the tests/default.nix
which wraps the official testing-python function to ensure
that the system is setup exactly as it is for a bare DevOS system. There are
already great resources for learning how to use these tests effectively,
including the official docs, a fantastic blog post,
and the examples in nixpkgs.