As far as I understand, sourcing harnessFunctions.sh is no longer needed as the test harness engine deals with this sourcing. Nice!

However, I wonder in this case if harnessFunction.sh should be considered as a "library" of the test harness engine and, in this sense, to move to the scripts/ directory. Moreover, both the engine an the library should be moved a subdirectory in the scripts/ directory (e.g. scripts/harness/).

This has implications also in the .spec, in the contextBroker-test definition part.