[cts9.0r1]CtsGraphicsTestCases 包四条case fail

[DESCRIPTION]
CtsGraphicsTestCases
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionByteArray
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionInputStream
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionInputStreamInBitmap
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionStringAndFileDescriptor

fail log如下
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionByteArray fail java.lang.AssertionError: MSE too large for normal case: 3.0239105224609375
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionInputStream fail java.lang.AssertionError: MSE too large for normal case: 3.0239105224609375
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionInputStreamInBitmap fail java.lang.AssertionError: MSE too large for normal case: 3.0239105224609375
android.graphics.cts.BitmapRegionDecoderTest#testDecodeRegionStringAndFileDescriptor fail java.lang.AssertionError: MSE too large for normal case: 3.18511962890625

[SOLUTION]

继续阅读“[cts9.0r1]CtsGraphicsTestCases 包四条case fail”

【CTS_All version】android.bluetooth.cts.BluetoothLeScanTest#testBasicBleScan fail

[DESCRIPTION]

android.bluetooth.cts.BluetoothLeScanTest

— testBasicBleScan

–testBatchScan

— testOpportunisticScan

— testScanFilter

一、Fail信息如下:

fail junit.framework.AssertionFailedError: Scan results shouldn’t be empty at junit.framework.Assert.fail(Assert.java:50)

二、Fail信息如下:
fail junit.framework.AssertionFailedError: Scan results shouldn’t be empty at junit.framework.Assert.fail(Assert.java:50)
[SOLUTION]

继续阅读“【CTS_All version】android.bluetooth.cts.BluetoothLeScanTest#testBasicBleScan fail”

【STS】 run sts-engbuild 测试到一半,发生DeviceNotFound,及Deviceoffline,无法继续跑

[DESCRIPTION]

报错讯息:
10-08 18:02:33 I/FailureListener: FailureListener.testFailed android.security.cts.Poc16_09#testPocCVE_2016_2471 false false false
10-08 18:02:33 D/ModuleListener: ModuleListener.testEnded(android.security.cts.Poc16_09#testPocCVE_2016_2471, {})
10-08 18:02:33 D/ModuleListener: ModuleListener.testRunFailed(Could not find device LCEAA000842E6EGC)
10-08 18:02:33 I/ConsoleReporter: [LCEAA000842E6EGC] Could not find device LCEAA000842E6EGC
10-08 18:02:33 D/JarHostTest: HostTestListener.testRunEnded(187806, {})
10-08 18:02:33 W/TestInvocation: Invocation did not complete due to device LCEAA000842E6EGC becoming not available. Reason: Could not find device LCEAA000842E6EGC
10-08 18:02:33 W/ResultReporter: Invocation failed: com.android.tradefed.device.DeviceNotAvailableException: Could not find device LCEAA000842E6EGC

[SOLUTION]

继续阅读“【STS】 run sts-engbuild 测试到一半,发生DeviceNotFound,及Deviceoffline,无法继续跑”

cts8.1_r8.:android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields fail

[DESCRIPTION]
 CtsShortcutManagerTestCases
android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields
FAIL: junit.framework.AssertionFailedError: Expected exception type was java.lang.IllegalArgumentException but caught java.lang.SecurityException: Shortcut package name mismatch (message=)
[SOLUTION]

继续阅读“cts8.1_r8.:android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields fail”

[CTS 8.0_R12] arm64-v8a CtsAppTestCases – android.app.cts.ActionBarTest#testOptionsMenuKey

[DESCRIPTION]

arm64-v8a CtsAppTestCases
android.app.cts.ActionBarTest#testOptionsMenuKey

fail
junit.framework.AssertionFailedError

[SOLUTION]

继续阅读“[CTS 8.0_R12] arm64-v8a CtsAppTestCases – android.app.cts.ActionBarTest#testOptionsMenuKey”

android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields fail

[DESCRIPTION]
android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields 失败。

unit.framework.AssertionFailedError: Expected exception type was java.lang.IllegalArgumentException but caught java.lang.SecurityException: Shortcut package name mismatch (message=)
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at com.android.server.pm.shortcutmanagertest.ShortcutManagerTestUtils.assertExpectException(ShortcutManagerTestUtils.java:427)
at com.android.server.pm.shortcutmanagertest.ShortcutManagerTestUtils.assertExpectException(ShortcutManagerTestUtils.java:408)

[SOLUTION]

继续阅读“android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields fail”

android.keystore.cts.KeyChainTest#testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported fail

[DESCRIPTION]
 android.keystore.cts.KeyChainTest#testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported fail
unit.framework.AssertionFailedError: RSA must be hardware-backed by a hardware-specific Keymaster HAL at junit.framework.Assert.fail(Assert.java:50) at junit.framework.Assert.assertTrue(Assert.java:20) at android.keystore.cts.KeyChainTest.testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported(KeyChainTest.java:76) at java.lang.reflect.Method.invoke(Native Method) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) at junit.framework.TestResult$1.protect(TestResult.java:115) at android.support.test.internal.runner.junit3.AndroidTestResult.runProtected(AndroidTestResult.java:77) at junit.framework.TestResult.run(TestResult.java:118) at android.support.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:55) at junit.framework.TestCase.run(TestCase.java:124) at android.support.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:63) at
[SOLUTION]

继续阅读“android.keystore.cts.KeyChainTest#testIsBoundKeyAlgorithm_RequiredAlgorithmsSupported fail”

android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields

[DESCRIPTION]
android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields 失败。

junit.framework.AssertionFailedError: Expected exception type was java.lang.IllegalArgumentException but caught java.lang.SecurityException: Shortcut package name mismatch (message=)
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at com.android.server.pm.shortcutmanagertest.ShortcutManagerTestUtils.assertExpectException(ShortcutManagerTestUtils.java:427)
at com.android.server.pm.shortcutmanagertest.ShortcutManagerTestUtils.assertExpectException(ShortcutManagerTestUtils.java:408)
at android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest.testShortcutInfoMissingMandatoryFields(ShortcutManagerClientApiTest.java:132)
at java.lang.reflect.Method.invoke(Native Method)
at android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:220)
at android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:205)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:115)

[SOLUTION]

继续阅读“android.content.pm.cts.shortcutmanager.ShortcutManagerClientApiTest#testShortcutInfoMissingMandatoryFields”

The October releases CTS for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are released and Test suites required-use date updated

The October releases of the Android Compatibility Test Suite (CTS) for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are released on the AOSP website; see the android-partners announcement for more details.

These releases also contain continuous improvements of tests and test infrastructure and verify security patches up to September 2018 Public Security Bulletin.

These versions will be required for GMS approvals as shown in the table below:

继续阅读“The October releases CTS for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are released and Test suites required-use date updated”

CTS 9.0 R2 and CTS September releases are available

The CTS September releases for Android 9.0, 8.1, 8.0, 7.1, 7.0 and 6.0 are available on the Compatibility Test Suite Downloads page. The releases for Android 8.1, 8.0, 7.1, 7.0 and 6.0 also contain continuous improvements of tests and test infrastructure, and verify security patches up to the August 2018 Public Security Bulletin.  

Details are available in the following change lists:

继续阅读“CTS 9.0 R2 and CTS September releases are available”

[8.1R7] [CTSV] USB Audio Peripheral Attributes Test

[DESCRIPTION]
 Google 从[8.1R7] 开始需要用新的设备测试USB Audio Peripheral Attributes Test

其中三条用到的设备如下:具体测试步骤请参考:

https://source.android.com/compatibility/cts/usb-audio

继续阅读“[8.1R7] [CTSV] USB Audio Peripheral Attributes Test”