The expected test result summary should be this:
Crypto Suite Report **
TOTAL TESTS : 61
TOTAL PASSED : 39
TOTAL SIM ERROR : 0
TOTAL FAILED : 21
TOTAL SKIPPED : 1
But the test result summary is:
Crypto Suite Report **
TOTAL TESTS : 61
TOTAL PASSED : 37
TOTAL SIM ERROR : 0
TOTAL FAILED : 23
TOTAL SKIPPED : 1
Test environment is:
ConfigPsaApiTest, ARMCLANG & GNUARM, Minsizerel, musca_b1_OTP.
ConfigPsaApiTestIPC & ConfigPsaApiTestIPCTfmLevel2, ARMCLANG, Minsizerel, musca_b1_OTP.
Update from Tamas
"
The two extra failing test case (TEST 241 and TEST 242) is the same which was failing in case of RC3. It's a known limitations of the CC312 crypto library: MD hashing is not supported.
Logs from TF-Mv1.0-RC3 test with enabled CC312 on Musca-B1:
TEST: 241 | DESCRIPTION: Testing crypto asymmetric APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_asymmetric_sign - RSA KEYPAIR PKCS1V15 RAW
DVIR: ERROR: MBEDTLS_MD_NONE is not supported!
Failed at Checkpoint: 6
Actual: -135
Expected: 0
TEST RESULT: FAILED (Error Code=0x1)
TEST: 242 | DESCRIPTION: Testing crypto asymmetric APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_asymmetric_verify - RSA KEYPAIR PKCS1V15 RAW
Failed at Checkpoint: 6
Actual: -135
Expected: 0
TEST RESULT: FAILED (Error Code=0x1)
Logs from TF-Mv1.0 test with enabled CC312 on Musca-B1:
TEST: 241 | DESCRIPTION: Testing crypto asymmetric APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_asymmetric_sign - RSA KEY_PAIR PKCS1V15 RAW
DVIR: ERROR: MBEDTLS_MD_NONE is not supported!
Failed at Checkpoint: 4
Actual: -135
Expected: 0
TEST RESULT: FAILED (Error Code=0x00000001)
TEST: 242 | DESCRIPTION: Testing crypto asymmetric APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_asymmetric_verify - RSA KEY_PAIR PKCS1V15 RAW
Failed at Checkpoint: 4
Actual: -135
Expected: 0
TEST RESULT: FAILED (Error Code=0x00000001)
"
Known limitation of CC312 crypto library. It does not require any further investigation.
Frustration never felt so good! I die. A lot. But every death fuels my determination to conquer that next obstacle. Geometry Dash World is a masterclass in rewarding challenge, and the MOD takes the sting out of starting over.
Test discrepancies are concerning and it is crucial to address the observed deviations between expected and actual results. Investigating the root cause and re executing the failed tests might help in achieving the expected outcome.
Professional Home Extension Services in Boisbriand Quebec
The discrepancy in the Crypto Suite Report test results, where the expected "TOTAL PASSED" is 39 but the actual result is 37, and "TOTAL FAILED" is 23 instead of the expected 21, indicates a potential issue in the test environment or configuration. Factors such as test dependencies, incorrect setup, or unexpected behavior in configurations like ConfigPsaApiTest, ARMCLANG & GNUARM, Minsizerel, and musca_b1_OTP could be contributing to the mismatch. Verifying the test cases and environment settings is essential to identify the cause. Just as R2parking ensures a smooth and precise parking registration process by eliminating errors through streamlined management, addressing these discrepancies in testing will help maintain the accuracy and reliability of the system.