Lines Matching refs:test
1 # Mbed TLS driver interface test strategy
3 This document describes the test strategy for the driver interfaces in Mbed TLS. Mbed TLS has inter…
25 …e element driver interface. Note that a test case may cover multiple requirements; for example a “…
35 * Make at least one test that successfully registers the maximum number of drivers and fails to reg…
41 * Make at least one test with a key in a secure element that checks that the driver method is calle…
42 * Make at least one test with a key that is not in a secure element that checks that the driver met…
43 * Make at least one test with a key in a secure element with a driver that does not have the requis…
44 * Make at least one test with a key in a secure element with a driver that does not have the substr…
45 * At least one test should register multiple drivers with a key in each driver and check that the e…
46 * At least one test should register the same driver structure with multiple lifetime values and che…
48 … that provides the MAC methods must provide all or none). In those cases, test with all of them nu…
56 * Check that the expected inputs reach the driver. This may be implicit in a test that checks the o…
65 * Unexpected errors. At least test that if the driver returns `PSA_ERROR_GENERIC_ERROR`, this is pr…
102 * Run the full driver validation test suite (which does not yet exist).
103 * Run at least one test application (e.g. the Mbed OS TLS example).
113 * Run the full driver validation test suite (which does not yet exist).
125 …cryptographic operations, …) must be exercised in at least one build. The test must verify that th…
129 …er handle the request. For each entry point, there must be at least three test runs with two or mo…