ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmytro Sen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19944) Increase SNMP Unit Test Coverage
Date Sat, 11 Feb 2017 11:47:41 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmytro Sen updated AMBARI-19944:
--------------------------------
    Status: Patch Available  (was: Open)

> Increase SNMP Unit Test Coverage
> --------------------------------
>
>                 Key: AMBARI-19944
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19944
>             Project: Ambari
>          Issue Type: Task
>          Components: alerts, test
>    Affects Versions: 2.5.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19944_3.patch, AMBARI-19944.patch
>
>
> The current unit tests for SNMP alert notifications do not provide enough of an end-to-end
coverage there should be. We should mock SNMP4J classes to ensure that the alert framework
is capable of completing an end-to-end dispatch of a trap. This includes:
> Instrumenting the SNMP4J dispatcher to intercept the SNMP message and validating the
OIDs stored
> Instrumenting Ambari alert code so that an AlertNotice is picked up and converted into
a delivered SNMP message.
> This unit test needs to cover test cases:
> 4 Verify AMBARI_SNMP trap is working fine when alerts are triggered (Need to confirm
whether covered in unit tests)
> 1 Setup a SNMP trap receiver server on one of the hosts
> 2 Create AMBARI_SNMP trap notification to use the receiver started in Step 1
> 3 Trigger an alert to be in CRIT status. E.g STOP MR to trigger HistoryServer Alert
> 4 Verify the traps are received by the receiver and verify the OID received is correct



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message