Lines Matching refs:be
11 Samples should be limited in scope and should focus only on demonstrating non-trivial or
19 1. Samples must not be used to test features or verify platforms
27 * If a sample can provide output that can be verified, then output should be evaluated against
33 comprehensive tests with full coverage to be submitted into the
38 2. Twister should be able to build every sample.
59 * Do not mark the test as build only. A sample should be able to build *and*
63 * The default configuration for the sample must be in the :file:`prj.conf`
64 file and should be operational on all supported platforms. Do not rely on the
69 never be used to test functionality of the subsystem or module the sample
72 operation can be verified using ``extra_args`` or
75 * Sample output can be validated by leveraging the ``harness_config`` regex option,
78 verified on. Those platforms should be listed in the sample's README file.
80 resource constraints. Ideally, one platform should be enough to verify the
93 * Must not be unit tests.
95 4. Samples must be documented.