ee5c520326
Add a series of unit tests which try to cover somewhat systematically the possible inputs and what we finally get at the exit of the Binding constructor. Running the assumption that any (valid) YAML binding file is something we can make a Binding instance with: - check which properties are defined at which level (binding, child-binding, grandchild-binding, etc) and their specifications once the binding is initialized - check how including bindings are permitted to specialize the specifications of inherited properties - check the rules applied when overwriting a binding's description or compatible string (at the binding, child-binding, etc, levels) Some tests covering known issues are disabled by default: - this permits to document these issues - while not causing CI errors (when running the python-devicetree unit tests) - enabling these tests without causing errors should allow us to consider the related issues are fixed Signed-off-by: Christophe Dufaza <chris@openmarl.org> |
||
|---|---|---|
| .. | ||
| test-bindings | ||
| test-bindings-2 | ||
| test-bindings-include | ||
| test-bindings-init | ||
| test-wrong-bindings | ||
| test-multidir.dts | ||
| test.dts | ||
| test_dtlib.py | ||
| test_edtlib.py | ||
| test_edtlib_binding_init.py | ||