mirror of
https://github.com/esphome/esphome.git
synced 2026-09-18 02:28:42 +00:00
J. Nick Koston
b8336cddf2
The libretiny upload path on `upload_program` SERIAL dispatch re-invokes PlatformIO (`pio run -t upload -t nobuild`), which needs a full build tree and `platformio.ini`. That makes it incompatible with a dashboard that only has prebuilt artifacts. Bypass PlatformIO for the libretiny+SERIAL+--prebuilt-dir case by calling `ltchiptool flash write -d <port> <firmware.uf2>` directly. The .uf2 encodes the chip family in its header so no extra config is needed. ltchiptool ships with the libretiny PlatformIO platform under ~/.platformio/penv/.libretiny/bin/ltchiptool; `get_ltchiptool_path()` prefers PATH first (pip install ltchiptool) and falls back to the PlatformIO penv. Without --prebuilt-dir the existing PlatformIO path remains in place, so this is purely additive. Issue: esphome/device-builder#572
Tests for ESPHome
This directory contains some tests for ESPHome.
At the moment, all the tests only work by simply executing
esphome over some YAML files that are made to test
whether the yaml gets converted to the proper C++ code.
Of course this is all just very high-level and things like unit tests would be much better. So if you have time and know how to set up a unit testing framework for python, please do give it a try.
When adding entries in test_.yaml files we usually need only
one file updated, unless conflicting code is generated for
different configurations, e.g. wifi and ethernet cannot
be tested on the same device.
Current test_.yaml file contents.
| Test name | Platform | Network | BLE |
|---|---|---|---|
| test1.yaml | ESP32 | wifi | None |
| test2.yaml | ESP32 | ethernet | esp32_ble_tracker |
| test3.yaml | ESP8266 | wifi | N/A |
| test4.yaml | ESP32 | ethernet | None |
| test5.yaml | ESP32 | wifi | ble_server |
| test6.yaml | RP2040 | wifi | N/A |
| test7.yaml | ESP32-C3 | wifi | N/A |
| test8.yaml | ESP32-S3 | wifi | None |
| test10.yaml | ESP32 | wifi | None |