The cts test testNoDebuggingFeaturesRestriction from com.android.cts.devicepolicy.ManagedProfileTest fails for me when I run adb as root but it passes when I don't. I am not sure I understand which is the correct behaviour. Is it OK that the results are different?
For adb root the test fails with the warning "Warning: Activity not started, its current task has been brought to the front." Please let me know in case I am not clear. Thanks.
Asked
Active
Viewed 572 times
-1
user2248720
- 11
- 1
- 6
1 Answers
0
You are supposed to run CTS on a user build without root access.
testNoDebuggingFeaturesRestriction() is properly failing when adbd is running with root privileges. Ignore the warning - it has nothing to do with the reason why the test is failing.
Make sure to read The Compatilbility Definition Document
Alex P.
- 30,437
- 17
- 118
- 169
-
Thanks for the reply. I didn't understand what you meant by "testNoDebuggingFeaturesRestriction() is properly failing when adbd is running with root privileges". Why is it failing? None of the other tests fail when I run adb using root. Thanks. – user2248720 Jun 30 '15 at 18:52