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