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
- Delete a file on a pillar.
- Run an integity check for missing files.
- A new alarm should be generated by the integrity service, indicating that a integrity problem has been detected.
- A new alarm should be generated by the integrity service, indicating that a integrity problem has been detected.
Alarm filtering
Dates
- Filter on a valid date range.
- Only alarms from the date range should be present in the list.
- Filter only on a start date.
- Only alarms from the start date and forward should be present in the list.
- Filter only on a end date.
- Only alarms prior and up to the end date should be present in the list.
Collection
- Filter on a Collection
- Only alarms related to the specified collection should be present in the list.
- Filter on an All collections.
- The full alarm list should be show again.
Component
- Filter on a known component
- Only alarms from the specified component should be present in the list.
- Filter on an unknown component
- No alarms should be listed.
Alarm code
- Select a specific alarm code
- Only alarms with the specific alarm code should be listed.
- 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.dkand runtomcat-init.sh start- 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)
- Ensure it is present under offline durable subscribers
- Stop the service with
alarm-service-it.sh stop - Checked that it is present under offline durable subscribers at http://int-bitmag-01.kb.dk:8001/admin/subscribers.jsp
- Stop the service with
- Generate an alarm (run a integrity check on a inconsistent collection).
- Start the alarm service again
- Using
alarm-service-it.sh start - Now run
tomcat-init.sh start - The alarm should be received on the alarm service.
- Using