LUMIERA.clone

History

Ichthyostega 540151b56b provide a mock handler for commands and state marks in the real system, this will be the task of the CoreService, while here, in test mode, we allow to install handling closures from the unit-test-code		2016-01-03 03:23:39 +01:00
..
test	provide a mock handler for commands and state marks	2016-01-03 03:23:39 +01:00
abstract-tangible-test.cpp	define first test case to cover the UI-Bus side of basic element interactions	2016-01-02 01:23:09 +01:00
bus-term-test.cpp	provide a mock handler for commands and state marks	2016-01-03 03:23:39 +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	extended planning to define the operation of UI-Bus and model update	2015-01-17 16:08:56 +01:00
tangible-update-test.cpp	extended planning to define the operation of UI-Bus and model update	2015-01-17 16:08:56 +01:00
test-gui-test.cpp	enable special unit-tests to link against the gui	2014-10-18 04:27:07 +02: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.