LUMIERA.clone/tests/stage
2023-10-05 03:21:51 +02:00
..
ctrl Global-Layer-Renaming: fix remaining textual usages and IDs in the code 2018-12-10 00:09:56 +01:00
interact the new design takes the old name 2023-06-22 20:23:55 +02:00
model the new design takes the old name 2023-06-22 20:23:55 +02:00
test Library: reconsider join / stringify API 2023-09-29 17:00:13 +02:00
abstract-tangible-test.cpp Project: update and clean-up Doxygen configuration 2021-01-24 19:35:45 +01:00
bus-term-test.cpp Library/Application: switch BusTerm_test 2023-10-05 03:21:51 +02:00
gen-node-location-query.hpp the new design takes the old name 2023-06-22 20:23:55 +02:00
README Global-Layer-Renaming: rearrange directories 2018-11-15 23:28:03 +01:00

GUI backbone tests

The tests in this subtree are a bit special: they cover the generic and
backbone internals of the Lumiera GTK GUI. They are linked against the
complete GUI-module (gui plugin), and thus may use all related ABIs.

Yet these tests are *deliberately* compiled without any GTK, GTKmm or SigC
includes. This effectively rules out the use, even indirectly, of any GTK
widgets and APIs -- forcing the covered GUI backbone entities to stay
clean and generic at API level.

This is a decision done on purpose. The concrete GUI framework technology
shall be treated as an implementation detail. There is no point in writing
tests which click buttons in the GUI -- better delegate any significant
logic or functionality to GUI agnostic components. GUI is meant to be
a presentation layer and must not develop intelligence on its own.