CTS test is like black box testing. Our automation tests are like gray box testing. Also, the tests are created by different, independent development teams. As a result, we don't know what test programs will be created by other teams.
We are thinking to create some guideline that other teams must follow so that we can create appropriate policy. However, it is not clear what the guideline should be yet. Thanks, Tai From: William Roberts <[email protected]<mailto:[email protected]>> Date: Wednesday, August 28, 2013 9:17 AM To: Stephen Smalley <[email protected]<mailto:[email protected]>> Cc: Tai Nguyen <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re: Automation test with SEAndroid Why don't you work on adding tests to CTS? You could also make a test suite that runs in the unconfined domain. If its truly native, by using the init daemon to start it, you will inherently run in that domain. You could declare a one shot service in the init.rc and then just use ctl.start ctl.stop to fire it off. Running an APK in that domain doesn't make sense as anything not system server has its capabilities to do anything DAC wise stripped out. However, you could always start up an instance of a dalvik vm by hand, similar to what is done in Zygote.
