Lines Matching +full:re +full:- +full:config

1 .. SPDX-License-Identifier: GPL-2.0
35 (see :ref:`kunit-on-qemu`).
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
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``,
86    ``setarch `uname -m` -R ./vmlinux`` to disable KASLR.)
87 4. Make sure the kernel .config has ``CONFIG_KUNIT=y`` and at least one test
88    (e.g. ``CONFIG_KUNIT_EXAMPLE_TEST=y``). kunit_tool will keep its .config
89    around, so you can see what config was used after running ``kunit.py run``.
90    It also preserves any config changes you might make, so you can
92    re-run kunit_tool.
94    may help clean up any residual config items which could be causing problems.
97    Doing so should allow you to determine if UML is causing the issue you're
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.