-
Notifications
You must be signed in to change notification settings - Fork 131
ble regression tests
James Sheppard edited this page Feb 24, 2016
·
4 revisions
All of these tests should be run before releasing a new version of the microbit-dal. This is to check there have been no regressions in expected behaviour.
Make sure you record all test results in BLE Regression Test Results.
- 1 x micro:bit
- 1 x Android device (OS versions TBC) with micro:bit mobile app or nRF Master Control Panel for Android
- 1 x iOS device (OS versions TBC) with micro:bit mobile app or nRF Master Control Panel for iOS
- 3 x additional devices for TEST 4
- forget all micro:bit bonds on mobile
- freshly USB-flash the micro:bit with the microbit-dal version under test
- Put micro:bit into PAIRING MODE
- Pair mobile with micro:bit
- Reset micro:bit
- CHECK: mobile can flash to micro:bit
- CHECK: mobile can flash to micro:bit multiple times
- Start with TEST 1.
- Choose "forget" from mobile Bluetooth Settings menu
- TBC DO WE NEED A CHECK FOR STILL BEING ABLE TO CONNECT? phone is still on micro:bit whitelist
- Pair again
- CHECK: mobile can flash to micro:bit multiple times
- Start with TEST 1.
- Re-flash micro:bit over USB
- Pair again
- CHECK: mobile can flash to micro:bit multiple times
- Pair 4 different mobiles to the micro:bit
- CHECK: each mobile can still flash micro:bit
- Pair with 1 more (different) mobile
- CHECK: none of the original 4 can flash micro:bit
- CHECK: new mobile can flash micro:bit