Use SignedCsrPayload validator in omecypto provisioning tests
To ensure the ref impl of OEMCrypto_GetDeviceSignedCsrPayload() in OPK and testbed returns the correct sample format. Test: opk_ta_p40, run_fake_l1_tests Bug: 300304834 Change-Id: I6d399774fbaac2e12096cf878d582cd3c1320318
This commit is contained in:
@@ -9,6 +9,7 @@
|
||||
#include "device_info_validator.h"
|
||||
#include "log.h"
|
||||
#include "platform.h"
|
||||
#include "signed_csr_payload_validator.h"
|
||||
#include "test_sleep.h"
|
||||
|
||||
namespace wvoec {
|
||||
@@ -406,6 +407,10 @@ TEST_F(OEMCryptoProv40Test, GetDeviceSignedCsrPayloadAPI18) {
|
||||
&signed_csr_payload_length),
|
||||
OEMCrypto_SUCCESS);
|
||||
EXPECT_NE(signed_csr_payload_length, 0uL);
|
||||
util::SignedCsrPayloadValidator validator;
|
||||
EXPECT_EQ(util::CborMessageStatus::kCborParseOk,
|
||||
validator.Parse(signed_csr_payload));
|
||||
EXPECT_EQ(util::CborMessageStatus::kCborValidateOk, validator.Validate());
|
||||
}
|
||||
|
||||
TEST_F(OEMCryptoProv40Test, GetDeviceSignedCsrPayloadInvalid) {
|
||||
|
||||
Reference in New Issue
Block a user