Lines Matching +full:run +full:- +full:control

1 .. SPDX-License-Identifier: GPL-2.0
17 the test's control like hardware.
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`.
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
51   external dependencies outside of the test's control like hardware.
52 - An integration test tests the interaction between a minimal set of components,
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
71 1. Try running ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
74 2. Instead of running ``kunit.py run``, try running ``kunit.py config``,
77    can run it manually against stdin or a file with ``kunit.py parse``.)
83    has KASLR enabled. (On older host kernels, you may need to run ``setarch
84    `uname -m` -R ./vmlinux`` to disable KASLR.)
87    around, so you can see what config was used after running ``kunit.py run``.
90    re-run kunit_tool.
91 5. Try to run ``make ARCH=um defconfig`` before running ``kunit.py run``. This
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.