1. Requirements traceability

Our infrastructure automatically tracks the traceability between requirements and tests, and the report is available as part of the documentation package. The report must show full coverage: when it is not possible to test a requirement on a target, an exception will be listed on this page.

Note that the reporting tool only considers tests that were actually executed as part of the test results. Ignored tests are not considered when determining the traceability.

1.1. Exceptions

Some requirements are marked as not covered in the traceability report linked above:

ID

Targets

Reasoning

fls_2d6bqnpy6tvs

Armv8-A bare-metal (aarch64-unknown-none)

Procedural macros are only available on host platforms, while this is a cross-compilation target

fls_4vjbkm4ceymk

Armv8-A bare-metal (aarch64-unknown-none)

Procedural macros are only available on host platforms, while this is a cross-compilation target