esphome/tests
Nathaniel Wesley Filardo 05ab49a615
climate: add on_control callbacks (#4511)
This lets downstream components respond to climate configuration
changes, which take place through ClimateCall objects, without also
being notified every time the state changes, which happens every time
the input sensor announces a new value.

FIXES https://github.com/esphome/feature-requests/issues/2136
2023-03-07 04:19:49 +00:00
..
component_tests Merge components in packages (#3555) 2023-02-07 14:08:40 +13:00
test_packages YAML linting (#3779) 2022-09-06 15:48:01 +12:00
unit_tests Bump python min to 3.9 (#3871) 2022-10-05 20:09:27 +13: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
README.md NeoPixel - Add support for ESP32-S3 (#4435) 2023-02-19 13:38:27 +00:00
test1.yaml climate: add on_control callbacks (#4511) 2023-03-07 04:19:49 +00:00
test2.yaml Add MICS-4514 gas sensor (#4316) 2023-01-25 09:58:44 +13:00
test3.yaml Fix copy-pasta mistake (#4492) 2023-02-27 01:20:56 +00:00
test4.yaml Add reports fahrenheit to tuya climate (#4032) 2022-12-07 07:29:18 +13:00
test5.yaml Add energy to pzemdc (#3626) 2023-02-23 17:38:34 +00:00
test6.yaml Add internal_temperature component (#4330) 2023-02-20 02:47:37 +00:00
test7.yaml Fix HttpRequestResponseTrigger again (#4285) 2023-01-11 14:50:01 +13:00
test8.yaml NeoPixel - Add support for ESP32-S3 (#4435) 2023-02-19 13:38:27 +00: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