Lines Matching full:tests

9 There are three sorts of tests:
11 - The KUnit tests.
12 - The ``#[test]`` tests.
15 The KUnit tests
18 These are the tests that come from the examples in the Rust documentation. They
19 get transformed into KUnit tests.
24 These tests can be run via KUnit. For example via ``kunit_tool`` (``kunit.py``)
37 	   Kernel hacking -> Kernel Testing and Coverage -> KUnit - Enable support for unit tests
43 KUnit tests are documentation tests
46 These documentation tests are typically examples of usage of any item (e.g.
63 In userspace, the tests are collected and run via ``rustdoc``. Using the tool
68 For the kernel, however, these tests get transformed into KUnit test suites.
93 Tests using the `? <https://doc.rust-lang.org/reference/expressions/operator-expr.html#the-question…
104 The tests are also compiled with Clippy under ``CLIPPY=1``, just like normal
114 Rust tests appear to assert using the usual ``assert!`` and ``assert_eq!``
126 Since these tests are examples, i.e. they are part of the documentation, they
133 The ``#[test]`` tests
136 Additionally, there are the ``#[test]`` tests. Like for documentation tests,
140 These tests are introduced by the ``kunit_tests`` procedural macro, which takes
144 tests section. We could write, in the same file where we have our function:
149 	mod tests {
168 Like documentation tests, the ``assert!`` and ``assert_eq!`` macros are mapped
177 	mod tests {
204 The ``rusttest`` host tests
207 These are userspace tests that can be built and run in the host (i.e. the one
221 The kernel config options required for the tests are listed in the
231 tests can be compiled and executed using the following command::