PSA Compliance (ITS and STORAGE) and Regression test suite runs storage
tests with the different combination of parameters which produces
unpredictable behavior results.
This is mainly because of the following:
PSA Compliance uses 2 WRITE_ONCE_UID with different size/data/flags
Regression use a WRITE_ONCE_UID with different size/data/flags
So if, Regression was executed first then PSA compliance
(ITS and STORAGE) test suite would fail and vice-versa.
The way to work around this problem is to erase ITS storage before we
run any test suite, but that introduces wearing out flash storage.
Therefore it is necessary to document the flow of execution to avoid
unpredictable behavior by the following steps:
Run Regression test
Run PSA Compliance test suites
The compare logs for ARM_MUSCA_B1 target have been updated to
account for storage-related failure which is bound to happen following
this flow.
Documentation is updated to reflect these changes.
PSA Compliance (ITS and STORAGE) and Regression test suite runs storage tests with the different combination of parameters which produces unpredictable behavior results.
This is mainly because of the following:
So if, Regression was executed first then PSA compliance (ITS and STORAGE) test suite would fail and vice-versa. The way to work around this problem is to erase ITS storage before we run any test suite, but that introduces wearing out flash storage.
Therefore it is necessary to document the flow of execution to avoid unpredictable behavior by the following steps:
ARM_MUSCA_B1target have been updated to account for storage-related failure which is bound to happen following this flow.Documentation is updated to reflect these changes.
Fixes #43