Lines Matching +full:always +full:- +full:running

1 .. SPDX-License-Identifier: GPL-2.0
25 Does KUnit support running on architectures other than UML?
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``,
80 3. Running the UML kernel directly can often reveal issues or error messages,
81    ``kunit_tool`` ignores. This should be as simple as running ``./vmlinux``
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
95 6. Finally, try running KUnit outside UML. KUnit and KUnit tests can be
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`.
103 If none of the above tricks help, you are always welcome to email any issues to
104 kunit-dev@googlegroups.com.