Lines Matching full:test

12 A `unit test <https://martinfowler.com/bliki/UnitTest.html>`_ is supposed to
13 test a single unit of code in isolation, hence the name. A unit test should be
15 paths to be tested in the code under test; this is only possible if the code
16 under test is very small and does not have any external dependencies outside of
17 the test's control like hardware.
20 require installing the kernel on a test machine or in a VM and all require
21 tests to be written in userspace and run on the kernel under test; this is true
42 What is the difference between a unit test and these other kinds of tests?
45 test, or an end-to-end test.
47 - A unit test is supposed to test a single unit of code in isolation, hence the
48   name. A unit test should be the finest granularity of testing and as such
49   should allow all possible code paths to be tested in the code under test; this
50   is only possible if the code under test is very small and does not have any
51   external dependencies outside of the test's control like hardware.
52 - An integration test tests the interaction between a minimal set of components,
54   test to test the interaction between a driver and a piece of hardware, or to
55   test the interaction between the userspace libraries the kernel provides and
56   the kernel itself; however, one of these tests would probably not test the
59 - An end-to-end test usually tests the entire system from the perspective of the
60   code under test. For example, someone might write an end-to-end test for the
85 4. Make sure the kernel .config has ``CONFIG_KUNIT=y`` and at least one test
97    modules will automatically execute associated tests when loaded. Test results
98    can be collected from ``/sys/kernel/debug/kunit/<test suite>/results``, and