1Test Suites
2###########
3
4TF-M includes two sets of test suites:
5
6* tf-m-tests - Standard TF-M specific regression tests
7* psa-arch-tests - Test suites for specific PSA APIs (secure storage, etc.)
8
9These test suites can be run from Zephyr via an appropriate sample application
10in the samples/tfm_integration folder.
11
12TF-M Regression Tests
13*********************
14
15The regression test suite can be run via the :ref:`tfm_regression_test` sample.
16
17This sample tests various services and communication mechanisms across the
18NS/S boundary via the PSA APIs. They provide a useful sanity check for proper
19integration between the NS RTOS (Zephyr in this case) and the secure
20application (TF-M).
21
22PSA Arch Tests
23**************
24
25The PSA Arch Test suite, available via :ref:`tfm_psa_test`, contains a number of
26test suites that can be used to validate that PSA API specifications are
27being followed by the secure application, TF-M being an implementation of
28the Platform Security Architecture (PSA).
29
30Only one of these suites can be run at a time, with the available test suites
31described via ``CONFIG_TFM_PSA_TEST_*`` KConfig flags:
32
33Purpose
34*******
35
36The output of these test suites is required to obtain PSA Certification for
37your specific board, RTOS (Zephyr here), and PSA implementation (TF-M in this
38case).
39
40They also provide a useful test case to validate any PRs that make meaningful
41changes to TF-M, such as enabling a new TF-M board target, or making changes
42to the core TF-M module(s). They should generally be run as a coherence check
43before publishing a new PR for new board support, etc.
44