Also, pull in the static libs associated with the graphics HALs to
VtsHalSensorsTargetTestUtils so that the VTS binaries that depend on it
don't need to all pull them in themselves.
Fixes: 158018963
Test: VtsHalSensorsV2_0TargetTest on a device supporting the v4.0 HALs
Change-Id: Idc47ffb8cacd1ac84d45b979cd45fe630b6808f6
These updates are based on input/experiences implementing this
HAL. There are no API changes.
- Specify that the validity for credentialKey certificate shall be
from current time and expire at the same time as the attestation
batch certificate.
- Require challenge passed to getAttestationCertificate() is
non-empty.
- Fix bug in VTS tests where the startPersonlization() result was not
checked.
- Remove verifyStartPersonalizationZero test since it cannot be
completed.
- Ensure secureUserId is non-zero if user authentication is needed.
- Specify format for signingKeyBlob in generateSigningKeyPair() same
way we do for credentialData in finishAddingEntries().
- Modify EndToEndTest to decrypt/unpack credentialData to obtain
credentialPrivKey and storageKey and do cross-checks on these.
- Modify EndToEndTest to decrypt/unpack signingKeyBlob to obtain
signingKeyPriv and check it matches the public key in the returned
certificate.
- Add new VTS tests for user and reader authentication.
- Relax unnecessary requirements about SessionTranscript structure -
just require it has X and Y of the ephemeral key created earlier.
- Allow calls in VTS tests to v2 HAL to fail - this should allow
these VTS tests to pass on a compliant v1 HAL.
Bug: 156911917
Bug: 158107945
Test: atest VtsHalIdentityTargetTest
Test: atest android.security.identity.cts
Change-Id: I11b79dbd57b1830609c70301fea9c99f9e5080cb
The current number of iterations is too high and results in a timeout
from the testing framework.
The goal of the test is to make sure that the generated challenges are
different on every run. It's impossible to test whether any two
challenges will ever be the same for any number of iterations. Hence,
since a 1000 iterations doesn't provide much more value over 10
iterations, 10 was chosen because of its better performance.
Bug: 155844206
Test: "atest VtsHalBiometricsFingerprintV2_1TargetTest" on a blueline
Change-Id: I5db887bdcfed8fb0e44fcedcf9e99dd185d395c3
Add checks that all returned output dimensions must be at
least as fully specified as the union of the information about the
corresponding operand in the model and in the request.
Bug: 154054474
Test: VTS
Change-Id: I934d084c7665160a98da9828604ce8297fef73b8
Merged-In: I934d084c7665160a98da9828604ce8297fef73b8
(cherry picked from commit d454751e00)
am skip reason: Change-Id I752b44f5cc20d85bf819188ccaaf0813a5607ba5 with SHA-1 08c7e71236 is in history
Original change: undetermined
Change-Id: I4d28a2a9cb0cb34a42601c7e54857033a6159025
Bug: 152932559
Test: Boot and observe that Strongbox gets the message
Merged-In: I752b44f5cc20d85bf819188ccaaf0813a5607ba5
Change-Id: I752b44f5cc20d85bf819188ccaaf0813a5607ba5
Bug: 156749607
Test: fake mark a camera id as a secure only, see that it doesn't get
tested unless a test calls getCameraDeviceNames with addSecure = true
Test: VtsHalCameraProviderV2_4TargetTest passes on device without any secure only
cameras
Change-Id: Ibe428b663bd8024f46f0273ed5dfaa108a90dd43
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
Note that this test also includes MediaCasService openSession test
to pass the session id as the key token to the IDescrambler
Test: atest VtsHalTvTunerV1_0TargetTest
Bug: 150987138
Change-Id: Iacd4ad5fcd957a6e3bb4a5730337ecaa3adc0aa2
The test doesn't need framework. It seems that the test can be flaky
when framework was stop/started earlier.
Bug: 154445273
Test: atest -a VtsHalBluetoothV1_0TargetTest \
VtsHalSapV1_0TargetTest \
VtsHalAudioV4_0TargetTest
Change-Id: I60f62923cfb826c5e33e9885ea08efdbe4c8f57e
am skip reason: Change-Id Ibe770e6eaf0b0018d60876926d824204e4eaf732 with SHA-1 cab019aae5 is in history
Change-Id: Icda771e7c01bd1bc2543ffb7e03ac76aaaa9f78f
am skip reason: Change-Id Ibe770e6eaf0b0018d60876926d824204e4eaf732 with SHA-1 cab019aae5 is in history
Change-Id: Ie01a0cb16b925f6224c0c0d5268ee7d366c3038c
VTS was running on a userdebug build GSI before Android 10.
Starting from Android 10, VTS is switched to running on top of a
user build GSI image, plus the device-specific boot-debug.img to
allow adb root.
https://source.android.com/compatibility/vts/vts-on-gsi
So 'ro.build.type' will be 'user' because the value comes from
/system/build.prop. Switching to using 'ro.debuggable' to decide
whether we should check the device is locked or not. Note that
'ro.debuggable' will be '1' for userdebug/eng images or when a
boot-debug.img is used.
Bug: 154449286
Test: atest VtsHalKeymasterV4_0TargetTest
Change-Id: If5a90d62f77489aa58f96e908553a052cf6d1e18
am skip reason: Change-Id I7d05413a9ec70225ce419079f3cc9daf026cf744 with SHA-1 a8ed82cbb4 is in history
Change-Id: I8d11d00557c47311495895b6ae889225b48c8c84
sendRefreshFrame is used to send refresh frame to composer, so even
composition changes should present frame to composer.
Bug: 157638511
Test: VtsHalGraphicsComposerV2_4TargetTest on C2, R3
Change-Id: I325668b7a75cbbe72841c424eb9fc43479ac48b6
am skip reason: Change-Id I72f4bf1f09d6271ac6367abc3972ee7747b18155 with SHA-1 15570c4681 is in history
Change-Id: I7b3f578bd2e5083da9390f995b5e4daa32176172
