Extend unit test coverage

[dg0yt]

puzzlepaint reported on Sourceforge [tickets:#98]:

At the moment, only very few unit tests exist but the basics for testing, esp. also for testing mouse input for tools are implemented. Based on this the unit test coverage should be extended.

[dg0yt]

puzzlepaint posted on Sourceforge:

• summary: Add unit testing --> Extend unit test coverage
• Description has changed:

Diff:

--- old
+++ new
@@ -1 +1 @@
-Add unit testing using Qt's unit test framework.
+At the moment, only very few unit tests exist but the basics for testing, esp. also for testing mouse input for tools are implemented. Based on this the unit test coverage should be extended.

• status: assigned --> open
• assigned_to: Thomas Schöps --> nobody

[dg0yt]

• labels: --> Quality
• category: Feature_Request --> Task

[dg0yt]

I refactored the existing tests. By default configuration, unit tests are now not only built but also run during build when a unit changes.

We have only a single pure unit test at the moment, georeferencing_t. All the other tests require a large collection of objects to interact. It would be good to consider the dependencies when implementing or refactoring Mapper features.

To explicitly build and run all Tests, invoke "make Mapper_Test". Mapper_Test is also available in KDevelop's project view.

In addition, CMake generates a "test" target. This is target is not available in KDevelop, it will not build any tests, and it will not display the output of failed tests.

Guidelines on unit test programming with (and for) Qt are available at
[http://qt-project.org/wiki/Writing_Unit_Tests].

[dg0yt]

Recommended reading: http://wiki.qt.io/Writing_Unit_Tests

[dg0yt]

Related: #835 coverage PR