You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
39 lines
1.4 KiB
39 lines
1.4 KiB
<section xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" xml:id="sec-running-nixos-tests-interactively">
|
|
<title>Running Tests interactively</title>
|
|
<para>
|
|
The test itself can be run interactively. This is particularly
|
|
useful when developing or debugging a test:
|
|
</para>
|
|
<programlisting>
|
|
$ nix-build nixos/tests/login.nix -A driverInteractive
|
|
$ ./result/bin/nixos-test-driver --interactive
|
|
starting VDE switch for network 1
|
|
>
|
|
</programlisting>
|
|
<para>
|
|
You can then take any Python statement, e.g.
|
|
</para>
|
|
<programlisting language="python">
|
|
> start_all()
|
|
> test_script()
|
|
> machine.succeed("touch /tmp/foo")
|
|
> print(machine.succeed("pwd")) # Show stdout of command
|
|
</programlisting>
|
|
<para>
|
|
The function <literal>test_script</literal> 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).
|
|
</para>
|
|
<para>
|
|
You can re-use the VM states coming from a previous run by setting
|
|
the <literal>--keep-vm-state</literal> flag.
|
|
</para>
|
|
<programlisting>
|
|
$ ./result/bin/nixos-test-driver --interactive --keep-vm-state
|
|
</programlisting>
|
|
<para>
|
|
The machine state is stored in the
|
|
<literal>$TMPDIR/vm-state-machinename</literal> directory.
|
|
</para>
|
|
</section>
|
|
|