[6.0r4]GtsAssistantHostTestCases fail

问题描述

 [gts6.0r4]GtsAssistantHostTestCases fail
com.google.android.assistant.gts.AssistantTest#testAssistantOpenFrontCamera
com.google.android.assistant.gts.AssistantTest#testAssistantOpenRearCamera
com.google.android.assistant.gts.AssistantTest#testAssistantTakePhotoWithoutVoiceInteraction
com.google.android.assistant.gts.AssistantTest#testAssistantTakeSelfieWithoutVoiceInteraction

解决方案

这是6.0人新增的case, Hal1的camera会四条全fail, Hal 3的会fail两条可以通过check log (mtkcam-dev1,表示hal1; mtkcam-dev3表示hal3)

GPS 更新豁免流程

GTS updated waiver approval process

 

We introduced Business Logic (BL) based tests as Partner Agreement Enforcement System in GTS 6.0 R1 release in July, 2018.  All Business-logics are hosted on Google servers and can be updated and pushed to production as and when required. This also gives the advantage that partners no longer need to wait for another GTS release to get the fixed test. After the fix is applied on production, a partner can rerun the test and get the test pass.

继续阅读“GPS 更新豁免流程”

GTS 6.0 R4 执行日期改为2019-4-15

GTS 6.0 R4 enforcement date changed and known issues

 

The enforcement date for GTS 6.0 R4 version is changed from April 11th, 2019 to April 15th, 2019. This will align GTS 6.0 R4 enforcement date with February Mandatory Functional Patches Due Dates.

GTS 6.0 R4 can fail for the following four test cases for certain devices with either no camera hardware or no HAL3 Camera:

继续阅读“GTS 6.0 R4 执行日期改为2019-4-15”

【GTS 6.0_R2】 failed com.google.android.nmgiarc.gts.CarrierServicesTests#testCarrierServicesIsTheDefaultImsPackage

问题描述

  GTS 6.0_R2 failed com.google.android.nmgiarc.gts.CarrierServicesTests#testCarrierServicesIsTheDefaultImsPackage
junit.framework.AssertionFailedError: CS not the default IMS package.

继续阅读“【GTS 6.0_R2】 failed com.google.android.nmgiarc.gts.CarrierServicesTests#testCarrierServicesIsTheDefaultImsPackage”

GTS 6.0 R4 released 2019-04-11起切换

GTS 6.0 R4 released

 

Google Mobile Services Test Suite (GTS) version 6.0 R4 has been released on the GTS Download page. GTS 6.0_r4 will support Android 7.0 to 9 and will be enforced for GMS approvals starting April 11, 2019.

GTS 6.0_r4 replaces GTS 6.0_r3 for approvals of GMS distribution per MADA/ EMADA on phone & tablet devices running Android 7.0 to 9. Major changes compared to previous release are following:

继续阅读“GTS 6.0 R4 released 2019-04-11起切换”

[GSI8.1R6]dEQP-EGL.functional.get_frame_timestamps#rgba8888_depth_stencil fail

问题描述

 CtsDeqpTestCases
dEQP-EGL.functional.get_frame_timestamps#rgba8888_depth_stencil fail
=== with config {glformat=rgba8888d24s8ms0,rotation=unspecified,surfacetype=window,required=true} === Fail: Composite to present latency is more than 3 vsyncs.!(131178320 < 66089160)

继续阅读“[GSI8.1R6]dEQP-EGL.functional.get_frame_timestamps#rgba8888_depth_stencil fail”

【GTS_6.0R3】GtsSimAppDialogTestCases三条case fail

问题描述


 com.google.android.simappdialog.gts.InstallCarrierAppActivityTest#testActivityAndNotificationShown_downloadPressed
fail java.lang.AssertionError: Dialog not shown. Is the test SIM inserted?
com.google.android.simappdialog.gts.InstallCarrierAppActivityTest#testActivityAndNotificationShown_notNowPressed
fail java.lang.AssertionError: Dialog not shown. Is the test SIM inserted?
com.google.android.simappdialog.gts.InstallCarrierAppActivityTest#testNotificationOnlyDuringSetupWizard
fail java.lang.AssertionError: Carrier install notification failed to show.

 

解决方案

【GTS_6.0R3】com.google.android.gts.cast.RemoteSubmixHostTest#testRecordFromRemoteSubmix

问题描述


 GtsGmscoreHostTestCases
com.google.android.gts.cast.RemoteSubmixHostTest#testRecordFromRemoteSubmix
fail junit.framework.AssertionFailedError:
com.google.android.gts.cast.RemoteSubmixTest.testRecordFromRemoteSubmix failed.

 

解决方案


继续阅读“【GTS_6.0R3】com.google.android.gts.cast.RemoteSubmixHostTest#testRecordFromRemoteSubmix”

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/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”