mirror of https://github.com/esphome/esphome.git synced 2026-08-31 01:56:01 +00:00

Files

T

J. Nick Koston 4cc3012d98 Read build_src_flags from its producer, share the ldscript rule, shape-check flash_mode

The throw_stubs force-include now comes from the build_src_flags option
esp8266/__init__ pins, collapsing the two spellings to one source of
truth; -include paths resolve against the source root. The ldscript
fallback consumes boards.board_ld_script instead of duplicating the
per-board rule, flash_mode is checked against its closed set before
landing unquoted in the elf2bin command, and the board-gate comment no
longer names a nonexistent validator.

2026-08-23 13:56:27 -05:00

benchmarks

[ci] Fail the benchmark job when the C++ benchmark build fails (#18480 )

2026-08-18 09:03:33 -05:00

component_tests

Merge branch 'esp8266-native-build-surgery' into esp8266-native-toolchain-plumbing

2026-08-22 21:24:07 -05:00

components

[core] Skip copying entity automation and filter sources when unused (#18602 )

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

integration

[tests] Keep PlatformIO libdeps per xdist worker to stop a compile race (#18524 )

2026-08-19 17:29:10 -05:00

script

Harden the shared library converter

2026-08-23 12:32:44 -05:00

test_build_components

[rp2040_ble][bluetooth_connection] 3 connection slots on rp2 with esp32 parity (#18247 )

2026-08-11 08:43:08 -05:00

test_packages

…

unit_tests

Read build_src_flags from its producer, share the ldscript rule, shape-check flash_mode

2026-08-23 13:56:27 -05: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