mirror of https://github.com/esphome/esphome.git synced 2026-08-25 23:56:19 +00:00

Files

T

J. Nick Koston 2ecf7af416 Name malformed manifests, diff drop-warnings by node key, surface bundled deps

A non-dict manifest or build section raises an EsphomeError naming the
library instead of an AttributeError. ConvertedLibrary remembers the
request-side node key it resolved from, so the converter-drop warning
diffs requests against those keys; a bare name resolving to a canonical
owner__pkg is no longer falsely listed missing. A bundled library whose
manifest declares dependencies warns that the walk never runs for it (a
no-op on the ESP8266 core, not on every core this module serves).

2026-08-21 16:52:32 -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

Add the arduino toolchain enum and validate --toolchain on every platform

2026-08-20 12:56:34 -05:00

components

[image] Restore defaults:/files: support for platform entries (#18032 )

2026-08-19 12:30:12 -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

Warn once per non-compiler path, accept versioned compiler names, and pin the trigger table

2026-08-20 13:57:30 -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

Name malformed manifests, diff drop-warnings by node key, surface bundled deps

2026-08-21 16:52:32 -05:00

__init__.py

…

.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