Lines Matching full:should

11 Samples should be limited in scope and should focus only on demonstrating non-trivial or
27   * If a sample can provide output that can be verified, then output should be evaluated against
32     functionality is working as expected, this should not replace dedicated and
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*
64     file and should be operational on all supported platforms. Do not rely on the
67   * The tests should verify the default configuration of the sample and any
68     optional features documented in the sample's README file. Sample should
73     ``extra_configs`` options in the YAML file. The :file:`prj.conf` file should have the
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
85 3. A sample should provide sufficient coverage of a subsystem, feature, or module.