Child pages
  • Alarm tests
Skip to end of metadata
Go to start of metadata
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.
    • Only alarms from the date range should be present in the list.
  2. Filter only on a start date.
    • Only alarms from the start date and forward should be present in the list.
  3. Filter only on a end date.
    • Only alarms prior and up to the end date should be present in the list.
Collection
  1. Filter on a Collection
    • Only alarms related to the specified collection should be present in the list.
  2. Filter on an All collections.
    1. The full alarm list should be show again.
Component
  1. Filter on a known component
    • Only alarms from the specified component should be present in the list.
  2. Filter on an unknown component
    • No alarms should be listed.
Alarm code
  1. Select a specific alarm code
    • Only alarms with the specific alarm code should be listed.
  2. Filter on an All codes.
    1. The full alarm list should be show again.
List size
  • Change the number of listed event and verify the number of listed event changes accordingly.
Durable alarms

Tests that alarms are stored on the messagebus persistent and durable ( BITMAG-432 - Getting issue details... STATUS ). 

  1. Start and stop the alarm service.
    • This should cause a durable subscriber to have been registered.
  2. Generate a alarm (run a integrity check on a  inconsistent collection).
  3. Start the alarm service.
    • The alarm should be received on 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.
    • The alarm should be received on the alarm service.

Unresolved audit trail issues. (${entries.size()} issues)

Key P Summary T Created Fix Version/s
Loading...
Refresh

  • No labels