tik4net: Skill for Claude Code

MikroTik integration tests

Covers the integration suite only — tik4net.integrationtests/ (MSTest, net48), which needs a live router and never runs in CI. Router-free tests live in tik4net.unittests/ (net8.0) and run in CI on every push; if a new test does not actually need hardware, write it there instead.

dotnet test tik4net.unittests/tik4net.unittests.csproj

Router coordinates come from tik4net.integrationtests/App.config (host, user, pass, routerMac, plus the topology keys consumed by TestConstants.cs). That file is the single source of truth — read it, never restate its values. The romonTarget* keys name the second lab router, CHR2: the RoMON target RomonRelayTest reaches through the first (and writes to), kept on RouterOS 6.49.21 as the older router — no REST, no proplist=, flags read as id lists (Docs/findings-routeros-6.md, which also holds the numbered list of what is still open on 6.x). Run CliFlagFieldsTest against it after any change to the CLI read path; not the full suite, which assumes the first router's topology. Empty romonTargetId = the RoMON tests are Inconclusive. The romonSshTarget* keys send the Telnet/SSH/MAC-Telnet relay rows to CHR3 instead: a RouterOS 7.25 agent cannot SSH to a 6.x router (packet not aligned, a RouterOS defect, not ours). The table is in tik4net.integrationtests/README.md, The lab routers.

Switch routers with -Router, never by editing App.config. A router profile is a set of <name>.<key> entries in App.config (chr2.host, chr2.routerMac, …) that override the plain keys; -Router chr2 sets TIK4NET_ROUTER for the run, writes to TestResults/chr2, and the chr2 profile switches the RoMON target off (CHR2 would relay to itself). Every test reads its settings through LabConfig.Get, and IntegrationTestConfigReadTests in the unit suite fails on a direct AppSettings read, which would reach the default router whatever the run selected. Without -Router the script clears an inherited TIK4NET_ROUTER, so a leftover variable cannot redirect a run.

powershell -NoProfile -ExecutionPolicy Bypass -Command "& 'Tools/probes/run-integration-tests.ps1' -Router chr2 -Transport @('api') -Filter 'FullyQualifiedName~CliFlagFieldsTest'"

TestBase.LabAddress picks which of them a run uses, and the choice is not cosmetic: the MAC-layer transports run with no host at all, addressed by routerMac alone. That is the case those transports exist for (a router with no IP address), so a mac* run that passed the host as well would leave it untested — and routerMac is therefore mandatory in App.config for those three runsettings, not an optimization that skips MNDP.