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

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