mirror of
https://github.com/esphome/esphome.git
synced 2026-08-23 06:36:23 +00:00
J. Nick Koston
a48fbd1cd1
The walk's version-less warning stays quiet for a name the config also requests top-level, and the provides-backend debug level carries the ownership rationale (the arduino backend defers drops and suppresses walk-resolved names this layer cannot know yet). _is_safe_library_name guards both the top-level bundled check and manifest dependencies, so a YAML libraries entry of '.' or a backslash name cannot join under the framework tree. The drop suppression strips only the sanitized owner prefix, keeping a library's own double underscores. An empty bundled directory raises naming the fix instead of warning into an unlinkable build, and the second real-converter test pins ESPHOME_DATA_DIR.
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 |