[CTS]It should be more reasonable to use setBatterySaverMode API to leave power-save mode instead of plugging in charger for "CtsHostsideNetworkTests" test case.
Symptom: It should be more reasonable to use setBatterySaverMode API to leave power-save mode instead of plugging in charger for "CtsHostsideNetworkTests" test case. Root Cause: It uses setBatterySaverMode API to enter power-save mode and uses plugging in charger to leave power save mode.It should be more reasonable to use setBatterySaverMode API to leave power-save mode instead of plugging in charger. Solution: To use setBatterySaverMode API to leave power-save mode instead of plugging in charger. Project: N70 Note: NA Test done by RD: Futher testing need Q team's support: Change-Id: I491c5d0675f340e1c9911b84e41f034663b1454d
This commit is contained in:
@@ -147,6 +147,8 @@ abstract class AbstractAppIdleTestCase extends AbstractRestrictBackgroundNetwork
|
||||
assertBackgroundNetworkAccess(true);
|
||||
setBatterySaverMode(true);
|
||||
assertBackgroundNetworkAccess(false);
|
||||
// Use setBatterySaverMode API to leave power-save mode instead of plugging in charger
|
||||
setBatterySaverMode(false);
|
||||
turnBatteryOn();
|
||||
assertBackgroundNetworkAccess(true);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user