GitLab

Remove the annotation since its presence is confusing. The
proper way is to just use the PackageManager#hasSystemFeature
check along with any other API methods.

Change-Id: I8e29b62a95c48c11939c52cf5a5270f5006d7a3a

Add annotations that allow CTS to be used for multiple device
profiles.

Example is shown in ProfileTest.java.

1. @SupportedProfiles - run the test only if the device's profile is
   the one passed via the "--profile" flag to CTS like:

   startcts --plan CTS --profile HANDHELD
   startcts --plan CTS --profile STB

2. @RequiredFeatures - run the test only if the device's
   PackageManager reports the features needed by the test. For
   instance tag wifi tests with this annotation's value set to
   the wifi feature to only run it on devices that declare the
   feature.

If not specified, the profile will be set to ALL, which means run all
the tests.

This creates an additional library for CTS test annotations, so this
will require a change to the build/core/cts.mk project too. A new
Makefile "CtsHostLibraryList.mk" can be used now to have the host
use additional libraries.

Change-Id: I69d76b65569160648020306fe14c94242d99efc1

Create a skeletal application for the CTS Verifier and tests
for the verifier itself. This is just a scaffold and
doesn't include any tests yet.

You should be be able to build the smoke tester and run the
tests for the verifier using:

runtest --path cts/apps/CtsVerifier

This should leave the smoke tester installed on your device.

Another way is build the app using "make cts"...

adb install -r out/target/product/generic/data/app/CtsVerifier.apk

Doing "make cts" will deposit the apk into the
repository/testcases directory. The app will be packaged as part
of the CTS zip bundle.

Change-Id: Ifd0080a444a0183736d064f68feb04ee49a4a1c6