d53a2336ad
1. Assert that we got permission to CoreBluetooth before doing anything. This makes it so that if permission has been denied, or if we're running on the bots and permission has not been granted, these tests won't run. It does not affect local test runs where permissions haven't been granted nor denied. 2. Rework the code to wait for CoreBluetooth to power on in the SetUp method. Mark the test as inconclusive if CoreBluetooth never powers on (this happens if nobody answers the bluetooth permission dialog, quite typical when running tests locally). Fixes these tests when running locally on a tvOS device: MonoTouchFixtures.CoreBluetooth.CBCentralManagerTest [FAIL] Constructors [FAIL] ScanForPeripherals |
||
---|---|---|
.. | ||
CentralManagerTest.cs | ||
ErrorTest.cs | ||
PeerTest.cs | ||
PeripheralScanningOptionsTest.cs | ||
UuidTest.cs |