The new engine should follow the same "API" for CLI and output in order to be compatible with the RPM generation framework (i.e. contextBroker.spec) and documentation (https://forge.fi-ware.org/plugins/mediawiki/wiki/fiware/index.php/Publish/Subscribe_Broker_-_Orion_Context_Broker_-_Unit_Testing_Plan).

In this sense:

* It should have the name testHarness.sh (this is easy: just to remove the old engine and change the name of the new one).
* It should allow to be invoked in the following way `scripts/testHarness.sh tests`. Currently, this causes an error:

```
[fermin@centollo fiware-orion]$ scripts/funcTest.sh test/testharness/
scripts/funcTest.sh: bad parameter/option: 'test/testharness/'
scripts/funcTest.sh [-u (usage)] [-v (verbose)] [--filter <test filter>] [--keep (don't remove output files)] [--dryrun (don't execute any tests)] [--dir <directory>] [--stopOnError (stop at first error encountered)]
```

* It should print output in the following way (maybe this could be configurable with a CLI option for "output style", at the `191/194: xmlParse/xmlParsePostRegisterContext.test ... 1 seconds` style is also nice):

```
SUCCESS: Convenience Individual Context Entity Attribute - GET FAILS
SUCCESS: Subscription availability sequence with wildcards
SUCCESS: broker version via REST
```