Test the driver dispatch layer #699

New issue

Open

opened 2026-02-25 10:03:33 -06:00 by gilles-peskine-arm · 0 comments

gilles-peskine-arm commented

2026-02-25 10:03:33 -06:00

(Migrated from github.com)

The goal of this issue is to add testing at the driver dispatch layer. This will be done in several steps, and we don't need to have a full plan ready before we can start executing the parts that we already know about.

The full plan should include:

Testing with good data for all supported mechanisms. Ideally the test cases should be generated automatically so that coverage of new algorithms is automatic, and ideally coverage of new functions as well.
Testing of errors that drivers are supposed to catch. This isn't settled yet. (Note that errors that the core is supposed to catch should not be tested here.)
Both transparent and opaque drivers.
Negative testing for when dispatch itself is supposed to fail. (Excluding cases that the core is supposed to handle, such as a bad operation state.)

PSA is standardizing the driver dispatch layer. We semi-officially allow third-party drivers to call the dispatch layer (only semi-officially for now, in that we do it ourselves and we know that some people do it, but we also know that the interface isn't stable yet). The goal of this issue is to add testing at the driver dispatch layer. This will be done in several steps, and we don't need to have a full plan ready before we can start executing the parts that we already know about. The full plan should include: * Testing with good data for all supported mechanisms. Ideally the test cases should be generated automatically so that coverage of new algorithms is automatic, and ideally coverage of new functions as well. * Testing of errors that drivers are supposed to catch. [This isn't settled yet](https://github.com/ARM-software/psa-api/issues/332). (Note that errors that the core is supposed to catch should not be tested here.) * Both transparent and opaque drivers. * Negative testing for when dispatch itself is supposed to fail. (Excluding cases that the core is supposed to handle, such as a bad operation state.)

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-Mbed-TLS/TF-PSA-Crypto#699

No description provided.

Rows
Columns