0e1dcc119e
Modbus — deletes tests/.../Modbus.IntegrationTests/Pymodbus/ (serve.ps1, standard.json, dl205.json, mitsubishi.json, s7_1500.json, README.md). Profile JSONs live only under Docker/profiles/ now. Docker/README.md loses its "Native-Python fallback" section; docs/drivers/Modbus-Test-Fixture.md "What the fixture is" bullet flipped from "primary launcher is Docker, native fallback under Pymodbus/" to "Docker is the only supported launch path". S7 — deletes tests/.../S7.IntegrationTests/PythonSnap7/ (server.py, s7_1500.json, serve.ps1, README.md). Docker/README.md loses "Native-Python fallback"; docs/drivers/S7-Test-Fixture.md updated to match. AB CIP — the biggest simplification because the native-binary spawn had the most code. AbServerFixture.cs rewrites: drops Process management (no more Process _proc + Kill/WaitForExit), drops LocateBinary() PATH lookup, drops the IAsyncLifetime initialize-spawns-server behavior. Fixture is now a thin TCP probe against localhost:44818 (or AB_SERVER_ENDPOINT override) — same shape as Snap7ServerFixture / ModbusSimulatorFixture / OpcPlcFixture. IsServerAvailable() simplifies to a single 500 ms probe. AbServerProfile.cs drops AbServerPlcArg + SeedTags + BuildCliArgs + ToCliSpec + the entire AbServerSeedTag record — the compose file is the canonical source of truth for which tags + which --plc mode each family gets; the profile record now carries just Family + ComposeProfile (matches the docker-compose service key) + Notes. KnownProfiles.ForFamily + .All stay for tests that iterate families. AbServerProfileTests.cs rewrites to match: drops BuildCliArgs_* + ToCliSpec_* + SeedTags_* tests; keeps the family-coverage contract tests + verifies the ComposeProfile strings match compose-file service names (a typo in either surfaces as a unit-test failure, not a silent "wrong family booted" at runtime). Docker/README.md loses "Native-binary fallback" section; docs/drivers/AbServer-Test-Fixture.md "What the fixture is" flipped to Docker-only with clearer skip rules. dev-environment.md §Docker fixtures — the "Native fallbacks" subsection goes away; replaced with a one-line note that Docker is the only supported path for these four fixtures + a fresh clone needs Docker Desktop and nothing else. Verified: whole-solution build 0 errors, AB CIP profile unit tests 6/6, AB CIP Docker smoke 4/4 (all family theory rows), S7 Docker smoke 3/3. Container lifecycle clean. The deleted native code surface was already redundant — every fixture the native paths served is now covered by Docker; keeping them invited drift between the two paths (the original AB CIP native profile had three undetected bugs per the #162 commit message: case-sensitive --plc, bracket tag notation, --path=1,0 requirement — noise the Docker path now avoids by never running the buggy code). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3.4 KiB
3.4 KiB
S7 integration-test fixture — python-snap7
python-snap7 Server class
wrapped in a pinned python:3.12-slim-bookworm image. Docker is the
only supported launch path — a fresh clone needs Docker Desktop and
nothing else.
| File | Purpose |
|---|---|
Dockerfile |
python:3.12-slim-bookworm + python-snap7>=2.0 + the server shim + the profile JSONs |
docker-compose.yml |
One service per profile; currently only s7_1500 |
server.py |
Same Python shim the native fallback uses — copy kept in the build context |
profiles/*.json |
Area-seed definitions (DB1 / MB layouts with typed seeds) |
Run
From the repo root:
docker compose -f tests\ZB.MOM.WW.OtOpcUa.Driver.S7.IntegrationTests\Docker\docker-compose.yml --profile s7_1500 up
Detached + stop:
docker compose -f tests\...\Docker\docker-compose.yml --profile s7_1500 up -d
docker compose -f tests\...\Docker\docker-compose.yml --profile s7_1500 down
Endpoint
- Default:
localhost:1102(non-privileged; sidesteps Windows Firewall prompt + Linux's root-required bind on port 102). - Override with
S7_SIM_ENDPOINTto point at a real S7 CPU on:102. - The driver's S7DriverOptions.Port flows through S7netplus's 5-arg
Plc(CpuType, host, port, rack, slot)ctor so the non-standard port works end-to-end.
Run the integration tests
In a separate shell with the container up:
cd C:\Users\dohertj2\Desktop\lmxopcua
dotnet test tests\ZB.MOM.WW.OtOpcUa.Driver.S7.IntegrationTests
Snap7ServerFixture probes localhost:1102 at collection init + records
a SkipReason when unreachable, so tests stay green on a fresh clone
without Docker running.
What's encoded in profiles/s7_1500.json
DB1 (1024 bytes) + MB (256 bytes) with typed seeds at known offsets:
| Address | Type | Seed | Purpose |
|---|---|---|---|
DB1.DBW0 |
u16 | 4242 |
read-back probe |
DB1.DBW10 |
i16 | -12345 |
smoke i16 read |
DB1.DBD20 |
i32 | 1234567890 |
smoke i32 read |
DB1.DBD30 |
f32 | 3.14159 |
smoke f32 read (big-endian) |
DB1.DBX50.3 |
bool | true |
smoke bool read at bit 3 |
DB1.DBW100 |
u16 | 0 |
scratch for write-then-read |
DB1.STRING[200] |
S7 STRING | "Hello" |
S7 STRING read |
MW0 |
u16 | 1 |
S7ProbeOptions.ProbeAddress default |
Seed types supported: u8, i8, u16, i16, u32, i32, f32,
bool (with "bit": 0..7), ascii (S7 STRING).
Known limitations
From the snap7.server.Server docstring upstream:
"Legacy S7 server implementation. Emulates a Siemens S7 PLC for testing and development purposes. [...] pure Python emulator implementation that simulates PLC behaviour for protocol compliance testing rather than full industrial-grade functionality."
Not exercised here — needs a lab rig:
- S7-1500 Optimized-DB symbolic access
- PG / OP / S7-Basic session-type differentiation
- PUT/GET-disabled-by-default enforcement
See docs/drivers/S7-Test-Fixture.md
for the full coverage map.
References
- python-snap7 GitHub
docs/drivers/S7-Test-Fixture.md— coverage mapdocs/v2/dev-environment.md§Docker fixtures