Alarm tests

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 specific functionalities.

Basic alarm

1. Delete a file on a pillar.
2. Run an integrity check for missing files.
   • 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.
• 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.
• 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 ). 

•  Ensure the alarm service is running,  and  that it is a durable subscriber
  • ssh bm_webservice@int-bitmag-02.kb.dk and run tomcat-init.sh start if it isn't running
  • The alarm service should be present under the active durable subscribers (can be checked at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp)
•  Shutdown the alarm service
  
  • Stop the service with alarm-service-it.sh stop
    • This will stop the webclient, remove the alarm service from the tomcat90/webapps/ folder and restart the webclient tomcat server
  • Checked that the alarm service is present under offline durable subscribers at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp
• Generate an alarm (run a integrity check on a  inconsistent collection).
  • Note the time of the alarm, and any other details to be able to identify it again.
• Start the alarm service again
  • Using alarm-service-it.sh start
  • When the webclient is restarted, it will automatically perform some checks that will cause alarms. This is where you need to use the details about the alarm you triggered to check that the alarm is present.