Lines Matching full:are

9 There are three sorts of tests:
18 These are the tests that come from the examples in the Rust documentation. They
43 KUnit tests are documentation tests
46 These documentation tests are typically examples of usage of any item (e.g.
49 They are very convenient because they are just written alongside the
63 In userspace, the tests are collected and run via ``rustdoc``. Using the tool
65 (thus enforcing they are kept in sync with the code they document) and as well
94 operator are also supported as usual, e.g.:
104 The tests are also compiled with Clippy under ``CLIPPY=1``, just like normal
124 actually failed. Additionally, doctests are not run for nonpublic functions.
126 Since these tests are examples, i.e. they are part of the documentation, they
136 Additionally, there are the ``#[test]`` tests. Like for documentation tests,
137 these are also fairly similar to what you would expect from userspace, and they
138 are also mapped to KUnit.
140 These tests are introduced by the ``kunit_tests`` procedural macro, which takes
168 Like documentation tests, the ``assert!`` and ``assert_eq!`` macros are mapped
207 These are userspace tests that can be built and run in the host (i.e. the one
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.
221 The kernel config options required for the tests are listed in the
227 The kselftests are built within the kernel source tree and are intended to