[
https://issues.apache.org/jira/browse/AMBARI-19944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15863487#comment-15863487
]
Hudson commented on AMBARI-19944:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6719 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6719/])
AMBARI-19944 Increase SNMP Unit Test Coverage (dsen) (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b8176ff63c00115156062a2af9d2e2cae164e514])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/state/services/AlertNoticeDispatchServiceTest.java
> 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)
