philipp/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Activity

nixos/tests: expose both the interactive and non-interactive driver

Browse source 
For a lot of the work the non-interactive drivers are enough and it is
probably a good idea to keep it accessible for debugging without
touching the Nix expression.
This commit is contained in:
Andreas Rammhold 2020-10-19 17:20:27 +02:00
parent c096880d46
commit 20893b3a70
No known key found for this signature in database
GPG key ID: E432E410B5E48C86
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
nixos/doc/manual/development/running-nixos-tests-interactively.xml
View file

@ -9,7 +9,7 @@
The test itself can be run interactively. This is particularly useful when
developing or debugging a test:
<screen>
<prompt>$ </prompt>nix-build nixos/tests/login.nix -A driver
<prompt>$ </prompt>nix-build nixos/tests/login.nix -A driverInteractive
<prompt>$ </prompt>./result/bin/nixos-test-driver
starting VDE switch for network 1
<prompt>&gt;</prompt>
@ -30,7 +30,7 @@ starting VDE switch for network 1
<para>
To just start and experiment with the VMs, run:
<screen>
<prompt>$ </prompt>nix-build nixos/tests/login.nix -A driver
<prompt>$ </prompt>nix-build nixos/tests/login.nix -A driverInteractive
<prompt>$ </prompt>./result/bin/nixos-run-vms
</screen>
The script <command>nixos-run-vms</command> starts the virtual machines

3
nixos/lib/testing-python.nix
View file

@ -172,7 +172,8 @@ rec {
else
test // {
inherit nodes test;
driver = driver testDriverInteractive;
driver = driver testDriver;
driverInteractive = driver testDriverInteractive;
};
runInMachine =