lumiera_

History

Ichthyostega 24b3bec4be Doxygen: prepare all unit tests for inclusion in the documentation Doxygen will only process files with a @file documentation comment. Up to now, none of our test code has such a comment, preventing the cross-links to unit tests from working. This is unfortunate, since unit tests, and even the code comments there, can be considered as the most useful form of technical documentation. Thus I'll start an initiative to fill in those missing comments automatically		2017-02-22 01:54:20 +01:00
..
interact	Doxygen: prepare all unit tests for inclusion in the documentation	2017-02-22 01:54:20 +01:00
test	Finish AbstractTangible_test and the basic UI-Element protocol	2016-10-04 03:50:44 +02:00
abstract-tangible-test.cpp	Finish AbstractTangible_test and the basic UI-Element protocol	2016-10-04 03:50:44 +02:00
bus-term-test.cpp	Doxygen: prepare all unit tests for inclusion in the documentation	2017-02-22 01:54:20 +01:00
README	enable special unit-tests to link against the gui	2014-10-18 04:27:07 +02:00
session-structure-mapping-test.cpp	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00
tangible-update-test.cpp	mass clean-up: adapt usage of std::cout pretty much everywhere	2016-01-07 20:12:46 +01:00
test-gui-test.cpp	Doxygen: prepare all unit tests for inclusion in the documentation	2017-02-22 01:54:20 +01:00

README

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.