esphome/tests
Guillermo Ruffino 1e227e8051
Schema dump (#1564)
* schema dump idea

accept boolean or anything default

accept null also for full dicts

added some common validators

more simple validators

support multi_conf

better handle automations

updates

updates

handle lists

removed not needed class

move to own folder

generalized for automations lists, etc

updates

updates

clean up

clean up

fix automations

made comment optional

basic docs support

added more docs

fixes docs handling

updates

updates

fix components parent

updates

updates

updates

Fix inkplate 6 registration

updates

Disable logging for vscode add on

better handle buses

keep extended order as in CONFIGs

updates

updates

updates

disable comments

moved to scripts/build_jsonschema

added configurable decorators

path handling

fix handle list_schema

fixes and cleanup

add jschema_extractor to maybe

updates

lint

no schema in git

add generated loggers list

* lint
2021-03-07 21:05:08 -03:00
..
component_tests Schema dump (#1564) 2021-03-07 21:05:08 -03:00
test_packages Packages feature (#1052) 2020-07-13 11:45:06 -03:00
unit_tests add-black (#1593) 2021-03-07 16:03:16 -03:00
.gitignore Rename esphomeyaml to esphome (#426) 2019-02-13 16:54:02 +01:00
custom.h Create Protobuf Plugin for automatically generating native API stubs (#633) 2019-06-18 19:31:22 +02:00
livingroom32.cpp Lint 2019-05-24 23:08:04 +02:00
livingroom8266.cpp Lint 2019-05-24 23:08:04 +02:00
README.md update test readme 2020-07-12 14:36:07 -03:00
test1.yaml Improve error checking: too many component id candidates (#1570) 2021-03-07 19:59:32 -03:00
test2.yaml Add duration option to action start deep sleep (#1526) 2021-02-15 14:32:22 -03:00
test3.yaml Improve error checking: too many component id candidates (#1570) 2021-03-07 19:59:32 -03:00
test4.yaml Allow Tuya climate temperature_multiplier to be current/target multiplier (#1345) 2020-11-12 06:31:35 +13:00

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
test1.yaml ESP32 wifi
test2.yaml ESP32 ethernet
test3.yaml ESP8266 wifi
test4.yaml ESP32 ethernet