mirror of https://github.com/esphome/esphome.git synced 2026-10-14 10:12:52 +00:00

Files

T

J. Nick Koston 5884ca4d32 [core] Add YAML discovery, secret and zstd helpers

Report unresolved includes and load errors from include discovery, share
the !secret reference scan between bundle and other callers, let callers
register extra secret values for a dump and see which names it emitted,
swap secrets in the !extend, !remove and scalar !include representers,
record the remote sources packages fetch, and move zstd_module out of the
api wizard into esphome.helpers.

2026-10-07 13:06:40 -10:00

benchmarks

[serial_proxy] Add USB_SERIAL port type and device identity (#19308 )

2026-10-07 19:05:07 +00:00

component_tests

[core] Add YAML discovery, secret and zstd helpers

2026-10-07 13:06:40 -10:00

components

[api] Keep the protobuf write cursor in a register and emit sub-message tags inline (#20124 )

2026-10-07 10:08:25 -10:00

integration

[core] Add YAML discovery, secret and zstd helpers

2026-10-07 13:06:40 -10:00

script

[ci] Run pylint when its version, dependencies or configuration change (#20202 )

2026-10-05 21:20:28 -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

…

unit_tests

[core] Add YAML discovery, secret and zstd helpers

2026-10-07 13:06:40 -10: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