David Cermak
6d07bcd611
mqtt-tests: rename tests to match the actual group
|
5 年之前 | |
|---|---|---|
| .. | ||
| main | 6 年之前 | |
| CMakeLists.txt | 6 年之前 | |
| Makefile | 6 年之前 | |
| README.md | 6 年之前 | |
| app_test.py | 5 年之前 | |
| ca.crt | 6 年之前 | |
| ca.der | 6 年之前 | |
| ca.key | 6 年之前 | |
| client_inv.crt | 6 年之前 | |
| client_no_pwd.key | 6 年之前 | |
| client_pwd.crt | 6 年之前 | |
| client_pwd.key | 6 年之前 | |
| sdkconfig.ci.default | 6 年之前 | |
| sdkconfig.qemu | 6 年之前 | |
| server.key | 6 年之前 | |
README.md
ESP-MQTT advanced publish and connect test project
Main purpose of this application is to test the MQTT library to correctly publish and receive messages (of different size and sequences) over different transports. It is possible to run this example manually without any test to exercise how the MQTT library deals with
- reception of fragmented messages
- runtime updates of URI
Runtime settings
This app waits for user input to provide these parameters:
- test-type: "conn" if connection test (host, port, test-case number)
- publish test:
- transport: string parameter, one of: tcp, ssl, ws, wss
- pattern: sample string to be transmitted as message
- pattern repeats: number of repeats of pattern in one MQTT message
- repeated: number of repeats ESP32 publishes the message, also ESP32 expects to receive the same message the same number of repeats
- qos: number specifying qos, one of: 0, 1, 2
Hardware Required
This test-app can be executed on any ESP32 board, the only required interface is WiFi and connection to a local network, then depending on the test either a mqtt test broker or a tls server.