mirror of
https://github.com/esphome/esphome.git
synced 2026-09-11 23:37:34 +00:00
J. Nick Koston
f4607cb521
The dashboard's source-routed runner ships idedata.json with bare basenames in prog_path and extra.flash_images[*].path (the receiver's build-host absolute paths don't resolve on the offloader, and the in-memory Web Serial consumer keys by basename). Without this change, the dashboard would have to write a fresh idedata.json into the staging tmpdir on every install just to flip basenames to absolute paths. Resolve relative paths in the prebuilt idedata against CORE.prebuilt_dir so both the dashboard's wire format and a hand-built directory with absolute paths work. cc_path is left alone because it points at a PlatformIO toolchain binary outside the prebuilt dir; the offloader's own PIO install provides the matching binary. Issue: esphome/device-builder#570 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 |