mirror of
https://github.com/esphome/esphome.git
synced 2026-10-07 11:26:39 +00:00
normalize_dependencies' parameter is manifest_name (the dict branch already binds owner to a package owner), and the arduino call site passes the library's name so its unrecognized-entry warning stops saying 'of manifest'. A version-less dependency warns when the backend declares no provides tree (espidf/zephyr/nrf52 have no post-emit pickup), and the shared walk mirrors the typed IncompatiblePlatform branch: routine platform skips stay at debug, any other InvalidLibrary cause warns naming the component. The two real-converter tests pin ESPHOME_DATA_DIR to tmp_path so an ambient data dir cannot leak in.
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 |