Configurable ports for the objects and states DBs of the integration tests

[krobipd]

Why

Two adapter test runs on the same machine collide: both start their objects and states DBs on the fixed ports 19001/19000, and the second run's databases never come up. That hits anyone who runs the integration tests of two adapters in parallel — two terminals, or two CI jobs on one self-hosted runner. A leftover run blocking the next one (#488) is the same fixed pair of ports from the other side.

Measured with two installed test controllers side by side: one DBConnection on the defaults comes up, a second one on the defaults does not (times out), a second one on 29001/29000 comes up next to the first — four listeners on 127.0.0.1.

What

• New option for tests.integration(adapterDir, { ports: { objects, states } }).
• Fallback to the environment variables IOBROKER_TESTING_OBJECTS_PORT / IOBROKER_TESTING_STATES_PORT (the option wins), then to the previous defaults 19001/19000 — nothing changes for existing users.
• The ports are handed to DBConnection (server and client settings) and to ControllerSetup.setupSystemConfig() (the controller's iobroker.json), so the adapter under test reaches the same DBs.
• Validation: integer between 1 and 65535, both DBs need different ports; an invalid value fails at testAdapter() time with a message naming the option or variable.
• The debug line Moving databases to different ports... stays verbatim (the repochecker expects it in the adapter-tests job log); the chosen ports are logged on a separate line.
• README: the option is described in its own paragraph for parallel runs on one machine (not in the main example), with the note to leave it unset in workflow-based tests on GitHub; CHANGELOG (WORK IN PROGRESS) updated; build/ rebuilt as in the other feature commits.

Tests

• src/tests/integration/lib/ports.test.ts — defaults, environment, option over environment, partial option, empty variable, invalid values, equal ports.
• src/tests/integration/lib/controllerSetup.test.ts — the given ports (and the defaults) land in the system config, the rest of the config stays untouched, DBConnection carries its ports.
• npm run check, npm run lint, npm test (51 passing), npm run build — all green.

🤖 Generated with Claude Code

[mcm1957]

NOTE: Such an option MUST NOT be used with workflow based tests at github as this would cause the external check to fail. As github uses seperated serves such a collision cannot occure in standard testing environment.

[krobipd]

Thanks, and you are right in a stronger sense than the note says: the PR also changed the debug line "Moving databases to different ports...", which is one of the lines the repochecker expects in the adapter-tests job log, so every adapter would have hit W3053 after a release. Fixed: the original line is back verbatim, the chosen ports are logged on a separate line, and the README now describes the option in its own paragraph for parallel runs on one machine, with the note that it is not to be set in workflow-based tests. GitHub jobs keep the defaults.