Lines Matching refs:kunit
24 ./tools/testing/kunit/kunit.py run
30 This happens because internally kunit.py specifies ``.kunit``
57 Documentation/dev-tools/kunit/run_wrapper.rst.
72 If you didn't run ``kunit.py run`` yet, you can generate it by running:
77 tools/testing/kunit/kunit.py config
78 cat .kunit/.kunitconfig
81 ``.kunitconfig`` lives in the ``--build_dir`` used by kunit.py, which is
82 ``.kunit`` by default.
90 a. Edit ``.kunit/.kunitconfig``. The file should contain the list of kconfig
94 If you need to run on an architecture other than UML see :ref:`kunit-on-qemu`.
96 b. Enable additional kconfig options on top of ``.kunit/.kunitconfig``.
99 ./tools/testing/kunit/kunit.py run \
105 ./tools/testing/kunit/kunit.py run \
109 d. If you change the ``.kunitconfig``, kunit.py will trigger a rebuild of the
111 tools like ``make menuconfig O=.kunit``. As long as its a superset of
112 ``.kunitconfig``, kunit.py won't overwrite your changes.
119 make savedefconfig O=.kunit
120 cp .kunit/defconfig .kunit/.kunitconfig
135 ./tools/testing/kunit/kunit.py run "kunit_executor_test"
140 ./tools/testing/kunit/kunit.py run "example.example_simple_test"
146 ./tools/testing/kunit/kunit.py run "*.*64*"
222 #include <kunit/test.h>
227 static void misc_example_add_test_basic(struct kunit *test)
236 static void misc_example_test_failure(struct kunit *test)
268 4. Add the following lines to ``.kunit/.kunitconfig``:
279 ./tools/testing/kunit/kunit.py run
297 If you're interested in using some of the more advanced features of kunit.py,
298 take a look at Documentation/dev-tools/kunit/run_wrapper.rst
300 If you'd like to run tests without using kunit.py, check out
301 Documentation/dev-tools/kunit/run_manual.rst
304 for testing different things), see Documentation/dev-tools/kunit/usage.rst