mirror of
https://github.com/esphome/esphome.git
synced 2024-11-14 11:08:10 +01:00
8bbe4efded
Some checks failed
CI / Run script/clang-tidy for ESP32 Arduino 2/4 (push) Blocked by required conditions
CI / Run script/clang-tidy for ESP32 Arduino 3/4 (push) Blocked by required conditions
CI / Run script/clang-tidy for ESP32 Arduino 4/4 (push) Blocked by required conditions
CI / Run script/clang-tidy for ESP32 IDF (push) Blocked by required conditions
CI / Run script/clang-tidy for ESP8266 (push) Blocked by required conditions
CI / list-components (push) Blocked by required conditions
CI / Run script/ci-custom (push) Blocked by required conditions
CI / Create common environment (push) Waiting to run
CI / Check black (push) Blocked by required conditions
CI / Check flake8 (push) Blocked by required conditions
CI / Check pylint (push) Blocked by required conditions
CI / Check pyupgrade (push) Blocked by required conditions
CI / Run pytest (push) Blocked by required conditions
CI / Check clang-format (push) Blocked by required conditions
CI / Run script/clang-tidy for ESP32 Arduino 1/4 (push) Blocked by required conditions
CI / Component test (push) Blocked by required conditions
CI / Split components for testing into 20 groups maximum (push) Blocked by required conditions
CI / Test split components (push) Blocked by required conditions
CI / CI Status (push) Blocked by required conditions
YAML lint / yamllint (push) Waiting to run
CI for docker images / Build docker containers (push) Has been cancelled
|
||
---|---|---|
.. | ||
component_tests | ||
components | ||
dashboard | ||
test_build_components | ||
test_packages | ||
unit_tests | ||
.gitignore | ||
custom.h | ||
dummy_main.cpp | ||
pnglogo.png | ||
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 |