Skip to content

Conversation

@gilles-peskine-arm
Copy link
Collaborator

I wrote a test strategy document describing what I think we should test about the secure element driver interface (the Mbed Crypto code — this is not about how to test drivers).

@gilles-peskine-arm gilles-peskine-arm added enhancement New feature or request needs: review The pull request is ready for review. This generally means that it has no known issues. writing Documentation wording and formatting labels Sep 4, 2019

* Wherever the specification guarantees parameters that satisfy certain preconditions, check these preconditions whenever practical.
* If the API function can take parameters that are invalid and must not reach the driver, call the API function with such parameters and verify that the driver method is not called.
* Check that the expect inputs reach the driver. This may be implicit in a test that checks the outputs if the only realistic way to obtain the correct outputs is to start from the expected inputs (as is often the case for cryptographic material, but not for metadata).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/expect/expected

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I amended the last commit.

@Patater
Copy link
Contributor

Patater commented Sep 5, 2019

LGTM other than one nit

@Patater Patater requested a review from dgreen-arm September 5, 2019 17:36
@gilles-peskine-arm gilles-peskine-arm force-pushed the psa-se_driver-interface_test_strategy branch from 5b1d027 to 8b193c1 Compare September 5, 2019 17:37
Patater
Patater previously approved these changes Sep 5, 2019
Copy link
Contributor

@dgreen-arm dgreen-arm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Patater Patater merged commit 3f20efc into ARMmbed:development Sep 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request needs: review The pull request is ready for review. This generally means that it has no known issues. writing Documentation wording and formatting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants