Lines Matching refs:not
5 …umented behavior of the product, in a realistic environment. However this is not always sufficient.
9 This is a test strategy document, not a test plan. A description of exactly what is tested is out o…
24 Always follow these rules unless you have a good reason not to. If you deviate, document the ration…
30 Do not add test-specific interfaces if there's a practical way of doing it another way. All public …
34 …eader files from `library/`. Do not define non-public interfaces in public headers. In contrast, s…
38 If test code or test data depends on internal details of the library and not just on its documented…
49 > # and not expected to be raised any time soon) is less than the maximum
58 * **Test-specific code must be guarded by `#if defined(MBEDTLS_TEST_HOOKS)`**. Do not create fine-g…
59 * **Do not use `MBEDTLS_TEST_HOOKS` for security checks or assertions.** Security checks belong in …
60 * **Merely defining `MBEDTLS_TEST_HOOKS` must not change the behavior**. It may define extra functi…
69 …not a macro, to avoid accidentally skipping side effects in its parameters), to provide a hook for…
85 * Coverage: we need to test behaviors which are not easy to trigger by using the API or which canno…
86 …ant to test the actual product, not a modified version, since conclusions drawn from a test of a m…
87 * Effacement: the product should not include features that are solely present for test purposes, si…
89 …uct's internal or implementation-specific behavior changes. We should also not give the impression…
143 …of this approach is that this requires adding a lot of interfaces that are not useful in productio…
145 As a rule, we do not add public interfaces solely for testing purposes. We only add public interfac…
151 | Coverage | ~ Many useful tests are not reasonably achievable |
160 …not use” in comments (or not described at all) and are not included in Doxygen-rendered documentat…
166 | Coverage | ~ Many useful tests are not reasonably achievable |
174 We can write tests that call internal functions that are not exposed in the public interfaces. This…
178 …rectly. We may accidentally rely on internal details in the tests that are not necessarily always …
180 …not be hidden at link time (but link-time hiding is not something we currently do). Another limita…
185 | Correctness | + Does not require a product change |
186 | | ~ The tests may call internal functions in a way that does not reflect actual usage…
197 * This does not work for platform-dependent properties unless we have a formal model of the platfor…
209 If there's code that we want to have in the product for testing, but not in production, we can add …
224 …Either we're testing or we're not. Fine-grained options for testing would require more test builds…
225 * **Merely enabling the compile-time option should not change the behavior.**<br>
228 …We should not have test-specific conditional compilation littered through the code, as that makes …
240 | Correctness | + Instrumentation generally does not affect the program's functional behavior |
253 * Due to compiler optimizations, the memory may not have the layout that we expect.
270 …e currently used for invasive testing, or planned to be used. This list is not intended to be exha…
280 …way, and any C code that observes the zeroization would cause the compiler not to optimize it away.
298 … of `mbedtls_psa_crypto_free()`. `PSA_DONE` fails the test if the key store in memory is not empty.
302 …ent before calling `mbedtls_psa_crypto_free()`. This feature is mostly but not exclusively useful …
346 Goal: test that the storage format does not change between versions (or if it does, an upgrade path…
350 Note that the storage format is defined not only by the general layout, but also by the numerical v…