Split the giant test binaries into smaller unit tests

This is an intermediate step to have smaller unit tests. It is a trade off
between having many many test executables compared to a few bigger ones. But
this comes a lot closer to what QtTest is meant to be used.

tests/blackmisc/testlibrarypath/testlibrarypath.cpp

@@ -0,0 +1,54 @@
+/* Copyright (C) 2016
+ * swift Project Community / Contributors
+ *
+ * This file is part of swift project. It is subject to the license terms in the LICENSE file found in the top-level
+ * directory of this distribution and at http://www.swift-project.org/license.html. No part of swift project,
+ * including this file, may be copied, modified, propagated, or distributed except according to the terms
+ * contained in the LICENSE file.
+ */
+
+//! \cond PRIVATE_TESTS
+//! \file
+//! \ingroup testblackmisc
+
+#include "blackconfig/buildconfig.h"
+#include "blackmisc/librarypath.h"
+#include "test.h"
+
+#include <QTest>
+
+namespace BlackMiscTest
+{
+    //! Geo classes tests
+    class CTestLibraryPath : public QObject
+    {
+        Q_OBJECT
+
+    private slots:
+        //! Basic unit tests for library path
+        void libraryPath();
+    };
+
+    void CTestLibraryPath::libraryPath()
+    {
+        if (!BlackConfig::CBuildConfig::isRunningOnWindowsNtPlatform()) { return; }
+
+        auto emptyPath = BlackMisc::getCustomLibraryPath();
+        QVERIFY2(emptyPath.isEmpty(), "Default path should be empty");
+
+        QString customLibraryPath("c:\test");
+        BlackMisc::setCustomLibraryPath(customLibraryPath);
+        QVERIFY2(BlackMisc::getCustomLibraryPath() == customLibraryPath, "setLibraryPath failed");
+
+        BlackMisc::setCustomLibraryPath(emptyPath);
+        QVERIFY2(emptyPath.isEmpty(), "Path should be empty again.");
+    }
+
+} // namespace
+
+//! main
+BLACKTEST_MAIN(BlackMiscTest::CTestLibraryPath);
+
+#include "testlibrarypath.moc"
+
+//! \endcond