Describes the tests needed to validate the Alarm functionality. This includes test of both the Alarm service and the alarm functionality on the contributing components.


Tests  that alarms can be generated and viewed correctly through the Alarm webgui. Specific alarms are tested in the tests cases related to the concrete functionalities.

Basic alarm
  1. Delete a file on a pillar.
  2. Run an integity check for missing files.
    1. A new alarm should be generated by the integrity service, indicating that a integrity problem has been detected. 

Alarm filtering

Dates
  1. Filter on a valid date range.
  2. Filter only on a start date.
  3. Filter only on a end date.
Collection
  1. Filter on a Collection
  2. Filter on an All collections.
    1. The full alarm list should be show again.
Component
  1. Filter on a known component
  2. Filter on an unknown component
Alarm code
  1. Select a specific alarm code
  2. Filter on an All codes.
    1. The full alarm list should be show again.
List size
Durable alarms

Tests that alarms are stored on the messagebus persistent and durable (). 

  1. Start and stop the alarm service.
  2. Generate a alarm (run a integrity check on a  inconsistent collection).
  3. Start the alarm service.
  4. Stop the alarm service.
  5. Generate a alarm (run a integrity check on a  inconsistent collection).
  6. Restart the message bus.
  7. Start the alarm service.