NixOS VM tests - Revision history

Mightyiam: Links to Nixcademy blog posts about NixOS integration tests

2025-12-26T06:55:32Z

Links to Nixcademy blog posts about NixOS integration tests

← Older revision		Revision as of 06:55, 26 December 2025
Line 388:		Line 388:
	/nix/store/bx7z3imvxxpwkkza10vb23czhw7873w2-vm-test-run-unnamed		/nix/store/bx7z3imvxxpwkkza10vb23czhw7873w2-vm-test-run-unnamed

			== Further reading ==

			* [https://nixcademy.com/posts/running-nixos-integration-tests-on-macos/ Run NixOS Integration Tests on macOS, Nixcademy]
			* [https://nixcademy.com/posts/nixos-integration-tests/ Unveiling the Power of the NixOS Integration Test Driver (Part 1), Nixcademy]
			* [https://nixcademy.com/posts/nixos-integration-tests-part-2/ Unveiling the Power of the NixOS Integration Test Driver (Part 2), Nixcademy]

	[[Category:NixOS]]		[[Category:NixOS]]

6543: pictures just describe things better sometime

2025-09-30T19:42:37Z

pictures just describe things better sometime

← Older revision		Revision as of 19:42, 30 September 2025
Line 27:		Line 27:
	Now you can connect to this VM via (on linux):		Now you can connect to this VM via (on linux):
	ssh -o User=root vsock/3		ssh -o User=root vsock/3
	If you are on MacOS or have multiple VMs look at the shell output that do run the interactive tests.		If you are on MacOS or have multiple VMs look at the shell output that do run the interactive tests:
			[[File:Screenshot of interactive test just started.png\|none\|thumb\|444x444px\|Screenshot of just started nixos test for meilisearch (interactive)]]

	== How to debug tests ? ==		== How to debug tests ? ==

654: learned this @ nixcon25 (https://github.com/applicative-systems/nixos-test-driver-nixcon)

2025-09-30T18:33:48Z

learned this @ nixcon25 (https://github.com/applicative-systems/nixos-test-driver-nixcon)

← Older revision		Revision as of 18:33, 30 September 2025
Line 23:		Line 23:
	Add this to your test config:		Add this to your test config:

	interactive.~~nodes~~.~~machine = {~~		interactive.sshBackdoor.enable = true;
	~~services.openssh = {~~
	enable = true;
	~~settings = {~~
	~~PermitRootLogin = "yes";~~
	~~PermitEmptyPasswords = "yes";~~
	};
	};

	~~security.pam.services.sshd.allowNullPassword = true;~~

	~~virtualisation.forwardPorts = [~~
	~~{ from = "host"; host.port = 2000; guest.port = 22; }~~
	];
	};

	Now you can connect to this VM via		Now you can connect to this VM via (on linux):
	ssh root~~@localhost -p 2000~~		ssh -o User=root vsock/3
			If you are on MacOS or have multiple VMs look at the shell output that do run the interactive tests.

	== How to debug tests ? ==		== How to debug tests ? ==

TobiasBora: Write that this page is outdated.

2025-05-27T13:26:00Z

Write that this page is outdated.

← Older revision		Revision as of 13:26, 27 May 2025
Line 1:		Line 1:


			WARNING: this page is mostly outdated as https://nixos.org/manual/nixos/stable/#chap-developing-the-test-driver mentions that <code>pkgs.nixosTest</code>, <code>testing-python.nix</code> and <code>make-test-python.nix</code> are outdated. Beside the documentation, you may also like https://nix.dev/tutorials/nixos/integration-testing-using-virtual-machines.html

	The primary documentation for the [https://nixos.org/manual/nixos/stable/index.html#sec-nixos-tests NixOS VM testing framework] is in [https://nixos.org/manual/nixos/stable/index.html#sec-nixos-tests the NixOS manual], and in [https://nixos.org/manual/nixpkgs/unstable/#tester-runNixOSTest the Nixpkgs manual]. A tutorial can be found at [https://nix.dev/tutorials/nixos/integration-testing-using-virtual-machines].		The primary documentation for the [https://nixos.org/manual/nixos/stable/index.html#sec-nixos-tests NixOS VM testing framework] is in [https://nixos.org/manual/nixos/stable/index.html#sec-nixos-tests the NixOS manual], and in [https://nixos.org/manual/nixpkgs/unstable/#tester-runNixOSTest the Nixpkgs manual]. A tutorial can be found at [https://nix.dev/tutorials/nixos/integration-testing-using-virtual-machines].

Osnyx: Remove leftover references to the perl test subsystem

2024-12-04T20:59:57Z

Remove leftover references to the perl test subsystem

← Older revision		Revision as of 20:59, 4 December 2024
Line 12:		Line 12:
	The wrapper `bin/nixos-run-vms` is in charge to start the driver with the correct VM script as arguments.		The wrapper `bin/nixos-run-vms` is in charge to start the driver with the correct VM script as arguments.

	Once the driver is loaded, depending on the environment variables `tests` it will run in an interactive mode or run some ~~perl~~ code (`~~testScript~~`).		Once the driver is loaded, depending on the environment variables `tests` it will run in an interactive mode or run some python code (`test_script()`).
	In interactive mode, you can run `start_all~~` followed by `join_all~~` to start and keep the VM alive		In interactive mode, you can run `start_all()` to start and keep the VM alive

	== Connecting to an interactive VM via SSH ==		== Connecting to an interactive VM via SSH ==

Hexa: /* I don't see any prompt ? (qemu window pitch black) */

2024-07-26T19:48:42Z

I don't see any prompt ? (qemu window pitch black)

← Older revision		Revision as of 19:48, 26 July 2024
Line 48:		Line 48:
	== I don't see any prompt ? (qemu window pitch black) ==		== I don't see any prompt ? (qemu window pitch black) ==

	Check the output for `malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "\x{0}\x{0}\x{0}\x{0}...") at /nix/store/1hkp2n6hz3ybf2rvkjkwrzgbjkrrakzl-update-users-groups.pl line 11`.		Check the output for

			<code>malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "\x{0}\x{0}\x{0}\x{0}...") at /nix/store/1hkp2n6hz3ybf2rvkjkwrzgbjkrrakzl-update-users-groups.pl line 11`</code>

	You should purge the state present in rm -rf /tmp/vm-state-<VM_NAME>		You should purge the state present in rm -rf /tmp/vm-state-<VM_NAME>

Klinger: Category:NixOS

2024-06-30T20:28:15Z

Category:NixOS

← Older revision		Revision as of 20:28, 30 June 2024
Line 3:		Line 3:
	The test infrastructure entry point is nixos/lib/testing.nix. Alternatively, for out-of-tree tests you can invoke it via Nixpkgs as the nixosTest function, which reuses your already evaluated Nixpkgs to generate your node configurations.		The test infrastructure entry point is nixos/lib/testing.nix. Alternatively, for out-of-tree tests you can invoke it via Nixpkgs as the nixosTest function, which reuses your already evaluated Nixpkgs to generate your node configurations.
	The test infra relies on the qemu build-vm code to generate virtual machines.		The test infra relies on the qemu build-vm code to generate virtual machines.


	It will generate a test driver (a wrapper of nixos/lib/test-driver/test-driver.py) in charge of creating the network.		It will generate a test driver (a wrapper of nixos/lib/test-driver/test-driver.py) in charge of creating the network.
Line 391:		Line 392:
	(0.00 seconds)		(0.00 seconds)
	/nix/store/bx7z3imvxxpwkkza10vb23czhw7873w2-vm-test-run-unnamed		/nix/store/bx7z3imvxxpwkkza10vb23czhw7873w2-vm-test-run-unnamed


			[[Category:NixOS]]

Tomodachi94: Tomodachi94 moved page NixOS Testing library to NixOS VM tests: title is clearer, "VM tests" is fairly common

2024-06-22T06:34:16Z

Tomodachi94 moved page NixOS Testing library to NixOS VM tests: title is clearer, "VM tests" is fairly common

← Older revision		Revision as of 06:34, 22 June 2024
(No difference)

Nikstur: /* Connecting to an interactive VM via SSH */

2024-05-29T15:56:08Z

Connecting to an interactive VM via SSH

← Older revision		Revision as of 15:56, 29 May 2024
Line 35:		Line 35:

	Now you can connect to this VM via		Now you can connect to this VM via
	ssh root@localhost -p ~~2200~~		ssh root@localhost -p 2000

	== How to debug tests ? ==		== How to debug tests ? ==

Nikstur: Add section on connecting to an interactive VM via SSH

2024-05-29T15:52:33Z

Add section on connecting to an interactive VM via SSH

← Older revision		Revision as of 15:52, 29 May 2024
Line 14:		Line 14:
	In interactive mode, you can run `start_all` followed by `join_all` to start and keep the VM alive		In interactive mode, you can run `start_all` followed by `join_all` to start and keep the VM alive

			== Connecting to an interactive VM via SSH ==

			Add this to your test config:

			interactive.nodes.machine = {
			services.openssh = {
			enable = true;
			settings = {
			PermitRootLogin = "yes";
			PermitEmptyPasswords = "yes";
			};
			};

			security.pam.services.sshd.allowNullPassword = true;

			virtualisation.forwardPorts = [
			{ from = "host"; host.port = 2000; guest.port = 22; }
			];
			};

			Now you can connect to this VM via
			ssh root@localhost -p 2200

	== How to debug tests ? ==		== How to debug tests ? ==