LUMIERA.clone

History

Ichthyostega 29b8b2b8bc Symbol: switch to using the symbol-table as backing implementation (#158 ) ...which means, from now on identical input strings will produce the same Symbol object (embedded pointer). TODO: does not handle null pointers passed in as c-String properly		2017-04-07 06:34:41 +02:00
..
interact	MERGE Doxygen clean-up done during the last months	2017-04-01 23:59:00 +02:00
test	Symbol: switch to using the symbol-table as backing implementation (#158 )	2017-04-07 06:34:41 +02:00
abstract-tangible-test.cpp	SessionCommand: draft the idea of a function(integration) test	2017-01-11 04:19:43 +01:00
bus-term-test.cpp	MERGE Doxygen clean-up done during the last months	2017-04-01 23:59:00 +02: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: magically insert a reference to the test class	2017-02-22 03:17:18 +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.