ygndotgg commented on PR #4303: URL: https://github.com/apache/iggy/pull/4303#issuecomment-5843861194
### Manual Testing & End-to-End Verification Report Below is the summary and visual proof of manual testing conducted for the **MQTT Source Connector**, verifying end-to-end telemetry ingestion, QoS handshakes, multi-instance routing, broker authentication, and TLS --- #### 1. Infrastructure Setup & Environment - Executed `iggy-server`, `iggy-connectors` runtime, and containerized **EMQX MQTT Broker** (running in Docker). <details> <summary><b>View Infrastructure Screenshots</b></summary> *Iggy Server, Connector Runtime, and EMQX Broker Initialization:* <img width="1920" height="1080" alt="screenshot-2026-09-23_18-05-15" src="https://github.com/user-attachments/assets/851af31f-98a7-41b5-9159-dfd83877a737"; /> *EMQX MQTT Broker Running in Docker Container:* <img width="1920" height="1080" alt="screenshot-2026-09-24_11-54-43" src="https://github.com/user-attachments/assets/98aae701-d986-4e3d-a570-323e7cc3d425"; /> </details> --- #### 2. End-to-End Data Flow & Web UI Persistence Verification - Published test packets through the EMQX MQTT broker and verified message ingestion and disk persistence via the **Iggy Web UI**. <details> <summary><b>View Broker & Web UI Persistence Screenshots</b></summary> *Iggy Web UI Data Persistence Verification:* <img width="1920" height="1080" alt="screenshot-2026-09-24_18-24-17" src="https://github.com/user-attachments/assets/55baf4f3-f427-47f3-bded-6176a96e87d4"; /> </details> --- #### 3. Packet-Level QoS Exchange Trace - Analyzed trace logs to verify wire-level packet handshakes across **QoS 0, QoS 1, and QoS 2** delivery modes. <details> <summary><b>View Packet Trace Log Screenshot</b></summary> *MQTT Broker Message Exchange:* <img width="1920" height="1080" alt="screenshot-2026-09-24_19-32-56" src="https://github.com/user-attachments/assets/a6012c07-abde-446a-8355-95441e24ea82"; /> <img width="1920" height="1080" alt="screenshot-2026-09-24_19-31-15" src="https://github.com/user-attachments/assets/b6bd25f0-16a2-4ec5-9b86-9e72e87987a1"; /> <img width="1920" height="1080" alt="screenshot-2026-09-24_19-06-24" src="https://github.com/user-attachments/assets/368c80f8-95a6-4f00-bde8-d9007b51e5a3"; /> </details> --- #### 4. Multi-Instance Routing & Destination Isolation - Configured and executed multiple parallel source connector instances routing distinct topic filters into isolated Iggy stream destinations. - Confirmed independent state isolation and disk log persistence for each route. <details> <summary><b>View Multi-Instance Routing Screenshots</b></summary> <img width="1920" height="1080" alt="screenshot-2026-09-24_20-13-05" src="https://github.com/user-attachments/assets/3a198199-7b12-4835-9dc7-1f035ddb1aec"; /> *Iggy Web UI Showing Multi-Destination Streams:* <img width="1920" height="1080" alt="screenshot-2026-09-24_20-13-33" src="https://github.com/user-attachments/assets/6b300ad8-909b-4200-89cd-a435fa4277a2"; /> </details> --- #### 5. Security Verification (Authentication & TLS) - Verified broker authentication using username and password credentials. - Verified encrypted communication over **TLS (`mqtts://`)**. <details> <summary><b>View Authentication & TLS Screenshot</b></summary> *Broker Authentication & TLS Connection Verification:* <img width="1920" height="1080" alt="screenshot-2026-09-24_20-34-43" src="https://github.com/user-attachments/assets/d39551e3-c11f-4891-a24d-ffb751246946"; /> <img width="1920" height="1080" alt="screenshot-2026-09-24_21-18-29" src="https://github.com/user-attachments/assets/67818476-5856-4eb3-a871-7e3253514030"; /> </details> --- ### Summary Checklist - [x] Iggy Server & Connectors Runtime integration operational - [x] Message persistence verified via Iggy Web UI - [x] QoS 0, QoS 1, and QoS 2 packet exchanges verified - [x] Multi-instance route isolation to separate streams tested - [x] Broker username/password authentication verified - [x] TLS encrypted transport verified -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
