2385f71abd
mbedtls_test_fail does not copy the failure explanation string, so passing a string on the stack doesn't work. This fixes a garbage message that would appear if a test triggered a non-implemented code path. More generally, just use TEST_ASSERT instead of explicitly calling mbedtls_test_fail, since we aren't playing any tricks with the error location. Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> |
||
---|---|---|
.. | ||
drivers | ||
asn1_helpers.c | ||
fake_external_rng_for_test.c | ||
helpers.c | ||
psa_crypto_helpers.c | ||
psa_exercise_key.c | ||
random.c | ||
threading_helpers.c |