Name | Date | Size | #Lines | LOC | ||
---|---|---|---|---|---|---|
.. | - | - | ||||
src/android/sample/ | 14-Jan-2024 | - | 401 | 185 | ||
Android.bp | D | 15-Dec-2024 | 1.2 KiB | 45 | 42 | |
AndroidManifest.xml | D | 14-Jan-2024 | 1.5 KiB | 40 | 20 | |
AndroidTest.xml | D | 14-Jan-2024 | 1.6 KiB | 32 | 15 | |
OWNERS | D | 15-Dec-2024 | 118 | 7 | 6 | |
README | D | 14-Jan-2024 | 1.1 KiB | 17 | 13 |
README
1This 'sample' folder is a sample which illustrates the basic structure and contents of a CTS module. 2 3Future users can refer to this folder to create their own CTS modules. 4 5Several things to notice: 6 1. The users should update the `misc` value in 7 `<option name="config-descriptor:metadata" key="component" value="misc" />` 8 of the 'AndroidTest.xml' file into an appropriate group for the module they created. 9 10 The list of all available groups: 11 <https://cs.android.com/android/platform/superproject/+/master:cts/tools/cts-tradefed/tests/src/com/android/compatibility/common/tradefed/presubmit/CtsConfigLoadingTest.java;l=66>. 12 13 2. If the module is added outside the 'cts/' folder, the user should also 1) add the module 14 directory into the ayeaye checker (as shown in 15 [this line in the configuration file](https://source.corp.google.com/piper///depot/google3/wireless/android/busytown/ayeaye/config/analyzers/api_test_coverage/api_test_coverage.gcl;l=32;bpv=0;cl=438517394), 16 whose format should be similar to `"packages/<MODULE_NAME>/<API_NAME>/tests/cts/"`), and 17 2) add an OWNERS file in the module directory accordingly.