← ClaudeAtlas

mqtt-testslisted

Use when a product speaks MQTT, STOMP or AMQP and its delivery guarantees need broker-backed tests: QoS 0, 1 and 2, retained messages, Last Will, shared subscriptions and $SYS with Mosquitto and paho-mqtt; STOMP and RabbitMQ AMQP tests via Testcontainers are in its references.
testland/qa-skills · ★ 0 · Testing & QA · score 72
Install: claude install-skill testland/qa-skills
# mqtt-tests This skill covers the v5.0 surfaces tests must exercise: QoS 0 / 1 / 2 delivery semantics, retained messages, Last Will and Testament (LWT), shared subscriptions, and `$SYS` topic introspection - all per the [MQTT v5.0 spec]. ## When to use - IoT / sensor / M2M product where MQTT is the wire protocol. - Pre-deploy gate: QoS 1 + 2 redelivery semantics correct, retained-message + LWT setup right. - Smoke test new broker config (auth, ACL, persistence). ## How to use 1. Stand up an `eclipse-mosquitto:2` broker as a CI service on port 1883 with a persistence-enabled config (Step 1). 2. Wire a paho-mqtt v5 client with `callback_api_version=VERSION2` (Step 2). 3. Exercise the QoS matrix - assert QoS 1 redelivers buffered messages to a reconnecting `clean_start=False` session (Step 3). 4. Verify a retained message reaches a late subscriber, then clear it with an empty retained payload (Step 4). 5. Cover the advanced broker behaviors - LWT on abnormal disconnect, shared-subscription round-robin, and `$SYS` diagnostics ([references/lwt-shared-subs-sys.md](references/lwt-shared-subs-sys.md)). 6. Use a unique `client_id` per test and clean up retained state between runs (Anti-patterns). ## Step 1 - Run Mosquitto broker in CI ```yaml # GitHub Actions service services: mosquitto: image: eclipse-mosquitto:2 ports: - 1883:1883 volumes: - ./tests/mosquitto.conf:/mosquitto/config/mosquitto.conf ``` `tests/mosquitto.conf`: ``` listener 1883 all