redis testing init has no system.config at startup

[foxriver76]

• if redis is used for objects testing, the system.config and other default objects are not available during the start, because they are created via addObjects in testAdapter.js. We should start the controller, call addObjects and then stop, this will simulate a the object creation of setupFirst

To test: This line https://github.com/ioBroker/db/blob/6f1253ede80b73ec1ffbc24d1afd19f2552bbdc4/packages/db-objects-redis/lib/objects/objectsInRedis.js#L413 should no longer be logged and this hack https://github.com/ioBroker/ioBroker.js-controller/blob/faa8411adc6aeb56a900690d029cdc358eba5723/test/lib/testObjectsACL.js#L159 should no longer be necessary

[foxthefox]

I observed today that all travis tests are failing, because of the loading of master repo from GitHub. Even old test were looping. Seems to be in relation to this issue. 1) Test fritzdect adapter 459 "before all" hook: Test fritzdect adapter: Start js-controller: 460 Uncaught Error: ENOENT: no such file or directory, open '/Users/travis/build/foxthefox/ioBroker.fritzdect/tmp/iobroker-data/objects.json'

[foxriver76]

I observed today that all travis tests are failing, because of the loading of master repo from GitHub. Even old test were looping. Seems to be in relation to this issue. 1) Test fritzdect adapter 459 "before all" hook: Test fritzdect adapter: Start js-controller: 460 Uncaught Error: ENOENT: no such file or directory, open '/Users/travis/build/foxthefox/ioBroker.fritzdect/tmp/iobroker-data/objects.json'

This was another problem which should be fixed now.

[Apollon77]

@foxthefox yes we did a bigger js-controlle 3.2 restructuring ... I'm still finalizing it. please try again. pot. clear travis caches

[foxthefox]

travis works again as expected, thanks for your efforts