mirror of https://github.com/esphome/esphome.git synced 2026-08-30 09:36:03 +00:00

Files

T

J. Nick Koston ad4c59873b Read flash mode from its real producer, share the mode set, store the scanf decision

flash_mode comes from the board_build.flash_mode option the component
already pins (validated by cv.one_of against the same BUILD_FLASH_MODES,
now living in const.py so the two sides cannot drift), retiring
KEY_FLASH_MODE from the generator. The scanf-float decision is stored in
CORE.data where it is computed instead of being a discarded local, so
KEY_SCANF_FLOAT has a producer in this PR. A trailing bare -include in
build_src_flags fails by name instead of degrading into the source dir.

2026-08-23 16:42:25 -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-23 13:57:13 -05:00

components

[modbus_client] Add continuous option to the read and send actions (#18542 )

2026-08-23 13:01:34 -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 flash mode from its real producer, share the mode set, store the scanf decision

2026-08-23 16:42:25 -05:00

__init__.py

…

.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