Lines Matching refs:tests

3 Running driver tests
6 Networking driver tests are executed within kselftest framework like any
7 other tests. They support testing both real device drivers and emulated /
13 By default, when no extra parameters are set or exported, tests execute
16 In this mode the tests are indistinguishable from other selftests and
22 Executing tests against a real device requires external preparation.
23 The netdevice against which tests will be run must exist, be running
27 the tests against a real device.
29 The current support for bash tests restricts the use of the same interface name
36 All tests in drivers/net must support running both against a software device
37 and a real device. SW-only tests should instead be placed in net/ or
38 drivers/net/netdevsim, HW-only tests in drivers/net/hw.
142 "Install" the tests and copy them over to the target machine::
149 On the target machine, running the tests will use netdevsim by default::
187 The tests have a handful of dependencies. For Fedora / CentOS::
194 This section mostly applies to Python tests but some of the guidance
201 configuration options the tests depend on. This file must be kept
204 Adding checks inside the tests to validate that the necessary kernel
206 checks, but standalone patches to make tests compatible e.g. with
223 tests), but any complex logic, test-specific environment configuration
224 and validation should be done in the tests (even if it means it has to
230 Dual-host tests (tests with an endpoint) should be written from the DUT
256 By default the tests are expected to be able to run on
257 single-interface systems. All tests which may disconnect ``NETIF``
299 Running tests CI-style
303 to easily run the tests using ``virtme-ng``.