Skip to content

Unit Tests

Alexandre D'Erman edited this page Jul 16, 2014 · 3 revisions

Here is a list of unit tests that should be implemented:

  • Monitoring startup - Done
  • Exchange startup -> should be able to receive Monitoring messages- Done
  • Producer connection -> receives the address of the Exchange on init - Done
  • Listener connection -> receives the address of the Exchange on init - Done
  • Producer activity-> should be able to send 1 message, verified by a listener which retrieves it
  • Producer activity-> Exchange should update meta data on connected producers
  • Listener activity -> should be able to receive 1 message, sent by a producer - Done
  • Exchange startup -> connected listener should receive a notice with the new exchange address to listen to
  • Exchange up -> should be detected by monitor, which updates the stored meta data of the exchanges
  • Exchange shut down -> should be detected by monitor, which updates the stored states of the exchanges
  • Multiple (>1) exchanges -> Monitor should be able to target the least loaded exchange
  • Multiple (>1) exchanges -> Monitor should be able to return the addresses of all exchanges to connecting listener
  • Multiple (>1) exchanges, 1 producers -> Relocation of the producer from 1 exchange to an other
  • Multiple (>1) exchanges, multiple (>1) producers -> Monitor should locate most productive of the producers
  • Multiple (>1) exchanges, multiple (>1) producers -> Monitor should relocate most productive of the producers
  • Multiple (>1) exchanges, exchange lost, multiple (>1) producers -> Monitor should detect it and update its meta data
  • Multiple (>1) exchanges, exchange lost, multiple (>1) producers -> Monitor should relocate connected producers
  • Multiple (>1) exchanges, exchange lost, multiple (>1) listeners -> Monitor should warn listeners for deregistration
  • Producer connected -> clean disconnect - Done
  • Listener connected -> clean disconnect - Done
  • ZooKeeper client tests - Done
Clone this wiki locally