Home
last modified time | relevance | path

Searched refs:feature (Results 1 – 9 of 9) sorted by relevance

/tools/tradefederation/core/src/com/android/tradefed/device/
DTestDevice.java1093 public boolean hasFeature(String feature) throws DeviceNotAvailableException {
1095 if (output.contains(feature)) {
1098 CLog.w("Feature: %s is not available on %s", feature, getSerialNumber());
1315 private void checkApiLevelAgainstNextRelease(String feature, int strictMinLevel)
1321 + "Must be API %d.", feature, getSerialNumber(), strictMinLevel));
DITestDevice.java545 public boolean hasFeature(String feature) throws DeviceNotAvailableException; in hasFeature() argument
DStubDevice.java517 public boolean supportsFeature(Feature feature) { in supportsFeature() argument
DNativeDevice.java3688 public boolean hasFeature(String feature) throws DeviceNotAvailableException { in hasFeature() argument
3829 protected void checkApiLevelAgainst(String feature, int strictMinLevel) { in checkApiLevelAgainst() argument
3833 + "Must be API %d.", feature, getSerialNumber(), strictMinLevel)); in checkApiLevelAgainst()
/tools/tradefederation/core/src/com/android/tradefed/testtype/junit4/
DBaseHostJUnit4Test.java673 public boolean hasDeviceFeature(String feature) throws DeviceNotAvailableException { in hasDeviceFeature() argument
674 return getDevice().hasFeature("feature:" + feature); in hasDeviceFeature()
/tools/apksig/
DREADME.md10 The key feature of apksig is that it knows about differences in APK signature verification logic
/tools/tradefederation/core/atest/
DREADME.md10 Curious about how atest works? Want to add a feature but not sure where to begin? [Go here.](./docs…
/tools/metalava/
DREADME.md402 For example, metalava has a feature to mark "newly annotated" nullness annotations
/tools/apkzlib/src/test/resources/testData/packaging/text-files/
Drfc2460.txt1750 o One desirable feature is that any multi-octet fields within the
1756 o Another desirable feature is that the Hop-by-Hop or Destination