esphome/tests
kahrendt afc848bf22
Add Bayesian type for binary_sensor_map component (#4640)
* initial support for Bayesian type

* Cast bool state of binary_sensor to uint64_t

* Rename channels to observations with Bayesian

* Improve/standardize comments for all types

* Use black to correct sensor.py formatting

* Add SUM and BAYESIAN binary sensor map tests

* Remove unused variable

* Update esphome/components/binary_sensor_map/binary_sensor_map.cpp

Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>

---------

Co-authored-by: Jesse Hills <3060199+jesserockz@users.noreply.github.com>
2023-04-13 01:48:29 +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 EntityBase: Move ObjectId to Flash (#4569) 2023-03-28 09:00:34 +00: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 Added in mmc5603 code (#4175) 2023-04-04 02:34:14 +00:00
test2.yaml Format test files (#4541) 2023-03-09 01:54:51 +00:00
test3.1.yaml Split test3.yaml (#4591) 2023-03-19 22:39:02 +00:00
test3.yaml Add Bayesian type for binary_sensor_map component (#4640) 2023-04-13 01:48:29 +00:00
test4.yaml Add push to talk voice assistant (#4648) 2023-04-11 23:45:10 +00:00
test5.yaml Disallow uart0/1/2 as ids in config (#4446) 2023-03-20 02:29:21 +00:00
test6.yaml Format test files (#4541) 2023-03-09 01:54:51 +00:00
test7.yaml Fix HttpRequestResponseTrigger again (#4285) 2023-01-11 14:50:01 +13:00
test8.yaml Format test files (#4541) 2023-03-09 01:54:51 +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