Lines Matching +full:in +full:- +full:between

1 .. SPDX-License-Identifier: GPL-2.0
13 test a single unit of code in isolation and hence the name *unit test*. A unit
15 code paths to be tested in the code under test. This is only possible if the
20 require installing the kernel on a test machine or in a virtual machine. All
21 testing frameworks require tests to be written in userspace and run on the
35 (see :ref:`kunit-on-qemu`).
37 In short, yes, you can run KUnit on other architectures, but it might require
40 For more information, see :ref:`kunit-on-non-uml`.
42 .. _kinds-of-tests:
44 What is the difference between a unit test and other kinds of tests?
47 test, or an end-to-end test.
49 - A unit test is supposed to test a single unit of code in isolation. A unit
51   possible code paths to be tested in the code under test. This is only possible
54 - An integration test tests the interaction between a minimal set of components,
56   test to test the interaction between a driver and a piece of hardware, or to
57   test the interaction between the userspace libraries the kernel provides and
61 - An end-to-end test usually tests the entire system from the perspective of the
62   code under test. For example, someone might write an end-to-end test for the
65   that depends on interactions between the hardware, the kernel, and userspace.
73 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
84    filesystem mounted), and has had issues in the past when built statically and
86    ``setarch `uname -m` -R ./vmlinux`` to disable KASLR.)
92    re-run kunit_tool.
98    seeing. When tests are built-in, they will execute when the kernel boots, and
101    can be parsed with ``kunit.py parse``. For more details, see :ref:`kunit-on-qemu`.
104 kunit-dev@googlegroups.com.