mirror of
https://github.com/esphome/esphome.git
synced 2024-11-24 12:06:26 +01:00
c6f528583b
* Test for each component. * When possible use commandline substitution. * Add wildcard support. * end file with new line. * Move component tests into subfolder. * Add component test to pipeline. * Remove trailing whitespace. * add restore python step. * Add `. venv/bin/activate` to pipeline. * step `changed-components` needs `common` step. * start `list-components-changed.py` different. * iterate on pipeline stage `list-components`. * Update `checkout` action. * Rename test folder from `tests` to `_test`. * validate file exists. * Move component test folder. * extend list-components to include child components. * File does not end with a newline * Handle empty list-components matrix. * list-components also check for changes in tests folder. * Improve `list-components.py`. * `*` is a forbidden character for filenames on windows. --------- Co-authored-by: Your Name <you@example.com> Co-authored-by: Keith Burzinski <kbx81x@gmail.com> |
||
|---|---|---|
| .. | ||
| component_tests | ||
| components | ||
| dashboard | ||
| test_build_components | ||
| test_packages | ||
| unit_tests | ||
| .gitignore | ||
| custom.h | ||
| dummy_main.cpp | ||
| pnglogo.png | ||
| README.md | ||
| test1.1.yaml | ||
| test1.yaml | ||
| test2.yaml | ||
| test3.1.yaml | ||
| test3.yaml | ||
| test4.yaml | ||
| test5.yaml | ||
| test6.yaml | ||
| test7.yaml | ||
| test8.1.yaml | ||
| test8.2.yaml | ||
| test8.yaml | ||
| test9.1.yaml | ||
| test9.yaml | ||
| test10.yaml | ||
| test11.5.yaml | ||
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 |