1
0
Fork 1
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-19 03:48:57 +00:00
nixpkgs/nixos/doc/manual/development/running-nixos-tests-interactively.xml

50 lines
1.7 KiB
XML
Raw Normal View History

<section xmlns="http://docbook.org/ns/docbook"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xi="http://www.w3.org/2001/XInclude"
version="5.0"
xml:id="sec-running-nixos-tests-interactively">
2018-05-02 00:57:09 +01:00
<title>Running Tests interactively</title>
2018-05-02 00:57:09 +01:00
<para>
The test itself can be run interactively. This is particularly useful when
developing or debugging a test:
<screen>
2019-06-17 12:25:50 +01:00
<prompt>$ </prompt>nix-build nixos/tests/login.nix -A driver
<prompt>$ </prompt>./result/bin/nixos-test-driver
starting VDE switch for network 1
2019-06-17 12:25:50 +01:00
<prompt>&gt;</prompt>
</screen>
2019-11-04 22:50:50 +00:00
You can then take any Python statement, e.g.
<screen>
2019-11-04 22:50:50 +00:00
<prompt>&gt;</prompt> start_all()
<prompt>&gt;</prompt> test_script()
<prompt>&gt;</prompt> machine.succeed("touch /tmp/foo")
<prompt>&gt;</prompt> print(machine.succeed("pwd")) # Show stdout of command
</screen>
2019-11-04 22:50:50 +00:00
The function <command>test_script</command> executes the entire test script
and drops you back into the test driver command line upon its completion.
This allows you to inspect the state of the VMs after the test (e.g. to debug
the test script).
2018-05-02 00:57:09 +01:00
</para>
<para>
To just start and experiment with the VMs, run:
<screen>
2019-06-17 12:25:50 +01:00
<prompt>$ </prompt>nix-build nixos/tests/login.nix -A driver
<prompt>$ </prompt>./result/bin/nixos-run-vms
</screen>
The script <command>nixos-run-vms</command> starts the virtual machines
defined by test.
2018-09-17 11:58:14 +01:00
</para>
<para>
You can re-use the VM states coming from a previous run
by setting the <command>--keep-vm-state</command> flag.
<screen>
<prompt>$ </prompt>./result/bin/nixos-run-vms --keep-vm-state
</screen>
The machine state is stored in the
<filename>$TMPDIR/vm-state-</filename><varname>machinename</varname> directory.
2018-05-02 00:57:09 +01:00
</para>
</section>