Files
esphome/tests
J. Nick Koston 7e179e6795 Catch non-UTF-8 build_info.json too, make the staleness tests prove the decision
UnicodeDecodeError is a ValueError, not an OSError, so a build_info.json
with invalid UTF-8 bytes still crashed the compile; widening the tuple to
(ValueError, OSError) also keeps JSONDecodeError covered.

The staleness tests now use a two-run steady-state shape so the assertion
can only pass when the comparison itself fires: run once to reach steady
state, then damage the file (or bump the hash/version) and assert the
second run regenerates it. The version test pins version.h so the bump is
visible only to the JSON comparison; the non-UTF-8 test stubs the writes
because regenerating over the damaged file needs write_file_if_changed's
own recovery, which lands separately.
2026-08-23 09:14:30 -05:00
..
2022-09-06 15:48:01 +12:00
2023-09-12 07:13:24 +12:00

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