mirror of
https://github.com/esphome/esphome.git
synced 2026-08-25 23:56:19 +00:00
The build.ninja python variable goes through strip_win_long_path_prefix like every other emitted binary path (the NSIS launcher's extended prefix cannot be spawned by cmd.exe). Compile rules are named by the shared source kinds directly, retiring the identity translation table and its drift test. write_project takes the caller's resolved ccache, get_flash_ld_path reads the InstalledPaths the ninja file linked against instead of re-resolving the version, the board backstop checks the one table it indexes with an honest comment, and cc/cxx/ar paths go through the shared toolchain_tool accessor (gaining the Windows suffix).
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 |