mirror of
https://github.com/esphome/esphome.git
synced 2026-09-13 16:18:41 +00:00
J. Nick Koston
cc6245b876
`StorageJSON.apply_to_core` was the inverse of `from_esphome_core`: two enumerations of the same fields that had to stay in sync. When a new CORE attribute joined the validation pipeline, both lists needed an update. Replace it with `_populate_core_from_validated_config(config)` in `compiled_config.py` that reads the cached config dict directly -- same source `read_config` writes into during validation, no separate sidecar schema. The fast path no longer touches StorageJSON at all; the sidecar stays in place for the dashboard's existing use. Drift surface shrinks to: name/friendly_name/build_path under the esphome block (config schema is stable) + target_platform discovered via `_is_target_platform` (the canonical detector) + framework via the `<platform>.framework.type` convention every platform component already follows.
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 |