CTS February releases are available

CTS February releases are available

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

For partners in China, the CTS packages can be downloaded from https://source.android.google.cn/ without using VPN for better reliability.

The details and delta from last release can be found in the following change lists:

继续阅读“CTS February releases are available”

【cts_P】CtsLibcoreTestCases libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight

问题描述


run cts -m CtsLibcoreTestCases -t libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight -o
 01-07 16:35:46 I/ModuleListener: [1/1] libcore.libcore.icu.DateIntervalFormatTest#testEndAtMidnight fail:
junit.framework.ComparisonFailure: expected:<February 27, []04:00 – 00:00> but was:<February 27, [2018, ]04:00 – 00:00>
at junit.framework.Assert.assertEquals(Assert.java:85)
at junit.framework.Assert.assertEquals(Assert.java:91)
at libcore.libcore.icu.DateIntervalFormatTest.testEndAtMidnight(DateIntervalFormatTest.java:442)
at java.lang.reflect.Method.invoke(Native Method)

 

设置Google Assistant 为默认的Assistant

问题描述


1.需求来源:
从2018年10月29日起,所有欧盟项目必须将Google设为默认的Assist应用, 对于非欧盟项目,运行Android 8.0或者更高版本的项目不管是初始送测版本还是维护版本,都需要将Google设为默认的Assist应用,具体执行的时间请看如下表格:

[CTS 8.1][VtsHalMediaOmxV1_0Host]FAIL 信息与OMX.MTK.AUDIO.DECODER.WMA_audio_decoder相关

问题描述


 CTS 和VTS mediatek相关测试,如果测试项目包含.OMX.MTK.AUDIO.DECODER.WMA_audio_decoder.wma相关信息引起的fail,
一般是由于客户没有拿到wma的licence,缺少相关的库而导致的失败;

 

解决方案

继续阅读“[CTS 8.1][VtsHalMediaOmxV1_0Host]FAIL 信息与OMX.MTK.AUDIO.DECODER.WMA_audio_decoder相关”

Android 9.0, 8.1, 8.0, 7.1, and 7.0 12月份CTS测试工具下载更新

  • December releases of the Android Compatibility Test Suite (CTS) for Android 9.0, 8.1, 8.0, 7.1, and 7.0 are released, please see the android-partners announcement for more details. These releases contain continuous improvements of tests (a.k.a. waiver patches) and test infrastructure, and verify security patches up to November 2018 Public Security Bulletin.

继续阅读“Android 9.0, 8.1, 8.0, 7.1, and 7.0 12月份CTS测试工具下载更新”

CTS/GTS 问题分析11 | weiinter105

gts case是不放出源码的,这很不方便我们进行问题的分析,如果测试是apk,我们可以通过修改smali重新编译的方式赋值我们分析,那么,如果测试文件是一个jar包,那么应该如何处理呢?以本文为例记录分析方法

问题初探

测试命令:

run gts -m GtsUnofficialApisUsageTestCases -t com.android.gts.api.UnofficialApisUsageTest#testNonApiReferences

继续阅读“CTS/GTS 问题分析11 | weiinter105”

CTS问题分析4拓展-无法抓取tombstone的原因 | weiinter105

前面说到,在bionic/linker客户端以及system/core/dubuggerd服务端之间都加了相关的SIGSYS信号量处理,但还是抓不出tombstone,现查看原因。

先说结论:由于设置了信号处理函数导致的问题

继续阅读“CTS问题分析4拓展-无法抓取tombstone的原因 | weiinter105”

CTS/GTS问题分析6 | weiinter105

遇到一个Android P相关的问题,和原来CTS/GTS 问题分析1的表现是一样的,但是将http://gerrit.pt.miui.com/#/c/387000/这个修复cp过来,发现不生效,仍然报错,因此记录一下

问题初探

测试命令: run gts -m GtsGmscoreHostTestCases -t com.google.android.gts.devicepolicy.managedprovisioning.DeviceOwnerProvisioningHostsideTest#testRequiredAppsInManagedDevice

报错堆栈:

继续阅读“CTS/GTS问题分析6 | weiinter105”

CTS/GTS问题分析5 | weiinter105

问题初探

测试命令:

run cts -m CtsDevicePolicyManagerTestCases -t com.android.cts.devicepolicy.MixedManagedProfileOwnerTestApi25#testResetPasswordFbe

错误有两种情况,一种是直接进入系统桌面,一种是起一个测试case中的空白activity,经过分析,两者都是同一个原因造成的。因此以任一种情况举例。报错堆栈如下:

继续阅读“CTS/GTS问题分析5 | weiinter105”

CTS/GTS问题分析4 | weiinter105

问题初探

测试命令:
run cts -m CtsOsTestCases -t android.os.cts.SeccompTest#testIsolatedServicePolicy

报错堆栈:
07-24 00:50:08.627 2633 4112 I ActivityManager: Process android.os.cts (pid 13402) has died: vis SF
07-24 00:50:08.627 2022 2022 I Zygote : Process 13402 exited due to signal (31)
07-24 00:50:08.627 13379 13399 I TestRunner: failed: testIsolatedServicePolicy(android.os.cts.SeccompTest)

继续阅读“CTS/GTS问题分析4 | weiinter105”

CTS/GTS问题分析3 | weiinter105

android.security.cts.ListeningPortsTest#testNoListeningLoopbackTcp6Ports
android.security.cts.ListeningPortsTest#testNoListeningLoopbackUdp6Ports
android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports

问题分析

本地测了一下,前两条没问题,那么下面重点先说下第三条的分析流程:

测试命令: run sts-userbuild -m CtsSecurityTestCases -t android.security.cts.ListeningPortsTest#testNoRemotelyAccessibleListeningUdp6Ports

测试结果:

继续阅读“CTS/GTS问题分析3 | weiinter105”

CTS/GTS问题分析2 | weiinter105

问题初探

测试命令: run gts-suite -s ID -o -m GtsGmscoreHostTestCases -t com.google.android.gts.devicepolicy.managedprovisioning.DeviceOwnerProvisioningHostsideTest#testRequiredAppsInManagedProfileForManagedDevice

报错堆栈:
07-27 06:59:30.611 32075 32125 I SilentProvisioningTest: managedProfileProvisionedReceiver.awaitForBroadcast(): failed
07-27 06:59:30.612 2091 2129 D ContactsDatabaseHelper: insertMimeType: vnd.android.cursor.item/website

继续阅读“CTS/GTS问题分析2 | weiinter105”