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

1 .. SPDX-License-Identifier: GPL-2.0
13 test a single unit of code in isolation, hence the name. A unit test should be
15 paths to be tested in the code under test; this is only possible if the code
20 require installing the kernel on a test machine or in a VM and all require
21 tests to be written in userspace and run on the kernel under test; this is true
37 In short, this means that, yes, you can run KUnit on other architectures, but
40 For more information, see :ref:`kunit-on-non-uml`.
42 What is the difference between a unit test and these other kinds of tests?
45 test, or an end-to-end test.
47 - A unit test is supposed to test a single unit of code in isolation, hence the
49   should allow all possible code paths to be tested in the code under test; this
52 - An integration test tests the interaction between a minimal set of components,
54   test to test the interaction between a driver and a piece of hardware, or to
55   test the interaction between the userspace libraries the kernel provides and
59 - An end-to-end test usually tests the entire system from the perspective of the
60   code under test. For example, someone might write an end-to-end test for the
63   that depends on interactions between the hardware, the kernel, and userspace.
71 1. Try running ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
82    mounted), and has had issues in the past when built statically and the host
84    `uname -m` -R ./vmlinux`` to disable KASLR.)
90    re-run kunit_tool.
96    seeing. When tests are built-in, they will execute when the kernel boots, and
100    non-UML architectures" in :doc:`usage`.
103 kunit-dev@googlegroups.com.