dapr
/
components-contrib
mirror of https://github.com/dapr/components-contrib.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
components-contrib/tests/certification/pubsub/mqtt3
History
Josh van Leeuwen 9be6d157a4
tests/certification: Updates dapr/dapr to `master` HEAD (#3084) 
Signed-off-by: joshvanl <me@joshvanl.dev>
Co-authored-by: Bernd Verst <github@bernd.dev>
 		2023-08-21 17:06:55 -07:00
..
components Fix mqtt pubsub: remove republishing when application is unhealthy (#2446) 2023-01-18 15:53:45 -08:00
README.md Renamed mqtt components to mqtt3 2023-01-13 09:51:30 -08:00
config.yaml Renamed mqtt components to mqtt3 2023-01-13 09:51:30 -08:00
docker-compose.yml Renamed mqtt components to mqtt3 2023-01-13 09:51:30 -08:00
mqtt_test.go tests/certification: Updates dapr/dapr to `master` HEAD (#3084) 2023-08-21 17:06:55 -07:00

README.md

MQTT certifcation testing

This project aims to test the MQTT Pub/Sub component under various conditions.

Test plan

Basic Test

  • Bring up a MQTT cluster
  • Start 1 sidecar/application(App1)
    • Publishes 1000+ unique messages
    • App: Simulate periodic errors
    • Component: Retries on error
    • App: Observes successful messages
    • Test: Confirms that all expected messages were received

Multiple Publishers-Subscribers

  • Start second sidecar/application(App2)
    • Each of the publishers publish a fixed number of messages to the topic
    • Test: Confirms that both applications receive all published messages

Infra Test

  • Start a constant flow of publishing and subscribing(App1)
    • Test: Keeps count of total sent/received
  • Start another sidecar/application with persistent session(App2)
    • Test: Publishes messages in background
    • Each of the applications should receive messages
  • Stop consumer connected with persistent session(App2)
    • Test: Publishes messages in background
    • Only App1 should receive messages
  • Stop publisher as well so that none of the components are active
    • No messages are published and received
  • Restart second consumer with persistent session
    • App2 receives all lost messages
  • Restart publisher so that both components are active
    • Test: Confirms that both applications received all published messages and no messages were lost

Network Test

  • Simulate network interruption
    • Test: Begins trying to reconnect & publish
    • Component: Begins trying to reconnect & re-subscribe