mirror of
https://github.com/esphome/esphome.git
synced 2026-09-20 03:28:41 +00:00
J. Nick Koston
b3a57d1395
Fixes esphome/esphome#11550 When clone_or_update is called with a ref or submodules, the initial clone uses --depth=1 but the subsequent git fetch and git submodule update commands run deep, pulling the full history on every refresh. This causes excess network traffic and disk usage for external_components, packages, and dashboard imports. Add --depth=1 to all four call sites (initial fetch, initial submodule init, refresh fetch, refresh submodule update). Shallow fetches still advance the local clone to the current remote tip when it moves, so the refresh path keeps working as before.
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 |