Further fixes to OEM templates
am: 5ea1946f81
Change-Id: I85d1eb13929ecdb935429778a31c7ce80f208066
diff --git a/oem_template/xts/AndroidTest.xml b/oem_template/xts/AndroidTest.xml
index cd86156..5fa472a 100644
--- a/oem_template/xts/AndroidTest.xml
+++ b/oem_template/xts/AndroidTest.xml
@@ -21,8 +21,8 @@
<!-- OEM-INSTRUCTION: Change this to match the package name of the data app -->
<option name="set-option" value="oem-data-app-package-name:com.oemcorp.android.timezone.data" />
<!-- OEM-INSTRUCTION: Change this to match the name of the target used to include the test .apks -->
- <!--
- This has to match the name of the .apk files included in the test
+ <!--
+ This has to match the name of the .apk files included in the test
suite. For example, if the value below is "oem-data-app-apk-prefix:TimeZoneData"
the test will look for TimeZoneData_test1.apk and TimeZoneData_test2.apk, etc. during tests.
-->
diff --git a/oem_template/xts/README.oem b/oem_template/xts/README.oem
index 307724d..a20045b 100644
--- a/oem_template/xts/README.oem
+++ b/oem_template/xts/README.oem
@@ -5,5 +5,9 @@
This directory contains a suggested structure for CTS-like host-side tests for checking the
time zone update feature has been integrated properly.
-These tests are not included in CTS because the OEM must perform their own integration and
-provide their own OEM-specific signed time zone data app .apks under their own package.
+These tests are not included in CTS because the OEM must perform their own feature
+integration and sign their own TimeZoneData app; no CTS-provided TimeZoneData app would be
+installable on an OEM's device.
+
+To pass, OEMs must provide their own OEM-specific signed time zone data app .apks under the
+correct package name and configure the test config.