nix-config/tests/hyprland.nix

# TODO: Write test to ensure that Hyprland starts with basic config
let
  inherit (builtins) attrValues;
in
(import ../lib/test.nix) {
  name = "hyprland";

  nodes.machine = { nix-config, ... }: {
    imports = attrValues {
      inherit (nix-config.nixosModules) system desktop;
    };
  };

  testScript = /* python */ ''
    output = machine.succeed("echo 'Hello world'")
    assert "Hello world" in output
  '';
}
meta: Begin writing tests in Nix Now that I've figured out how to dynamically import modules and use those modules as outputs, the next step is to ensure that these modules work as intended when being used by end users. NixOS offers a built-in testing solution that enables us to conveniently spin up virtual machines with a given configuration, then verify their correctness through python scripting. The lib.nix file in particular is based on Jörg Thalheim's very useful blog post that explains how to use the built-in testing functionality with Nix flakes, which isn't covered in official documentation. See: https://blog.thalheim.io/2023/01/08/how-to-use-nixos-testing-framework-with-flakes/ 2024-04-02 11:15:15 +02:00			`# TODO: Write test to ensure that Hyprland starts with basic config`
chore: Add missing imports to tests Necessary since system now depends on home-manager and desktop depends on stylix, which also depends on home-manager. Note that since conditional imports can't be used and we include the system module inside of our containers which don't have access to self, importing the required modules inside the module itself cannot be used. 2024-04-05 15:02:00 +02:00			`let`
			`inherit (builtins) attrValues;`
chore: Format with nixpkgs-fmt Note that we will continue to use nixpkgs-fmt for the time being here since nixfmt-rfc-style breaks string syntax highlighting and comments like `/* this */` get turned into `# this`. The conversion from lisp-like formatting to something else in flake.nix is a bit unfortunate, but I'd rather have a singular style for the entire code base to make things easier. 2024-04-05 17:26:22 +02:00			`in`
meta(nix): Move test lib to separate directory 2024-04-09 14:02:16 +02:00			`(import ../lib/test.nix) {`
meta: Begin writing tests in Nix Now that I've figured out how to dynamically import modules and use those modules as outputs, the next step is to ensure that these modules work as intended when being used by end users. NixOS offers a built-in testing solution that enables us to conveniently spin up virtual machines with a given configuration, then verify their correctness through python scripting. The lib.nix file in particular is based on Jörg Thalheim's very useful blog post that explains how to use the built-in testing functionality with Nix flakes, which isn't covered in official documentation. See: https://blog.thalheim.io/2023/01/08/how-to-use-nixos-testing-framework-with-flakes/ 2024-04-02 11:15:15 +02:00			`name = "hyprland";`

chore: Simplify tests Removes the redundant `self`. 2024-04-05 17:50:28 +02:00			`nodes.machine = { nix-config, ... }: {`
chore: Add missing imports to tests Necessary since system now depends on home-manager and desktop depends on stylix, which also depends on home-manager. Note that since conditional imports can't be used and we include the system module inside of our containers which don't have access to self, importing the required modules inside the module itself cannot be used. 2024-04-05 15:02:00 +02:00			`imports = attrValues {`
chore: Simplify tests Removes the redundant `self`. 2024-04-05 17:50:28 +02:00			`inherit (nix-config.nixosModules) system desktop;`
chore: Add missing imports to tests Necessary since system now depends on home-manager and desktop depends on stylix, which also depends on home-manager. Note that since conditional imports can't be used and we include the system module inside of our containers which don't have access to self, importing the required modules inside the module itself cannot be used. 2024-04-05 15:02:00 +02:00			`};`
meta: Begin writing tests in Nix Now that I've figured out how to dynamically import modules and use those modules as outputs, the next step is to ensure that these modules work as intended when being used by end users. NixOS offers a built-in testing solution that enables us to conveniently spin up virtual machines with a given configuration, then verify their correctness through python scripting. The lib.nix file in particular is based on Jörg Thalheim's very useful blog post that explains how to use the built-in testing functionality with Nix flakes, which isn't covered in official documentation. See: https://blog.thalheim.io/2023/01/08/how-to-use-nixos-testing-framework-with-flakes/ 2024-04-02 11:15:15 +02:00			`};`

			`testScript = /* python */ ''`
			`output = machine.succeed("echo 'Hello world'")`
			`assert "Hello world" in output`
			`'';`
			`}`