Lines Matching refs:kunit

7 Using ``kunit.py run`` ("kunit tool")
18 	  ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run $@ )
22 	Early versions of ``kunit.py`` (before 5.6) didn't work unless run from
28 ``kunit.py run`` accepts an optional glob argument to filter tests. Currently
35 	$ echo -e 'CONFIG_KUNIT=y\nCONFIG_KUNIT_ALL_TESTS=y' > .kunit/.kunitconfig
36 	$ ./tools/testing/kunit/kunit.py run 'sysctl*'
48 ``kunit.py run`` (along with ``build``, and ``config``) supports a
53 E.g. kunit has one for its tests:
57 	$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
64 	$ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit
79 	One alternative would be to have kunit tool recursively combine configs
90 	$ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false
118 	$ echo -e "CONFIG_DEBUG_KERNEL=y\nCONFIG_DEBUG_INFO=y\nCONFIG_GCOV=y" >> .kunit/.kunitconfig
119 	$ ./tools/testing/kunit/kunit.py run
120 	# Extract the coverage information from the build dir (.kunit/)
121 	$ lcov -t "my_kunit_tests" -o coverage.info -c -d .kunit/
132 	$ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6
133 	$ lcov -t "my_kunit_tests" -o coverage.info -c -d .kunit/ --gcov-tool=/usr/bin/gcov-6
139 Running tests without using ``kunit.py run`` is also an important use case.
190 	$ modprobe kunit-example-test
196 	failed (as of 5.13). But ``kunit.py parse`` would, see below.
209 You can use ``kunit.py parse`` to parse dmesg for test output and print out
210 results in the same familiar format that ``kunit.py run`` does.
214 	$ ./tools/testing/kunit/kunit.py parse /var/log/dmesg
230 ``/sys/kernel/debug/kunit/<suite>/results``.
235 	$ modprobe kunit-example-test > /dev/null
236 	$ cat /sys/kernel/debug/kunit/example/results
240 	$ modprobe -r kunit-example-test
241 	$ cat /sys/kernel/debug/kunit/example/results
242 	/sys/kernel/debug/kunit/example/results: No such file or directory
257 	$ modprobe kunit-example-test