Lines Matching full:that

21 …s that drivers must implement. To make a driver usable by Mbed Crypto, the initialization code mus…
25 …that must be implemented to validate the secure element driver interface. Note that a test case ma…
35 * Make at least one test that successfully registers the maximum number of drivers and fails to reg…
39 For each API function that can lead to a driver call (more precisely, for each driver method call s…
41 …ecure element that checks that the driver method is called. A few API functions involve multiple d…
42 * Make at least one test with a key that is not in a secure element that checks that the driver met…
43 …driver that does not have the requisite method (i.e. the method pointer is `NULL`) but has the sub…
44 … with a driver that does not have the substructure containing that method (i.e. the pointer to the…
45 * At least one test should register multiple drivers with a key in each driver and check that the e…
46 …egister the same driver structure with multiple lifetime values and check that the driver receives…
48 Some methods only make sense as a group (for example a driver that provides the MAC methods must pr…
52 For each API function that can lead to a driver call (more precisely, for each driver method call s…
54 * Wherever the specification guarantees parameters that satisfy certain preconditions, check these …
55 …on can take parameters that are invalid and must not reach the driver, call the API function with …
56 * Check that the expected inputs reach the driver. This may be implicit in a test that checks the o…
60 For each API function that leads to a driver call, call it with parameters that cause a driver to b…
65 * Unexpected errors. At least test that if the driver returns `PSA_ERROR_GENERIC_ERROR`, this is pr…
70 * Check that the storage ends up in the expected state. At least make sure that no intermediate fil…
76 * Test that keys in a secure element survive `psa_close_key(); psa_open_key()`.
77 * Test that keys in a secure element survive `mbedtls_psa_crypto_free(); psa_crypto_init()`.
78 * Test that the driver's persistent data survives `mbedtls_psa_crypto_free(); psa_crypto_init()`.
79 * Test that `psa_destroy_key()` does not leave any trace of the key.
85 …rypto_free(); psa_crypto_init()` at that point and check that this either rolls back or completes …
87 * This must be done for each possible flow, including error cases (e.g. a key creation that fails m…
89 * Two things need to be tested: the key that is being created or destroyed, and the driver's persis…
90 …that the storage has the expected content (this can be done by e.g. using a key that is supposed t…
98 We must have at least one driver that is close to real-world conditions:
109 We should have at least one driver that covers the whole interface:
125 …rations, …) must be exercised in at least one build. The test must verify that the driver code is …
129 The driver interface includes a fallback mechanism so that a driver can reject a request at runtime…