lumiera_/tests/gui
Ichthyostega 8097485dbf ViewSpec: integrate the simple View access case (Unit test PASS)
This finishes the first round of design drafts in this area.
Right now it seems difficult to get any further, since most of
the actual view creation and management in the UI is not yet coded.
2018-06-15 18:02:08 +02:00
..
ctrl ElementAccess: rearrange files according to namespace 2018-04-14 02:06:31 +02:00
interact ViewSpec: integrate the simple View access case (Unit test PASS) 2018-06-15 18:02:08 +02:00
model ElementAccess: somewhat improve the mock implementation to cover the standard case 2018-04-14 03:58:02 +02:00
test ViewSpec: integrate the simple View access case (Unit test PASS) 2018-06-15 18:02:08 +02:00
abstract-tangible-test.cpp Modernise Unknown Exception handler and Exception messages 2018-04-02 01:48:51 +02:00
bus-term-test.cpp GCC-7: integrate recent clean-up and refactoring work (lib::Depend) 2018-04-27 02:23:20 +02:00
gen-node-location-query.hpp ElementAccess: initial brainstorming about the interface mechanics 2018-04-07 02:28:29 +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 DockAccess: analysis continued... 2017-09-08 03:53:52 +02:00
test-gui-test.cpp Doxygen: magically insert a reference to the test class 2017-02-22 03:17:18 +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.