Lines Matching refs:tests

25 infrastructure for running tests, and much more.
28 writing unit tests. Tests written against KUnit will run on kernel boot if
29 built-in, or when loaded if built as a module. These tests write out results to
32 To make running these tests (and reading the results) easier, KUnit offers
35 results. This provides a quick way of running KUnit tests during development,
49 KUnit provides a common framework for unit tests within the kernel.
51 KUnit tests can be run on most architectures, and most tests are architecture
52 independent. All built-in KUnit tests run on kernel startup.  Alternatively,
53 KUnit and KUnit tests can be built as modules and tests will run when the test
58         KUnit can also run tests without needing a virtual machine or actual
65 several dozen tests in only 10 to 20 seconds; this might not sound like a big
66 deal to some people, but having such fast and easy to run tests fundamentally
77 but this point also applies to testing. If your tests are slow, unreliable, are
79 then you wait a lot longer to write tests, and you wait a lot longer to run
80 tests; this means that tests are likely to break, unlikely to test a lot of
81 things, and are unlikely to be rerun once they pass. If your tests are really
83 someone sends you some code. Why trust that someone ran all their tests