Here's the original proposal:

The TF-A project uses the OpenCI project https://www.trustedfirmware.org/projects/open-ci/ to provide "Daily" and "Gerrit patch review" testing through a Jenkins infrastructure system with jobs visible here https://ci.trustedfirmware.org and these make use of tests defined in the TF-A Tests repository and from other reposititories. Please refer to the OpenCI documentation for more information https://tf-ci-users-guide.readthedocs.io/en/latest/

Cipher/MAC single-shot APIs patches:

ACS can be updated to skip checks for this. But spec isn't specific about whether this way of retrieving memory is optional.

Hash: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/10544
MAC: Support in mbedtls-2.26.0 for the single-shot APIs is not present. I have a patch to enable the tests and the shim layer in TF-M, I will keep it private until support from the backend side is available somehow for the feature-cc-psa-crypto-drivers dev branch.
Cipher: Support in mbedtls-2.26.0 for the single-shot APIs is not present. I have a patch to enable the tests and the shim layer in TF-M, I will keep it private until support from the backend side is available somehow for the feature-cc-psa-crypto-drivers dev branch.
AEAD: Single-shot APIs for AEAD are already supported, multipart is missing (both in TF-M and in the backend and driver entry points, still pending review in mbedTLS)
No Key agreement single shot API test yet. Need to understand and add it.

This patch extends tests coverate in the TF-M regression test suite for the single-shot hash API.

Prototypes derived from: https://github.com/ARMmbed/mbedtls/blob/development/library/psa_crypto_driver_wrappers.h

Prototypes derived from: https://github.com/ARMmbed/mbedtls/pull/4338/

Prototypes derived from: https://github.com/ARMmbed/mbedtls/blob/development/library/psa_crypto_driver_wrappers.h

These prototypes are available upstream either in https://github.com/ARMmbed/mbedtls/blob/development/library/psa_crypto_driver_wrappers.h or as a Pull Request: https://github.com/ARMmbed/mbedtls/pull/4338/

I think you could start from the single-shot AEAD APIs because it's the only single shot API that I am sure we test 100% in the TF-M regression tests.

Due to a bug recently discovered in Qemu, we should mention in the docs that minimum required version is 6.1 (to be released around mid-end of August)

There is also an hash_clone entry point which is not currently documented in the spec draft but is present as a call in the core layer.