[
https://issues.apache.org/jira/browse/AMBARI-25691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429756#comment-17429756
]
David Sutta edited comment on AMBARI-25691 at 10/26/21, 3:13 PM:
-----------------------------------------------------------------
||Test||Result||
|Validate changing items per page on Alerts page|(/)|
|Validate changing page (previous, next) on Alerts page|(/)|
|Validate ordering of alerts (ascending/descending) by all columns|(/)|
|Validate filtering works on Alerts page|(/)|
|Stop Hive service - check if critical alert is displayed|(/)|
|Check disabling/enabling a Critical alert|(/)|
|Validate *Cancel* button on an alert's Edit page|(/)|
Alert Groups
||Test||Result||
|Default Alert Groups contained alerts are in-sync with the alerts displayed on
the given service's alert page|(/)|
|New custom group can be added / renamed / removed / duplicated|(/)|
|Default groups are non-modifiable|(/)|
|Component and Service filter works on the 'Select Alert Group Definitions'
panel|(/)|
Alert Notifications
||Test||Result||
|New alert notification can be added, modified, removed|(/)|
|Multiple target severity can be selected|(/)|
|Multiple alert groups can be selected|(/)(!)|
|Alert actually triggers notification (tested with script)|(/)|
Alerts API
||Test||Result||
|Same number of alerts definitions present over API as on UI
(api/v1/clusters/[clustertname]/alert_definitions)|(/)|
|Changing an alert definition on UI - change is represented in API response as
well|(/)|
|Alert details (status, etc...) over API
(api/v1/clusters/[clustertname]/alerts/[alert_id]) is the same as on UI|(/)|
Alert Definitions
||Test||Result||
|Alert definition can be created via API|(/) |
|Created alert definition shows up on UI|(/) |
|Added alert definition shows up on Alert Groups UI|(/)|
|Added alert definition can be edited on UI|(/)|
|Alert definition can be deleted via API|(/)|
|Created alert status is correct (tested with multiple cases)|(/)|
|New alert definitions are listed on API endpoint
(/api/v1/clusters/[clustername]/alert_definitions)|(/)|
was (Author: suttadavid):
||Test||Result||
|Validate changing items per page on Alerts page|(/)|
|Validate changing page (previous, next) on Alerts page|(/)|
|Validate ordering of alerts (ascending/descending) by all columns|(/)|
|Validate filtering works on Alerts page|(/)|
|Stop Hive service - check if critical alert is displayed|(/)|
|Check disabling/enabling a Critical alert|(/)|
|Validate *Cancel* button on an alert's Edit page|(/)|
Alert Groups
||Test||Result||
|Default Alert Groups contained alerts are in-sync with the alerts displayed on
the given service's alert page|(/)|
|New custom group can be added / renamed / removed / duplicated|(/)|
|Default groups are non-modifiable|(/)|
|Component and Service filter works on the 'Select Alert Group Definitions'
panel|(/)|
Alert Notifications
||Test||Result||
|New alert notification can be added, modified, removed|(/)|
|Multiple target severity can be selected|(/)|
|Multiple alert groups can be selected|(/)(!)|
|Alert actually triggers notification (tested with script)|(/)|
Alert Definitions
||Test||Result||
|Alert definition can be created via API|(/) |
|Created alert definition shows up on UI|(/) |
|Added alert definition shows up on Alert Groups UI|(/)|
|Added alert definition can be edited on UI|(/)|
|Alert definition can be deleted via API|(/)|
|Created alert status is correct (tested with multiple cases)|(/)|
|New alert definitions are listed on API endpoint
(/api/v1/clusters/[clustername]/alert_definitions)|(/)|
> Test Ambari Alerts (UI) on an HDP 3.1.x cluster
> -----------------------------------------------
>
> Key: AMBARI-25691
> URL: https://issues.apache.org/jira/browse/AMBARI-25691
> Project: Ambari
> Issue Type: Sub-task
> Affects Versions: 2.7.6
> Reporter: David Sutta
> Assignee: David Sutta
> Priority: Major
>
> The goal here is to validate the Ambari Alerts functionality from the UI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
