Analysis of the Fail of 7.0 CTS (II.)

1, ctstelecomtestcases
Android.telecom.cts.wiredheadsettest#testincalllongpress_hangupcall fail
Junit.framework.AssertionFailedError:Call:Call [id:tc@1, state:holding, details: [pa:phoneaccounthandle{ Ctsconnectionservice, xtstest_call_provider_id, userhandle{0}}, hdl:tel:10000, caps: [capabilities:], props: [ Properties:]]] should is in the state 7 expected:<7> but was:<3>

Android.telecom.cts.wiredheadsettest#testincallshortpress_togglesmute fail
Junit.framework.AssertionFailedError:No call added to Incallservice.

Problem Analysis: These two tests are related to headphones, analog insert headphones in the state of short press, long press button behavior, Google CTS requires short press mute, long press hang up the phone.

2, Ctssecurityhosttestcases
Android.security.cts.selinuxhosttest#testaospservicecontexts fail
Junit.framework.ComparisonFailure:Lines do not match:expected:<media. [Log u:object_r:audio]server_service:s0> but was:<media. [Imageeffect u:object_r:camera]server_service:s0>

Problem analysis: In this test example in the test machine root directory of service_contexts corresponding to the source of the/system/sepolicy/service_contexts 71 lines, should be:
Media.log U:object_r:audioserver_service:s0
Can exactly match the general_service_contexts in the CTS jar, and if not, it will be an error.

3, Ctsnettestcases
Android.net.cts.dnstest#testdnsworks fail
Junit.framework.AssertionFailedError: [rerun] DNS could not resolve ipv6.google.com, check the network supports

Problem Analysis: This test item needs to erect the IPV6 network to be possible

3, Ctshostsidenetworktests
Com.android.cts.net.hostsiderestrictbackgroundnetworktests#testdatasavermode_blacklisted fail
Java.lang.assertionerror:on-device Tests failed:
Junit.framework.ComparisonFailure:wrong Status Expected:<[en]abled> but was:<[dis]abled>

Cause analysis: Mobile phone in the test, will be 10111 blacklist, but the follow-up test, found that there is removed from the blacklist, so do not meet the expected error. Log is as follows:
Add the 10111 app to the Blacklist
11-15 18:15:41.215154 8677 8691 D restrictbackgroundnetworktests:command ' cmd netpolicy add Restrict-background-blacklist 10111 ' returned '
11-15 18:15:41.134780 968 4744 V networkpolicy:updateruleforrestrictbackgroundlocked (10111): IsForeground=false, Isblacklisted=true, Iswhitelisted=false, Oldrule=0 (NONE), newrule=4 (reject_metered), newuidrules=4 (REJECT_METERED) , Olduidrules=0 (NONE)
Returns the state of being restricted, in accordance with expectations
11-15 18:15:41.318794 8765 8765 D CtsNetApp2:getRestrictBackgroundStatus:returning 3//public static final int restrict_ background_status_enabled = 3;
It's been changed here.
11-15 18:15:46.701290 968 983 V networkpolicy:updateruleforrestrictbackgroundlocked (10111): IsForeground=false, Isblacklisted=false, Iswhitelisted=false, oldrule=4 (reject_metered), newrule=0 (None), newuidrules=0 (none), Olduidrules=4 (reject_metered)
Return status to 1, does not match expectations, error
11-15 18:15:52.486557 8765 8765 D CtsNetApp2:getRestrictBackgroundStatus:returning 1//public static final int RESTRICT _background_status_disabled = 1;
11-15 18:15:52.747362 8677 8691 D restrictbackgroundnetworktests:command ' cmd netpolicy set restrict-background false ' re Turned '