mirror of
https://github.com/esphome/esphome.git
synced 2026-10-07 11:26:39 +00:00
A raw MMU_* define alongside a PIO_FRAMEWORK_ARDUINO_MMU_* knob, or a raw TCP_MSS/LWIP_* alongside the lwIP knobs, would win the compile line while the linker script or prebuilt library keeps the knob's values; both now raise like the no-knob case. _MMU_VARIANTS holds tuples and the resolved config gets a copy, so nothing aliases the module table. _lexed_build_flags lexes once and both consumers accept the tokens, so a malformed entry warns once per build. The linker-script stamp covers the header's size and mtime, an unreadable or non-UTF-8 cache regenerates instead of aborting, plain-form linker flags warn that they are not routed to the link line, and a moved rate-table anchor surfaces as a named build error.
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 |