mirror of https://github.com/esphome/esphome.git synced 2026-09-17 01:58:39 +00:00

Files

T

J. Nick Koston 82ba873ea7 [analyze_memory] Attribute main.cpp setup()/loop() to esphome core

The generated src/main.cpp.o was being skipped by _scan_source_symbols
(which only walked src/esphome/) and _source_file_to_component had no
rule for it. As a result setup()/loop() fell through to the
"app_framework" heuristic in const.py instead of being counted as
[esphome]core, both via the nm scan path and the linker map path.

Scan all of src/ and recognize .../src/main.cpp.o as core.

2026-04-26 15:10:48 -05:00

benchmarks

[core] Add uint32_to_str helper and use in preferences (#15597 )

2026-04-14 07:49:44 -10:00

component_tests

[core] Unify skip_external_update and honor it in external_files for faster esphome logs (#16016 )

2026-04-26 07:24:33 -05:00

components

[mitsubishi_cn105] add support for half-degree temperature setpoint (#15919 )

2026-04-26 07:19:49 -05:00

dashboard

[dashboard] Add --no-states support to logs WebSocket handler (#15993 )

2026-04-25 15:43:05 -05:00

integration

[core] decouple main loop cadence from scheduler wake timing (#15792 )

2026-04-21 14:48:21 +02:00

script

[ci] Trigger CodSpeed benchmarks on host platform changes (#15995 )

2026-04-25 17:18:21 -04:00

test_build_components

[emontx] emonTx component (#9027 )

2026-04-07 22:29:55 +00:00

test_packages

…

unit_tests

[analyze_memory] Attribute main.cpp setup()/loop() to esphome core

2026-04-26 15:10:48 -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

[logger] Move task log buffer storage to BSS (#15153 )

2026-03-25 00:52:37 +00: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