| /linux/tools/testing/selftests/net/rds/ |
| H A D | README.txt | 18 -d Log directory. Defaults to tools/testing/selftests/net/rds/rds_logs
29 tools/testing/selftests/net/rds/config.sh -g
32 tools/testing/selftests/net/rds/config.sh
35 vng --build --config tools/testing/selftests/net/config
39 "export PYTHONPATH=tools/testing/selftests/net/; tools/testing/selftests/net/rds/run.sh"
41 An HTML coverage report will be output in tools/testing/selftests/net/rds/rds_logs/coverage/.
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | index.rst | 21 This section details the kernel unit testing framework.
26 KUnit (Kernel unit testing framework) provides a common framework for
33 (C++ unit testing framework).
42 KUnit follows the white-box testing approach. The test has access to
46 In addition, KUnit has kunit_tool, a script (``tools/testing/kunit/kunit.py``)
69 granularity of testing and allows all possible code paths to be tested in the
91 - Increases testing speed and development in the long run.
93 compared to acceptance testing.
106 or to experiment with tools/testing/kunit/kunit.py and the example test under
109 Happy testing!
|
| H A D | faq.rst | 9 KUnit is a unit testing framework. Autotest, kselftest (and some others) are
14 test should be the finest granularity of testing and should allow all possible
19 There are no testing frameworks currently available for the kernel that do not
21 testing frameworks require tests to be written in userspace and run on the
23 disqualifying any of them from being considered unit testing frameworks.
34 (``tools/testing/kunit/kunit.py``) that might not support some architectures
50 test should be the finest granularity of testing and, as such, allows all
73 1. Run ``./tools/testing/kunit/kunit.py run`` with the ``--raw_output``
|
| H A D | running_tips.rst | 18 ( cd "$(git rev-parse --show-toplevel)" && ./tools/testing/kunit/kunit.py run "$@" )
36 $ ./tools/testing/kunit/kunit.py run 'sysctl*'
43 $ ./tools/testing/kunit/kunit.py run 'sysctl*.*write*'
64 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit/.kunitconfig
71 $ ./tools/testing/kunit/kunit.py run --kunitconfig=lib/kunit
97 $ ./tools/testing/kunit/kunit.py run --kernel_args=param=42 --kernel_args=param2=false
126 …$ ./tools/testing/kunit/kunit.py run --kunitconfig=.kunit/ --kunitconfig=tools/testing/kunit/confi…
139 $ ./tools/testing/kunit/kunit.py run --make_options=CC=/usr/bin/gcc-6
147 …$ ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --kunitconfig=.kunit/ --kunitconfig=too…
162 the kernel, run the ``./linux`` binary), this section will focus on testing
[all …]
|
| H A D | start.rst | 24 ./tools/testing/kunit/kunit.py run
77 tools/testing/kunit/kunit.py config
99 ./tools/testing/kunit/kunit.py run \
105 ./tools/testing/kunit/kunit.py run \
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*"
284 ./tools/testing/kunit/kunit.py run
309 for testing different things), see Documentation/dev-tools/kunit/usage.rst
|
| H A D | architecture.rst | 15 The kernel testing library supports KUnit tests written in C using
114 In the event of a failure, the testing flow differs as follows:
159 ``kunit_tool`` is a Python script, found in ``tools/testing/kunit/kunit.py``. It
170 (for example, ``tools/testing/kunit/qemu configs/powerpc.py``) contains
180 ``./tools/testing/kunit/kunit.py config`` and
186 ``build`` argument: ``./tools/testing/kunit/kunit.py build``.
193 argument: ``./tools/testing/kunit/kunit.py exec``.
|
| /linux/tools/testing/selftests/rcutorture/bin/ |
| H A D | torture.sh | 474 …tools/testing/selftests/rcutorture/bin/kvm.sh --datestamp "$ds/results-rcutasksflavors/$flavor" --…
496 …torture_set "rcutorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$dura…
502 …torture_set "locktorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture lock --allcpus -…
510 …torture_set "scftorture" tools/testing/selftests/rcutorture/bin/kvm.sh --torture scf --allcpus --d…
521 …torture_set "rcurttorture" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration "$du…
525 …torture_set "rcurttorture-exp" tools/testing/selftests/rcutorture/bin/kvm.sh --allcpus --duration …
551 …./tools/testing/kunit/kunit.py run --make_options LLVM=1 --make_options CLIPPY=1 --arch arm64 --kc…
572 …tools/testing/selftests/rcutorture/bin/srcu_lockdep.sh --datestamp "$ds/results-srcu-lockdep" > $T…
649 …torture_set "rcuscale-$prim" tools/testing/selftests/rcutorture/bin/kvm.sh --torture rcuscale --al…
677 …torture_set "rcuscale-$prim$torture_suffix" tools/testing/selftests/rcutorture/bin/kvm-again.sh "`…
[all …]
|
| /linux/tools/testing/kunit/configs/ |
| H A D | coverage_uml.config | 4 # ./tools/testing/kunit/kunit.py run \
5 # --kunitconfig=tools/testing/kunit/configs/all_tests_uml.config \
6 # --kunitconfig=tools/testing/kunit/configs/coverage_uml.config
|
| /linux/Documentation/bpf/ |
| H A D | map_sockmap.rst | 348 - `tools/testing/selftests/bpf/progs/test_sockmap_kern.h`_
349 - `tools/testing/selftests/bpf/progs/sockmap_parse_prog.c`_
350 - `tools/testing/selftests/bpf/progs/sockmap_verdict_prog.c`_
351 - `tools/testing/selftests/bpf/progs/test_sockmap_listen.c`_
352 - `tools/testing/selftests/bpf/progs/test_sockmap_update.c`_
439 - `tools/testing/selftests/bpf/prog_tests/sockmap_basic.c`_
440 - `tools/testing/selftests/bpf/test_sockmap.c`_
441 - `tools/testing/selftests/bpf/test_maps.c`_
491 … _`tools/testing/selftests/bpf/progs/test_sockmap_kern.h`: https://git.kernel.org/pub/scm/linux/ke…
492 …_`tools/testing/selftests/bpf/progs/sockmap_parse_prog.c`: https://git.kernel.org/pub/scm/linux/ke…
[all …]
|
| H A D | prog_lsm.rst | 134 `tools/testing/selftests/bpf/progs/lsm.c`_ and the corresponding
135 userspace code in `tools/testing/selftests/bpf/prog_tests/test_lsm.c`_
140 .. _tools/testing/selftests/bpf/progs/lsm.c:
141 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
142 .. _tools/testing/selftests/bpf/prog_tests/test_lsm.c:
143 …https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/bpf/…
|
| H A D | s390.rst | 29 testing \
97 testing \
122 -C tools/testing/selftests \
124 INSTALL_PATH=$PWD/tools/testing/selftests/kselftest_install \
162 cd /linux/tools/testing/selftests/kselftest_install
167 cd /linux/tools/testing/selftests/bpf
|
| /linux/tools/testing/selftests/rcutorture/doc/ |
| H A D | rcu-test-image.txt | 5 $ size tools/testing/selftests/rcutorture/initrd/init
7 328 0 8 336 150 tools/testing/selftests/rcutorture/initrd/init
10 some aspect of the rcutorture testing. This will require a more fully
15 tools/testing/selftests/rcutorture/initrd
17 For example, your tools/testing/selftests/rcutorture/initrd/init might
19 scripts need starting to properly monitor or control your testing.
|
| H A D | initrd.txt | 4 tools/testing/selftests/rcutorture/bin/mkinitrd.sh.
11 cd tools/testing/selftests/rcutorture
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-hyperv | 5 Description: Fuzz testing status of a vmbus device, whether its in an ON
13 Description: Fuzz testing buffer interrupt delay value between 0 - 1000
21 Description: Fuzz testing message delay value between 0 - 1000 microseconds
|
| /linux/drivers/net/wireless/virtual/ |
| H A D | Kconfig | 2 tristate "Simulated radio testing tool for mac80211"
5 This driver is a developer testing tool that can be used to test
7 needed for normal wireless LAN usage and is only for testing. See
|
| /linux/drivers/thermal/testing/ |
| H A D | Makefile | 5 obj-$(CONFIG_THERMAL_CORE_TESTING) += thermal-testing.o
7 thermal-testing-y := command.o zone.o
|
| /linux/Documentation/driver-api/rapidio/ |
| H A D | sysfs.rst | 6 Documentation/ABI/testing/sysfs-bus-rapidio and
7 Documentation/ABI/testing/sysfs-class-rapidio
|
| /linux/Documentation/rust/ |
| H A D | testing.rst | 27 ./tools/testing/kunit/kunit.py run --make_options LLVM=1 --arch x86_64 --kconfig_add CONFIG_RUST=y
32 built-in vs. command line testing.
73 testing facilities. For instance, the kernel log would look like::
117 require passing context, unlike those for KUnit testing (i.e.
119 documentation do not need to care about which testing framework is used. In
214 Currently, they are mostly used for testing the ``macros`` crate's examples.
219 Kselftests are also available in the ``tools/testing/selftests/rust`` folder.
222 ``tools/testing/selftests/rust/config`` file and can be included with the aid
225 ./scripts/kconfig/merge_config.sh .config tools/testing/selftests/rust/config
|
| /linux/lib/ |
| H A D | Kconfig.kfence | 19 Note that, KFENCE is not a substitute for explicit testing with tools
76 int "Stress testing of fault handling and error reporting" if EXPERT
82 and allocations/frees. A value of 0 disables stress testing logic.
84 Only for KFENCE testing; set to 0 if you are not a KFENCE developer.
91 Test suite for KFENCE, testing various error detection scenarios with
|
| /linux/drivers/media/test-drivers/vivid/ |
| H A D | Kconfig | 18 It is highly configurable and is ideal for testing applications.
34 bool "Enable Framebuffer for testing Output Overlay"
41 testing Output Overlay.
|
| /linux/Documentation/translations/zh_CN/dev-tools/ |
| H A D | index.rst | 15 Documentation/translations/zh_CN/dev-tools/testing-overview.rst
21 testing-overview
|
| /linux/Documentation/translations/zh_TW/dev-tools/ |
| H A D | index.rst | 17 Documentation/translations/zh_TW/dev-tools/testing-overview.rst
26 testing-overview
|
| /linux/Documentation/virt/kvm/ |
| H A D | review-checklist.rst | 47 These are low level tests that allow granular testing of kernel APIs.
49 guest instructions, and testing multiple calls to ``KVM_CREATE_VM``
51 ``tools/testing/selftests/kvm``.
66 The best testing approach depends on the feature's complexity and
94 tests suffice. Explain your testing process in the cover letter,
101 open source, though that is of course preferrable for easier testing.
116 Following the above suggestions for testing in selftests and
|
| /linux/Documentation/translations/zh_CN/doc-guide/ |
| H A D | checktransupdate.rst | 39 - ``./scripts/checktransupdate.py Documentation/translations/zh_CN/dev-tools/testing-overview.rst``
49 Documentation/translations/zh_CN/dev-tools/testing-overview.rst
|
| /linux/tools/testing/selftests/arm64/ |
| H A D | README | 16 $ make -C tools/testing/selftests TARGETS=arm64 \
21 $ make -C tools/testing/selftests TARGETS=arm64 ARM64_SUBTARGETS="tags signal" \
|