Lines Matching refs:can
13 It can be handy to create a bash function like:
38 We can filter down to just the "write" tests via:
57 regular basis (especially if they have other dependencies), you can create a
67 file ``.kunitconfig``, you can just pass in the dir, e.g.
93 You can use ``--kernel_args`` to pass arbitrary kernel arguments, e.g.
111 Instead of enabling ``CONFIG_GCOV_KERNEL=y``, we can set these options:
131 # E.g. can generate an HTML report in a tmp dir like so:
135 If your installed version of gcc doesn't work, you can tweak the steps:
142 Alternatively, LLVM-based toolchains can also be used:
150 …# The coverage.info file is in lcov-compatible format and it can be used to e.g. generate HTML rep…
195 Depending on the tests, you can build them as loadable modules.
204 Then after booting into our kernel, we can run the test via
217 You can set ``CONFIG_KUNIT=m`` as well, however, some features will not
227 You can use ``kunit.py parse`` to parse dmesg for test output and print out
238 Regardless of how you're running your tests, you can enable
268 your tests as modules. That way you can isolate the coverage from tests from
281 Test suites and cases can be marked with test attributes, such as speed of
282 test. These attributes will later be printed in test output and can be used to
291 Test cases can be marked using the ``KUNIT_CASE_ATTR(test_name, attributes)``
305 To mark a test case as slow, you can also use ``KUNIT_CASE_SLOW(test_name)``.
308 Test suites can be marked with an attribute by setting the "attr" field in the
334 for all passing tests but the raw kernel output can be accessed using the
355 Additionally, users can output a full attribute report of tests with their
363 This report can be accessed when running KUnit manually by passing in the
369 Users can filter tests using the ``--filter`` command line flag when running
377 You can also use the following operations on filters: "<", ">", "<=", ">=",
388 Additionally, you can use multiple filters at once. Simply separate filters
396 You can use this filtering feature when running KUnit manually by passing
399 Filtered tests will not run or show up in the test output. You can use the
407 Since both suites and test cases can have attributes, there may be conflicts
433 The macro ``KUNIT_CASE_SLOW(test_name)`` can be easily used to set the speed
441 Tests can also be filtered using this attribute.
447 This attribute is automatically saved as a boolean and tests can also be