mirror of https://github.com/esphome/esphome.git synced 2026-10-14 10:12:52 +00:00

Files

T

J. Nick Koston 54b34edf2d [ota] Fall back to a UDP data phase when the link is lossy

TCP gives up on links that lose many packets: retransmit timers back off and
the connection drops, so devices on poor Wi-Fi cannot be updated without being
moved. After the TCP handshake, a client that saw loss moves the upload to a
UDP byte stream that the device acks from lwIP's receive callback as datagrams
arrive, keeping at most four of them like TCP's window. Clean links stay on
TCP; blocked UDP falls back to TCP.

2026-10-10 12:15:36 -10:00

benchmarks

[light] Keep the effect list in a flash table (#20204 )

2026-10-09 15:55:09 -10:00

component_tests

[teleinfo] Add predefined properties for main tags of TIC standard and historical (#9167 )

2026-10-10 08:31:06 -04:00

components

[teleinfo] Add predefined properties for main tags of TIC standard and historical (#9167 )

2026-10-10 08:31:06 -04:00

integration

[core] Add status_momentary_warning/error overloads without a name (#20362 )

2026-10-09 15:51:38 -10:00

script

[core] Catch heap allocating helper calls with explicit template arguments (#20391 )

2026-10-10 02:00:41 +00:00

test_build_components

[ci] Compile esp8266 component tests with the native toolchain (#19740 )

2026-09-27 12:09:06 +02:00

test_packages

…

unit_tests

[ota] Fall back to a UDP data phase when the link is lossy

2026-10-10 12:15:36 -10:00

__init__.py

[mipi_spi] Template code, partial buffer support (#9314 )

2025-07-16 11:05:27 +10:00

.gitignore

…

custom.h

…

dummy_main.cpp

[core] Register the OTA component in dummy_main like its siblings (#18666 )

2026-08-23 09:04:06 -05:00

pnglogo.png

…

README.md

…

testing_helpers.py

[core] cpp tests: Allow customizing code generation during tests (#14681 )

2026-03-18 00:16:01 +00:00

README.md

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