mirror of
https://github.com/esphome/esphome.git
synced 2026-09-11 15:27:33 +00:00
Jesse Hills
bfb8569636
Linking an HTTPS client (http_request, mqtt) pulls in TLS features no ESPHome client ever negotiates: the server-side handshake, static RSA and static ECDH key exchange, renegotiation, session tickets, AES-CCM suites, the EC private-key parsing extras and deterministic ECDSA. Two new esp32 advanced options, on by default, turn them off and save around 14 KB per build; OpenThread opts back in through require hooks because its DTLS commissioner is a server and it uses CCM and deterministic ECDSA directly. On the ESP32-C6 the ROM exports a full-format vsnprintf but no vasprintf, so esp_http_client's vasprintf call was the only thing dragging newlib's printf engine (~20 KB) into the image. A linker-wrapped vasprintf built on the ROM vsnprintf keeps it out.
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 |