mirror of
https://github.com/esphome/esphome.git
synced 2026-08-24 15:16:20 +00:00
J. Nick Koston
3728669fa6
The collapse of the CONNECTING branch dropped a real race fix: HA re-requesting a connect while a scheduled teardown was still pending used to cancel the teardown and let the in-flight open complete; without it the request was ignored and HA paid a teardown plus a fresh connect during exactly the reconnect churn this path sees most. cancel_gatt_disconnect() joins the contract: true only for a scheduled teardown that has not started closing (Bluedroid clears the latched want_disconnect_); rp2 and the stubs return false since their teardowns start inside gatt_disconnect(). The wrapper's cancel_teardown() returns its state to CONNECTING and the proxy handler carries the dev branch verbatim.
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 |