GTS 中testForBlacklistedApps fail 详解

来源：

https://blog.csdn.net/shift_wwx/article/details/81565909

GTS 在测试case armeabi-v7a GtsAppBlacklistDeviceTestCases 的时候出现下面异常，本文总结一下。

com.google.android.appblacklist.gts.GtsAppBlacklistDeviceTest#testForBlacklistedApps

测试的host log 如下：

junit.framework.AssertionFailedError: Packages with a blacklisted signature:
com.android.providers.telephony
com.android.providers.media
com.android.wallpapercropper
com.android.documentsui...
...com.android.certinstaller
android
com.android.contacts...
...com.android.phoneat junit.framework.Assert.fail(Assert.java:50)at junit.framework.Assert.assertTrue(Assert.java:20)at com.google.android.appblacklist.gts.GtsAppBlacklistDeviceTest.checkContainsBlacklistedCerts(GtsAppBlacklistDeviceTest.java:153)at com.google.android.appblacklist.gts.GtsAppBlacklistDeviceTest.testForBlacklistedApps(GtsAppBlacklistDeviceTest.java:212)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)at android.support.test.internal.runner.junit3.AndroidTestResult.runProtected(AndroidTestResult.java:73)at junit.framework.TestResult.run(TestResult.java:118)at android.support.test.internal.runner.junit3.AndroidTestResult.run(AndroidTestResult.java:51)at junit.framework.TestCase.run(TestCase.java:124)at android.support.test.internal.runner.junit3.NonLeakyTestSuite$NonLeakyTest.run(NonLeakyTestSuite.java:62)at android.support.test.internal.runner.junit3.AndroidTestSuite$2.run(AndroidTestSuite.java:101)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:457)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)at java.lang.Thread.run(Thread.java:764)

会列出很多的包不满足要求，从log 看应该是这些包都属于黑名单中的一员。

来看下GTS 的source code：

    public void testForBlacklistedApps() throws IOException, XmlPullParserException, NameNotFoundException {List<PackageInfo> packageInfos = getAllPackages();DynamicConfigDeviceSide dcds = new DynamicConfigDeviceSide(MODULE_NAME);checkContainsBlacklistedCerts(packageInfos, dcds.getValues("cert_digests"));checkContainsBlacklistedPackageNames(packageInfos, dcds.getValues("package_names"));checkContainsBlacklistedAppDigests(packageInfos, dcds.getValues("app_digests"));}

本文不去详细解释code，大概梳理一下：

1、DynamicConfigDeviceSide 为了解析GTS 中一些配置文件，一般都是以dynamic 结尾的文件，例如：

<dynamicConfig><entry key="package_names"><value>com.android.tools.callassistant</value><value>com.android.tools.hfmsrv</value><value>com.android.tools.srv</value></entry><entry key="app_digests"><value>28f04c37f5c8f91e015328cf55dec5a3be053ca41f1dd98f4cb3a857bebd172f</value></entry><entry key="cert_digests"><value>c891f9eb64179e0c8919dd79f230770a5c2dc1dbcada4747f7b82c54b842a9ec</value></entry>
</dynamicConfig>

2、从log看，这里应该是checkContainsBlacklistedCerts() 出了fail

    private void checkContainsBlacklistedCerts(List<PackageInfo> packageInfos, List<String> blacklistedCerts) throws IOException, XmlPullParserException, NameNotFoundException {if (!blacklistedCerts.isEmpty()) {List<String> blacklistedInstalledPackages = new ArrayList();for (PackageInfo packageInfo : packageInfos) {String packageName = packageInfo.packageName;if (blacklistedCerts.contains(computePackageCertDigest(packageInfo.signatures[0]))) {blacklistedInstalledPackages.add(packageName);}}assertTrue(String.format("Packages with a blacklisted signature:\n%s", new Object[]{TextUtils.join("\n", blacklistedInstalledPackages)}), blacklistedInstalledPackages.isEmpty());}}

code 比较清晰，每个package 中的signature 经过compute 之后，确认是否是dynamic 文件中规定的属于黑名单，如果是，那就会assert失败。

结论：

这个case 是因为package 的签名是默认签名，也就是dynamic 里面规定的 cert_digests 的value，导致了assert fail。

GTS 要求系统必须要签名，但key 不能是Default key。

更多GTS 测试的case 见：

CTS/GTS 常见问题汇总