mirror of https://github.com/esphome/esphome.git synced 2026-10-17 03:32:50 +00:00

Files

T

J. Nick Koston 6793dad8ed Only use a range table when enough numbers share it

Below three users the table and set_range() cost more than the inline
setters, so the choice is made at render time once every number is
known. Lambda bounds (lvgl arc/bar) keep the setters. set_range reads
the table with aligned loads instead of memcpy_P.

2026-10-02 17:32:24 -05:00

benchmarks

[light] Shrink LightState by 12 bytes per light (#19711 )

2026-09-27 11:53:03 +02:00

component_tests

Only use a range table when enough numbers share it

2026-10-02 17:32:24 -05:00

components

[tcp_uart] Add a server role with an IPv4 allow list (#20026 )

2026-10-02 13:47:10 -05:00

integration

[tcp_uart] Add a server role with an IPv4 allow list (#20026 )

2026-10-02 13:47:10 -05:00

script

[espidf] Skip the lwip sources that compile to empty objects (#20000 )

2026-10-02 07:59:52 -05:00

test_build_components

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

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

test_packages

YAML linting (#3779 )

2022-09-06 15:48:01 +12:00

unit_tests

[nrf52] Use the shared managed ccache settings for the native build (#20027 )

2026-10-02 13:28:40 -05:00

__init__.py

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

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

.gitignore

Rename esphomeyaml to esphome (#426 )

2019-02-13 16:54:02 +01:00

custom.h

Add attribute support to Home Assistant sensors (#1770 )

2021-05-17 11:16:22 +12:00

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

Add transparency support to all image types (#4600 )

2023-05-22 08:03:21 +12:00

README.md

Wireguard component (#4256 )

2023-09-12 07:13:24 +12:00

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