• Home
Name Date Size #Lines LOC

..--

AssociationRevokedTestApp/04-Jul-2025-172116

CompanionDeviceTestApp/04-Jul-2025-445323

PermissionsSyncTestApp/04-Jul-2025-537399

common/04-Jul-2025-1,384912

core/04-Jul-2025-3,9052,554

multidevice/04-Jul-2025-1,167811

multiprocess/04-Jul-2025-350198

noservices/04-Jul-2025-17081

res/drawable/04-Jul-2025-5220

uiautomation/04-Jul-2025-1,8131,167

uicommon/04-Jul-2025-263166

Android.bpD04-Jul-20255.5 KiB233204

OWNERSD04-Jul-2025119 76

README.mdD04-Jul-2025712 1512

README.md

1CTS tests for `CompanionDeviceManager` are split into 2 modules:
2`CtsCompanionDeviceManagerCoreTestCases` (a.k.a. "Core Tests") and
3`CtsCompanionDeviceManagerUiAutomationTestCases` (a.k.a. "UiAutomation Tests").
4
5The core difference between the two test modules is that `CtsCompanionDeviceManager_Core_TestCases`
6does NOT use `UiAutomation` which makes it:
7- faster
8- suitable for to run on NFFs
9- less prone to flakiness
10- better suitable to run in `PRESUBMIT`.
11
12`CtsCompanionDeviceManager_UiAutomation_TestCases`, on the other hand, uses `UiAutomation` in order
13to test CDM flows end-to-end and is (at least for now) designed to run only on the mobile
14form-factor and requires a discoverable BT device nearby.
15