mirror of
https://github.com/esphome/esphome.git
synced 2026-09-11 15:27:33 +00:00
J. Nick Koston
370cfb8898
The responder's ephemeral key pair was generated inside the handshake write step, a base point multiply of about 60 ms on ESP8266 that every connecting client waited for. The noise component now keeps one spare key pair (64 bytes of static storage, only in builds with an encrypted api since the api server is the only refiller), the api server refills it from loop() once the network is up and no api client is mid handshake, and both the api and ota handshakes take it through noise-c's noise_handshakestate_set_local_ephemeral(). A handshake that finds the slot empty, or whose spare noise-c refuses, generates its own key as before. The host gtest suite covers the slot's single use, the key pair's consistency, and a full handshake whose message carries the supplied key.
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 |