esphome/tests
Samuel Sieb b56c606523
add value option to timeout filter (#5222)
Co-authored-by: Samuel Sieb <samuel@sieb.net>
2023-08-10 17:11:03 +12:00
..
component_tests Run black over tests folder (#4824) 2023-05-15 16:09:56 +12:00
test_packages YAML linting (#3779) 2022-09-06 15:48:01 +12:00
unit_tests Allow substitutions to be valid names (#4726) 2023-05-17 16:33:08 +12:00
.gitignore Rename esphomeyaml to esphome (#426) 2019-02-13 16:54:02 +01:00
custom.h Add attribute support to Home Assistant sensors (#1770) 2021-05-17 11:16:22 +12:00
dummy_main.cpp Display the configured esphome:comment on the WebServer (#4246) 2023-01-17 13:02:54 +13:00
pnglogo.png Add transparency support to all image types (#4600) 2023-05-22 08:03:21 +12:00
README.md NeoPixel - Add support for ESP32-S3 (#4435) 2023-02-19 13:38:27 +00:00
test1.yaml New PM sensor Panasonic SN-GCJA5 (#4988) 2023-08-10 17:04:22 +12:00
test2.yaml New 'Duty Time' sensor component (#5069) 2023-07-13 08:48:16 +12:00
test3.1.yaml add value option to timeout filter (#5222) 2023-08-10 17:11:03 +12:00
test3.yaml Add missing on_(arming|pending|armed_home|armed_night|armed_away|disarmed) triggers to alarm_control_panel (#5219) 2023-08-10 17:09:21 +12:00
test4.yaml Add support for a01nyub (#4863) 2023-08-07 12:22:18 +12:00
test5.yaml RTC implementation of pcf8563 (#4998) 2023-07-12 09:19:28 +12:00
test6.yaml move pio tools to LED component (#4903) 2023-05-28 20:49:27 +00:00
test7.yaml Swap ADC back to use 'int' because C3 (#5151) 2023-07-31 09:19:06 +12:00
test8.yaml Add TT21100 touchscreen component (#4793) 2023-07-12 13:19:19 +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