Searched full:suite (Results 1 – 25 of 64) sorted by relevance
123
| /Documentation/dev-tools/kunit/ |
| D | style.rst | 24 suite is a group of tests which test a related area of the kernel. A subsystem
31 Every test suite must belong to a subsystem. A subsystem is a collection of one
81 shutdown code which is run for all tests in the suite. Not all subsystems need
90 put into separate suites, with the type of test as the last element in the suite
92 or similar in the suite name.
94 The full test suite name (including the subsystem name) should be specified as
105 The ``kasan`` subsystem has only one suite, so the suite name is the same as
113 The suite name is ambiguous without the subsystem name.
115 Because there is only one suite in the ``kasan`` subsystem, the suite should
117 ``integration_test``. It should be a separate test suite. For example, if the
[all …]
|
| D | run_manual.rst | 73 to the kernel log and thus, may have different test suite numbering.
79 boot. To run the test suite, you can use the following command to write to
86 As a result, the test suite runs and the results are printed to the kernel
|
| D | architecture.rst | 47 A KUnit suite includes a collection of test cases. The KUnit suites
67 In the above example, the test suite ``example_test_suite``, runs the
71 The ``kunit_test_suite(example_test_suite)`` registers the test suite
88 :alt: KUnit Suite Memory
90 KUnit Suite Memory Diagram
|
| D | running_tips.rst | 235 Retrieving per suite results
239 ``CONFIG_KUNIT_DEBUGFS`` to expose per-suite TAP-formatted results:
247 The results for each suite will be exposed under
248 ``/sys/kernel/debug/kunit/<suite>/results``.
309 suite definition.
415 - Otherwise, the value falls back to the suite's value.
440 This attribute is automatically saved as a string and is printed for each suite.
|
| D | start.rst | 128 separator between the name of the test suite and the test case,
129 otherwise, it will be interpreted as the name of the test suite.
132 a. inform the name of a test suite, like ``"kunit_executor_test"``,
137 b. inform the name of a test case prefixed by its test suite,
144 any test suite::
|
| D | usage.rst | 126 in the suite's exit() function, or in the free function for a resource. These
167 *test suite*. A test suite is a collection of test cases for a unit of code
169 suite and/or every test case.
172 A test case will only run if it is associated with a test suite.
195 In the above example, the test suite ``example_test_suite`` would first run
201 test suite with the KUnit test framework.
210 specified test suite in a special linker section so that it can be run by KUnit
758 * the init function) is allocated in the suite's .init */
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | arm,arm-firmware-suite.yaml | 4 $id: http://devicetree.org/schemas/mtd/partitions/arm,arm-firmware-suite.yaml#
7 title: ARM Firmware Suite (AFS) Partitions
15 The ARM Firmware Suite is a flash partitioning system found on the
21 const: arm,arm-firmware-suite
28 compatible = "arm,arm-firmware-suite";
|
| D | partitions.yaml | 17 - $ref: arm,arm-firmware-suite.yaml
|
| /Documentation/ABI/testing/ |
| D | debugfs-scmi | 9 Users: Debugging, any userspace test suite
20 Users: Debugging, any userspace test suite
28 Users: Debugging, any userspace test suite
36 Users: Debugging, any userspace test suite
44 Users: Debugging, any userspace test suite
52 Users: Debugging, any userspace test suite
61 Users: Debugging, any userspace test suite
70 Users: Debugging, any userspace test suite
|
| D | debugfs-scmi-raw | 14 Users: Debugging, any userspace test suite
32 Users: Debugging, any userspace test suite
43 Users: Debugging, any userspace test suite
54 Users: Debugging, any userspace test suite
66 Users: Debugging, any userspace test suite
90 Users: Debugging, any userspace test suite
117 Users: Debugging, any userspace test suite
|
| D | debugfs-tpmi | 10 Users: Debugging, any user space test suite
18 Users: Debugging, any user space test suite
31 Users: Debugging, any user space test suite
|
| /Documentation/devicetree/bindings/riscv/ |
| D | extensions.yaml | 301 The standard Zkn NIST algorithm suite extensions as ratified in
307 The standard Zknd for NIST suite: AES decryption instructions as
313 The standard Zkne for NIST suite: AES encryption instructions as
319 The standard Zknh for NIST suite: hash function instructions as
333 The standard Zks ShangMi algorithm suite extensions as ratified in
339 The standard Zksed for ShangMi suite: SM4 block cipher instructions
345 The standard Zksh for ShangMi suite: SM3 hash function instructions
496 The standard Zvkn extension for NIST algorithm suite instructions, as
502 The standard Zvknc extension for NIST algorithm suite with carryless
514 The standard Zvkng extension for NIST algorithm suite with GCM
[all …]
|
| /Documentation/arch/arm/vfp/ |
| D | release-notes.rst | 14 John R. Hauser using the TestFloat-2a test suite. Details of this
15 library and test suite can be found at:
|
| /Documentation/bpf/ |
| D | s390.rst | 15 The following is required to build and run the test suite:
105 In addition to the usual Kconfig options required to run the BPF test suite, it
127 4. Running the test suite
160 After that, the test suite can be run using the following commands::
|
| /Documentation/admin-guide/ |
| D | clearing-warn-once.rst | 9 This can be useful after test suite runs to reproduce problems.
|
| /Documentation/networking/device_drivers/atm/ |
| D | cxacru-cf.py | 16 # Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
| /Documentation/nvme/ |
| D | feature-and-quirk-policy.rst | 31 NVMe is a large suite of specifications, and contains features that are only
|
| /Documentation/input/devices/ |
| D | pxrc.rst | 44 the `input layer utilities` suite [1]_.
|
| /Documentation/usb/ |
| D | raw-gadget.rst | 69 Raw Gadget usage examples and a test suite:
|
| /Documentation/arch/arm/nwfpe/ |
| D | nwfpe.rst | 62 part by the International Computer Science Institute, located at Suite 600,
|
| /Documentation/devicetree/bindings/iio/addac/ |
| D | adi,ad74413r.yaml | 19 four configurable input/output channels and a suite of diagnostic functions.
|
| /Documentation/driver-api/rapidio/ |
| D | tsi721.rst | 112 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
| /Documentation/admin-guide/cifs/ |
| D | todo.rst | 88 file system xfstest suite.
|
| /Documentation/mm/ |
| D | hwpoison.rst | 170 Test suite (hwpoison specific portable tests in tsrc)
|
| /Documentation/networking/device_drivers/ethernet/chelsio/ |
| D | cxgb.rst | 377 Suite 100
387 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
|
123