Skip to content

Commit d535ffe

Browse files
Improvements to the BLE app testing from PR review.
1 parent 96e012e commit d535ffe

File tree

1 file changed

+23
-8
lines changed

1 file changed

+23
-8
lines changed

docs/release-tests/ble-flashing.md

Lines changed: 23 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,17 @@ Four hex files needed:
1515
project can be flashed via Bluetooth with the MakeCode editor under test.
1616
- Create a hex file from the latest MakeCode live editor:
1717
https://makecode.microbit.org/
18-
- Python Editor hex file: To ensure MakeCode editor under test can BLE flash
19-
micro:bits after using the Python Editor.
18+
- Python Editor hex file: To ensure the MakeCode editor under test can
19+
BLE flash micro:bits after using the Python Editor.
2020
- Go to https://python.microbit.org and download the hex file
21-
from the default project.
21+
with the default project.
22+
- This hex file can only be tested with micro:bit V2
23+
- MakeCode Under Test hex file: To ensure it can be flashed over.
2224

2325
Two mobile/tablet devices needed:
2426
- Android device with the micro:bit app installed.
25-
- To load a different MakeCode URL, long touch the micro:bit logo in the
26-
app main screen and a modal will appear with the option to change
27+
- To load a custom MakeCode URL long touch the micro:bit logo in the app
28+
main screen. A modal will appear with the option change the MakeCode URL.
2729
- iOS device with the micro:bit app installed.
2830
- To load a different MakeCode URL, long press the MakeCode back chevron
2931
to choose beta.
@@ -49,12 +51,13 @@ A test run for each of these hex files is required:
4951
- "Out of Box" hex file
5052
- "Meet the micro:bit" hex file
5153
- MakeCode Live Editor hex file
52-
- Python Editor hex file
54+
- Python Editor hex file (micro:bit V2 only)
55+
- MakeCode Under Test hex file
5356

5457
Steps:
5558
1. Connect the micro:bit to the computer via USB.
5659
2. Copy the hex file under test to the `MICROBIT` USB drive.
57-
3. Open the app and load the MakeCode editor under test.
60+
3. Open the micro:bit app and load the MakeCode editor under test.
5861
- From the front page, select "Create Code"
5962
4. Create a new MakeCode project with a simple programme (e.g. display
6063
something on the LED matrix).
@@ -83,7 +86,10 @@ And the following micro:bit versions:
8386
- micro:bit V2 only
8487

8588
Steps:
86-
1. Flash the micro:bit with this MakeCode programme, using any method:
89+
1. Flash the micro:bit with this programme usin the MakeCode Under Test.
90+
This project needs the datalogger extension to be added.
91+
Ensure this project does not have the Bluetooth extension.
92+
The board can be flashed using any method.
8793
```javascript
8894
basic.forever(function () {
8995
datalogger.log(
@@ -98,3 +104,12 @@ Steps:
98104
to connect the micro:bit via Bluetooth.
99105
4. Verify that the data as a table of Time, X and Y acceleration values
100106
is shown in the app.
107+
5. Add the Bluetooth extension to the project and flash the micro:bit again.
108+
6. Back to the app main menu, tap on the "Pair" button to pair the micro:bit.
109+
- A WebUSB flash would have deleted the previous pair.
110+
7. Press the reset button on the micro:bit to ensure the programme is running.
111+
8. Back to the app main menu, go to "My Programs" and tap on the
112+
"Fetch MY_DATA (V2 only)" button.
113+
9. In the "Fecth MY_DATA" screen, select "During Logging" at the top and
114+
tap the "Fetch" button.
115+
10. Verify data is displayed and the fetch has not failed.

0 commit comments

Comments
 (0)