mockAdapterCore.controllerDir not working as expected in some situations about testing HOT 4 CLOSED

I need to rethink the unit tests. They don't rely on a real js-controller so the directory is not expected to actually exist or even point to a real controller. The constant merely exists so adapters that import tools.js can use that in unit tests - with a mocked tools.js of course.

Mocking and then copying the original behavior in mocks doesn't make sense.

from testing.

In this case it tries to load the letsencrypt.js file from js-controler. So that should be mocked, too?

from testing.

Jup, but like I wrote, this is becoming pointless, so probably just comment out the unit test in travis/Github Actions

from testing.

I re-read the documentation and tried a bit more. The issue of loading letsencrypt works, if I change the default unit.js to something like this, i.e. add the mock of letsencrypt. Of course that will fail, if the adapter tries to use something from letsencrypt. Hm... But for the default config it works. ;-)

from testing.