On 08/27/2013 02:12 PM, Tai Nguyen (tainguye) wrote: > All, > > We are looking for recommendation to support incremental automation test for > SEAndroid device. Since it is expected that developers will add automation > tests and those tests are run automatically on the device for every build, > having the policies to support those unknown test programs is a challenge. > > I think SEAndroid can handle test apk pretty well – However, we are not sure > about native (Linux) test programs. It seems that we may need to add rules to > transition these test programs to right domain. So, it seems that the whole > development team need to create rules for test programs. This is not > desirable because these test rules may end up in release/official loads. In > addition, the team may not have SEAndroid knowledge to create right rules. > > We really appreciate if you can provide us your feedback or recommendation.
When you say "native (Linux) test programs", do you mean: a) such programs executed from a regular (unprivileged) adb shell, b) such programs executed from an adb shell after an adb root or via su, c) such programs executed from an app Do the test programs do things that you don't want to permit on production devices? Or are they testing functionality that should in fact work on production devices? -- This message was distributed to subscribers of the seandroid-list mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe seandroid-list" without quotes as the message.
