/linux/Documentation/dev-tools/ |
H A D | kselftest.rst | 5 The kernel contains a set of "self tests" under the tools/testing/selftests/ 41 testing-devices 49 $ make -C tools/testing/selftests 53 $ make -C tools/testing/selftests run_tests 96 $ make -C tools/testing/selftests TARGETS=ptrace run_tests 115 $ make -C tools/testing/selftests SKIP_TARGETS=ptrace run_tests 126 See the top-level tools/testing/selftests/Makefile for the list of all 134 $ make -C tools/testing/selftests hotplug 138 $ make -C tools/testing/selftests run_hotplug 147 tool) to install selftests in the default location (`tools/testing/selftest [all...] |
H A D | index.rst | 10 A brief overview of testing-specific tools can be found in 11 Documentation/dev-tools/testing-overview.rst 20 testing-overview
|
H A D | testing-devices.rst | 5 Device testing with kselftest 9 There are a few different kselftests available for testing devices generically, 14 (``tools/testing/selftests``).
|
/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! [all...] |
H A D | run_wrapper.rst | 19 ./tools/testing/kunit/kunit.py run 33 ./tools/testing/kunit/kunit.py run --timeout=30 --jobs=`nproc --all` 53 ./tools/testing/kunit/kunit.py run --kunitconfig=fs/ext4/.kunitconfig 59 ./tools/testing/kunit/kunit.py run --help 67 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/kunit/configs/default.config. 81 cp tools/testing/kunit/configs/default.config .kunit/.kunitconfig 111 ./tools/testing/kunit/kunit.py config 118 ./tools/testing/kunit/kunit.py build 126 ./tools/testing/kunit/kunit.py exec 141 ./tools/testing/kuni [all...] |
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``
|
/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/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.
|
/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/kernel/git/torvalds/linux.git/tree/tools/testing/selftest [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/progs/lsm.c 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/prog_tests/test_lsm.c
|
/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/Documentation/translations/zh_CN/security/ |
H A D | landlock.rst | 87 找到:tools/testing/selftests/landlock/ 121 .. _tools/testing/selftests/landlock/: 123 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/tools/testing/selftests/landlock/
|
/linux/drivers/thermal/testing/ |
H A D | Makefile | 3 # Thermal core testing facility. 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/gpu/ |
H A D | automated_testing.rst | 4 Automated testing of the DRM subsystem 13 testing to have to acquire and maintain what can be a considerable amount of 21 can be used as well for testing the DRM subsystem. This document explains how 22 people interested in testing it can use this shared infrastructure to save 98 How to enable automated testing on your tree 147 For testing changes to the scripts in the drm-ci repo, change the 153 How to incorporate external fixes in your testing 156 Often, regressions in other trees will prevent testing changes local to the 165 How to deal with automated testing labs that may be down
|
/linux/Documentation/admin-guide/ |
H A D | abi.rst | 16 abi-testing 27 abi-testing-files
|
/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/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/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/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/iommu/iommufd/ |
H A D | Kconfig | 33 purpose of testing IOMMUFD with unmodified userspace supporting VFIO 37 Unless testing IOMMUFD, say N here. 48 tools/testing/selftests/iommu
|
/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
|