mirror of https://github.com/esphome/esphome.git synced 2025-01-18 20:10:55 +00:00

History

* Added vl53l0x change address and timeout

* Added vl53l0x change address and timeout

* vl53l0x code cleanup and update test

* remove executable bit

* lint code cleanup

* code review fixes including timeout default to 10ms

* Code review cleanup and change a WARN log level message to DEBUG

* Fix issue where warn should be temporary

* Added name of sensor to warning message

* Fix blacklist lint issue

* Remove unused import

2021-02-25 19:12:06 -03:00

component_tests

Device class attribute for sensor component (#1525 )

2021-02-15 12:49:02 -03:00

test_packages

Packages feature (#1052 )

2020-07-13 11:45:06 -03:00

unit_tests

Add hyphen to supported name characters (#1223 )

2020-07-30 00:02:34 +02: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

fix substitution losing track of document range (#1547 )

2021-02-19 21:52:42 -03:00

test2.yaml

Add duration option to action start deep sleep (#1526 )

2021-02-15 14:32:22 -03:00

test3.yaml

Vl53l0x change address (#1126 )

2021-02-25 19:12:06 -03:00

test4.yaml

Allow Tuya climate temperature_multiplier to be current/target multiplier (#1345 )

2020-11-12 06:31:35 +13:00

README.md

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