Gaphas view and the model meta data are not always consistent or changes not notified -> Unit-Test needed

[franzlst]

A unit test for Gaphas is needed that secures the gui (of the gaphas setup) has notified and stored all meta-data to the meta-data dictionary (of respective element) which is used to prepare the view shown to the user.

One example can be seen in issue #174.

This issue is needed and should include all methods gaphas is notified of (I mean the respective gaphas response to it), so shortcuts it is registered for and mvc observables it is listening to.

This unit test is maybe not that easy but should have a high coverage rate because it secures the rule "You see, what you get" we are aiming for. The usability of gaphas will improve because it will maybe show not known clashes of view and meta-data in the models.

Maybe the easiest is a test that patches gaphas response methods in the way that the gaphas view is cross-checked with the data in the model meta-data dictionaries (plus checks if the meta data updates were notified by gtkmvc) and use an already existing test (with high coverage) to run the most important actions.

Originally created by @Rbelder at 2016-09-22 10:43:18+00:00 (moved from RMC internal repository)

[franzlst]

This issue is important to get a stable gaphas version. I will put it on the agenda for the next meeting. We already have had issue #261 (closed) and at the moment two others #174 and #291 which is connected to this issue. The idea would be to share the work load and get it done for the OpenSource milestone and the release. 👍

Originally created by @Rbelder at 2017-02-16 13:26:23+00:00 (moved from RMC internal repository)