mirror of
https://github.com/esphome/esphome.git
synced 2026-08-23 06:36:23 +00:00
Jesse Hills
eb53ed5558
The ESP-IDF framework can also be built with the PlatformIO toolchain, and the managed components are used on both. Record why that choice is deliberately toolchain-independent: wireguard splits on the same condition, and if the two ever disagree one of them converts a second libsodium next to the managed one. The test now sets the toolchain explicitly and asserts the PlatformIO one takes the managed path too, so the condition cannot narrow without a test failing.
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 |