mirror of
https://github.com/esphome/esphome.git
synced 2026-06-24 13:45:15 +00:00
5b1618331f
Chained on top of the memory-impact fix to exercise it in real CI. Changed components and their base-test platforms: - const: variant-only test (test-display.esp32-s3-idf.yaml, no base test). --base-only cannot build it, so the fix must exclude it; it only injects an esp32-s3-idf platform hint. - shelly_dimmer: base test esp8266-ard (real C++). - daikin: base test esp8266-ard (real C++), the working third component. Without the fix, the esp32-s3-idf hint (and const's variant counted as a supported platform) selects esp32-s3-idf, which none of the three can build under --base-only, yielding 0 builds and a failed memory extraction. With the fix, const is excluded, the unbuildable hint is ignored in favor of the common esp8266-ard platform, and shelly_dimmer + daikin generate memory impact.
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 |